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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability64%Agent Easeof Use63%Security& Trust64%GEO, AIO, AEO69%SEO100%Performance100%Accessibility97%
  • AI Discoverability 64 out of 100
  • Agent Ease of Use 63 out of 100
  • Security & Trust 64 out of 100
  • GEO, AIO and AEO 69 out of 100
  • SEO 100 out of 100
  • Performance 100 out of 100
  • Accessibility 97 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Cloudflare Developer Docs | Cloudflare Docs favicon

Cloudflare Developer Docs | Cloudflare Docs

Connect, protect, and build everywhere.

Next step

Turn this report into a fix workflow

12 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
64
Needs work30134View details
Discoverability
80
Mostly ready810View details
Content Readiness
54
Needs work19112View details
Bot Access Control
58
Needs work312View details
Agent Ease of Use
63
Needs work19414View details
API
84
Mostly ready1122View details
Auth
48
Priority fix112View details
MCP
60
Needs work206
Skill Discovery
61
Needs work514View details
GEO, AIO and AEO
69
Needs work1026View details
GEO Readiness
61
Needs work312View details
AIO Readiness
88
Mostly ready402
AEO Readiness
59
Needs work312View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
64
Needs work1746View details
Security & Trust
64
Needs work1746View details
Performance
100
Strong1520View details
Performance
100
Strong1520View details
Accessibility
97
Strong710View details
Accessibility
97
Strong710View details

Prioritized recommendations

Issues ranked by score impact

36 items need attention

AI DiscoverabilityDiscoverabilityEstablished

robots.txt

robots.txt failed at "Validate RFC 9309 core syntax".

60 Fail

Needs attention

robots.txt

Failed check
01

Issue

robots.txt was found but did not contain a valid, parseable User-agent group.

02

Why it matters

robots.txt gives crawlers and agents a standard place to read crawl permissions, disallowed paths, and sitemap locations before requesting site content.

Check name

robots.txt

Score

40/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish /robots.txt with clear crawl rules.

Result

robots.txt failed at "Validate RFC 9309 core syntax".

Validation steps

  1. Validate RFC 9309 core syntax

    robots.txt was found but did not contain a valid, parseable User-agent group.

Evidence log1 step · 5 lines
Validate RFC 9309 core syntax [fail]! robots.txt was found but did not contain a valid, parseable User-agent group.INFOValidate RFC 9309 core syntaxINFOParsing robots.txt into User-agent groups and Allow/Disallow recordsPASSCheck User-agent group count actual=1 expected=">= 1 parseable group" parsedUserAgents=["*"]FAILCheck malformed lines and orphan Allow/Disallow records actual={"invalidLines":0,"orphanRecords":6} expected={"invalidLines":0,"orphanRecords":0}FAILAllow/Disallow records appeared before any User-agent group orphanRecords=[{"directive":"allow","value":"/","line":33},{"directive":"disallow","value":"/client-ip-geolocation","line":34},{"directive":"disallow","value":"/plans/","line":35},{"directive":"disallow","value":"/constellation","line":36},{"directive":"disallow","value":"/cdn-cgi/","line":37}]

Agent Ease of UseMCPEmerging recommendation

WebMCP

WebMCP has a validation warning at "Probe WebMCP operability".

25 Warning

Needs attention

WebMCP

Warning
01

Issue

No WebMCP surface was found to probe.

Details

02

Why it matters

WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.

Result

WebMCP has a validation warning at "Probe WebMCP operability".

Validation steps

  1. Detect WebMCP runtime API

    Expose current WebMCP tools through document.modelContext.registerTool(), or clearly document navigator.modelContext as a compatibility/polyfill profile.

  2. Probe WebMCP operability

    No WebMCP surface was found to probe.

    WebMCP operability findings
    • No WebMCP surface was found to probe.
    • Conventional WebMCP manifest paths were checked but did not return a valid manifest.
  3. Validate declarative WebMCP form tools

    No W3C-style declarative WebMCP form attributes were found.

  4. Validate MCP-aware HTML annotations

    No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.

  5. Validate static WebMCP JSON compatibility

    No static WebMCP JSON manifest or WMCP interaction graph was found.

  6. Validate WebMCP tool metadata quality

    Use clear tool names, useful descriptions, constrained schemas, side-effect clarity, and profile-appropriate naming.

  7. Review WebMCP security and policy signals

    Remove secrets and prompt-injection text from WebMCP metadata, avoid private endpoints, and use Permissions-Policy and annotations for tool safety.

Evidence log7 steps · 32 lines
Detect WebMCP runtime API [informational]INFODetect WebMCP runtime API status="informational"INFOProbe rendered browser for WebMCP runtime objects SKIPCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"INFOWebMCP evidence was recorded for context. status="informational"Probe WebMCP operability [warning]! No WebMCP surface was found to probe.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="No WebMCP surface was found to probe."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."WARNNo WebMCP surface was found to probe.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://developers.cloudflare.com/.well-known/webmcp.json" statusCode=404 contentType="text/html"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://developers.cloudflare.com/webmcp.json" statusCode=404 contentType="text/html"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

23 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

20 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

No Organization or Organization subtype was found in Schema.org structured data. No WebSite entity was found in Schema.org structured data. Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url. WebSite.publisher is missing. Organization schema is missing logo and sameAs or public contact evidence.

02

Why it matters

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Validation steps

  1. Organization entity

    No Organization or Organization subtype was found in Schema.org structured data.

  2. WebSite entity

    No WebSite entity was found in Schema.org structured data.

  3. Identity fields

    Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url.

  4. WebSite publisher linkage

    WebSite.publisher is missing.

  5. Organization trust fields

    Organization schema is missing logo and sameAs or public contact evidence.

Evidence log5 steps · 23 lines
Organization entity [fail]! No Organization or Organization subtype was found in Schema.org structured data.INFOOrganization entityINFOLooking for Organization or Organization subtype in structured data observedTypes=[]FAILCheck Organization entity presence actual=false expected=true fields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}]FAILOrganization entity is missingWebSite entity [fail]! No WebSite entity was found in Schema.org structured data.INFOWebSite entityINFOLooking for WebSite entity in structured data FAILCheck WebSite entity presence actual=false expected=true fields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]FAILWebSite entity is missingIdentity fields [fail]! Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields FAILCheck required identity fields actual=0 expected=4 missing=["Organization.name","Organization.url","WebSite.name","WebSite.url"] organizationFields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}] websiteFields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":false,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}FAILIdentity fields are missing missing=["Organization.name","Organization.url","WebSite.name","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={} organization={}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missingOrganization trust fields [fail]! Organization schema is missing logo and sameAs or public contact evidence.INFOOrganization trust fieldsINFOChecking logo, sameAs, and public contact evidence FAILCheck logo presence actual=false expected=true fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILCheck sameAs or contact evidence actual=0 expected=">= 1" sameAsCount=0 contactSignalCount=0 fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILOrganization trust fields are missing

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery failed at "Fetch discovery metadata".

19 Fail

Needs attention

OAuth / OIDC discovery

Failed check
01

Issue

OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.

02

Why it matters

OAuth and OIDC discovery let agents and API clients find authorization, token, and key endpoints programmatically instead of scraping login pages or guessing provider setup.

Check name

OAuth / OIDC discovery

Score

43/100

Status

fail

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata only when the site operates or advertises a real OAuth/OIDC authorization server.

Result

OAuth / OIDC discovery failed at "Fetch discovery metadata".

Validation steps

  1. Fetch discovery metadata

    OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.

Evidence log1 step · 6 lines
Fetch discovery metadata [fail]! OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found.INFOFetch discovery metadataINFOTrying OAuth/OIDC well-known metadata candidates checkedCount=2INFOChecked discovery candidate path="/.well-known/openid-configuration" statusCode=404 contentType="text/html" length=32241INFOChecked discovery candidate path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/html" length=32241FAILCheck discovery metadata fetch succeeded actual=2 expected="HTTP 2xx JSON metadata document"FAILFetch discovery metadata failed issue="OAuth/OIDC was claimed or referenced, but no registered OAuth/OIDC discovery document was found."

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate CSP frame-ancestors".

19 Fail

Needs attention

Frame protection

Failed check
01

Issue

frame-ancestors contains invalid source expressions: cloudflare.com, *.cloudflare.com.

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

25/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection failed at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    frame-ancestors contains invalid source expressions: cloudflare.com, *.cloudflare.com.

  2. Validate X-Frame-Options

    No valid X-Frame-Options fallback is present.

  3. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Evidence log3 steps · 12 lines
Validate CSP frame-ancestors [fail]! frame-ancestors contains invalid source expressions: cloudflare.com, *.cloudflare.com.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=true reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=1 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual={"values":["'self'","cloudflare.com","*.cloudflare.com"],"mode":"malformed","valid":false,"restrictive":false,"broadSources":[]} expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors contains invalid source expressions: cloudflare.com, *.cloudflare.com."FAILframe-ancestors contains invalid source expressions: cloudflare.com, *.cloudflare.com.Validate X-Frame-Options [fail]! No valid X-Frame-Options fallback is present.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="missing" parsedValues=[] normalizedValues=[]FAILCompare X-Frame-Options value actual="missing" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="No valid X-Frame-Options fallback is present."FAILNo valid X-Frame-Options fallback is present.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=37 sameOriginCount=32 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://developers.cloudflare.com/","status":200,"resourceType":"document","contentType":"text/html","contentSecurityPolicy":"form-action 'self'; frame-src 'self' company-target.com *.company-target.com cloudflarestream.com *.cloudflarestream.com youtube-nocookie.com *.youtube-nocookie.com videodelivery.net *.videodelivery.net cloudflare.com *.cloudflare.com; frame-ancestors 'self' cloudflare.com *.cloudflare.com; script-s","contentSecurityPolicyReportOnly":null}]} expected="0 missing/invalid or broad same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit valid frame protection."WARNOne or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

17 Warning

Needs attention

Auth.md Agent Registration

Warning
01

Issue

The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

Validation steps

  1. Warn when auth surface lacks Auth.md

    The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Evidence log1 step · 2 lines
Warn when auth surface lacks Auth.md [warning]! The site appears to support login, signup, account access, or credentials but does not publish /auth.md.INFOWarn when auth surface lacks Auth.mdWARNThe site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

17 Warning

Needs attention

OAuth Protected Resource

Warning
01

Issue

Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

02

Why it matters

Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.

Check name

OAuth Protected Resource

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.

Result

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

Validation steps

  1. Detect protected-resource applicability

    Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

Evidence log1 step · 4 lines
Detect protected-resource applicability [warning]! Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.INFODetect protected-resource applicabilityINFOInspecting auth headers, MCP/OAuth claims, and protected-resource hints applies=false requiresAuthorizationServers=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://developers.cloudflare.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://developers.cloudflare.com","statusCode":404,"contentType":"text/html","length":32241}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

17 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Declare machine-readable content licensing terms for compliant AI and crawler systems when the site needs them.

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

Evidence log1 step · 4 lines
Discover RSL declarations [warning]! No RSL declarations were found.INFODiscover RSL declarationsINFOChecking robots.txt License records, HTTP Link rel=license headers, HTML license links, and inline RSL XML robotsFound=trueSKIPCount discovered RSL declarations actual=0 expected=">= 1 when RSL licensing terms are published" sources={}WARNNo RSL declarations were found on any supported discovery surface.

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

17 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

No TDMRep declaration was found at /.well-known/tdmrep.json.

02

Why it matters

TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish a machine-readable text and data mining reservation declaration and verifiable ODRL policy when the site needs one.

Result

No TDMRep declaration was found.

Validation steps

  1. Fetch /.well-known/tdmrep.json

    No TDMRep declaration was found at /.well-known/tdmrep.json.

Evidence log1 step · 4 lines
Fetch /.well-known/tdmrep.json [warning]! No TDMRep declaration was found at /.well-known/tdmrep.json.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonWARNCompare TDMRep file response actual=404 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html" length=32241WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy failed at "Find Referrer-Policy header".

15 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy header is missing.

02

Why it matters

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Check name

Referrer-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site with an explicit Referrer-Policy header.

Result

Referrer-Policy failed at "Find Referrer-Policy header".

Validation steps

  1. Find Referrer-Policy header

    Referrer-Policy header is missing.

  2. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.

Evidence log2 steps · 8 lines
Find Referrer-Policy header [fail]! Referrer-Policy header is missing.INFOFind Referrer-Policy headerINFORead Referrer-Policy delivery header="referrer-policy" value="missing" metaReferrerPolicyCount=0 browserDefault="strict-origin-when-cross-origin"FAILRequire explicit HTTP Referrer-Policy header actual="missing" expected="HTTP response header present" issue="Referrer-Policy header is missing."FAILReferrer-Policy header is missing.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=37 sameOriginCount=32 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://developers.cloudflare.com/","status":200,"resourceType":"document","contentType":"text/html","referrerPolicy":null,"classification":"invalid"}]} expected="0 missing, unsafe, invalid, or weak same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy."WARNOne or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card has a validation warning at "Discover MCP server card".

15 Warning

Needs attention

MCP Server Card

Warning
01

Issue

The MCP server card was found only at a transitional or linked path.

02

Why it matters

MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.

Check name

MCP Server Card

Score

70/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card that helps agents discover remote MCP server transports before opening a session.

Result

MCP Server Card has a validation warning at "Discover MCP server card".

Validation steps

  1. Discover MCP server card

    The MCP server card was found only at a transitional or linked path.

  2. Validate MCP remotes

    At least one MCP remote is cross-origin and was not actively probed by this scanner.

  3. Validate HTTP delivery

    CORS header Access-Control-Allow-Origin is absent.

  4. Probe same-origin MCP endpoint

    MCP remotes were discovered, but none could be safely probed by this scanner.

Evidence log4 steps · 46 lines
Discover MCP server card [warning]! The MCP server card was found only at a transitional or linked path.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]INFOTrying to fetch /.well-known/mcp-server-card url="https://developers.cloudflare.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType="text/html"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://developers.cloudflare.com/.well-known/mcp/server-card.json" source="transitional"PASS/.well-known/mcp/server-card.json returned a successful response statusCode=200 contentType="application/json; charset=utf-8" finalUrl="https://developers.cloudflare.com/.well-known/mcp/server-card.json"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://developers.cloudflare.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType="text/html"INFOTrying to fetch /mcp.json url="https://developers.cloudflare.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/html"INFOTrying to fetch /.well-known/mcp.json url="https://developers.cloudflare.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="text/html"WARNCheck selected card is published at the current well-known path actual="/.well-known/mcp/server-card.json" expected="/.well-known/mcp-server-card" source="transitional" finalUrl="https://developers.cloudflare.com/.well-known/mcp/server-card.json"WARNMCP server card was discovered through a transitional or linked path path="/.well-known/mcp/server-card.json" source="transitional" reason="The MCP server card was found only at a transitional or linked path."Validate MCP remotes [warning]! At least one MCP remote is cross-origin and was not actively probed by this scanner.INFOValidate MCP remotes remoteCount=27PASSCheck at least one MCP remote is declared actual=27 expected="> 0"PASSCheck invalid remote count actual=0 expected=0 invalidRemotes=[]WARNCheck same-origin remote coverage actual=0 expected=27PASSRemote #0 is syntactically usable index=0 source="remotes" type="streamable-http" url="https://mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #1 is syntactically usable index=1 source="remotes" type="streamable-http" url="https://docs.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=false issues=[]PASSRemote #2 is syntactically usable index=2 source="remotes" type="streamable-http" url="https://observability.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #3 is syntactically usable index=3 source="remotes" type="streamable-http" url="https://bindings.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #4 is syntactically usable index=4 source="remotes" type="streamable-http" url="https://builds.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #5 is syntactically usable index=5 source="remotes" type="streamable-http" url="https://containers.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #6 is syntactically usable index=6 source="remotes" type="streamable-http" url="https://browser.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]PASSRemote #7 is syntactically usable index=7 source="remotes" type="streamable-http" url="https://logs.mcp.cloudflare.com/mcp" sameOrigin=false authRequired=true issues=[]WARNMCP remotes are valid but not all can be actively probed reason="At least one MCP remote is cross-origin and was not actively probed by this scanner."Validate HTTP delivery [warning]! CORS header Access-Control-Allow-Origin is absent.INFOValidate HTTP delivery finalUrl="https://developers.cloudflare.com/.well-known/mcp/server-card.json"PASSCheck server card returned HTTP 2xx actual=200 expected="200-299"PASSCheck card is served as JSON actual="application/json; charset=utf-8" expected="application/json or +json"PASSCheck card is served over HTTPS actual="https:" expected="https:"WARNCheck browser-readable CORS header actual="missing" expected="Access-Control-Allow-Origin present"WARNCheck cache header is present actual="missing" expected="Cache-Control present"WARNMCP server-card HTTP delivery has non-blocking issues issues=["CORS header Access-Control-Allow-Origin is absent.","Cache-Control is absent."] reason="CORS header Access-Control-Allow-Origin is absent."Probe same-origin MCP endpoint [warning]! MCP remotes were discovered, but none could be safely probed by this scanner.INFOProbe same-origin MCP endpoint probeCount=27INFOSelecting same-origin unauthenticated MCP remotes for a bounded initialize probeSKIPSkipped MCP endpoint probe url="https://mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://docs.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://observability.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://bindings.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://builds.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://containers.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://browser.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."SKIPSkipped MCP endpoint probe url="https://logs.mcp.cloudflare.com/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."WARNCheck successful initialize probe count actual=0 expected="> 0 when a safe same-origin unauthenticated remote exists" activeProbeCount=0 authBlocked=0WARNMCP endpoint probe could not fully confirm operability reason="MCP remotes were discovered, but none could be safely probed by this scanner."

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

13 Warning

Needs attention

A2A Agent Card

Warning
01

Issue

No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

Validation steps

  1. Discover A2A Agent Card

    No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Evidence log1 step · 8 lines
Discover A2A Agent Card [warning]! No A2A Agent Card was found at the current, legacy, or fallback discovery paths.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType="text/html"WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType="text/html"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html"WARNNo A2A Agent Card candidate was selectedWARNNo A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json has a validation warning at "Discover agents.json".

13 Warning

Needs attention

agents.json

Warning
01

Issue

No Wildcard-style agents.json file was found.

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json has a validation warning at "Discover agents.json".

Validation steps

  1. Discover agents.json

    No Wildcard-style agents.json file was found.

Evidence log1 step · 6 lines
Discover agents.json [warning]! No Wildcard-style agents.json file was found.INFODiscover agents.jsonINFOTry agents.json discovery paths in priority order paths=["/.well-known/agents.json","/agents.json"]WARNagents.json candidate path did not return a usable contract path="/.well-known/agents.json" statusCode=404 contentType="text/html"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/html"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 0/100 and needs a fix.

12 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 0/100 and needs a fix.

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Parseability".

12 Fail

Needs attention

Structured data

Failed check
01

Issue

Detected structured data could not be parsed for: rdfa.

02

Why it matters

Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.

Check name

Structured data

Score

42/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose machine-readable page entities and relationships through a recognized structured-data syntax.

Result

Structured data failed at "Parseability".

Validation steps

  1. Parseability

    Detected structured data could not be parsed for: rdfa.

  2. Schema.org entity typing

    Structured data was detected, but no typed Schema.org entities were extracted.

  3. Page-relevant schema family

    The page has specific visible content intent, but structured data does not include a matching primary schema family.

Evidence log3 steps · 12 lines
Parseability [fail]! Detected structured data could not be parsed for: rdfa.INFOParseabilityINFOChecking detected structured data for parse errors formatsFound=["rdfa"]FAILCheck invalid detected formats actual=1 expected=0 invalidPresentFormats=["rdfa"] parseErrors=[{"format":"rdfa","error":"property attributes found without a typeof subject: meta[property=\"image\"] value=\"https://developers.cloudflare.com/cf-twitter-card.png\" html=\"<meta property=\"image\" content=\"https://developers.cloudflare.com/cf-twitter-card.png\">\""}]FAILDetected structured data has fatal parse issues invalidPresentFormats=["rdfa"]Schema.org entity typing [fail]! Structured data was detected, but no typed Schema.org entities were extracted.INFOSchema.org entity typingINFOExtracting typed Schema.org entities from parsed structured dataFAILCheck extracted Schema.org type count actual=0 expected="> 0" schemaTypes=[] entityCount=0FAILNo typed Schema.org entities were extractedPage-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["software"] expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] matchingTypes=[] observedTypes=[]FAILNo primary schema family matches the inferred page intent expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] primaryTypes=[]

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

11 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://developers.cloudflare.com/api/index.md (service-doc) advertised text/markdown but returned text/plain; charset=utf-8.

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

79/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog targets".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

  2. Validate API catalog targets

    API catalog target https://developers.cloudflare.com/api/index.md (service-doc) advertised text/markdown but returned text/plain; charset=utf-8.

Evidence log2 steps · 12 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\""WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog targets [fail]! API catalog target https://developers.cloudflare.com/api/index.md (service-doc) advertised text/markdown but returned text/plain; charset=utf-8.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="service-desc" href="https://developers.cloudflare.com/openapi.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"FAILAPI catalog target failed validation rel="service-doc" href="https://developers.cloudflare.com/api/index.md" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/markdown" typeMatches=falsePASSAPI catalog target is reachable rel="service-doc" href="https://developers.cloudflare.com/api/" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"SKIPSkipped API catalog target fetch rel="status" href="https://www.cloudflarestatus.com/api/v2/status.json" resolvedUrl="https://www.cloudflarestatus.com/api/v2/status.json" reason="External target was recorded but not fetched."FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://developers.cloudflare.com/api/index.md (service-doc) advertised text/markdown but returned text/plain; charset=utf-8.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 20/100 and needs a fix.

9 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

14 section(s) bury or omit a concise opening answer.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

20/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 20/100 and needs a fix.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

9 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

  2. Author identity quality

    No named author or publisher identity could be extracted.

Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

9 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

65/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

  2. Evaluate script execution

    script-src allows unsafe-inline without nonce or hash controls.

  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri.

Evidence log3 steps · 12 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=["frame-src","script-src"]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [warning]! script-src allows unsafe-inline without nonce or hash controls.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","cloudflarestream.com","*.cloudflarestream.com","cloudflareinsights.com","*.cloudflareinsights.com","cloudflare.com","*.cloudflare.com","google.com","*.google.com","demandbase.com","*.demandbase.com","bizible.com","*.bizible.com","jsdelivr.net","*.jsdelivr.net","'wasm-unsafe-eval'","'unsafe-inline'"]WARNCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":true,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows unsafe-inline without nonce or hash controls."WARNscript-src allows unsafe-inline without nonce or hash controls.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives formAction=["'self'"] frameAncestors=["'self'","cloudflare.com","*.cloudflare.com"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

9 Warning

Needs attention

DNS-AID Agent Discovery

Warning
01

Issue

No DNS-AID HTTPS/SVCB records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

65/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

Validation steps

  1. Query DNS-AID records

    No DNS-AID HTTPS/SVCB records were found under _agents.

Evidence log1 step · 10 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="developers.cloudflare.com" labels=["_index._agents.developers.cloudflare.com","_a2a._agents.developers.cloudflare.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.developers.cloudflare.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.developers.cloudflare.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.developers.cloudflare.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.developers.cloudflare.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.developers.cloudflare.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.developers.cloudflare.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.developers.cloudflare.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.developers.cloudflare.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Review OpenAPI safety".

6 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

Server URL points to localhost.

02

Why it matters

OpenAPI documents let agents understand operations, schemas, authentication, servers, and request/response formats before calling an API.

Check name

OpenAPI discovery

Score

88/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.

Result

OpenAPI discovery failed at "Review OpenAPI safety".

Validation steps

  1. Check machine-usable details

    OpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.

  2. Review OpenAPI safety

    Server URL points to localhost.

Evidence log2 steps · 15 lines
Check machine-usable details [warning]! OpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.INFOCheck machine-usable details status="warning"INFOInspect machine-usable operation details hasServers=true hasSecuritySchemes=true hasExplicitNoAuth=true requestBodyOperationCount=1263 parameterOperationCount=2954 responseSchemaOperationCount=3002 operationIdCount=3099 taggedOperationCount=3148 exampleOperationCount=1001WARNCheck OpenAPI operations include enough detail for agents to call them safely actual="5 machine-usability warning(s)" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"WARNMachine-usability warning warning="One or more operations are missing parameters or request bodies."WARNMachine-usability warning warning="One or more operations lack response schema or response media type detail."WARNMachine-usability warning warning="One or more operations are missing operationId."WARNMachine-usability warning warning="One or more operations do not include examples."WARNMachine-usability warning warning="One or more URLs look internal, private, credential-bearing, or admin-only."WARNOpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.Review OpenAPI safety [fail]! Server URL points to localhost.INFOReview OpenAPI safety status="fail"INFOInspect advertised server URLs serverUrls=["https://api.cloudflare.com/client/v4"]FAILCheck for unsafe public server URLs actual=2 expected=0FAILUnsafe server URL advertised url="http://localhost:3000" issue="Server URL points to localhost."FAILUnsafe server URL advertised url="https://localhost:8001" issue="Server URL points to localhost."FAILServer URL points to localhost.

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate skill content".

6 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Archive contains too many entries.

Details

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

78/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index failed at "Validate skill content".

Validation steps

  1. Validate skill content

    Archive contains too many entries.

    Skill content findings
    • Archive contains too many entries.
    • description does not clearly state when an agent should activate the skill.
    • SKILL.md body is over 500 lines; move detailed material into references/ for progressive disclosure.
  2. Review skill artifact security

    Archive contains scripts/ entries; clients should not execute scripts by default.

    Agent Skills security findings
    • Archive contains scripts/ entries; clients should not execute scripts by default.
    • SKILL.md references external URLs; fetched content is an additional trust boundary (https://web.dev/articles/vitals`, https://developer.chrome.com/docs/devtools/performance`, https://developer.chrome.com/docs/lighthouse/performance/performance-scoring`).
    • SKILL.md references external URLs; fetched content is an additional trust boundary (https://developers.cloudflare.com/workers/wrangler/`, https://developers.cloudflare.com/workers/`, https://developers.cloudflare.com/workers/configuration/compatibility-dates/, http://localhost:8787/__scheduled).
Evidence log2 steps · 20 lines
Validate skill content [fail]! Archive contains too many entries.INFOValidate skill contentFAILCompare skill artifact content failures actual=0 expected=0 name="agents-sdk" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/agents-sdk.tar.gz"FAILCompare skill artifact content failures actual=1 expected=0 name="cloudflare" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/cloudflare.tar.gz"FAILSkill content validation failure name="cloudflare" failure="Archive contains too many entries."FAILCompare skill artifact content failures actual=0 expected=0 name="cloudflare-email-service" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/cloudflare-email-service.tar.gz"FAILCompare skill artifact content failures actual=0 expected=0 name="durable-objects" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/durable-objects.tar.gz"FAILCompare skill artifact content failures actual=0 expected=0 name="sandbox-sdk" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/sandbox-sdk.tar.gz"FAILCompare skill artifact content failures actual=0 expected=0 name="turnstile-spin" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/turnstile-spin.tar.gz"FAILCompare skill artifact content failures actual=0 expected=0 name="web-perf" type="skill-md" url="https://developers.cloudflare.com/.well-known/agent-skills/web-perf/SKILL.md"FAILCompare skill artifact content failures actual=0 expected=0 name="workers-best-practices" type="archive" url="https://developers.cloudflare.com/.well-known/agent-skills/workers-best-practices.tar.gz"FAILCompare skill artifact content failures actual=0 expected=0 name="wrangler" type="skill-md" url="https://developers.cloudflare.com/.well-known/agent-skills/wrangler/SKILL.md"WARNSkill content validation warning name="wrangler" warning="description does not clearly state when an agent should activate the skill."WARNSkill content validation warning name="wrangler" warning="SKILL.md body is over 500 lines; move detailed material into references/ for progressive disclosure."FAILArchive contains too many entries.Review skill artifact security [warning]! Archive contains scripts/ entries; clients should not execute scripts by default.INFOReview skill artifact securityFAILCompare security finding count actual=3 expected=0WARNAgent Skills artifact security warning finding="Archive contains scripts/ entries; clients should not execute scripts by default."WARNAgent Skills artifact security warning finding="SKILL.md references external URLs; fetched content is an additional trust boundary (https://web.dev/articles/vitals`, https://developer.chrome.com/docs/devtools/performance`, https://developer.chrome.com/docs/lighthouse/performance/performance-scoring`)."WARNAgent Skills artifact security warning finding="SKILL.md references external URLs; fetched content is an additional trust boundary (https://developers.cloudflare.com/workers/wrangler/`, https://developers.cloudflare.com/workers/`, https://developers.cloudflare.com/workers/configuration/compatibility-dates/, http://localhost:8787/__scheduled)."WARNArchive contains scripts/ entries; clients should not execute scripts by default.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 57/100 and needs improvement.

5 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: author, publisher, sameAs.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

57/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 57/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 67/100 and needs improvement.

5 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: author, publisher.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 67/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is partially implemented.

4 Warning

Needs attention

Markdown negotiation

Warning
01

Issue

Markdown negotiation is missing or incomplete.

02

Why it matters

Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.

Check name

Markdown negotiation

Score

78/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose a useful Markdown representation through negotiation or an explicit alternate URL.

Result

Markdown negotiation is partially implemented.

Validation steps

  1. Advertised Markdown alternate

    Advertise dedicated Markdown URLs with Link: <url>; rel="alternate"; type="text/markdown" or an HTML link rel=alternate tag.

  2. Conventional .md mirror

    If a .md mirror is intentional, advertise it with rel=alternate and type=text/markdown.

Evidence log2 steps · 6 lines
Advertised Markdown alternate [fail]INFOAdvertised Markdown alternateFAILCheck advertised Markdown alternate candidates actual=1 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=["https://developers.cloudflare.com/index.md"] candidateCount=0FAILAdvertised Markdown alternate failed Conventional .md mirror [informational]INFOConventional .md mirrorINFOCheck conventional Markdown mirror candidates actual=0 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=[] candidateCount=0PASSConventional .md mirror recorded for context status="informational"

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

4 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: expected exactly one visible main landmark, found 2; 1 ARIA/native semantic issues.

Details

02

Why it matters

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Check name

Semantic HTML

Score

78/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is partially implemented.

Validation steps

  1. Page landmarks

    Expected exactly one visible main landmark; found 2.

  2. Native semantics and ARIA

    1 ARIA/native semantic conflicts or redundancies were found.

Evidence log2 steps · 6 lines
Page landmarks [fail]! Expected exactly one visible main landmark; found 2.INFOPage landmarksFAILCheck page landmarks evidence actual={"counts":{"main":2,"roleMain":0,"nav":1,"roleNavigation":0,"header":1,"roleBanner":0,"footer":1,"pageFooter":0,"roleContentinfo":0},"main":false} expected="semantic HTML evidence for this step"FAILPage landmarks failed issue="Expected exactly one visible main landmark; found 2."Native semantics and ARIA [warning]! 1 ARIA/native semantic conflicts or redundancies were found.INFONative semantics and ARIAWARNCheck native semantics and aria evidence actual={"counts":{"ariaIssues":1},"nativeSemanticIntegrity":false} expected="native HTML semantics are present and not replaced by conflicting ARIA"WARNNative semantics and ARIA has a warning issue="1 ARIA/native semantic conflicts or redundancies were found."

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 63/100 and needs improvement.

4 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: summary or key takeaways, FAQ or question-answer section where appropriate, typed JSON-LD structured data.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 63/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 67/100 and needs improvement.

4 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: authorOrOwner, entityLinks.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 75/100 and needs improvement.

4 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

16 image(s) are missing width/height attributes. 1 possible modal/interstitial element(s) detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 75/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header has a validation warning at "Review subdomain scope".

3 Warning

Needs attention

HSTS header

Warning
01

Issue

HSTS is valid, but includeSubDomains is absent.

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

Check name

HSTS header

Score

90/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.

Result

HSTS header has a validation warning at "Review subdomain scope".

Validation steps

  1. Review subdomain scope

    HSTS is valid, but includeSubDomains is absent.

  2. Review preload opt-in

    preload is present, but header-level preload requirements are missing: includeSubDomains, max-age >= 31536000.

Evidence log2 steps · 8 lines
Review subdomain scope [warning]! HSTS is valid, but includeSubDomains is absent.INFOReview subdomain scopeINFOInspect subdomain enforcement scope includeSubDomains=falseWARNCompare includeSubDomains coverage actual="absent" expected="included after subdomains are HTTPS-ready" issue="HSTS is valid, but includeSubDomains is absent."WARNHSTS is valid, but includeSubDomains is absent.Review preload opt-in [warning]! preload is present, but header-level preload requirements are missing: includeSubDomains, max-age >= 31536000.INFOReview preload opt-inINFOInspect preload opt-in preload=true includeSubDomains=false maxAge=15552000WARNCompare header-level preload requirements actual="not eligible by header" expected="preload + includeSubDomains + max-age >= 31536000" issue="preload is present, but header-level preload requirements are missing: includeSubDomains, max-age >= 31536000."WARNpreload is present, but header-level preload requirements are missing: includeSubDomains, max-age >= 31536000.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 81/100 and needs improvement.

2 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

14 section(s) bury or omit a concise opening answer.

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

81/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Question and answer structure scored 81/100 and needs improvement.

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

Verify that IndexNow ownership key placement is detectable when the site advertises it.

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

    No IndexNow key location was advertised in HTML, Link headers, or robots.txt.

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

Evidence log2 steps · 10 lines
Find advertised IndexNow key location [informational]! No IndexNow key location was advertised in HTML, Link headers, or robots.txt.INFOFind advertised IndexNow key locationINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"WARNNo IndexNow key location was advertised in HTML, Link headers, or robots.txt.Fetch and validate IndexNow key file [informational]! No discoverable IndexNow key file was found.INFOFetch and validate IndexNow key fileINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"INFOFetch each advertised same-origin key file and validate filename/body matchFAILCompare valid IndexNow key file count actual=0 expected="> 0"WARNNo discoverable IndexNow key file was found.

AccessibilityAccessibilityBrowser audit

Background and foreground colors do not have a sufficient contrast ratio.

100 Fail

Check name

Background and foreground colors do not have a sufficient contrast ratio.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).

Evidence
{
  "description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}

PerformancePerformanceBrowser audit

Network dependency tree

50 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."
}

PerformancePerformanceBrowser audit

Render-blocking requests

50 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 30 ms

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.",
  "displayValue": "Est savings of 30 ms"
}

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.

1 reports
Public score history report links
Scan dateScoreReadinessReport
71/100Level 3, Bot-AwareCurrent report