Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 42 out of 100
- Agent Ease of Use 47 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 63 out of 100
- SEO 92 out of 100
- Performance and Accessibility 96 out of 100
What AI sees of your website
CircularApp.com is for sale | HugeDomains
Find your domain name at HugeDomains. Start using this domain right away.
Next step
Turn this report into a fix workflow
17 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.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 42 | Priority fix | 16 | 22 | 9 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 13 | Priority fix | 6 | 17 | 5 | View details |
| Bot Access Control | 44 | Priority fix | 2 | 3 | 4 | View details |
| Agent Ease of Use | 47 | Priority fix | 8 | 8 | 12 | View details |
| API | 37 | Priority fix | 3 | 4 | 1 | View details |
| Auth | 52 | Needs work | 3 | 2 | 4 | View details |
| MCP | 47 | Priority fix | 2 | 2 | 2 | View details |
| Skill Discovery | 50 | Needs work | 0 | 0 | 5 | |
| GEO, AIO and AEO | 63 | Needs work | 10 | 5 | 3 | View details |
| GEO Readiness | 55 | Needs work | 3 | 2 | 1 | View details |
| AIO Readiness | 81 | Mostly ready | 4 | 1 | 1 | View details |
| AEO Readiness | 54 | Needs work | 3 | 2 | 1 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| Security & Trust | 45 | Priority fix | 7 | 5 | 4 | View details |
| Security & Trust | 45 | Priority fix | 7 | 5 | 4 | View details |
| Performance and Accessibility | 96 | Strong | 22 | 1 | 3 | View details |
| Performance | 97 | Strong | 17 | 0 | 3 | |
| Accessibility | 95 | Strong | 5 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
41 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
63 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
Needs attention
API Catalog
Issue
Content-Type "text/html" is not valid for an RFC 9727 API catalog.
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
37/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 media type".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
Validate API catalog media type
Content-Type "text/html" is not valid for an RFC 9727 API catalog.
Validate Linkset shape
Unexpected token '<', "<meta name"... is not valid JSON
Unexpected token '<', "<meta name"... is not valid JSON
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
Validate API catalog targets
API catalog did not expose any href targets to validate.
Evidence log5 steps · 23 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="text/html"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 media type [fail]! Content-Type "text/html" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', "<meta name"... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"<meta name\"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"<meta name\"... is not valid JSON"FAILUnexpected token '<', "<meta name"... is not valid JSONClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP failed at "Probe WebMCP operability".
28 Fail
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP failed at "Probe WebMCP operability".
Needs attention
WebMCP
Issue
Discovered WebMCP static metadata was fetchable but invalid.
Details
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
44/100
Status
fail
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 failed at "Probe WebMCP operability".
Validation steps
Detect WebMCP runtime API
WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.
Probe WebMCP operability
Discovered WebMCP static metadata was fetchable but invalid.
WebMCP operability findings
- Discovered WebMCP static metadata was fetchable but invalid.
Validate declarative WebMCP form tools
No W3C-style declarative WebMCP form attributes were found.
Validate MCP-aware HTML annotations
No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.
Validate static WebMCP JSON compatibility
A discovered WebMCP static manifest or WMCP interaction graph was invalid.
Body is not valid JSON.
Body is not valid JSON.
Evidence log5 steps · 23 lines
Detect WebMCP runtime API [warning]! WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.INFODetect WebMCP runtime API status="warning"INFOProbe rendered browser for WebMCP runtime objects WARNCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"WARNWebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.Probe WebMCP operability [fail]! Discovered WebMCP static metadata was fetchable but invalid.INFOProbe WebMCP operability status="fail"INFORun safe WebMCP operability checks safeProbeOnly=trueFAILCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"FAILWebMCP operability failure issue="Discovered WebMCP static metadata was fetchable but invalid."FAILDiscovered WebMCP static metadata was fetchable but invalid.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 [fail]! A discovered WebMCP static manifest or WMCP interaction graph was invalid.INFOValidate static WebMCP JSON compatibility status="fail"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={"unknown-webmcp-json":2}PASSWebMCP manifest candidate found source="path" path="/.well-known/webmcp.json" url="https://www.hugedomains.com/.well-known/webmcp.json" statusCode=200 contentType="text/html"PASSWebMCP manifest candidate found source="path" path="/webmcp.json" url="https://www.hugedomains.com/webmcp.json" statusCode=200 contentType="text/html"FAILValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":2,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"FAILA discovered WebMCP static manifest or WMCP interaction graph was invalid.
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card has a validation warning at "Discover MCP server card".
25 Warning
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card has a validation warning at "Discover MCP server card".
Needs attention
MCP Server Card
Issue
No MCP server card was found at current, transitional, or linked discovery paths.
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
50/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
Discover MCP server card
No MCP server card was found at current, transitional, or linked discovery paths.
Evidence log1 step · 14 lines
Discover MCP server card [warning]! No MCP server card was found at current, transitional, or linked discovery paths.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=[]PASSCheck whether page claims MCP support actual=false expected="true only when HTML or Link headers mention MCP" textMatches=[] headerLinkCount=0INFOTrying to fetch /.well-known/mcp-server-card url="https://www.hugedomains.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=403 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://www.hugedomains.com/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=403 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://www.hugedomains.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=403 contentType="text/html; charset=UTF-8"INFOTrying to fetch /mcp.json url="https://www.hugedomains.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=403 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp.json url="https://www.hugedomains.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=403 contentType="text/html; charset=UTF-8"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
17 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Validate Last-Modified header
No valid Last-Modified HTTP header was found.
Validate structured freshness dates
No Schema.org freshness dates were found.
Validate metadata freshness dates
No Open Graph, Dublin Core, or generic meta freshness date was found.
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1
AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
17 Fail
AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
Needs attention
Organization / WebSite schema
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.
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
Organization entity
No Organization or Organization subtype was found in Schema.org structured data.
WebSite entity
No WebSite entity was found in Schema.org structured data.
Identity fields
Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url.
WebSite publisher linkage
WebSite.publisher is missing.
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
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Recognized structured data format".
17 Fail
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Recognized structured data format".
Needs attention
Structured data
Issue
No JSON-LD, Microdata, or RDFa structured data was found.
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
0/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 "Recognized structured data format".
Validation steps
Recognized structured data format
No JSON-LD, Microdata, or RDFa structured data was found.
Page-relevant schema family
The page has specific visible content intent, but structured data does not include a matching primary schema family.
Evidence log2 steps · 8 lines
Recognized structured data format [fail]! No JSON-LD, Microdata, or RDFa structured data was found.INFORecognized structured data formatINFODetecting JSON-LD, Microdata, and RDFa in the page HTMLFAILCheck recognized structured-data formats found actual=0 expected="> 0" formatsFound=[]FAILNo recognized structured-data format foundPage-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=["commerce","editorial"] expectedTypes=["Product","ProductGroup","Offer","AggregateOffer","Service","Article","BlogPosting","NewsArticle","Report","Review"] matchingTypes=[] observedTypes=[]FAILNo primary schema family matches the inferred page intent expectedTypes=["Product","ProductGroup","Offer","AggregateOffer","Service","Article","BlogPosting","NewsArticle","Report","Review"] primaryTypes=[]
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
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".
Needs attention
Auth.md Agent Registration
Issue
The site appears to support login, signup, account access, or credentials but does not publish /auth.md.
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
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 UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has a validation warning at "Detect OAuth/OIDC applicability".
17 Warning
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has a validation warning at "Detect OAuth/OIDC applicability".
Needs attention
OAuth / OIDC discovery
Issue
Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.
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
50/100
Status
warning
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 has a validation warning at "Detect OAuth/OIDC applicability".
Validation steps
Detect OAuth/OIDC applicability
Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.
Evidence log1 step · 4 lines
Detect OAuth/OIDC applicability [warning]! Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.INFODetect OAuth/OIDC applicabilityINFOInspecting homepage, headers, and known auth/API signals for OAuth or OIDC claims applies=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=2WARNCheck OAuth/OIDC applicability signal actual=false expected="true when metadata exists or OAuth/OIDC is claimed" checked=[{"path":"/.well-known/openid-configuration","statusCode":403,"contentType":"text/html; charset=UTF-8","length":5471},{"path":"/.well-known/oauth-authorization-server","statusCode":403,"contentType":"text/html; charset=UTF-8","length":5471}]WARNDetect OAuth/OIDC applicability completed with warnings issue="Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected."AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
15 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.
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
10/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose a useful Markdown representation through negotiation or an explicit alternate URL.
Result
Markdown negotiation is missing or incomplete.
Validation steps
Markdown representation
No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.
Same-URL negotiation
Same-URL Accept: text/markdown did not return a valid Markdown representation.
Markdown format validation
Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.
Advertised Markdown alternate
No Link or HTML rel=alternate text/markdown URL was advertised.
Conventional .md mirror
Conventional .md mirror candidates did not return valid Markdown.
Evidence log5 steps · 15 lines
Markdown representation [fail]! No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.INFOMarkdown representationFAILCheck usable Markdown representation was selected actual={"source":"negotiated","url":"https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":4678,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":853,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<!-- Start cookieyes banner -->\n<script id=\"cookieyes\" type=\"text/javascript\" src=\"https://cdn-cookieyes.com/client_data/e71bc53f1cb88666d160c1e2/script.js\"></script>\n<!-- End cookieyes banner -->\n<me","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":4678,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":853,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<!-- Start cookieyes banner -->\n<script id=\"cookieyes\" type=\"text/javascript\" src=\"https://cdn-cookieyes.com/client_data/e71bc53f1cb88666d160c1e2/script.js\"></script>\n<!-- End cookieyes banner -->\n<me","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} candidatesChecked=2FAILMarkdown representation failed issue="No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks."Same-URL negotiation [fail]! Same-URL Accept: text/markdown did not return a valid Markdown representation.INFOSame-URL negotiationFAILCheck negotiated Markdown response actual={"statusCode":200,"mediaType":"text/html","vary":"Accept-Encoding"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com" statusCode=200 mediaType="text/html" vary="Accept-Encoding"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":4678,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=4678 headingCount=0FAILMarkdown format validation failed issue="Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."Advertised Markdown alternate [warning]! No Link or HTML rel=alternate text/markdown URL was advertised.INFOAdvertised Markdown alternateWARNCheck advertised Markdown alternate candidates actual=0 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=[] candidateCount=0WARNAdvertised Markdown alternate has a warning issue="No Link or HTML rel=alternate text/markdown URL was advertised."Conventional .md mirror [fail]! Conventional .md mirror candidates did not return valid Markdown.INFOConventional .md mirrorFAILCheck conventional Markdown mirror candidates actual=1 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://www.hugedomains.com/domain_profile.cfm.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate metadata shape".
15 Fail
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate metadata shape".
Needs attention
OAuth Protected Resource
Issue
Response is not valid JSON.
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
55/100
Status
fail
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 failed at "Validate metadata shape".
Validation steps
Validate metadata shape
Response is not valid JSON.
Validate resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
Validate authorization servers
authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.
Validate protected resource challenge
No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.
Evidence log4 steps · 23 lines
Validate metadata shape [fail]! Response is not valid JSON.INFOValidate metadata shapeINFOParsing and validating RFC 9728 protected-resource metadata valid=false compatibleContentType=false issue="Response is not valid JSON." warningsCount=0 resourceIssuesCount=0 authorizationServersCount=0 authorizationServerIssuesCount=0 scopesSupportedCount=0 bearerMethodsSupportedCount=0 optionalFieldIssuesCount=0FAILCheck metadata resource field is present actual="missing" expected="absolute protected resource identifier"PASSCheck required metadata field failures actual=0 expected=0 missing=[]PASSCheck protected-resource metadata is browser-readable and complete for OAuth clients actual="no client-usage warnings" expected="no CORS, authorization-server, or compatibility warnings" warnings=[]FAILValidate metadata shape failed issue="Response is not valid JSON."Validate resource identity [fail]! Protected resource metadata `resource` did not match the resource identifier used to retrieve it.INFOValidate resource identityINFOComparing metadata resource identifier with the candidate resource expectedResource="https://www.hugedomains.com" candidatePresent=trueFAILCheck protected resource identity matches expected="https://www.hugedomains.com"FAILValidate resource identity failed issue="Protected resource metadata `resource` did not match the resource identifier used to retrieve it."Validate authorization servers [warning]! authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.INFOValidate authorization serversINFOValidating advertised authorization server issuer URLs authorizationServerCount=0PASSCheck authorization server count actual=0 expected="> 0 when required"PASSCheck authorization server URL issue count actual=0 expected=0 issues=[]WARNValidate authorization servers completed with warnings issue="authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery."Validate protected resource challenge [warning]! No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.INFOValidate protected resource challengeINFOProbing protected routes for WWW-Authenticate resource_metadata linkage checkedCount=4INFOChecked protected route challenge url="https://www.hugedomains.com/api/scans" statusCode=403 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.hugedomains.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.hugedomains.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.hugedomains.com/api/admin/scans" statusCode=403 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.hugedomains.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.hugedomains.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.hugedomains.com/api/admin/summary" statusCode=403 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.hugedomains.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.hugedomains.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.hugedomains.com/mcp" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.hugedomains.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.hugedomains.com" resourceMatches=true scopePresent=falseWARNCheck challenge includes resource_metadata linkage actual=4 expected="> 0 matching protected route challenges"WARNValidate protected resource challenge completed with warnings issue="No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven."
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
14 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
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
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=0Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy failed at "Find Referrer-Policy header".
13 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy failed at "Find Referrer-Policy header".
Needs attention
Referrer-Policy
Issue
Referrer-Policy header is missing.
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
33/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
Find Referrer-Policy header
Referrer-Policy header is missing.
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=56 sameOriginCount=8 htmlDocumentCount=5WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":5,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","referrerPolicy":null,"classification":"invalid"},{"url":"https://www.hugedomains.com/rjs/gen-hdc.cfm?s=https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com&r=","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","referrerPolicy":null,"classification":"invalid"},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","referrerPolicy":null,"classification":"invalid"},{"url":"https://www.hugedomains.com/rjs/hdv3-rjs/hurry-cart.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","referrerPolicy":null,"classification":"invalid"},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","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 UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card has a validation warning at "Discover A2A Agent Card".
13 Warning
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card has a validation warning at "Discover A2A Agent Card".
Needs attention
A2A Agent Card
Issue
No A2A Agent Card was found at the current, legacy, or fallback discovery paths.
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
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=403 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=403 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=403 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=403 contentType="text/html; charset=UTF-8"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
Agent Skills index
Agent Skills index has a validation warning at "Discover Agent Skills index".
13 Warning
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index has a validation warning at "Discover Agent Skills index".
Needs attention
Agent Skills index
Issue
No Agent Skills discovery index was found at the canonical or legacy path.
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
50/100
Status
warning
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 has a validation warning at "Discover Agent Skills index".
Validation steps
Discover Agent Skills index
No Agent Skills discovery index was found at the canonical or legacy path.
Evidence log1 step · 5 lines
Discover Agent Skills index [warning]! No Agent Skills discovery index was found at the canonical or legacy path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://www.hugedomains.com/.well-known/agent-skills/index.json" statusCode=403WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://www.hugedomains.com/.well-known/skills/index.json" statusCode=403WARNNo Agent Skills discovery index was found at the canonical or legacy path.Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json has a validation warning at "Discover agents.json".
13 Warning
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json has a validation warning at "Discover agents.json".
Needs attention
agents.json
Issue
No Wildcard-style agents.json file was found.
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
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=403 contentType="text/html; charset=UTF-8"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=403 contentType="text/html; charset=UTF-8"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
13 Warning
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID HTTPS/SVCB records were found under _agents.
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
50/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
Query DNS-AID records
No DNS-AID HTTPS/SVCB records were found under _agents.
Check DNSSEC authentication evidence
DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
Evidence log2 steps · 24 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="www.hugedomains.com" labels=["_index._agents.www.hugedomains.com","_a2a._agents.www.hugedomains.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.www.hugedomains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.hugedomains.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.hugedomains.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.www.hugedomains.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.hugedomains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.hugedomains.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.hugedomains.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.www.hugedomains.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.hugedomains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.hugedomains.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.hugedomains.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.hugedomains.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.hugedomains.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.hugedomains.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.hugedomains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.hugedomains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="www.hugedomains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="hugedomains.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
12 Fail
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
Needs attention
ai.txt policy
Issue
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Why it matters
ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.
Check name
ai.txt policy
Score
38/100
Status
fail
Category
Bot Access Control
Maturity
Emerging recommendation
Goal
Publish an advisory human-readable AI usage policy only when the site intentionally needs one.
Result
ai.txt policy failed at "Validate transport".
Validation steps
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
Validate policy content
ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
Evidence log3 steps · 14 lines
Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html" length=262 lineCount=1FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="unknown-text" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
12 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
Needs attention
Content-Security-Policy
Issue
Applicable HTML response is missing an enforcing Content-Security-Policy header.
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
40/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 "Find enforcing CSP delivery".
Validation steps
Find enforcing CSP delivery
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
12 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
Needs attention
GEO: Citable passages
Issue
No evidence-backed, citation-length explanatory paragraph was found.
Details
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.
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate X-Frame-Options".
11 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate X-Frame-Options".
Needs attention
Frame protection
Issue
No valid X-Frame-Options fallback is present.
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
44/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 X-Frame-Options".
Validation steps
Validate CSP frame-ancestors
No enforcing CSP frame-ancestors directive is present.
Validate X-Frame-Options
No valid X-Frame-Options fallback is present.
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 [warning]! No enforcing CSP frame-ancestors directive is present.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=0 duplicateDirectives=[]WARNCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="No enforcing CSP frame-ancestors directive is present."WARNNo enforcing CSP frame-ancestors directive is present.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=56 sameOriginCount=8 htmlDocumentCount=5WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":5,"broadFrameAncestorsCount":0,"affected":[{"url":"https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null},{"url":"https://www.hugedomains.com/rjs/gen-hdc.cfm?s=https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com&r=","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null},{"url":"https://www.hugedomains.com/rjs/hdv3-rjs/hurry-cart.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8","contentSecurityPolicy":null,"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.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 33/100 and needs a fix.
10 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 33/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate, sourceLinks.
Details
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
33/100
Status
fail
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 33/100 and needs a fix.
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
10 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
Needs attention
HSTS header
Issue
HTTPS response is missing Strict-Transport-Security.
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
50/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.
Result
HSTS header failed at "Find Strict-Transport-Security".
Validation steps
Find Strict-Transport-Security
HTTPS response is missing Strict-Transport-Security.
Evidence log1 step · 4 lines
Find Strict-Transport-Security [fail]! HTTPS response is missing Strict-Transport-Security.INFOFind Strict-Transport-SecurityINFORead Strict-Transport-Security header header="strict-transport-security" value="missing" effectiveValue=null duplicateHeaderValueCount=0FAILRequire HSTS header on HTTPS response actual="missing" expected="present" issue="HTTPS response is missing Strict-Transport-Security."FAILHTTPS response is missing Strict-Transport-Security.AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
10 Warning
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
Needs attention
Content Signal
Issue
No Content-Usage or Content-Signal declarations were found.
Why it matters
Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.
Check name
Content Signal
Score
50/100
Status
warning
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.
Result
Content Signal has a validation warning at "Validate declared usage preferences".
Validation steps
Validate declared usage preferences
No Content-Usage or Content-Signal declarations were found.
Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! No Content-Usage or Content-Signal declarations were found.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=0SKIPSkipping declaration validation because no Content-Usage or Content-Signal records were declared.SKIPCompare declared records to validation requirement actual=0 expected="No validation needed when no records are declared"WARNNo Content-Usage or Content-Signal declarations were present.AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
10 Warning
AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
Needs attention
RSL license signal
Issue
No RSL declarations were found.
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
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.
10 Warning
AI DiscoverabilityBot Access ControlEmerging recommendation
TDMRep declaration
No TDMRep declaration was found.
Needs attention
TDMRep declaration
Issue
No TDMRep declaration was found at /.well-known/tdmrep.json.
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
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=403 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html; charset=UTF-8" length=5471WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options failed at "Find X-Content-Type-Options".
9 Fail
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options failed at "Find X-Content-Type-Options".
Needs attention
X-Content-Type-Options
Issue
Browser-loadable response is missing X-Content-Type-Options.
Why it matters
X-Content-Type-Options tells browsers to trust declared media types instead of sniffing content, reducing the risk that mislabeled files execute as active content.
Check name
X-Content-Type-Options
Score
57/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent browser MIME sniffing for browser-loadable responses with X-Content-Type-Options: nosniff.
Result
X-Content-Type-Options failed at "Find X-Content-Type-Options".
Validation steps
Find X-Content-Type-Options
Browser-loadable response is missing X-Content-Type-Options.
Review observed browser responses
One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
Evidence log2 steps · 8 lines
Find X-Content-Type-Options [fail]! Browser-loadable response is missing X-Content-Type-Options.INFOFind X-Content-Type-OptionsINFORead X-Content-Type-Options header header="x-content-type-options" value="missing"FAILRequire nosniff header actual="missing" expected="present" issue="Browser-loadable response is missing X-Content-Type-Options."FAILBrowser-loadable response is missing X-Content-Type-Options.Review observed browser responses [warning]! One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.INFOReview observed browser responsesINFOSample Chrome-observed same-origin resources observedResponseCount=56 sameOriginCount=8 eligibleCount=7WARNCompare observed nosniff coverage actual={"missingNosniffCount":6,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":5,"affected":[{"url":"https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8"},{"url":"https://www.hugedomains.com/rjs/hdv3-rjs/hd-js.cfm?aa=2022-10-32","status":200,"resourceType":"script","contentType":"text/javascript;charset=UTF-8"},{"url":"https://www.hugedomains.com/rjs/gen-hdc.cfm?s=https://www.hugedomains.com/domain_profile.cfm?d=circularapp.com&r=","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8"},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8"},{"url":"https://www.hugedomains.com/rjs/hdv3-rjs/hurry-cart.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8"},{"url":"https://www.hugedomains.com/rjs/favorite-domain.cfm","status":200,"resourceType":"xhr","contentType":"text/html;charset=UTF-8"}]} expected="0 missing or malformed eligible same-origin responses" issue="One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff."WARNOne or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 29/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 29/100 and needs a fix.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: author, publisher, freshnessDate, sources, sameAs.
Details
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
29/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: Evidence and trust scored 29/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 33/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 33/100 and needs a fix.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: authorOrOwner, freshnessDate, sourceLinks, entityLinks.
Details
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
33/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: Source and trust signals scored 33/100 and needs a fix.
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
7 Warning
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: skipped or empty headings; 3 controls missing accessible names; 1 image alt text quality issues.
Details
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
56/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
Heading structure
Headings skip levels or include empty heading elements.
Links
1 links use generic anchor text.
Buttons and interactive controls
3 button controls are missing accessible names.
Image text alternatives
1 image alt text issues were found.
Evidence log4 steps · 12 lines
Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":13,"emptyHeadings":0},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."Links [warning]! 1 links use generic anchor text.INFOLinksWARNCheck links evidence actual={"counts":{"links":63,"inaccessibleLinks":0,"nonCrawlableLinks":0,"genericLinks":1},"accessibleLinks":true} expected="semantic HTML evidence for this step"WARNLinks has a warning issue="1 links use generic anchor text."Buttons and interactive controls [fail]! 3 button controls are missing accessible names.INFOButtons and interactive controlsFAILCheck buttons and interactive controls evidence actual={"counts":{"buttons":12,"inaccessibleButtons":3},"accessibleButtons":false} expected="links, buttons, and form controls expose accessible names"FAILButtons and interactive controls failed issue="3 button controls are missing accessible names."Image text alternatives [warning]! 1 image alt text issues were found.INFOImage text alternativesWARNCheck image text alternatives evidence actual={"counts":{"images":17,"imagesWithAlt":17,"imageAltIssues":1},"imageAltCoverage":true} expected="semantic HTML evidence for this step"WARNImage text alternatives has a warning issue="1 image alt text issues were found."
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate Markdown discovery shape".
7 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate Markdown discovery shape".
Needs attention
llms.txt
Issue
llms.txt did not provide the minimum expected Markdown discovery shape.
Details
Why it matters
llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.
Check name
llms.txt
Score
58/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish a concise llms.txt index that helps agents discover useful public site context.
Result
llms.txt failed at "Validate Markdown discovery shape".
Validation steps
Validate Markdown discovery shape
llms.txt did not provide the minimum expected Markdown discovery shape.
Findings
- Content-Type "text/html" is not text/markdown, another Markdown type, or text/plain.
- Missing H1 title, such as '# Example Docs'.
Score llms.txt structure and usefulness
llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.
Findings
- Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
- Missing H2 sections for grouping important links.
- No Markdown-formatted links were found.
- Several links have vague labels or raw URL labels.
{ "truncated": true, "omittedCount": 1, "originalCount": 5 }
Inspect optional llms-full.txt
Passed.
Evidence log3 steps · 21 lines
Validate Markdown discovery shape [fail]! llms.txt did not provide the minimum expected Markdown discovery shape.INFOValidate Markdown discovery shapeINFOChecking response compatibility, title, content length, and usable linksFAILCheck content type is Markdown-compatible text actual="text/html" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"PASSCheck response is not HTML actual=false expected=falseFAILCheck H1 title is present actual=false expected=truePASSCheck minimum text length actual=261 expected=">= 160"PASSCheck at least one usable public link actual=2 expected="> 0" linkCount=2FAILMarkdown discovery shape validation failedScore llms.txt structure and usefulness [warning]! llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsWARNCheck blockquote summary is present actual=false expected=trueWARNCheck H2 section count actual=0 expected="> 0"WARNCheck Markdown-formatted links actual=0 expected="> 0"PASSCheck unsafe/private link count actual=0 expected=0WARNllms.txt structure-quality validation completed with warnings reason="llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://www.hugedomains.com/llms-full.txt"PASS/llms-full.txt returned HTTP 2xx statusCode=200 contentType="text/html;charset=UTF-8" length=56231WARNCheck llms-full.txt content type is Markdown-compatible text actual="text/html;charset=UTF-8" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"PASSCheck llms-full.txt looks like supplemental full corpus content actual=true expected=truePASSOptional llms-full.txt inspection recorded
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 47/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 47/100 and needs a fix.
Needs attention
AEO: Question and answer structure
Issue
No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected.
Details
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
47/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: Question and answer structure scored 47/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 50/100 and needs improvement.
6 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 50/100 and needs improvement.
Needs attention
AEO: Answer-first passages
Issue
5 section(s) bury or omit a concise opening answer.
Details
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
50/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: Answer-first passages scored 50/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 50/100 and needs improvement.
6 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 50/100 and needs improvement.
Needs attention
GEO: Structured extraction
Issue
Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, FAQ or question-answer section where appropriate, typed JSON-LD structured data.
Details
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
50/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 50/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 70/100 and needs improvement.
5 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 70/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
17 image(s) are missing width/height attributes. 6 possible modal/interstitial element(s) detected.
Details
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
70/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 70/100 and needs improvement.
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
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
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
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.
Performance and AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
100 Fail
Performance and AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
Check name
Heading elements are not in a sequentially-descending order
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order)."
}SEOSEOBrowser audit
Links do not have descriptive text
100 Fail
SEOSEOBrowser audit
Links do not have descriptive text
Check name
Links do not have descriptive text
Score
0/100
Status
fail
Device
desktop
Category
SEO
Estimated savings
1 link found
Fix guidance
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).
Evidence
{
"description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).",
"displayValue": "1 link found"
}Performance and AccessibilityPerformanceBrowser audit
Image elements do not have explicit `width` and `height`
17 Warning
Performance and AccessibilityPerformanceBrowser audit
Image elements do not have explicit `width` and `height`
Check name
Image elements do not have explicit `width` and `height`
Score
50/100
Status
warning
Device
desktop
Category
Performance
Fix guidance
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)
References
https://web.dev/learn/performance/Evidence
{
"description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)"
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
17 Warning
Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
Check name
Reduce unused JavaScript
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 357 KiB
Fix guidance
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).
References
https://web.dev/learn/performance/Evidence
{
"description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
"displayValue": "Est savings of 357 KiB",
"numericValue": 0
}Performance and AccessibilityPerformanceBrowser audit
Use efficient cache lifetimes
17 Warning
Performance and AccessibilityPerformanceBrowser audit
Use efficient cache lifetimes
Check name
Use efficient cache lifetimes
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 146 KiB
Fix guidance
A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).
References
https://web.dev/learn/performance/Evidence
{
"description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).",
"displayValue": "Est savings of 146 KiB"
}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.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 51/100 | Level 3, Bot-Aware | View report | |
| 51/100 | Level 3, Bot-Aware | View report | |
| 49/100 | Level 2, Agent-Limited | View report | |
| 51/100 | Level 3, Bot-Aware | View report | |
| 56/100 | Level 3, Bot-Aware | View report | |
| 55/100 | Level 3, Bot-Aware | View report | |
| 57/100 | Level 3, Bot-Aware | Current report | |
| 55/100 | Level 3, Bot-Aware | View report | |
| 54/100 | Level 3, Bot-Aware | View report | |
| 53/100 | Level 3, Bot-Aware | View report | |
| 52/100 | Level 3, Bot-Aware | View report | |
| 52/100 | Level 3, Bot-Aware | View report |