Measured on the home page. Overall grade: Poor.
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 ~80% vs 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 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.
GPTBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
ClaudeBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
ChatGPT-User is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
Claude-SearchBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
Google-Extended is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
PerplexityBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
OAI-SearchBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
CCBot is allowed in robots.txt but its User-Agent is blocked
Your WAF or bot management rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (e.g., Cloudflare "Block AI Crawlers"). Note: if your WAF verifies bots cryptographically (Web Bot Auth / verified-bots lists), the real crawler may still pass while this unverified probe is rejected — verify against your WAF logs.
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.
/.well-known/agent.json exists
/.well-known/agent.json Content-Type is "text/html"
Configure your server to serve /.well-known/agent.json as application/json so AI agents parse it correctly.
Invalid JSON
Fix the JSON syntax in your agent.json file. Validate it with a JSON linter.
/.well-known/openapi.json exists
/.well-known/openapi.json Content-Type is "text/html"
Configure your server to serve /.well-known/openapi.json as application/json so AI agents parse it correctly.
Invalid JSON
Fix the JSON syntax in your openapi.json file. Validate with a JSON linter.
/.well-known/mcp.json exists
/.well-known/mcp.json Content-Type is "text/html"
Configure your server to serve /.well-known/mcp.json as application/json so AI agents parse it correctly.
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 agent.json in HTML
Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent.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.
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.
2/5 emerging AI discovery files published
ai.txt present at /.well-known/ai.txt
genai.txt present at /.well-known/genai.txt
ai-plugin.json present at /.well-known/ai-plugin.json but does not look valid
Publish /ai-plugin.json (legacy ChatGPT plugin manifest). Schema: name_for_model, description_for_model, api.url. Still consumed by some agents.
agents.json present at /agents.json but does not look valid
Publish /agents.json describing your site as a callable agent (OpenAgents / Wildcard emerging spec). Includes name, description, and operations[].
nlweb.json present at /.well-known/nlweb.json but does not look valid
Publish /.well-known/nlweb.json (Microsoft NLWeb) so agents can interact with the site through a natural-language interface.
/.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
No optional fields (Canonical, Preferred-Languages, Policy, etc.)
Consider adding Canonical: (canonical URL), Preferred-Languages: (e.g., en), and Policy: (link to your security policy).
/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.
No Sitemap directive found
Add a Sitemap directive to your robots.txt: Sitemap: https://your-site.com/sitemap.xml
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. Generate yours at contentsignals.org.
0/48 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
Sparse server-rendered content (24 words, 172 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.
Low text-to-markup ratio (1.9%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Only 2 semantic landmark(s) found
Use semantic HTML tags so AI agents can understand page structure: <header>, <nav>, <main>, <article>, <section>, <footer>.
Single <h1> heading: "Canada.ca"
8/8 <img> tags have alt attributes
/llms.txt exists
/llms.txt Content-Type is "text/html"
Configure your server to serve /llms.txt as text/plain so AI agents parse it correctly.
Missing H1 heading (first line should start with "# ")
Add an H1 heading as the first line of your llms.txt file, e.g.: # Your Site Name
No blockquote description found ("> ...")
Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
No section headings found (## ...)
Organize your llms.txt content with ## section headings (e.g., ## About, ## API, ## Documentation).
No Markdown links found
Add Markdown links to relevant pages: [Page Title](https://example.com/page). This helps AI agents navigate your site.
/llms-full.txt also available (bonus)
Only 3/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.json)
Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent.json>; rel="alternate"; type="application/json"
CORS enabled on .well-known resources
<title> is too short (9 chars): "Canada.ca"
Lengthen the title to 20-70 characters with a clear topic indicator.
Meta description length 158 chars
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">
UTF-8 charset declared
Viewport meta present: "width=device-width,initial-scale=1"
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 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.
Sitemap located: https://canada.ca/sitemap.xml
Content-Type is XML (application/xml)
Sitemap-index references 294 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 135 URL(s) across 3 child(ren)
Newest <lastmod> is recent (7 day(s) ago)
Response compressed with gzip
Cache validator present (Last-Modified)
Conditional request returns 304 Not Modified
Homepage size is reasonable (8.7 KB decompressed)