Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 70 out of 100
- Agent Ease of Use 61 out of 100
- Security & Trust 69 out of 100
- GEO, AIO and AEO 54 out of 100
- SEO 92 out of 100
- Performance and Accessibility 62 out of 100
What AI sees of your website
Geekflare Docs - Geekflare
No page metadata or readable excerpt was captured.
Next step
Turn this report into a fix workflow
13 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 | 70 | Needs work | 34 | 10 | 6 | View details |
| Discoverability | 82 | Mostly ready | 9 | 1 | 0 | View details |
| Content Readiness | 72 | Needs work | 22 | 8 | 4 | View details |
| Bot Access Control | 58 | Needs work | 3 | 1 | 2 | View details |
| Agent Ease of Use | 61 | Needs work | 23 | 6 | 14 | View details |
| API | 67 | Needs work | 2 | 0 | 2 | |
| Auth | 68 | Needs work | 10 | 1 | 5 | View details |
| MCP | 45 | Priority fix | 2 | 2 | 4 | View details |
| Skill Discovery | 63 | Needs work | 9 | 3 | 3 | View details |
| GEO, AIO and AEO | 54 | Needs work | 6 | 3 | 9 | View details |
| GEO Readiness | 43 | Priority fix | 1 | 1 | 4 | View details |
| AIO Readiness | 85 | Mostly ready | 4 | 0 | 2 | |
| AEO Readiness | 34 | Priority fix | 1 | 2 | 3 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| Security & Trust | 69 | Needs work | 17 | 4 | 5 | View details |
| Security & Trust | 69 | Needs work | 17 | 4 | 5 | View details |
| Performance and Accessibility | 62 | Needs work | 20 | 4 | 1 | View details |
| Performance | 47 | Priority fix | 13 | 3 | 1 | View details |
| Accessibility | 89 | Mostly ready | 7 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
44 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Fetch same-origin Link header targets".
55 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Fetch same-origin Link header targets".
Needs attention
Link headers
Issue
Link header target /.well-known/api-catalog (api-catalog) returned HTTP 404 instead of a 2xx/3xx response.
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
45/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Fetch same-origin Link header targets".
Validation steps
Fetch same-origin Link header targets
Link header target /.well-known/api-catalog (api-catalog) returned HTTP 404 instead of a 2xx/3xx response.
Evidence log1 step · 5 lines
Fetch same-origin Link header targets [fail]! Link header target /.well-known/api-catalog (api-catalog) returned HTTP 404 instead of a 2xx/3xx response.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILLink target failed reachability or media-type validation rel="api-catalog" url="/.well-known/api-catalog" statusCode=404 contentType="text/plain;charset=UTF-8" typeMatches=trueFAILCompare same-origin Link target failures actual=1 expected=0FAILLink header target /.well-known/api-catalog (api-catalog) returned HTTP 404 instead of a 2xx/3xx response.Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
30 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, transport or transports.
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
40/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, transport or transports.
Missing required fields
- protocolVersion
- transport or transports
Compatibility warnings
- Card uses the transitional serverInfo/protocolVersion/transport shape instead of the current remotes[] model.
- Static tools/resources/prompts are present; MCP primitives should normally be listed at runtime after connection.
Validate MCP remotes
No usable MCP remote transport was declared.
Probe same-origin MCP endpoint
No MCP remote endpoint could be probed.
Evidence log4 steps · 30 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=["/.well-known/mcp/server-card.json"]INFOTrying to fetch /.well-known/mcp-server-card url="https://docs.geekflare.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://docs.geekflare.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://docs.geekflare.com/.well-known/mcp/server-card.json"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://docs.geekflare.com/.well-known/mcp/server-cards.json" source="transitional"PASS/.well-known/mcp/server-cards.json returned a successful response statusCode=200 contentType="application/json" finalUrl="https://docs.geekflare.com/.well-known/mcp/server-cards.json"INFOTrying to fetch /mcp.json url="https://docs.geekflare.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/plain;charset=UTF-8"INFOTrying to fetch /.well-known/mcp.json url="https://docs.geekflare.com/.well-known/mcp.json" source="transitional"PASS/.well-known/mcp.json returned a successful response statusCode=200 contentType="application/json" finalUrl="https://docs.geekflare.com/.well-known/mcp.json"WARNCheck selected card is published at the current well-known path actual="/.well-known/mcp/server-card.json" expected="/.well-known/mcp-server-card" source="transitional" finalUrl="https://docs.geekflare.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, transport or transports.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=2 expected=0 missing=["protocolVersion","transport or transports"]WARNCheck MCP server-card uses the current remotes[] profile without legacy compatibility warnings actual="2 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.","Static tools/resources/prompts are present; MCP primitives should normally be listed at runtime after connection."]FAILMCP server-card shape validation failed reason="MCP Server Card is missing required fields: protocolVersion, transport or transports."Validate MCP remotes [fail]! No usable MCP remote transport was declared.INFOValidate MCP remotes remoteCount=0FAILCheck at least one MCP remote is declared actual=0 expected="> 0"PASSCheck invalid remote count actual=0 expected=0 invalidRemotes=[]PASSCheck same-origin remote coverage actual=0 expected=0FAILMCP remote validation failed reason="No usable MCP remote transport was declared."Probe same-origin MCP endpoint [warning]! No MCP remote endpoint could be probed.INFOProbe same-origin MCP endpoint probeCount=0INFOSelecting same-origin unauthenticated MCP remotes for a bounded initialize probeWARNCheck 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="No MCP remote endpoint could be probed."
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://docs.geekflare.com/.well-known/webmcp.json" statusCode=404 contentType="text/plain;charset=UTF-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://docs.geekflare.com/webmcp.json" statusCode=404 contentType="text/plain;charset=UTF-8"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
23 Fail
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=0AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
18 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Same-URL Markdown negotiation is missing Vary: Accept; current Vary header is "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding".
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 appears to expose MDX/JSX source rather than rendered agent-facing Markdown.
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://docs.geekflare.com/","statusCode":200,"contentType":"text/markdown; charset=utf-8","mediaType":"text/markdown","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding","requireVaryAccept":true,"contentTypeStatus":"pass","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":true,"headingCount":1,"wordCount":304,"features":{"markdownLinks":2,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":0,"jsxOrMdxSignals":3},"issues":["mdx-jsx-source-leakage"],"excerpt":"> ## Documentation Index\n> Fetch the complete documentation index at: https://docs.geekflare.com/llms.txt\n> Use this file to discover all available pages before exploring further.\n\n# Geekflare Docs\n\nYour central docs for [Geekflare AI](http","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://docs.geekflare.com/","statusCode":200,"contentType":"text/markdown; charset=utf-8","mediaType":"text/markdown","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding","requireVaryAccept":true,"contentTypeStatus":"pass","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":true,"headingCount":1,"wordCount":304,"features":{"markdownLinks":2,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":0,"jsxOrMdxSignals":3},"issues":["mdx-jsx-source-leakage"],"excerpt":"> ## Documentation Index\n> Fetch the complete documentation index at: https://docs.geekflare.com/llms.txt\n> Use this file to discover all available pages before exploring further.\n\n# Geekflare Docs\n\nYour central docs for [Geekflare AI](http","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} 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/markdown","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://docs.geekflare.com/" statusCode=200 mediaType="text/markdown" vary="rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, 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 appears to expose MDX/JSX source rather than rendered agent-facing Markdown.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":304,"headingCount":1,"dialect":"mdx-like"} expected="valid Markdown with substantive text and headings" valid=false dialect="mdx-like" wordCount=304 headingCount=1FAILMarkdown format validation failed issue="Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."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://docs.geekflare.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."
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.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="text/plain;charset=UTF-8" length=15WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. Agent Ease of UseAPIEstablished
API Catalog
API Catalog has a validation warning at "Fetch API catalog".
17 Warning
Agent Ease of UseAPIEstablished
API Catalog
API Catalog has a validation warning at "Fetch API catalog".
Needs attention
API Catalog
Issue
This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.
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
67/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 "Fetch API catalog".
Validation steps
Fetch API catalog
This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.
Evidence log1 step · 4 lines
Fetch API catalog [warning]! This origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found.INFOFetch API catalogINFOFetch /.well-known/api-catalog requestedUrl="https://docs.geekflare.com/.well-known/api-catalog"WARNCompare API catalog HTTP status actual=404 expected="2xx/3xx"WARNThis origin appears to publish or claim public APIs, but no RFC 9727 API catalog was found. status="warning"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="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.json" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.json" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.json" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/docs/openapi.json" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/docs/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/plain;charset=UTF-8"INFOFetch OpenAPI candidate path="/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/v3/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"WARNSelect 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.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="text/plain;charset=UTF-8"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/plain;charset=UTF-8"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is partially implemented.
12 Warning
AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is partially implemented.
Needs attention
Organization / WebSite schema
Issue
No Organization or Organization subtype was found in Schema.org structured data. 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
38/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Identify the site owner and website entity in structured data.
Result
Organization / WebSite schema is partially implemented.
Validation steps
Organization entity
No Organization or Organization subtype was found in Schema.org structured data.
Identity fields
Missing identity field(s): Organization.name, Organization.url, WebSite.url.
WebSite publisher linkage
WebSite.publisher is missing.
Organization trust fields
Organization schema is missing logo and sameAs or public contact evidence.
Evidence log4 steps · 19 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 missingIdentity fields [warning]! Missing identity field(s): Organization.name, Organization.url, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields websiteFormat="json-ld"WARNCheck required identity fields actual=1 expected=4 missing=["Organization.name","Organization.url","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":true,"value":"WebSite","format":"json-ld"},{"name":"WebSite.@id","present":false,"format":"json-ld"},{"name":"WebSite.name","present":true,"value":"Geekflare","format":"json-ld"},{"name":"WebSite.url","present":false,"format":"json-ld"},{"name":"WebSite.publisher.@id","present":false,"format":"json-ld"},{"name":"WebSite.publisher.name","present":false,"format":"json-ld"},{"name":"WebSite.publisher.url","present":false,"format":"json-ld"}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":false,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["Organization.name","Organization.url","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity websiteFormat="json-ld"FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={"name":"Geekflare"} 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
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=75 sameOriginCount=68 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://docs.geekflare.com/","status":200,"resourceType":"document","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 failed at "Validate version-specific card shape".
11 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate version-specific card shape".
Needs attention
A2A Agent Card
Issue
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
Details
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
58/100
Status
fail
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 failed at "Validate version-specific card shape".
Validation steps
Validate version-specific card shape
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
Missing required fields
- description
Invalid skills
- #0 (geekflare): tags[]
Probe same-origin A2A endpoint
The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Evidence log2 steps · 9 lines
Validate version-specific card shape [fail]! A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.INFOValidate version-specific card shapeFAILCompare missing required card fields actual=["description"] expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=1 expected=0 invalidSkills=[{"index":0,"id":"geekflare","issues":["tags[]"]}]INFOReview declared endpoint interfaces interfaces=[{"url":"https://docs.geekflare.com/","protocolBinding":"HTTP+JSON","issues":[]}]FAILA2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.Probe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://docs.geekflare.com/message:send" statusCode=404FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate resource identity".
10 Fail
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate resource identity".
Needs attention
OAuth Protected Resource
Issue
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
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
70/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 resource identity".
Validation steps
Validate metadata shape
scopes_supported is omitted; clients may need additional documentation to request the right scopes.
Validate resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
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 log3 steps · 19 lines
Validate metadata shape [warning]! scopes_supported is omitted; clients may need additional documentation to request the right scopes.INFOValidate metadata shapeINFOParsing and validating RFC 9728 protected-resource metadata valid=true compatibleContentType=true warningsCount=1 resource="https://geekflare.main-kill-isr.mintlify.me" resourceIssuesCount=0 authorizationServersCount=1 authorizationServerIssuesCount=0 scopesSupportedCount=0 bearerMethodsSupportedCount=0PASSCheck metadata resource field is present actual="https://geekflare.main-kill-isr.mintlify.me" expected="absolute protected resource identifier"PASSCheck required metadata field failures actual=0 expected=0 missing=[]WARNCheck protected-resource metadata is browser-readable and complete for OAuth clients actual="1 client-usage warning(s)" expected="no CORS, authorization-server, or compatibility warnings" warnings=["scopes_supported is omitted; clients may need additional documentation to request the right scopes."]WARNProtected-resource metadata client-usage warning warning="scopes_supported is omitted; clients may need additional documentation to request the right scopes."WARNValidate metadata shape completed with warnings issue="scopes_supported is omitted; clients may need additional documentation to request the right scopes."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 resource="https://geekflare.main-kill-isr.mintlify.me" expectedResource="https://docs.geekflare.com" candidatePresent=trueFAILCheck protected resource identity matches actual="https://geekflare.main-kill-isr.mintlify.me" expected="https://docs.geekflare.com"FAILValidate resource identity failed issue="Protected resource metadata `resource` did not match the resource identifier used to retrieve it."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://docs.geekflare.com/api/scans" statusCode=404 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://docs.geekflare.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://docs.geekflare.com" metadataResource="https://geekflare.main-kill-isr.mintlify.me" resourceMatches=false scopePresent=falseINFOChecked protected route challenge url="https://docs.geekflare.com/api/admin/scans" statusCode=404 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://docs.geekflare.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://docs.geekflare.com" metadataResource="https://geekflare.main-kill-isr.mintlify.me" resourceMatches=false scopePresent=falseINFOChecked protected route challenge url="https://docs.geekflare.com/api/admin/summary" statusCode=404 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://docs.geekflare.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://docs.geekflare.com" metadataResource="https://geekflare.main-kill-isr.mintlify.me" resourceMatches=false scopePresent=falseINFOChecked protected route challenge url="https://docs.geekflare.com/mcp" statusCode=405 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://docs.geekflare.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://docs.geekflare.com" metadataResource="https://geekflare.main-kill-isr.mintlify.me" resourceMatches=false scopePresent=falseWARNCheck challenge includes resource_metadata linkage actual=0 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."
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
9 Warning
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
65/100
Status
warning
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
Validation steps
Query DNS-AID records
No DNS-AID HTTPS/SVCB records were found under _agents.
Evidence log1 step · 10 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="docs.geekflare.com" labels=["_index._agents.docs.geekflare.com","_a2a._agents.docs.geekflare.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.docs.geekflare.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.docs.geekflare.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.docs.geekflare.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.docs.geekflare.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.docs.geekflare.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.docs.geekflare.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=true answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.docs.geekflare.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.docs.geekflare.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.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=75 sameOriginCount=68 eligibleCount=68WARNCompare observed nosniff coverage actual={"missingNosniffCount":68,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":66,"affected":[{"url":"https://docs.geekflare.com/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/9ffc684b9a12d113.css?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"stylesheet","contentType":"text/css; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/d260340e1c30c06e.css?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"stylesheet","contentType":"text/css; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/f114e33eea8ff240.css?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"stylesheet","contentType":"text/css; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/media/83afe278b6a6bb3c.p.3a6ba036.woff2","status":200,"resourceType":"font","contentType":"font/woff2"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/ac0991e1ed3da4fb.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/cae723b407113d75.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/f486afc314643ce1.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/b55b3e3cc920a52e.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/90079180db6f14a4.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/6fd3acb5d5a9a0e5.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; charset=utf-8"},{"url":"https://docs.geekflare.com/mintlify-assets/_next/static/chunks/e7e2d9fa0f487835.js?dpl=dpl_9AoVKJdsHBcRbwHpghKf1XV7Xg2W","status":200,"resourceType":"script","contentType":"application/javascript; 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.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
8 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
CSP does not define default-src; several fetch directives may have no restrictive fallback.
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
58/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Evaluate fetch baseline".
Validation steps
Evaluate fetch baseline
CSP does not define default-src; several fetch directives may have no restrictive fallback.
Evaluate script execution
No script-src or default-src directive constrains script execution.
Review CSP reporting
CSP does not define a reporting endpoint.
Evidence log3 steps · 12 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=["object-src","worker-src"]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 50/100 and needs improvement.
8 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 50/100 and needs improvement.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: publisher, freshnessDate, policyLinks.
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
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Source and trust signals scored 50/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
7 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
5 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.
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate skill content".
6 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate skill content".
Needs attention
Agent Skills index
Issue
SKILL.md frontmatter is malformed or incomplete.
Details
Why it matters
An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.
Check name
Agent Skills index
Score
78/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.
Result
Agent Skills index failed at "Validate skill content".
Validation steps
Validate skill content
SKILL.md frontmatter is malformed or incomplete.
Skill content findings
- SKILL.md frontmatter is malformed or incomplete.
- SKILL.md frontmatter name does not match the discovery index name.
Review skill artifact security
SKILL.md references external URLs; fetched content is an additional trust boundary (https://api.geekflare.com`, https://docs.geekflare.com/api/`, https://docs.geekflare.com/ai/`, https://ai.geekflare.com`, https://chat.geekflare.com`, https://dash.geekflare.com/playground`, https://api.geekflare.com, https://example.com).
Agent Skills security findings
- SKILL.md references external URLs; fetched content is an additional trust boundary (https://api.geekflare.com`, https://docs.geekflare.com/api/`, https://docs.geekflare.com/ai/`, https://ai.geekflare.com`, https://chat.geekflare.com`, https://dash.geekflare.com/playground`, https://api.geekflare.com, https://example.com).
Evidence log2 steps · 9 lines
Validate skill content [fail]! SKILL.md frontmatter is malformed or incomplete.INFOValidate skill contentFAILCompare skill artifact content failures actual=1 expected=0 name="geekflare" type="skill-md" url="https://docs.geekflare.com/.well-known/agent-skills/geekflare/skill.md"FAILSkill content validation failure name="geekflare" failure="SKILL.md frontmatter is malformed or incomplete."WARNSkill content validation warning name="geekflare" warning="SKILL.md frontmatter name does not match the discovery index name."FAILSKILL.md frontmatter is malformed or incomplete.Review skill artifact security [warning]! SKILL.md references external URLs; fetched content is an additional trust boundary (https://api.geekflare.com`, https://docs.geekflare.com/api/`, https://docs.geekflare.com/ai/`, https://ai.geekflare.com`, https://chat.geekflare.com`, https://dash.geekflare.com/playground`, https://api.geekflare.com, https://example.com).INFOReview skill artifact securityFAILCompare security finding count actual=1 expected=0WARNAgent Skills artifact security warning finding="SKILL.md references external URLs; fetched content is an additional trust boundary (https://api.geekflare.com`, https://docs.geekflare.com/api/`, https://docs.geekflare.com/ai/`, https://ai.geekflare.com`, https://chat.geekflare.com`, https://dash.geekflare.com/playground`, https://api.geekflare.com, https://example.com)."WARNSKILL.md references external URLs; fetched content is an additional trust boundary (https://api.geekflare.com`, https://docs.geekflare.com/api/`, https://docs.geekflare.com/ai/`, https://ai.geekflare.com`, https://chat.geekflare.com`, https://dash.geekflare.com/playground`, https://api.geekflare.com, https://example.com).
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has a validation warning at "Validate metadata profile".
5 Warning
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has a validation warning at "Validate metadata profile".
Needs attention
OAuth / OIDC discovery
Issue
jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification.
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
85/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 "Validate metadata profile".
Validation steps
Validate metadata profile
jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification.
Validate JWKS when required
jwks_uri is absent; this can be valid for pure OAuth but is required for OIDC and signed-token verification.
Evidence log2 steps · 14 lines
Validate metadata profile [warning]! jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification.INFOValidate metadata profileINFOParsing and validating OAuth/OIDC metadata profile valid=true compatibleContentType=true profile="oauth-authorization-server" missingCount=0 warningsCount=4 endpointIssuesCount=0 issuer="https://geekflare.main-kill-isr.mintlify.me/mcp/oauth" authorizationEndpoint="https://geekflare.main-kill-isr.mintlify.me/mcp/oauth/authorize" tokenEndpoint="https://geekflare.main-kill-isr.mintlify.me/mcp/oauth/token"PASSCheck metadata profile was recognized actual="oauth-authorization-server" expected="oauth-authorization-server, oidc, or hybrid"PASSCheck required metadata fields are present actual=0 expected=0 missing=[]WARNCheck OAuth metadata is fully usable by browser and agent clients actual="4 client-usage warning(s)" expected="no CORS, endpoint, or compatibility warnings" warnings=["jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification.","response_modes_supported is omitted.","revocation_endpoint is omitted.","introspection_endpoint is omitted."]WARNOAuth metadata client-usage warning warning="jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification."WARNOAuth metadata client-usage warning warning="response_modes_supported is omitted."WARNOAuth metadata client-usage warning warning="revocation_endpoint is omitted."WARNOAuth metadata client-usage warning warning="introspection_endpoint is omitted."WARNValidate metadata profile completed with warnings issue="jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification."Validate JWKS when required [warning]! jwks_uri is absent; this can be valid for pure OAuth but is required for OIDC and signed-token verification.INFOValidate JWKS when requiredINFOValidating advertised JWKS signing-key document profile="oauth-authorization-server"WARNCheck valid JWK count actual=0 expected="> 0 when jwks_uri is advertised" warnings=[]WARNValidate JWKS when required completed with warnings issue="jwks_uri is absent; this can be valid for pure OAuth but is required for OIDC and signed-token verification."
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 35/100 and needs a fix.
5 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.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 43/100 and needs a fix.
4 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 43/100 and needs a fix.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: publisher, freshnessDate, sameAs, policyLinks.
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
43/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 43/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 74/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 74/100 and needs improvement.
Needs attention
AIO: Visible content clarity
Issue
Missing meta description or Open Graph description. 5 section(s) may benefit from clearer answer-first openings.
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: Visible content clarity
Score
74/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: Visible content clarity scored 74/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 50/100 and needs improvement.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: freshnessDate, policyLinks, 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
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: Source and trust signals scored 50/100 and needs improvement.
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Page-relevant schema family".
3 Fail
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Page-relevant schema family".
Needs attention
Structured data
Issue
The page has specific visible content intent, but structured data does not include a matching primary schema family.
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
83/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 "Page-relevant schema family".
Validation steps
Page-relevant schema family
The page has specific visible content intent, but structured data does not include a matching primary schema family.
Evidence log1 step · 4 lines
Page-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["software"] expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] matchingTypes=[] observedTypes=["WebSite"]FAILNo primary schema family matches the inferred page intent expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] primaryTypes=[]GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 53/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 53/100 and needs improvement.
Needs attention
AEO: Extractable visible copy
Issue
Client-rendering root signals were found with limited visible text. Visible text has few answer-oriented terms or explanatory markers.
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: Extractable visible copy
Score
53/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: Extractable visible copy scored 53/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 58/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 58/100 and needs improvement.
Needs attention
AEO: Question and answer structure
Issue
No natural question headings 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
58/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Question and answer structure scored 58/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 62/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 62/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Missing meta description or Open Graph description. 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
62/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 62/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extractable HTML
GEO: Extractable HTML scored 65/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extractable HTML
GEO: Extractable HTML scored 65/100 and needs improvement.
Needs attention
GEO: Extractable HTML
Issue
Only 122 visible words were found in the initial HTML. Initial HTML has low visible-text density.
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: Extractable HTML
Score
65/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: Extractable HTML scored 65/100 and needs improvement.
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt has a validation warning at "Score llms.txt structure and usefulness".
2 Warning
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt has a validation warning at "Score llms.txt structure and usefulness".
Needs attention
llms.txt
Issue
llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.
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
89/100
Status
warning
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish a concise llms.txt index that helps agents discover useful public site context.
Result
llms.txt has a validation warning at "Score llms.txt structure and usefulness".
Validation steps
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.
Inspect optional llms-full.txt
Passed.
Evidence log2 steps · 13 lines
Score 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=truePASSCheck H2 section count actual=3 expected="> 0"PASSCheck Markdown-formatted links actual=66 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://docs.geekflare.com/llms-full.txt"PASS/llms-full.txt returned HTTP 2xx statusCode=200 contentType="text/plain; charset=utf-8" length=227065PASSCheck llms-full.txt content type is Markdown-compatible text actual="text/plain; 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
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
2 Warning
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
Needs attention
Semantic HTML
Issue
Semantic HTML is missing or incomplete.
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
91/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
Page landmarks
The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark.
Evidence log1 step · 3 lines
Page landmarks [warning]! The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark.INFOPage landmarksWARNCheck page landmarks evidence actual={"counts":{"main":1,"roleMain":0,"nav":2,"roleNavigation":0,"header":2,"roleBanner":0,"footer":1,"pageFooter":0,"roleContentinfo":0},"main":true} expected="semantic HTML evidence for this step"WARNPage landmarks has a warning issue="The page has a main landmark but is missing a primary navigation, header/banner, or page-level footer/contentinfo landmark."GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 80/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 80/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Missing meta or Open Graph description. Title/H1 terms missing from description: geekflare, docs.
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: Entity clarity
Score
80/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: Entity clarity scored 80/100 and needs improvement.
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header has a validation warning at "Review subdomain scope".
1 Warning
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header has a validation warning at "Review subdomain scope".
Needs attention
HSTS header
Issue
HSTS is valid, but includeSubDomains is absent.
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
94/100
Status
warning
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.
Result
HSTS header has a validation warning at "Review subdomain scope".
Validation steps
Review subdomain scope
HSTS is valid, but includeSubDomains is absent.
Evidence log1 step · 4 lines
Review subdomain scope [warning]! HSTS is valid, but includeSubDomains is absent.INFOReview subdomain scopeINFOInspect subdomain enforcement scope includeSubDomains=falseWARNCompare includeSubDomains coverage actual="absent" expected="included after subdomains are HTTPS-ready" issue="HSTS is valid, but includeSubDomains is absent."WARNHSTS is valid, but includeSubDomains is absent.Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection has a validation warning at "Review CSP and XFO interaction".
1 Warning
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection has a validation warning at "Review CSP and XFO interaction".
Needs attention
Frame protection
Issue
CSP frame-ancestors and X-Frame-Options express different framing policies.
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
95/100
Status
warning
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 has a validation warning at "Review CSP and XFO interaction".
Validation steps
Review CSP and XFO interaction
CSP frame-ancestors and X-Frame-Options express different framing policies.
Evidence log1 step · 4 lines
Review CSP and XFO interaction [warning]! CSP frame-ancestors and X-Frame-Options express different framing policies.INFOReview CSP and XFO interactionINFOCompare modern CSP and legacy XFO behavior modernBrowserMechanism="csp-frame-ancestors" cspOverridesXfo=true cspMode="explicit" xfoDirective="deny"WARNCheck CSP/XFO policy alignment actual="conflict detected" expected="no conflicting framing policy" issue="CSP frame-ancestors and X-Frame-Options express different framing policies."WARNCSP frame-ancestors and X-Frame-Options express different framing policies.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 88/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 88/100 and needs improvement.
Needs attention
GEO: Structured extraction
Issue
Missing or weak extraction signals: summary or key takeaways.
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
88/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 88/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
`[aria-hidden="true"]` elements contain focusable descendents
100 Fail
Performance and AccessibilityAccessibilityBrowser audit
`[aria-hidden="true"]` elements contain focusable descendents
Check name
`[aria-hidden="true"]` elements contain focusable descendents
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements](https://dequeuniversity.com/rules/axe/4.11/aria-hidden-focus).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Focusable descendents within an `[aria-hidden=\"true\"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements](https://dequeuniversity.com/rules/axe/4.11/aria-hidden-focus)."
}SEOSEOBrowser audit
Document does not have a meta description
100 Fail
SEOSEOBrowser audit
Document does not have a meta description
Check name
Document does not have a meta description
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).
Evidence
{
"description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}Performance and AccessibilityPerformanceBrowser audit
Forced reflow
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Forced reflow
Check name
Forced reflow
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
References
https://web.dev/learn/performance/Evidence
{
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 48 KiB
Fix guidance
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
References
https://web.dev/learn/performance/Evidence
{
"description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
"displayValue": "Est savings of 48 KiB",
"numericValue": 80
}Performance and AccessibilityPerformanceBrowser audit
Use efficient cache lifetimes
13 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 16 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 16 KiB"
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
11 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
56/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "total-blocking-time",
"score": 0,
"title": "Total Blocking Time",
"displayValue": "1,970 ms",
"numericValue": 1973
},
{
"id": "speed-index",
"score": 84,
"title": "Speed Index",
"displayValue": "1.5 s",
"numericValue": 1485.6500513011342
},
{
"id": "network-rtt",
"score": 100,
"title": "Network Round Trip Times",
"displayValue": "20 ms",
"numericValue": 24.29838
},
{
"id": "interactive",
"score": 48,
"title": "Time to Interactive",
"displayValue": "4.6 s",
"numericValue": 4575.876343049564
},
{
"id": "first-contentful-paint",
"score": 100,
"title": "First Contentful Paint",
"displayValue": "0.3 s",
"numericValue": 321.00469712622225
},
{
"id": "server-response-time",
"score": 100,
"title": "Initial server response time was short",
"displayValue": "Root document took 0 ms",
"numericValue": 4
},
{
"id": "largest-contentful-paint",
"score": 16,
"title": "Largest Contentful Paint",
"displayValue": "4.1 s",
"numericValue": 4081.5266170485925
},
{
"id": "max-potential-fid",
"score": 0,
"title": "Max Potential First Input Delay",
"displayValue": "980 ms",
"numericValue": 980
}
]
}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 |
|---|---|---|---|
| 64/100 | Level 3, Bot-Aware | Current report |