Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
97/100

OVERALL SCORE

Level 5, Agent-Ready

Excellent readiness for AI agents
AIDiscoverability100%Agent Easeof Use96%Security& Trust100%GEO, AIO, AEO86%SEO100%Performance& Accessibility97%
  • AI Discoverability 100 out of 100
  • Agent Ease of Use 96 out of 100
  • Security & Trust 100 out of 100
  • GEO, AIO and AEO 86 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 97 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

CanAgentUse Scanner | AI SEO and Agent-Readiness Audits favicon

CanAgentUse Scanner | AI SEO and Agent-Readiness Audits

Run deep AI SEO and agent-readiness audits across crawler policy, structured data, performance, accessibility, API discovery, OAuth, MCP, WebMCP, agent skills, and commerce signals.

Next step

Turn this report into a fix workflow

2 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
100
Strong2800
Discoverability
100
Strong1200
Content Readiness
100
Strong1100
Bot Access Control
100
Strong500
Agent Ease of Use
96
Strong6231View details
API
100
Strong1100
Auth
100
Strong1410View details
MCP
100
Strong1700
Skill Discovery
85
Mostly ready1621View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
86
Mostly ready809
GEO Readiness
87
Mostly ready204
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
81
Mostly ready205
SEO
100
Strong1100
SEO
100
Strong1100
Security & Trust
100
Strong1000
Security & Trust
100
Strong500
AI Training Exposure
100
Strong500
Performance and Accessibility
97
Strong2512View details
Performance
96
Strong1712View details
Accessibility
100
Strong800

Prioritized recommendations

Issues ranked by score impact

12 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

75 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

    Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.

  3. Check DNSSEC material

    DNSSEC material was not visible for the hostname or parent zone from this resolver.

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "canagentuse.com",
        "probes": [
          {
            "name": "_index._agents.canagentuse.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.canagentuse.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          }
        ]
      },
      "issue": "No DNS-AID entrypoint records were found under _agents.",
      "howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
    },
    {
      "id": "service-params",
      "title": "Validate alpn and endpoint parameters",
      "status": "informational",
      "evidence": {
        "discovered": []
      },
      "howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
    },
    {
      "id": "dnssec",
      "title": "Check DNSSEC material",
      "status": "warning",
      "evidence": {
        "hasDnssecMaterial": false,
        "checked": [
          {
            "name": "canagentuse.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          }
        ]
      },
      "issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
      "howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

AEO: Answer-first sections scored 65/100 and needs improvement.

5 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

12 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer-first sections scored 65/100 and needs improvement.

Evidence
{
  "sectionCount": 14,
  "passing": 2,
  "failing": [
    {
      "heading": "137 signals across 15 readiness areas for the AI agent age.",
      "headingHtml": "<h2 id=\"scanner-coverage-heading\" class=\"mt-3 max-w-xl text-4xl font-semibold leading-[1.05] sm:text-5xl\">137<!-- --> signals across <!-- -->15<!-- --> readiness areas for the AI agent age.</h2>",
      "firstParagraph": "The scanner measures whether websites and web apps give AI systems the signals they need to discover public pages, trust crawler policy, understand content, call documented APIs, and complete approved workflows.",
      "paragraphHtml": "<p class=\"mt-4 max-w-2xl text-sm leading-6 theme-muted\">The scanner measures whether websites and web apps give AI systems the signals they need to discover public pages, trust crawler policy, understand content, call documented APIs, and complete approved workflows.</p>",
      "words": 31,
      "direct": false,
      "issue": "First paragraph is 31 words and does not look like a concise direct answer."
    },
    {
      "heading": "Agent-readiness field notes",
      "headingHtml": "<h2 id=\"latest-blog-heading\" class=\"mt-2 text-3xl font-semibold sm:text-4xl\">Agent-readiness field notes</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Auth.md and DNS-AID: Provider Setup Guide",
      "headingHtml": "<h3 class=\"mt-3 text-xl font-semibold leading-tight\">Auth.md and DNS-AID: Provider Setup Guide</h3>",
      "firstParagraph": "Set up Auth.md and DNS-AID in 2026 with Cloudflare, Vercel, Netlify, OAuth metadata, HTTPS/SVCB records, DNSSEC, and 8 checks.",
      "paragraphHtml": "<p class=\"mt-3 line-clamp-3 text-sm leading-6 theme-muted\">Set up Auth.md and DNS-AID in 2026 with Cloudflare, Vercel, Netlify, OAuth metadata, HTTPS/SVCB records, DNSSEC, and 8 checks.</p>",
      "words": 21,
      "direct": false,
      "issue": "First paragraph is 21 words and does not look like a concise direct answer."
    },
    {
      "heading": "Agent Card Discovery: agents.json Checklist",
      "headingHtml": "<h3 class=\"mt-3 text-xl font-semibold leading-tight\">Agent Card Discovery: agents.json Checklist</h3>",
      "firstParagraph": "Plan A2A agent card discovery in 2026 with agent-card.json, agent.json, agents.json, mcp.json, OpenAPI links, OAuth scopes, and 8 audit checks.",
      "paragraphHtml": "<p class=\"mt-3 line-clamp-3 text-sm leading-6 theme-muted\">Plan A2A agent card discovery in 2026 with agent-card.json, agent.json, agents.json, mcp.json, OpenAPI links, OAuth scopes, and 8 audit checks.</p>",
      "words": 24,
      "direct": false,
      "issue": "First paragraph is 24 words and does not look like a concise direct answer."
    },
    {
      "heading": "AI Bot Access: Web Bot Auth Audit Guide",
      "headingHtml": "<h3 class=\"mt-3 text-xl font-semibold leading-tight\">AI Bot Access: Web Bot Auth Audit Guide</h3>",
      "firstParagraph": "Audit AI bot access with Web Bot Auth, signed agents, Cloudflare verified bots, HTTP message signatures, OAuth, API keys, and edge rules.",
      "paragraphHtml": "<p class=\"mt-3 line-clamp-3 text-sm leading-6 theme-muted\">Audit AI bot access with Web Bot Auth, signed agents, Cloudflare verified bots, HTTP message signatures, OAuth, API keys, and edge rules.</p>",
      "words": 22,
      "direct": false,
      "issue": "First paragraph is 22 words and does not look like a concise direct answer."
    },
    {
      "heading": "MCP in your IDE",
      "headingHtml": "<h3 class=\"mt-4 text-xl font-semibold\">MCP in your IDE</h3>",
      "firstParagraph": "Connect CanAgentUse to Codex, Claude Desktop, or Cursor so failed checks turn into direct repair prompts inside your coding workflow.",
      "paragraphHtml": "<p class=\"mt-3 text-sm leading-6 theme-muted\">Connect CanAgentUse to Codex, Claude Desktop, or Cursor so failed checks turn into direct repair prompts inside your coding workflow.</p>",
      "words": 20,
      "direct": false,
      "issue": "First paragraph is 20 words and does not look like a concise direct answer."
    },
    {
      "heading": "CI in pull requests",
      "headingHtml": "<h3 class=\"mt-4 text-xl font-semibold\">CI in pull requests</h3>",
      "firstParagraph": "Turn the scanner into a release check that compares baseline and preview results before changes reach production.",
      "paragraphHtml": "<p class=\"mt-3 text-sm leading-6 theme-muted\">Turn the scanner into a release check that compares baseline and preview results before changes reach production.</p>",
      "words": 17,
      "direct": false,
      "issue": "First paragraph is 17 words and does not look like a concise direct answer."
    },
    {
      "heading": "Want help making your site agent-ready?",
      "headingHtml": "<h2 id=\"scanner-connect-title\" class=\"mt-3 max-w-2xl text-3xl font-semibold leading-tight md:text-4xl\">Want help making your site agent-ready?</h2>",
      "firstParagraph": "Send your site and goals. We can review readiness gaps, implementation options, and the right next step before or after you scan.",
      "paragraphHtml": "<p class=\"mt-4 max-w-xl text-sm leading-6 theme-muted\">Send your site and goals. We can review readiness gaps, implementation options, and the right next step before or after you scan.</p>",
      "words": 22,
      "direct": false,
      "issue": "First paragraph is 22 words and does not look like a concise direct answer."
    },
    {
      "heading": "Questions about AI SEO and agent-readiness scans",
      "headingHtml": "<h2 id=\"faq-heading\" class=\"mt-3 text-3xl font-semibold leading-tight sm:text-4xl\">Questions about AI SEO and agent-readiness scans</h2>",
      "firstParagraph": "The scanner focuses on the public, machine-readable, technical, and content signals that AI search systems and agents need before they can cite, understand, or use a website reliably.",
      "paragraphHtml": "<p class=\"mt-5 max-w-xl text-base leading-7 theme-muted\">The scanner focuses on the public, machine-readable, technical, and content signals that AI search systems and agents need before they can cite, understand, or use a website reliably.</p>",
      "words": 28,
      "direct": false,
      "issue": "First paragraph is 28 words and does not look like a concise direct answer."
    },
    {
      "heading": "Product",
      "headingHtml": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Product</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Developers",
      "headingHtml": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Developers</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Agent Files",
      "headingHtml": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Agent Files</h2>",
      "firstParagraph": "© 2026 CanAgentUse. All rights reserved.",
      "paragraphHtml": "<p>&#xa9; <!-- -->2026<!-- --> CanAgentUse. All rights reserved.</p>",
      "words": 5,
      "direct": false,
      "issue": "First paragraph is 5 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 83/100 and needs improvement.

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: canagentuse, scanner, website, ready, agents.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Entity clarity

Score

83/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Entity clarity scored 83/100 and needs improvement.

Evidence
{
  "title": "CanAgentUse Scanner | AI SEO and Agent-Readiness Audits",
  "h1": "Is your website ready for AI agents?",
  "description": "Run deep AI SEO and agent-readiness audits across crawler policy, structured data, performance, accessibility, API discovery, OAuth, MCP, WebMCP, agent skills, and commerce signals.",
  "topicOverlap": 0.4444444444444444,
  "topicTerms": [
    "canagentuse",
    "scanner",
    "seo",
    "agent",
    "readiness",
    "audits",
    "website",
    "ready",
    "agents"
  ],
  "descriptionTerms": [
    "run",
    "deep",
    "seo",
    "agent",
    "readiness",
    "audits",
    "across",
    "crawler",
    "policy",
    "structured",
    "data",
    "performance",
    "accessibility",
    "api",
    "discovery",
    "oauth",
    "mcp",
    "webmcp",
    "skills"
  ],
  "missingFromDescription": [
    "canagentuse",
    "scanner",
    "website",
    "ready",
    "agents"
  ],
  "score": 83,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 75/100 and needs improvement.

2 Warning

Needs attention

GEO: Explanatory content depth

Warning
01

Issue

3 explanatory paragraph(s) could be stronger for citation or AI extraction.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Explanatory content depth

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Explanatory content depth scored 75/100 and needs improvement.

Evidence
{
  "candidatePassages": 3,
  "citablePassages": 0,
  "failingCandidateParagraphs": [
    {
      "index": 32,
      "heading": "H2: Questions about AI SEO and agent-readiness scans",
      "text": "CanAgentUse checks AI SEO, crawler policy, structured data, semantic HTML, performance, accessibility, API catalog, OpenAPI, OAuth/OIDC discovery, protected resource metadata, MCP, WebMCP, A2A, agent skills, Web Bot Auth, AI training policy, and agent commerce signals such as x402, MPP, UCP, and ACP.",
      "words": 43,
      "hasEvidence": true,
      "reasons": [
        "Too short for a citation-ready passage (43 words; target 80-220)."
      ],
      "html": "<p class=\"mt-3 max-w-3xl text-base leading-7 theme-muted\">CanAgentUse checks AI SEO, crawler policy, structured data, semantic HTML, performance, accessibility, API catalog, OpenAPI, OAuth/OIDC discovery, protected resource metadata, MCP, WebMCP, A2A, agent skills, Web Bot Auth, AI training policy, and agent commerce signals such as x402, MPP, UCP, and ACP.</p>"
    },
    {
      "index": 33,
      "heading": "H2: Questions about AI SEO and agent-readiness scans",
      "text": "No. Robots.txt and llms.txt are only a small part of the scan. The report also evaluates content extraction, AI SEO, structured data, API discovery, authentication metadata, MCP and WebMCP surfaces, agent-facing skills, security headers, performance, accessibility, and commerce-readiness metadata.",
      "words": 41,
      "hasEvidence": true,
      "reasons": [
        "Too short for a citation-ready passage (41 words; target 80-220)."
      ],
      "html": "<p class=\"mt-3 max-w-3xl text-base leading-7 theme-muted\">No. Robots.txt and llms.txt are only a small part of the scan. The report also evaluates content extraction, AI SEO, structured data, API discovery, authentication metadata, MCP and WebMCP surfaces, agent-facing skills, security headers, performance, accessibility, and commerce-readiness metadata.</p>"
    },
    {
      "index": 34,
      "heading": "H2: Questions about AI SEO and agent-readiness scans",
      "text": "Yes. It checks API catalog discovery, OpenAPI or Swagger documents, OAuth and OIDC discovery metadata, OAuth Protected Resource metadata, MCP server cards, mcp.json, WebMCP manifests, browser tool annotations, A2A agent cards, agent.json, agents.json, and agent skills indexes.",
      "words": 40,
      "hasEvidence": false,
      "reasons": [
        "Too short for a citation-ready passage (40 words; target 80-220).",
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"mt-3 max-w-3xl text-base leading-7 theme-muted\">Yes. It checks API catalog discovery, OpenAPI or Swagger documents, OAuth and OIDC discovery metadata, OAuth Protected Resource metadata, MCP server cards, mcp.json, WebMCP manifests, browser tool annotations, A2A agent cards, agent.json, agents.json, and agent skills indexes.</p>"
    }
  ],
  "citableParagraphs": [],
  "score": 75,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

AEO: Answer evidence and trust scored 80/100 and needs improvement.

2 Warning

Needs attention

AEO: Answer evidence and trust

Warning
01

Issue

Missing AIO trust signals: publisher.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer evidence and trust

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer evidence and trust scored 80/100 and needs improvement.

Evidence
{
  "signals": {
    "author": true,
    "publisher": false,
    "freshnessDate": true,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "publisher"
  ],
  "authorMeta": "Senior Editor",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [
    "2026-06-08T21:44:17.000Z"
  ],
  "visibleDates": [
    "2026-06-08",
    "2026-06-08",
    "2026-06-08"
  ],
  "aboutLinks": [
    {
      "href": "/about",
      "text": "About",
      "html": "<a class=\"focus-ring rounded-lg px-1 py-1 text-left underline-offset-4 hover:underline hover:theme-accent transition-colors duration-200\" href=\"/about\" data-mcp-tool=\"open_about\" tool-name=\"open_about\" tool-description=\"Open information about CanAgentUse\">About</a>"
    }
  ],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "/llms.txt",
      "text": "Terms for agents",
      "html": "<a class=\"focus-ring rounded-lg px-1 py-1 text-left underline-offset-4 hover:underline hover:theme-accent transition-colors duration-200\" href=\"/llms.txt\" data-mcp-tool=\"open_agent_terms\" tool-name=\"open_agent_terms\" tool-description=\"Open machine-readable terms and guidance for agents\">Terms for agents</a>"
    }
  ],
  "score": 80,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

GEO: Extraction-friendly structure scored 85/100 and needs improvement.

2 Warning

Needs attention

GEO: Extraction-friendly structure

Warning
01

Issue

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Extraction-friendly structure

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Extraction-friendly structure scored 85/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": true,
  "definitionPatterns": 2,
  "schemaBlocks": 3,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "ordered list only if the page explains a workflow/process"
  ],
  "score": 85,
  "weight": 24
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 86/100 and needs improvement.

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: canagentuse, scanner, website, ready, agents.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Entity and definition clarity

Score

86/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Entity and definition clarity scored 86/100 and needs improvement.

Evidence
{
  "title": "CanAgentUse Scanner | AI SEO and Agent-Readiness Audits",
  "h1": "Is your website ready for AI agents?",
  "description": "Run deep AI SEO and agent-readiness audits across crawler policy, structured data, performance, accessibility, API discovery, OAuth, MCP, WebMCP, agent skills, and commerce signals.",
  "topicOverlap": 0.4444444444444444,
  "definitionCount": 2,
  "topicTerms": [
    "canagentuse",
    "scanner",
    "seo",
    "agent",
    "readiness",
    "audits",
    "website",
    "ready",
    "agents"
  ],
  "descriptionTerms": [
    "run",
    "deep",
    "seo",
    "agent",
    "readiness",
    "audits",
    "across",
    "crawler",
    "policy",
    "structured",
    "data",
    "performance",
    "accessibility",
    "api",
    "discovery",
    "oauth",
    "mcp",
    "webmcp",
    "skills"
  ],
  "missingFromDescription": [
    "canagentuse",
    "scanner",
    "website",
    "ready",
    "agents"
  ],
  "score": 86,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

AEO: Answer intent coverage scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

Missing likely AI Overview intent sections: what, how, cost, compare.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer intent coverage scored 70/100 and needs improvement.

Evidence
{
  "headings": [
    {
      "text": "137 signals across 15 readiness areas for the AI agent age.",
      "html": "<h2 id=\"scanner-coverage-heading\" class=\"mt-3 max-w-xl text-4xl font-semibold leading-[1.05] sm:text-5xl\">137<!-- --> signals across <!-- -->15<!-- --> readiness areas for the AI agent age.</h2>"
    },
    {
      "text": "Agent-readiness field notes",
      "html": "<h2 id=\"latest-blog-heading\" class=\"mt-2 text-3xl font-semibold sm:text-4xl\">Agent-readiness field notes</h2>"
    },
    {
      "text": "Fix failing checks inside the tools your team already uses.",
      "html": "<h2 id=\"integration-guide-title\" class=\"mt-3 max-w-3xl text-3xl font-semibold leading-tight sm:text-4xl\">Fix failing checks inside the tools your team already uses.</h2>"
    },
    {
      "text": "Want help making your site agent-ready?",
      "html": "<h2 id=\"scanner-connect-title\" class=\"mt-3 max-w-2xl text-3xl font-semibold leading-tight md:text-4xl\">Want help making your site agent-ready?</h2>"
    },
    {
      "text": "Questions about AI SEO and agent-readiness scans",
      "html": "<h2 id=\"faq-heading\" class=\"mt-3 text-3xl font-semibold leading-tight sm:text-4xl\">Questions about AI SEO and agent-readiness scans</h2>"
    },
    {
      "text": "Product",
      "html": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Product</h2>"
    },
    {
      "text": "Developers",
      "html": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Developers</h2>"
    },
    {
      "text": "Agent Files",
      "html": "<h2 class=\"text-xs font-semibold uppercase tracking-[0.16em] theme-text\">Agent Files</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is CanAgentUse Scanner?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does CanAgentUse Scanner work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use CanAgentUse Scanner?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is CanAgentUse Scanner free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does CanAgentUse Scanner compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is CanAgentUse Scanner?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does CanAgentUse Scanner work?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is CanAgentUse Scanner free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does CanAgentUse Scanner compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

A protected route returned 401 without a valid WWW-Authenticate: Bearer challenge, matching resource_metadata URL, or matching protected resource identifier.

02

Why it matters

Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.

Result

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Validation steps

  1. Probe protected API Bearer challenge

    A protected route returned 401 without a valid WWW-Authenticate: Bearer challenge, matching resource_metadata URL, or matching protected resource identifier.

Evidence
{
  "failedStep": "protected-route-challenge",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 200,
        "contentType": "application/oauth-protected-resource+json; charset=utf-8"
      },
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "pass",
      "evidence": {
        "valid": true,
        "compatibleContentType": true,
        "hasResource": true,
        "authorizationServerCount": 1,
        "resource": "https://canagentuse.com",
        "resourceIssues": [],
        "authServerIssues": [],
        "scopesSupported": [
          "scan:read",
          "scan:write"
        ],
        "bearerMethodsSupported": [
          "header"
        ],
        "rawExcerpt": "{\"resource\":\"https://canagentuse.com\",\"authorization_servers\":[\"https://canagentuse.com/.well-known/oauth-authorization-server\"],\"scopes_supported\":[\"scan:read\",\"scan:write\"],\"bearer_methods_supported\":[\"header\"],\"resource_documentation\":\"https://canagentuse.com/api\"}"
      },
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "pass",
      "evidence": {
        "resource": "https://canagentuse.com",
        "expectedResource": "https://canagentuse.com"
      },
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 401,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://canagentuse.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://canagentuse.com",
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 401,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://canagentuse.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://canagentuse.com",
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 200,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://canagentuse.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://canagentuse.com",
            "resourceMatchesRequestContext": true
          }
        ]
      },
      "issue": "A protected route returned 401 without a valid WWW-Authenticate: Bearer challenge, matching resource_metadata URL, or matching protected resource identifier.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 15,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "button:attribute",
        "weight": 3,
        "match": "auth control annotation"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "oauth"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "oidc"
      }
    ]
  },
  "resourceFetchSucceeded": true
}

Performance and AccessibilityPerformanceBrowser audit

Network dependency tree

33 Fail

Check name

Network dependency tree

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Evidence
{
  "description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load."
}

Performance and AccessibilityPerformanceBrowser audit

Legacy JavaScript

17 Warning

Check name

Legacy JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 12 KiB

Fix guidance

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)

Evidence
{
  "displayValue": "Est savings of 12 KiB",
  "description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

17 Warning

Check name

Render-blocking requests

Score

50/100

Status

warning

Device

desktop

Category

Performance

Fix guidance

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.

Evidence
{
  "description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

5 reports
Public score history report links
Scan dateScoreReadinessReport
79/100Level 4, Mostly ReadyView report
96/100Level 5, Agent-ReadyView report
96/100Level 5, Agent-ReadyView report
98/100Level 5, Agent-ReadyView report
97/100Level 5, Agent-ReadyCurrent report
canagentuse.com AI SEO Report: 97/100 (Level 5, Agent-Ready)