Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 83 out of 100
- Agent Ease of Use 58 out of 100
- Security & Trust 46 out of 100
- GEO, AIO and AEO 64 out of 100
- SEO 100 out of 100
- Performance and Accessibility 97 out of 100
What AI sees of your website
PDF Generator API — Design Templates, Generate via API or No-Code
Design PDF templates visually, generate thousands via API or no-code. Free generators for invoices, certificates, and labels. SDKs for 7 languages.
Next step
Turn this report into a fix workflow
10 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 | 83 | Mostly ready | 39 | 7 | 4 | View details |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 85 | Mostly ready | 25 | 7 | 1 | View details |
| Bot Access Control | 69 | Needs work | 4 | 0 | 3 | |
| Agent Ease of Use | 58 | Needs work | 10 | 1 | 15 | View details |
| API | 82 | Mostly ready | 8 | 0 | 2 | |
| Auth | 50 | Needs work | 0 | 0 | 3 | |
| MCP | 50 | Needs work | 2 | 1 | 5 | View details |
| Skill Discovery | 50 | Needs work | 0 | 0 | 5 | |
| GEO, AIO and AEO | 64 | Needs work | 9 | 4 | 5 | View details |
| GEO Readiness | 51 | Needs work | 2 | 2 | 2 | View details |
| AIO Readiness | 89 | Mostly ready | 4 | 0 | 2 | |
| AEO Readiness | 52 | Needs work | 3 | 2 | 1 | View details |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 46 | Priority fix | 8 | 5 | 4 | View details |
| Security & Trust | 46 | Priority fix | 8 | 5 | 4 | View details |
| Performance and Accessibility | 97 | Strong | 24 | 2 | 1 | View details |
| Performance | 100 | Strong | 16 | 2 | 1 | View details |
| Accessibility | 92 | Strong | 8 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
36 items need attention
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
30 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Best candidate returned Content-Type "text/html" 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://templatefox.com/","statusCode":200,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":64145,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":936,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html><!--HI_yeyy2IVfdwQLWb8rU9--><html lang=\"en\" data-theme=\"light\" class=\"__variable_472ac2\" style=\"font-family:var(--font-inter)\"><head><meta charSet=\"utf-8\"/><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-wi","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://templatefox.com/","statusCode":200,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":64145,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":936,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html><!--HI_yeyy2IVfdwQLWb8rU9--><html lang=\"en\" data-theme=\"light\" class=\"__variable_472ac2\" style=\"font-family:var(--font-inter)\"><head><meta charSet=\"utf-8\"/><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-wi","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":""} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://templatefox.com/" statusCode=200 mediaType="text/html"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":64145,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=64145 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://templatefox.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
25 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
Needs attention
MCP Server Card
Issue
MCP Server Card is missing required fields: protocolVersion.
Details
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
fail
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 failed at "Validate server-card shape".
Validation steps
Discover MCP server card
The MCP server card was found only at a transitional or linked path.
Validate server-card shape
MCP Server Card is missing required fields: protocolVersion.
Missing required fields
- protocolVersion
Compatibility warnings
- Card uses the transitional serverInfo/protocolVersion/transport shape instead of the current remotes[] model.
Validate MCP remotes
At least one MCP remote is cross-origin and was not actively probed by this scanner.
Probe same-origin MCP endpoint
MCP remotes were discovered, but none could be safely probed by this scanner.
Evidence log4 steps · 32 lines
Discover MCP server card [warning]! The MCP server card was found only at a transitional or linked path.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]INFOTrying to fetch /.well-known/mcp-server-card url="https://templatefox.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType=nullINFOTrying to fetch /.well-known/mcp/server-card.json url="https://templatefox.com/.well-known/mcp/server-card.json" source="transitional"PASS/.well-known/mcp/server-card.json returned a successful response statusCode=200 contentType="application/json" finalUrl="https://templatefox.com/.well-known/mcp/server-card.json"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://templatefox.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType=nullINFOTrying to fetch /mcp.json url="https://templatefox.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType=nullINFOTrying to fetch /.well-known/mcp.json url="https://templatefox.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType=nullWARNCheck selected card is published at the current well-known path actual="/.well-known/mcp/server-card.json" expected="/.well-known/mcp-server-card" source="transitional" finalUrl="https://templatefox.com/.well-known/mcp/server-card.json"WARNMCP server card was discovered through a transitional or linked path path="/.well-known/mcp/server-card.json" source="transitional" reason="The MCP server card was found only at a transitional or linked path."Validate server-card shape [fail]! MCP Server Card is missing required fields: protocolVersion.INFOValidate server-card shape profile="legacy-server-card"PASSCheck response body parsed as JSON actual=true expected=truePASSCheck Content-Type is JSON-compatible actual=true expected=trueWARNCheck recognized MCP server-card profile actual="legacy-server-card" expected="sep-2127-draft" reason="Document uses the transitional serverInfo/protocolVersion/transport metadata model."FAILCheck required card fields are present actual=1 expected=0 missing=["protocolVersion"]WARNCheck MCP server-card uses the current remotes[] profile without legacy compatibility warnings actual="1 compatibility warning(s)" expected="current sep-2127-draft card shape with no legacy compatibility warnings" warnings=["Card uses the transitional serverInfo/protocolVersion/transport shape instead of the current remotes[] model."]FAILMCP server-card shape validation failed reason="MCP Server Card is missing required fields: protocolVersion."Validate MCP remotes [warning]! At least one MCP remote is cross-origin and was not actively probed by this scanner.INFOValidate MCP remotes remoteCount=1PASSCheck at least one MCP remote is declared actual=1 expected="> 0"PASSCheck invalid remote count actual=0 expected=0 invalidRemotes=[]WARNCheck same-origin remote coverage actual=0 expected=1PASSRemote #0 is syntactically usable index=0 source="transport" type="streamable-http" url="https://mcp-server-599407781746.us-central1.run.app/mcp" sameOrigin=false authRequired=false issues=[]WARNMCP remotes are valid but not all can be actively probed reason="At least one MCP remote is cross-origin and was not actively probed by this scanner."Probe same-origin MCP endpoint [warning]! MCP remotes were discovered, but none could be safely probed by this scanner.INFOProbe same-origin MCP endpoint probeCount=1INFOSelecting same-origin unauthenticated MCP remotes for a bounded initialize probeSKIPSkipped MCP endpoint probe url="https://mcp-server-599407781746.us-central1.run.app/mcp" reason="Cross-origin MCP remote was validated syntactically but not actively probed."WARNCheck successful initialize probe count actual=0 expected="> 0 when a safe same-origin unauthenticated remote exists" activeProbeCount=0 authBlocked=0WARNMCP endpoint probe could not fully confirm operability reason="MCP remotes were discovered, but none could be safely probed by this scanner."
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP has a validation warning at "Probe WebMCP operability".
25 Warning
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP has a validation warning at "Probe WebMCP operability".
Needs attention
WebMCP
Issue
No WebMCP surface was found to probe.
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
50/100
Status
warning
Category
MCP
Maturity
Emerging recommendation
Goal
Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.
Result
WebMCP has a validation warning at "Probe WebMCP operability".
Validation steps
Detect WebMCP runtime API
Expose current WebMCP tools through document.modelContext.registerTool(), or clearly document navigator.modelContext as a compatibility/polyfill profile.
Probe WebMCP operability
No WebMCP surface was found to probe.
WebMCP operability findings
- No WebMCP surface was found to probe.
- Conventional WebMCP manifest paths were checked but did not return a valid manifest.
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
No static WebMCP JSON manifest or WMCP interaction graph was found.
Validate WebMCP tool metadata quality
Use clear tool names, useful descriptions, constrained schemas, side-effect clarity, and profile-appropriate naming.
Review WebMCP security and policy signals
Remove secrets and prompt-injection text from WebMCP metadata, avoid private endpoints, and use Permissions-Policy and annotations for tool safety.
Evidence log7 steps · 32 lines
Detect WebMCP runtime API [informational]INFODetect WebMCP runtime API status="informational"INFOProbe rendered browser for WebMCP runtime objects SKIPCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"INFOWebMCP evidence was recorded for context. status="informational"Probe WebMCP operability [warning]! No WebMCP surface was found to probe.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="No WebMCP surface was found to probe."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."WARNNo WebMCP surface was found to probe.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://templatefox.com/.well-known/webmcp.json" statusCode=404 contentType=nullINFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://templatefox.com/webmcp.json" statusCode=404 contentType=nullWARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"
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=1 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":404,"contentType":null,"length":0},{"path":"/.well-known/oauth-authorization-server","statusCode":404,"contentType":null,"length":0}]WARNDetect OAuth/OIDC applicability completed with warnings issue="Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected."Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".
17 Warning
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".
Needs attention
OAuth Protected Resource
Issue
Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.
Why it matters
Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.
Check name
OAuth Protected Resource
Score
50/100
Status
warning
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.
Result
OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".
Validation steps
Detect protected-resource applicability
Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.
Evidence log1 step · 4 lines
Detect protected-resource applicability [warning]! Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.INFODetect protected-resource applicabilityINFOInspecting auth headers, MCP/OAuth claims, and protected-resource hints applies=false requiresAuthorizationServers=false signalsCount=0 genericAuthSignalsCount=1 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://templatefox.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://templatefox.com","statusCode":404,"contentType":null,"length":0}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
17 Warning
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.
17 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=404 expected="2xx with JSON array when origin-level TDMRep is published" contentType=null length=0WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery has a validation warning at "Discover OpenAPI document".
17 Warning
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery has a validation warning at "Discover OpenAPI document".
Needs attention
OpenAPI discovery
Issue
The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.
Why it matters
OpenAPI documents let agents understand operations, schemas, authentication, servers, and request/response formats before calling an API.
Check name
OpenAPI discovery
Score
67/100
Status
warning
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.
Result
OpenAPI discovery has a validation warning at "Discover OpenAPI document".
Validation steps
Discover OpenAPI document
The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.
Evidence log1 step · 16 lines
Discover OpenAPI document [warning]! The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.INFODiscover OpenAPI document status="warning"INFOBuild OpenAPI candidate list conventionalPaths=19 candidateCount=19 sources={"conventional-path":19}INFOFetch OpenAPI candidate path="/openapi.json" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/openapi.yaml" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/swagger.json" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/swagger.yaml" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/api/openapi.json" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/api/openapi.yaml" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/api/swagger.json" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/api/swagger.yaml" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/docs/openapi.json" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/docs/openapi.yaml" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/api-docs" source="conventional-path" statusCode=404 contentType=nullINFOFetch OpenAPI candidate path="/v3/api-docs" source="conventional-path" statusCode=404 contentType=nullWARNSelect a usable OpenAPI candidate actual="none" expected="same-origin candidate with a parseable OpenAPI or Swagger document"WARNThe site appears to publish or document a public API, but no OpenAPI or Swagger document was found.AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Score llms.txt structure and usefulness".
16 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Score llms.txt structure and usefulness".
Needs attention
llms.txt
Issue
llms.txt includes unsafe or private links that should not be advertised to agents.
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
53/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 "Score llms.txt structure and usefulness".
Validation steps
Score llms.txt structure and usefulness
llms.txt includes unsafe or private links that should not be advertised to agents.
Findings
- 1 links point to private, internal, credentialed, or non-HTTP(S) targets.
Probe sampled linked resources
Most sampled llms.txt links were broken or none returned agent-readable content.
Findings
- 13/25 probed links were broken or unreachable.
- 13/25 probed links did not look agent-readable.
Inspect optional llms-full.txt
Passed.
Evidence log3 steps · 19 lines
Score llms.txt structure and usefulness [fail]! llms.txt includes unsafe or private links that should not be advertised to agents.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsPASSCheck blockquote summary is present actual=true expected=truePASSCheck H2 section count actual=11 expected="> 0"PASSCheck Markdown-formatted links actual=23 expected="> 0"FAILCheck unsafe/private link count actual=1 expected=0FAILllms.txt structure-quality validation failed reason="llms.txt includes unsafe or private links that should not be advertised to agents."Probe sampled linked resources [fail]! Most sampled llms.txt links were broken or none returned agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=25PASSCheck probed links were attempted actual=25 expected="> 0"FAILCheck broken probed link count actual=13 expected=0PASSCheck agent-readable probed links actual=12 expected="> 0"FAILLinked resource probe validation failed reason="Most sampled llms.txt links were broken or none returned agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://templatefox.com/llms-full.txt"PASS/llms-full.txt returned HTTP 2xx statusCode=200 contentType="text/plain" length=13633PASSCheck llms-full.txt content type is Markdown-compatible text actual="text/plain" 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
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=404 contentType=nullWARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType=nullWARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType=nullWARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType=nullWARNNo 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://templatefox.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://templatefox.com/.well-known/skills/index.json" statusCode=404WARNNo 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=404 contentType=nullWARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType=nullWARNNo 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 · 23 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="templatefox.com" labels=["_index._agents.templatefox.com","_a2a._agents.templatefox.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.templatefox.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.templatefox.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.templatefox.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.templatefox.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.templatefox.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.templatefox.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.templatefox.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.templatefox.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.templatefox.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.templatefox.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.templatefox.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.templatefox.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.templatefox.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.templatefox.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.templatefox.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.templatefox.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="templatefox.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
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.Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy failed at "Find Referrer-Policy header".
12 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
40/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site with an explicit Referrer-Policy header.
Result
Referrer-Policy failed at "Find Referrer-Policy header".
Validation steps
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=41 sameOriginCount=36 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://templatefox.com/","status":200,"resourceType":"document","contentType":"text/html","referrerPolicy":null,"classification":"invalid"}]} expected="0 missing, unsafe, invalid, or weak same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy."WARNOne or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
12 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
Needs attention
AEO: Answer-first passages
Issue
19 section(s) bury or omit a concise opening answer. No direct definition pattern was 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: Answer-first passages
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Answer-first passages scored 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=41 sameOriginCount=36 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://templatefox.com/","status":200,"resourceType":"document","contentType":"text/html","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.
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.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=41 sameOriginCount=36 eligibleCount=36WARNCompare observed nosniff coverage actual={"missingNosniffCount":36,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":32,"affected":[{"url":"https://templatefox.com/","status":200,"resourceType":"document","contentType":"text/html"},{"url":"https://templatefox.com/_next/static/media/icon-200.67fd2c4d.webp","status":200,"resourceType":"image","contentType":"image/webp"},{"url":"https://templatefox.com/_next/static/media/e4af272ccee01ff0-s.p.woff2","status":200,"resourceType":"font","contentType":"font/woff2"},{"url":"https://templatefox.com/_next/static/chunks/6619-0b4e298f5c44ef82.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/2619-024c323f8ca0f6aa.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/2521-390587e8db4ea7e0.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/webpack-87764a41c20d0b23.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/7704-87b61d994d79d34b.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/4bd1b696-100b9d70ed4e49c1.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/5707-191565f1b177e10d.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/107-bb32fe647a609fa0.js","status":200,"resourceType":"script","contentType":"text/javascript"},{"url":"https://templatefox.com/_next/static/chunks/8936-05d7ceb5b48f48b0.js","status":200,"resourceType":"script","contentType":"text/javascript"}]} 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.
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
8 Warning
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
Needs attention
Content Signal
Issue
Declared content usage preferences are valid but partial or include unrecognized extension terms.
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
75/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
Declared content usage preferences are valid but partial or include unrecognized extension terms.
Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! Declared content usage preferences are valid but partial or include unrecognized extension terms.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=1INFORecognized declaration formats formats=["legacy-content-signal"] sources=["robots.txt"]WARNCompare valid declarations to declared records actual=1 expected=">= 1 valid declaration with recognized preference terms" invalidRecords=[] warningRecords=[{"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"],"warnings":["Legacy Content-Signal declaration is partial; missing ai-input."]}]WARNLegacy Content-Signal declaration is partial; missing ai-input. record={"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"]}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 48/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 48/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. No list or table answer format was 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
48/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 48/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI retrieval access
GEO: AI retrieval access scored 35/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI retrieval access
GEO: AI retrieval access scored 35/100 and needs a fix.
Needs attention
GEO: AI retrieval access
Issue
Relevant AI retrieval crawler(s) appear blocked for this URL: ClaudeBot.
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: AI retrieval access
Score
35/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: AI retrieval access scored 35/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 35/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 35/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
35/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 35/100 and needs a fix.
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
5 Warning
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: 1 links missing accessible names.
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
84/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
Links
1 links are missing accessible names.
Evidence log1 step · 3 lines
Links [fail]! 1 links are missing accessible names.INFOLinksFAILCheck links evidence actual={"counts":{"links":101,"inaccessibleLinks":1,"nonCrawlableLinks":0,"genericLinks":0},"accessibleLinks":false} expected="semantic HTML evidence for this step"FAILLinks failed issue="1 links are missing accessible names."GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 50/100 and needs improvement.
4 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: summary or key takeaways, lists for grouped facts or steps, FAQ or question-answer section where appropriate, direct definition sentence.
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 80/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 80/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
16 image(s) are missing width/height attributes.
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
80/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 80/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 75/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 75/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
No direct definition sentence was 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: Entity and definition clarity
Score
75/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: Entity and definition clarity scored 75/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Structured data consistency
AIO: Structured data consistency scored 85/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Structured data consistency
AIO: Structured data consistency scored 85/100 and needs improvement.
Needs attention
AIO: Structured data consistency
Issue
2 structured-data value(s) were not found in visible page text.
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: Structured data consistency
Score
85/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: Structured data consistency scored 85/100 and needs improvement.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog has a validation warning at "Check API catalog HEAD Link header".
2 Warning
Agent Ease of UseAPIEstablished
API Catalog
API Catalog has a validation warning at "Check API catalog HEAD Link header".
Needs attention
API Catalog
Issue
HEAD /.well-known/api-catalog did not expose a Link header with rel="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
96/100
Status
warning
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 has a validation warning at "Check API catalog HEAD Link header".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
Evidence log1 step · 4 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\""WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 83/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 83/100 and needs improvement.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: sourceLinks.
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
83/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Source and trust signals scored 83/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 AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
100 Fail
Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
Check name
Browser errors were logged to the console
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Fix guidance
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)
Evidence
{
"description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}Performance and AccessibilityPerformanceBrowser audit
Touch targets do not have sufficient size or spacing.
33 Fail
Performance and AccessibilityPerformanceBrowser audit
Touch targets do not have sufficient size or spacing.
Check name
Touch targets do not have sufficient size or spacing.
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size).
References
https://web.dev/learn/performance/Evidence
{
"description": "Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size)."
}Performance and AccessibilityPerformanceBrowser audit
Use efficient cache lifetimes
33 Fail
Performance and AccessibilityPerformanceBrowser audit
Use efficient cache lifetimes
Check name
Use efficient cache lifetimes
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 5 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 5 KiB"
}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 123 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 123 KiB",
"numericValue": 0
}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 |
|---|---|---|---|
| 73/100 | Level 3, Bot-Aware | Current report |