Site report: 1 measured page. Overall grade: Poor.
Historical measurement: original scores are preserved. Run a new scan to apply the corrected handling of non-HTML resources and page averages.
Bring the findings to the people who can fix them. Copy a ready-to-send summary for Slack, Teams or your next planning meeting.
This is a public report. Your team can open it without an account.
Areas group the checks shown in this report. Their scores are weighted summaries, not individual pages.
Is there substance an agent can read?
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.
Sparse server-rendered content (9 words, 55 chars)
Render at least the main page content server-side. Many AI crawlers (GPTBot, ClaudeBot, CCBot) do not execute JavaScript and will see only the static HTML.
Text-to-markup ratio is healthy (7.1%)
No semantic HTML landmarks found
Replace generic <div> structures with semantic tags: <main>, <article>, <header>, <nav>, <footer>. Agents use these to identify the primary content region.
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
<title> is too short (11 chars): "reuters.com"
Lengthen the title to 20-70 characters with a clear topic indicator.
<meta name="description"> is missing
Add <meta name="description" content="..."> in <head> with a 70-160 character summary. Agents use this as the canonical short description.
No <link rel="canonical"> found
Add <link rel="canonical" href="https://your-site.com/page"> so agents have an unambiguous URL to cite even when crawled via a redirect or query-string variant.
<html lang="en">
No UTF-8 charset declaration in HTML head
Add <meta charset="utf-8"> as the first child of <head>. Without it, agents can mis-decode non-ASCII content.
Missing or incomplete viewport meta tag
Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
Method note: this reads markup, not a rendered accessibility tree
Can an agent retrieve it at all?
Baseline homepage request failed — cannot compare crawler access
Homepage request failed — cannot assess crawl efficiency
Site is served over HTTPS
Could not verify HTTP→HTTPS redirect
Test manually: a request to http://your-site.com should respond with 301 → https://your-site.com.
No Strict-Transport-Security header
Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. This locks browsers and many agents to HTTPS for 1 year.
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
Content-Type: text/html with charset
Homepage is indexable
Google-Extended is disallowed, but this page is still eligible for AI Overviews
Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode follow Googlebot and the snippet directives instead. If the intent was to stay out of AI Overviews, use nosnippet or max-snippet. If the intent was to opt out of training, this is already correct.
Can an agent find what you publish?
/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.
/robots.txt exists
3/12 core AI crawlers configured
Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
9 core AI crawler(s) blocked via wildcard User-agent: *
Your "User-agent: * / Disallow: /" rule blocks these crawlers. Add explicit User-agent entries with Allow: / for each AI crawler you want to permit.
1 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.
1 training crawler(s) blocked — recorded as a deliberate policy choice
6 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.
7/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
Missing critical header: Strict-Transport-Security
Add the Strict-Transport-Security response header to your server configuration. This is a critical security header.
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 1/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.reuters.com/arc/outboundfeeds/sitemap-index/?outputType=xml
Content-Type is XML (application/xml)
Sitemap-index references 100 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 300 URL(s) across 3 child(ren)
Newest <lastmod> is recent (0 day(s) ago)
What can an agent call?
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.
/.well-known/ucp requires authentication
The UCP profile must be publicly accessible with no authentication. An agent reads it before it has any credentials.
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
Nothing on this site requires authorization — auth discovery does not apply
What usage rights are declared?
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" missing (RFC 9116)
Add "Contact:" to your security.txt. Use a mailto: or https: URI, e.g., Contact: mailto:security@example.com
Required field "Expires" missing (RFC 9116)
Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
3/5 optional fields present
Give your team full reports, prioritized fixes and monitoring, so improvements last beyond the next release.