Rapport du site : 1 page mesurée. Note globale : Moyen.
Score du site · theguardian.com
Combine l'origine et 1 page mesurée. Le rapport ci-dessous détaille uniquement la page d'origine.
Transmettez les constats à ceux qui peuvent les résoudre. Copiez un résumé prêt pour Slack, Teams ou votre prochaine réunion.
Ce rapport est public. Votre équipe peut l’ouvrir sans compte.
Y a-t-il de la substance qu'un agent puisse lire ?
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.
Server-rendered content detected (3360 words, 20412 chars of visible text)
Low text-to-markup ratio (1.4%)
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)
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
121/122 <img> tags have alt attributes
398/398 interactive elements have an accessible name
9/9 form controls are labelled
121/122 images, frames or videos have no declared dimensions
Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.
Method note: this reads markup, not a rendered accessibility tree
<title> length 48 chars: "Latest news, sport and opinion from the Guardian"
Meta description length 128 chars
Canonical URL: https://www.theguardian.com
<html lang="en">
UTF-8 charset declared
Viewport meta present: "width=device-width,minimum-scale=1,initial-scale=1"
Un agent peut-il seulement la récupérer ?
Homepage is indexable
noarchive excludes this page from Microsoft Copilot grounding
Microsoft documents that noarchive means a page is not included in Copilot answers and not linked from them. nocache is the lighter option: Copilot may use the URL, title and snippet but not the body.
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 takes 2 redirects to answer
Every hop is a round trip the agent pays for, and some clients cap redirects well below a browser. Collapse the chain: point the first URL straight at the final one.
HEAD requests are supported
Content-Type: text/html with charset
Response compressed with gzip
Cache validator present (ETag)
Conditional request returns 304 Not Modified
Homepage is on the large side (1.4 MB decompressed)
Consider trimming inlined payloads to reduce crawl cost.
Roughly 5,103 tokens of content in 355,187 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 63ms
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=63072000
HSTS includes subdomains
HSTS preload-eligible
ClaudeBot blocked at the server — consistent with its robots.txt Disallow
Meta-ExternalAgent blocked at the server — consistent with its robots.txt Disallow
Amazonbot blocked at the server — consistent with its robots.txt Disallow
Bytespider blocked at the server — consistent with its robots.txt Disallow
CCBot blocked at the server — consistent with its robots.txt Disallow
Claude-SearchBot blocked at the server — consistent with its robots.txt Disallow
PerplexityBot blocked at the server — consistent with its robots.txt Disallow
Un agent trouve-t-il ce que vous publiez ?
/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">.
No OpenGraph meta tags found
Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.
Twitter Card required tags missing: twitter:card, twitter:title, twitter:description
Add these meta tags: <meta name="twitter:card" content="...">, <meta name="twitter:title" content="...">, <meta name="twitter:description" content="...">.
/robots.txt exists
8/12 core AI crawlers configured
Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
17 AI crawler(s) explicitly blocked
These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
6 assistant search crawler(s) blocked — your site cannot be cited by those assistants
Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
10 training crawler(s) blocked — recorded as a deliberate policy choice
3 robots.txt rule(s) target a retired or non-existent crawler token
These rules have no effect. Remove them so the file reflects your actual policy.
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.
17/57 known AI crawlers have explicit rules
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: http://www.theguardian.com/sitemaps/news.xml
Content-Type is XML (text/xml)
508 URL(s) declared
100% of URLs have <lastmod>
Newest <lastmod> is recent (0 day(s) ago)
Qu'un agent peut-il appeler ?
/.well-known/agent-card.json not found
This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
API surface present but no machine-readable description found
The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
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.
2 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 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
Quels droits d'usage sont déclarés ?
RSL license discovered via robots.txt License directive (1 reference(s))
RSL license document Content-Type is "application/xml"
Configure your server to serve RSL license document as application/rsl+xml so AI agents parse it correctly.
Root <rsl> element with correct namespace
1 <content> element(s), all with url attribute
License terms declared — permits[usage]: ai-train ai-input; prohibits[usage]: all
/.well-known/security.txt exists
Required field "Contact" present
Required field "Expires" present
Expires date is in the future (2027-05-31)
2/5 optional fields present
1 usage declaration(s) found
Consistent across 1 declaration(s): training on your content is denied
Consistent across 1 declaration(s): grounding an answer in your content is denied
Consistent across 1 declaration(s): indexing your content for search is denied
Enforcement note: only robots.txt access rules are documented as honored by major AI operators
Offrez à votre équipe des rapports complets, des corrections prioritaires et un suivi pour préserver les progrès après chaque livraison.