Rapporto del sito: 1 pagina misurata. Valutazione complessiva: Buono.
Punteggio del sito · gov.uk
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.
No JSON-LD structured data found
Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
<title> is too short (17 chars): "Welcome to GOV.UK"
Lengthen the title to 20-70 characters with a clear topic indicator.
Meta description is short (68 chars)
Expand the description to 70-160 characters with the page's main value proposition.
Canonical URL: https://www.gov.uk/
<html lang="en">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1"
120/120 interactive elements have an accessible name
5/5 form controls are labelled
Method note: this reads markup, not a rendered accessibility tree
Server-rendered content detected (799 words, 5476 chars of visible text)
Text-to-markup ratio is healthy (6.4%)
Semantic landmarks present (main, section, header, footer, nav)
Single <h1> heading: "The best place to find government services and information"
4/4 <img> tags have alt attributes
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
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS does not include subdomains
Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.
HSTS has preload directive but does not satisfy preload-list requirements
Preload requires max-age >= 31536000 and includeSubDomains. See https://hstspreload.org.
All 10 core AI crawler user-agents receive the same page as a regular client
Homepage is indexable
1 data-nosnippet region(s) — scoped exclusions, main content still quotable
No directive restricts how AI assistants may use this page
Response compressed with Brotli (br)
Cache validator present (ETag)
Conditional request returns 304 Not Modified
Homepage size is reasonable (83.5 KB decompressed)
Roughly 1,369 tokens of content in 21,364 tokens of response (94% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 20ms
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 missing: og:url, og:type
Add these meta tags: <meta property="og:url" content="...">, <meta property="og:type" content="...">.
No Twitter Card meta tags found
Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.
/robots.txt exists
1/12 core AI crawlers configured
Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
1 AI crawler(s) have partial path restrictions
These crawlers have Disallow rules on specific paths. For full AI access, use only "Allow: /" and let the wildcard User-agent: * handle path restrictions.
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.
1/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
All 7 security headers present
Link header present but does not reference AI discovery files
Add AI discovery entries to your Link header: 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.gov.uk/sitemap.xml
Content-Type is XML (application/xml)
Sitemap-index references 35 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 75000 URL(s) across 3 child(ren)
Newest <lastmod> is recent (4 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.
3 form(s) on the page, none declared as agent tools
A declared form is called by an agent rather than driven pixel by pixel. Add toolname and tooldescription to the forms worth automating — search, filter, subscribe — and toolparamdescription to each field.
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 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-12-01)
2/5 optional fields present
Dai al team rapporti completi, correzioni prioritarie e monitoraggio per mantenere i miglioramenti dopo ogni rilascio.