Rapporto del sito: 1 pagina misurata. Valutazione complessiva: Buono.
Punteggio del sito · ikea.com
Combina l'origine e 1 pagina misurata. Il report qui sotto dettaglia soltanto la pagina di origine.
Porta i risultati a chi può risolverli. Copia un riepilogo pronto per Slack, Teams o la prossima riunione.
Questo rapporto è pubblico. Il team può aprirlo senza un account.
C'è sostanza che un agente possa leggere?
Homepage does not serve Markdown via content negotiation
Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
No <link rel="alternate" type="text/markdown"> fallback found on the homepage
If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
1 JSON-LD block(s) found
@context references schema.org
No @graph array (single-entity only)
Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
Only 1 key type found: Organization
Add more entity types to your @graph. AI agents use these to understand site structure. Common types: Person, Organization, WebSite, WebPage.
No BreadcrumbList found
Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
No author declared in structured data
An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
4 sameAs link(s) tie your entity to external identifiers
No dateModified or datePublished in structured data
Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.
Server-rendered content detected (491 words, 5376 chars of visible text)
Low text-to-markup ratio (0.9%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Semantic landmarks present (main, section, header, footer, nav)
Single <h1> heading: "Welcome to IKEA Global!"
34/34 <img> tags have alt attributes
169/169 interactive elements have an accessible name
Method note: this reads markup, not a rendered accessibility tree
<title> length 27 chars: "Hej! Welcome to IKEA Global"
Meta description length 130 chars
Canonical URL: https://www.ikea.com/
<html lang="en">
UTF-8 charset declared
Viewport meta present: "width=device-width, minimum-scale=1.0, initial-scale=1"
116 hreflang alternate(s) including x-default
Un agente riesce a recuperarla?
A missing page redirects (301) instead of returning 404
A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
Homepage answers after 1 redirect
HEAD requests are supported
Content-Type: text/html with charset
Response compressed with Brotli (br)
Cache validator present (Last-Modified)
Conditional request returned 200 instead of 304 Not Modified
The server advertises a cache validator but does not honor If-None-Match / If-Modified-Since. Configure it to return 304 when the validator matches, so crawlers avoid re-downloading unchanged pages.
Homepage is on the large side (558.2 KB decompressed)
Consider trimming inlined payloads to reduce crawl cost.
Roughly 1,344 tokens of content in 142,879 tokens of response (99% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 260ms
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS includes subdomains
HSTS lacks the preload directive
Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
All 10 core AI crawler user-agents receive the same page as a regular client
Homepage is indexable
No directive restricts how AI assistants may use this page
Un agente trova ciò che pubblichi?
/llms.txt not found
Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
No AI meta tags (ai:*) found
Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
No rel="alternate" link to llms.txt in HTML
Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
No rel="alternate" link to the Agent Card in HTML
Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
No rel="me" identity links found
Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
OpenGraph required tags present (og:title, og:description, og:url, og:type)
Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
/robots.txt exists
No core AI crawlers explicitly configured
Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
Sitemap directive present
No Content-Signal directive found (optional)
Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
Missing critical header: X-Content-Type-Options
Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.
Only 2/7 security headers present
Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.
No Link header for AI discovery (llms.txt, Agent Card)
Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
No machine-readable discovery relations beyond llms.txt and the Agent Card
Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
Sitemap located: https://www.ikea.com/sitemaps/sitemap.xml
Content-Type is XML (application/xml)
Sitemap-index references 2166 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 14997 URL(s) across 3 child(ren)
Newest <lastmod> is recent (1 day(s) ago)
Che cosa può chiamare un agente?
No agent resource catalog found
A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
No agent-facing surface — an Agent Card does not apply to this site
No API surface — API discovery does not apply to this site
No MCP server — MCP discovery does not apply to this site
No developer-facing surface — skills do not apply to this site
No forms and no WebMCP code — nothing here for an agent to invoke as a tool
No commerce surface — agentic-commerce discovery does not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
Quali diritti d'uso sono dichiarati?
No RSL license discovery found
Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
No machine-readable usage policy declared
State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
/.well-known/security.txt exists
Required field "Contact" present
Required field "Expires" present
Expires date is in the future (2026-09-20)
3/5 optional fields present
Dai al team rapporti completi, correzioni prioritarie e monitoraggio per mantenere i miglioramenti dopo ogni rilascio.