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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability32%Agent Easeof Use48%Security& Trust99%GEO, AIO, AEO61%SEO92%Performance66%Accessibility100%
  • AI Discoverability 32 out of 100
  • Agent Ease of Use 48 out of 100
  • Security & Trust 99 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 92 out of 100
  • Performance 66 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

GitHub Education · GitHub favicon

GitHub Education · GitHub

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

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.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
32
Priority fix192810View details
Discoverability
20
Priority fix270View details
Content Readiness
38
Priority fix16167View details
Bot Access Control
36
Priority fix153View details
Agent Ease of Use
48
Priority fix6612View details
API
50
Needs work430View details
Auth
48
Priority fix112View details
MCP
43
Priority fix125View details
Skill Discovery
50
Needs work005
GEO, AIO and AEO
61
Needs work729View details
GEO Readiness
52
Needs work213View details
AIO Readiness
80
Mostly ready303
AEO Readiness
51
Needs work213View details
SEO
92
Strong910View details
SEO
92
Strong910View details
Security & Trust
99
Strong2802
Security & Trust
99
Strong2802
Performance
66
Needs work1681View details
Performance
66
Needs work1681View details

Prioritized recommendations

Issues ranked by score impact

49 items need attention

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Parse OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

02

Why it matters

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

Check name

OpenAPI discovery

Score

50/100

Status

fail

Category

API

Maturity

Established

Goal

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

Result

OpenAPI discovery failed at "Parse OpenAPI document".

Validation steps

  1. Parse OpenAPI document

    OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

  2. Validate OpenAPI shape

    Response is not valid JSON and does not match baseline OpenAPI YAML shape.

  3. Check machine-usable details

    Add servers, parameters, request bodies, response schemas, operation IDs, tags, examples, and security or explicit no-auth declarations where they apply.

Evidence log3 steps · 14 lines
Parse OpenAPI document [fail]! OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.INFOParse OpenAPI document status="fail"INFOParse selected document as JSON first, then YAML-like OpenAPI parsed=false format="unknown" versionFamily="missing"FAILCheck parse result actual="not parseable" expected="parseable OpenAPI 3.x or Swagger 2.0 document" compatibleContentType=falseFAILOpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.Validate OpenAPI shape [fail]! Response is not valid JSON and does not match baseline OpenAPI YAML shape.INFOValidate OpenAPI shape status="fail"INFOValidate required OpenAPI shape versionFamily="missing" pathCount=0 webhookCount=0 operationCount=0PASSCheck operations define responses actual=0 expected="every operation should define responses"FAILCheck info metadata actual={"hasInfoTitle":false,"hasInfoVersion":false} expected="info.title and info.version present"FAILOpenAPI shape issue issue="Response is not valid JSON and does not match baseline OpenAPI YAML shape."FAILResponse is not valid JSON and does not match baseline OpenAPI YAML shape.Check machine-usable details [fail]INFOCheck machine-usable details status="fail"INFOInspect machine-usable operation details hasServers=false hasSecuritySchemes=false hasExplicitNoAuth=false requestBodyOperationCount=0 parameterOperationCount=0 responseSchemaOperationCount=0 operationIdCount=0 taggedOperationCount=0 exampleOperationCount=0PASSCheck OpenAPI operations include enough detail for agents to call them safely actual="no machine-usability warnings" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"FAILOpenAPI discovery validation failed.

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

33 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

Evidence log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Validate server-card shape".

33 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

The JSON document does not match a recognized MCP server-card profile.

Details

02

Why it matters

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

Check name

MCP Server Card

Score

35/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

  1. Discover MCP server card

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

  2. Validate server-card shape

    The JSON document does not match a recognized MCP server-card profile.

    Missing required fields
    • known MCP server-card profile
    • transport or transports
  3. Validate MCP remotes

    No usable MCP remote transport was declared.

  4. Validate HTTP delivery

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

  5. Probe same-origin MCP endpoint

    No MCP remote endpoint could be probed.

Evidence log5 steps · 37 lines
Discover MCP server card [warning]! The MCP server card was found only at a transitional or linked path.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]INFOTrying to fetch /.well-known/mcp-server-card url="https://github.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/plain; charset=utf-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://github.com/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=404 contentType="application/json; charset=utf-8"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://github.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType="application/json; charset=utf-8"INFOTrying to fetch /mcp.json url="https://github.com/mcp.json" source="transitional"PASS/mcp.json returned a successful response statusCode=200 contentType="application/json; charset=utf-8" finalUrl="https://github.com/mcp.json"INFOTrying to fetch /.well-known/mcp.json url="https://github.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="application/json; charset=utf-8"WARNCheck selected card is published at the current well-known path actual="/mcp.json" expected="/.well-known/mcp-server-card" source="transitional" finalUrl="https://github.com/mcp.json"WARNMCP server card was discovered through a transitional or linked path path="/mcp.json" source="transitional" reason="The MCP server card was found only at a transitional or linked path."Validate server-card shape [fail]! The JSON document does not match a recognized MCP server-card profile.INFOValidate server-card shape profile="unknown-json"PASSCheck response body parsed as JSON actual=true expected=truePASSCheck Content-Type is JSON-compatible actual=true expected=trueFAILCheck recognized MCP server-card profile actual="unknown-json" expected="sep-2127-draft" reason="Document does not match a known MCP server-card profile."FAILCheck required card fields are present actual=2 expected=0 missing=["known MCP server-card profile","transport or transports"]PASSCheck MCP server-card uses the current remotes[] profile without legacy compatibility warnings actual="no compatibility warnings" expected="current sep-2127-draft card shape with no legacy compatibility warnings" warnings=[]FAILMCP server-card shape validation failed reason="The JSON document does not match a recognized MCP server-card profile."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."Validate HTTP delivery [warning]! CORS header Access-Control-Allow-Origin is absent.INFOValidate HTTP delivery finalUrl="https://github.com/mcp.json"PASSCheck server card returned HTTP 2xx actual=200 expected="200-299"PASSCheck card is served as JSON actual="application/json; charset=utf-8" expected="application/json or +json"PASSCheck card is served over HTTPS actual="https:" expected="https:"WARNCheck browser-readable CORS header actual="missing" expected="Access-Control-Allow-Origin present"PASSCheck cache header is present actual="max-age=0, private, must-revalidate" expected="Cache-Control present"WARNMCP server-card HTTP delivery has non-blocking issues issues=["CORS header Access-Control-Allow-Origin is absent."] reason="CORS header Access-Control-Allow-Origin is absent."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."

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap failed at "Fetch a sitemap candidate".

27 Fail

Needs attention

Sitemap

Failed check
01

Issue

No sitemap candidate returned a successful HTTP response.

02

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, update timestamps, and deeper content that may not be obvious from homepage navigation alone.

Check name

Sitemap

Score

20/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a standards-aligned sitemap or sitemap index at a discoverable URL.

Result

Sitemap failed at "Fetch a sitemap candidate".

Validation steps

  1. Fetch a sitemap candidate

    No sitemap candidate returned a successful HTTP response.

  2. Parse sitemap

    Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.

  3. Validate sitemap field quality

    No valid sitemap was available for field-quality validation.

  4. Validate URL scope

    No valid sitemap was available for URL scope validation.

Evidence log4 steps · 21 lines
Fetch a sitemap candidate [fail]! No sitemap candidate returned a successful HTTP response.INFOFetch sitemap candidateINFOTrying sitemap candidates in discovery order candidateCount=4INFOTrying to fetch /sitemap.xml url="https://github.com/sitemap.xml"FAIL/sitemap.xml did not return a successful response url="https://github.com/sitemap.xml" statusCode=406INFOTrying to fetch /sitemap.txt url="https://github.com/sitemap.txt"FAIL/sitemap.txt did not return a successful response url="https://github.com/sitemap.txt" statusCode=406INFOTrying to fetch /sitemap_index.xml url="https://github.com/sitemap_index.xml"FAIL/sitemap_index.xml did not return a successful response url="https://github.com/sitemap_index.xml" statusCode=404INFOTrying to fetch /sitemap-index.xml url="https://github.com/sitemap-index.xml"FAIL/sitemap-index.xml did not return a successful response url="https://github.com/sitemap-index.xml" statusCode=404FAILNo sitemap candidate returned HTTP 2xxParse sitemap [fail]! Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.INFOParse sitemapINFOInspecting fetched sitemap content url="https://github.com/sitemap.xml" contentType="application/xml" statusCode=406FAILCheck sitemap contains at least one URL entry or child sitemap entry actual=0 expected="> 0"PASSCheck loc values are absolute HTTP(S) URLs actual=0 expected=0 invalidLocs=[]FAILFetched content was not a valid sitemap format="unknown"Validate sitemap field quality [fail]! No valid sitemap was available for field-quality validation.INFOValidate sitemap field qualitySKIPSkipped field-quality checks because no valid sitemap was availableValidate URL scope [fail]! No valid sitemap was available for URL scope validation.INFOValidate URL scope origin="https://github.com"INFOChecking listed URLs against the scanned origin hostSKIPSkipped URL-scope checks because no valid sitemap was available

Agent Ease of UseMCPEmerging recommendation

WebMCP

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

25 Warning

Needs attention

WebMCP

Warning
01

Issue

No WebMCP surface was found to probe.

Details

02

Why it matters

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

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Detect WebMCP runtime API

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

  2. Probe WebMCP operability

    No WebMCP surface was found to probe.

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

    No W3C-style declarative WebMCP form attributes were found.

  4. Validate MCP-aware HTML annotations

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

  5. Validate static WebMCP JSON compatibility

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

  6. Validate WebMCP tool metadata quality

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

  7. Review WebMCP security and policy signals

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

Evidence log7 steps · 32 lines
Detect WebMCP runtime API [informational]INFODetect WebMCP runtime API status="informational"INFOProbe rendered browser for WebMCP runtime objects SKIPCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"INFOWebMCP evidence was recorded for context. status="informational"Probe WebMCP operability [warning]! No WebMCP surface was found to probe.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="No WebMCP surface was found to probe."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."WARNNo WebMCP surface was found to probe.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://github.com/.well-known/webmcp.json" statusCode=404 contentType="application/json; charset=utf-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://github.com/webmcp.json" statusCode=410 contentType="application/json; 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 ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Fetch /ai.txt".

20 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

/ai.txt returned HTTP 406.

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Fetch /ai.txt".

Validation steps

  1. Fetch /ai.txt

    /ai.txt returned HTTP 406.

  2. Validate transport

    ai.txt was reachable but empty.

  3. Parse ai.txt policy

    Transport validation failed before policy parsing could be trusted.

  4. Validate policy content

    ai.txt is too short to provide useful advisory policy guidance.

Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 406.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=406 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/plain" length=0FAIL/ai.txt returned HTTP 406. statusCode=406Validate transport [fail]! ai.txt was reachable but empty.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/plain" length=0 lineCount=1FAILCompare media type to preferred text/plain transport actual="text/plain" expected="text/plain preferred; readable text required"FAILai.txt was reachable but empty.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="unknown-text" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [fail]! ai.txt is too short to provide useful advisory policy guidance.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseFAILCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}FAILai.txt is too short to provide useful advisory policy guidance.

AI DiscoverabilityDiscoverabilityEstablished

robots.txt

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

20 Fail

Needs attention

robots.txt

Failed check
01

Issue

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

02

Why it matters

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

Check name

robots.txt

Score

40/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish /robots.txt with clear crawl rules.

Result

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

Validation steps

  1. Validate RFC 9309 core syntax

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

Evidence log1 step · 5 lines
Validate RFC 9309 core syntax [fail]! robots.txt was found but did not contain a valid, parseable User-agent group.INFOValidate RFC 9309 core syntaxINFOParsing robots.txt into User-agent groups and Allow/Disallow recordsPASSCheck User-agent group count actual=5 expected=">= 1 parseable group" parsedUserAgents=["bingbot","adidxbot","BingPreview","baidu","*"]FAILCheck malformed lines and orphan Allow/Disallow records actual={"invalidLines":0,"orphanRecords":59} expected={"invalidLines":0,"orphanRecords":0}FAILAllow/Disallow records appeared before any User-agent group orphanRecords=[{"directive":"disallow","value":"/*/*/pulse","line":39},{"directive":"disallow","value":"/*/*/projects","line":40},{"directive":"disallow","value":"/*/*/forks","line":41},{"directive":"disallow","value":"/*/*/issues/new","line":42},{"directive":"disallow","value":"/*/*/milestones/new","line":43}]

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

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

19 Fail

Needs attention

OAuth / OIDC discovery

Failed check
01

Issue

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

02

Why it matters

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

Check name

OAuth / OIDC discovery

Score

43/100

Status

fail

Category

Auth

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Fetch discovery metadata

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

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

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

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

17 Warning

Needs attention

Auth.md Agent Registration

Warning
01

Issue

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

02

Why it matters

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

Check name

Auth.md Agent Registration

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Warn when auth surface lacks Auth.md

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

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

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

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

17 Warning

Needs attention

OAuth Protected Resource

Warning
01

Issue

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

02

Why it matters

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

Check name

OAuth Protected Resource

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Detect protected-resource applicability

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

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

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

14 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

  4. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

14 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

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

02

Why it matters

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

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Validation steps

  1. Organization entity

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

  2. WebSite entity

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

  3. Identity fields

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

  4. WebSite publisher linkage

    WebSite.publisher is missing.

  5. Organization trust fields

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

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

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

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

14 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

02

Why it matters

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

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Classify AI crawler rules

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

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

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

13 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.

02

Why it matters

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

Check name

Markdown negotiation

Score

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

  1. Markdown representation

    No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.

  2. Same-URL negotiation

    Same-URL Accept: text/markdown did not return a valid Markdown representation.

  3. Markdown format validation

    Markdown response is missing a heading.

  4. Advertised Markdown alternate

    No Link or HTML rel=alternate text/markdown URL was advertised.

  5. 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://github.com/education","statusCode":406,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Accept-Language,Accept-Encoding, Accept, X-Requested-With","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"plain-text-like","hasHeading":false,"headingCount":0,"wordCount":0,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":0,"jsxOrMdxSignals":0},"issues":["missing-heading","thin-body","plain-text-like"],"excerpt":"","issue":"Markdown response is missing a heading."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://github.com/education","statusCode":406,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Accept-Language,Accept-Encoding, Accept, X-Requested-With","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"plain-text-like","hasHeading":false,"headingCount":0,"wordCount":0,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":0,"jsxOrMdxSignals":0},"issues":["missing-heading","thin-body","plain-text-like"],"excerpt":"","issue":"Markdown response is missing a heading."}} 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":406,"mediaType":"text/html","vary":"X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Accept-Language,Accept-Encoding, Accept, X-Requested-With"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://github.com/education" statusCode=406 mediaType="text/html" vary="X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Accept-Language,Accept-Encoding, Accept, X-Requested-With"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response is missing a heading.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":0,"headingCount":0,"dialect":"plain-text-like"} expected="valid Markdown with substantive text and headings" valid=false dialect="plain-text-like" wordCount=0 headingCount=0FAILMarkdown format validation failed issue="Markdown response is missing a heading."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://github.com/education.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

13 Warning

Needs attention

A2A Agent Card

Warning
01

Issue

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

02

Why it matters

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

Check name

A2A Agent Card

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Discover A2A Agent Card

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

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index has a validation warning at "Discover Agent Skills index".

13 Warning

Needs attention

Agent Skills index

Warning
01

Issue

No Agent Skills discovery index was found at the canonical or legacy path.

02

Why it matters

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

Check name

Agent Skills index

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

Agent Skills index has a validation warning at "Discover Agent Skills index".

Validation steps

  1. Discover Agent Skills index

    No Agent Skills discovery index was found at the canonical or legacy path.

Evidence log1 step · 5 lines
Discover Agent Skills index [warning]! No Agent Skills discovery index was found at the canonical or legacy path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://github.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://github.com/.well-known/skills/index.json" statusCode=404WARNNo Agent Skills discovery index was found at the canonical or legacy path.

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

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

13 Warning

Needs attention

agents.json

Warning
01

Issue

No Wildcard-style agents.json file was found.

02

Why it matters

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

Check name

agents.json

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Discover agents.json

    No Wildcard-style agents.json file was found.

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

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

13 Warning

Needs attention

DNS-AID Agent Discovery

Warning
01

Issue

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

02

Why it matters

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

Check name

DNS-AID Agent Discovery

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Query DNS-AID records

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

  2. Check DNSSEC authentication evidence

    DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Evidence log2 steps · 23 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="github.com" labels=["_index._agents.github.com","_a2a._agents.github.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.github.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.github.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.github.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.github.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.github.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.github.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.github.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.github.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.github.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.github.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.github.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.github.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.github.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.github.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.github.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.github.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="github.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal has a validation warning at "Validate declared usage preferences".

10 Warning

Needs attention

Content Signal

Warning
01

Issue

No Content-Usage or Content-Signal declarations were found.

02

Why it matters

Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.

Check name

Content Signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.

Result

Content Signal has a validation warning at "Validate declared usage preferences".

Validation steps

  1. Validate declared usage preferences

    No Content-Usage or Content-Signal declarations were found.

Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! No Content-Usage or Content-Signal declarations were found.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=0SKIPSkipping declaration validation because no Content-Usage or Content-Signal records were declared.SKIPCompare declared records to validation requirement actual=0 expected="No validation needed when no records are declared"WARNNo Content-Usage or Content-Signal declarations were present.

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

10 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

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

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

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

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

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

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

10 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

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

02

Why it matters

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

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

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

Result

No TDMRep declaration was found.

Validation steps

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

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

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

9 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

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

Details

02

Why it matters

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

Check name

GEO: Citable passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

7 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: invalid h1 structure (visible h1 count 4); 1 form controls missing labels; 2 ARIA/native semantic issues.

Details

02

Why it matters

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

Check name

Semantic HTML

Score

54/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is partially implemented.

Validation steps

  1. Heading structure

    Expected one meaningful visible h1; found 4.

  2. Links

    1 links use generic anchor text.

  3. Form labels and autocomplete

    1 user-fillable form controls are missing labels.

  4. Native semantics and ARIA

    2 ARIA/native semantic conflicts or redundancies were found.

Evidence log4 steps · 12 lines
Heading structure [fail]! Expected one meaningful visible h1; found 4.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":4,"visibleH1":4,"headings":29,"emptyHeadings":0},"meaningfulH1":false} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Expected one meaningful visible h1; found 4."Links [warning]! 1 links use generic anchor text.INFOLinksWARNCheck links evidence actual={"counts":{"links":130,"inaccessibleLinks":0,"nonCrawlableLinks":0,"genericLinks":1},"accessibleLinks":true} expected="semantic HTML evidence for this step"WARNLinks has a warning issue="1 links use generic anchor text."Form labels and autocomplete [fail]! 1 user-fillable form controls are missing labels.INFOForm labels and autocompleteFAILCheck form labels and autocomplete evidence actual={"counts":{"formControls":1,"unlabeledFormControls":1,"autocompleteInputs":0,"inputsWithAutocomplete":0,"missingAutocompleteInputs":0},"formLabelCoverage":false} expected="semantic HTML evidence for this step"FAILForm labels and autocomplete failed issue="1 user-fillable form controls are missing labels."Native semantics and ARIA [warning]! 2 ARIA/native semantic conflicts or redundancies were found.INFONative semantics and ARIAWARNCheck native semantics and aria evidence actual={"counts":{"ariaIssues":2},"nativeSemanticIntegrity":false} expected="native HTML semantics are present and not replaced by conflicting ARIA"WARNNative semantics and ARIA has a warning issue="2 ARIA/native semantic conflicts or redundancies were found."

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

6 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

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

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

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

  2. Author identity quality

    No named author or publisher identity could be extracted.

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

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

6 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer-first passages

Score

28/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 28/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

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

4 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Evidence and trust

Score

57/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

3 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: author, publisher.

Details

02

Why it matters

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

Check name

AIO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

3 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Expected exactly one h1, found 4. Title/H1 terms missing from description: education, search, code, repositories, users, issues, pull, requests.

Details

02

Why it matters

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

Check name

GEO: Entity clarity

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

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

3 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AIO: Page experience proxy

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 71/100 and needs improvement.

3 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

Expected exactly one h1, found 4. Title, h1, description, and opening copy are weakly aligned. 17 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.

Details

02

Why it matters

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

Check name

AIO: Visible content clarity

Score

71/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 71/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

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

3 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: authorOrOwner, entityLinks.

Details

02

Why it matters

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

Check name

GEO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Expected exactly one h1, found 4. Title, h1, description, and opening copy are weakly aligned.

Details

02

Why it matters

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

Check name

AEO: Entity and definition clarity

Score

70/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 70/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header has a validation warning at "Review preload opt-in".

3 Warning

Needs attention

HSTS header

Warning
01

Issue

preload is present; verify hstspreload.org operational requirements before submission.

02

Why it matters

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

Check name

HSTS header

Score

95/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 preload opt-in".

Validation steps

  1. Review preload opt-in

    preload is present; verify hstspreload.org operational requirements before submission.

Evidence log1 step · 4 lines
Review preload opt-in [warning]! preload is present; verify hstspreload.org operational requirements before submission.INFOReview preload opt-inINFOInspect preload opt-in preload=true includeSubDomains=true maxAge=31536000WARNCompare header-level preload requirements actual="eligible by header" expected="preload + includeSubDomains + max-age >= 31536000" issue="preload is present; verify hstspreload.org operational requirements before submission."WARNpreload is present; verify hstspreload.org operational requirements before submission.

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Page-relevant schema family".

2 Fail

Needs attention

Structured data

Failed check
01

Issue

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

02

Why it matters

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

Check name

Structured data

Score

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

  1. Page-relevant schema family

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

  2. Supporting schema linkage

    Primary schema exists without linked supporting entities.

Evidence log2 steps · 8 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=["FAQPage"]FAILNo primary schema family matches the inferred page intent expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] primaryTypes=["FAQPage"]Supporting schema linkage [warning]! Primary schema exists without linked supporting entities.INFOSupporting schema linkageINFOChecking supporting schema types and @id referencesWARNCheck supporting entity or linked reference evidence actual=0 expected="> 0" supportingTypes=[] referenceCount=0WARNPrimary schema exists without linked supporting entities

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

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

2 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways.

Details

02

Why it matters

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

Check name

GEO: Structured extraction

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt has a validation warning at "Probe sampled linked resources".

2 Warning

Needs attention

llms.txt

Warning
01

Issue

Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.

Details

02

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

87/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 "Probe sampled linked resources".

Validation steps

  1. Probe sampled linked resources

    Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.

    Findings
    • 3/25 probed links were broken or unreachable.
    • 3/25 probed links did not look agent-readable.
  2. Inspect optional llms-full.txt

    Passed.

Evidence log2 steps · 12 lines
Probe sampled linked resources [warning]! Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=25PASSCheck probed links were attempted actual=25 expected="> 0"WARNCheck broken probed link count actual=3 expected=0WARNBroken sampled llms.txt link url="https://docs.github.com/api/article" label="Article API" statusCode=400 contentType="application/json; charset=utf-8" method="GET" agentReadable=falseWARNBroken sampled llms.txt link url="https://docs.github.com/api/article/body" label="Article Body API" statusCode=400 contentType="application/json; charset=utf-8" method="GET" agentReadable=falseWARNBroken sampled llms.txt link url="https://docs.github.com/api/search/v1" label="Search API" statusCode=400 contentType="application/json; charset=utf-8" method="GET" agentReadable=falsePASSCheck agent-readable probed links actual=22 expected="> 0"WARNLinked resource probe validation completed with warnings reason="Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://github.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=406

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

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

1 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

Heading structure issues were detected.

Details

02

Why it matters

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

Check name

AEO: Question and answer structure

Score

85/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 85/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy has a validation warning at "Review CSP reporting".

1 Warning

Needs attention

Content-Security-Policy

Warning
01

Issue

CSP does not define a reporting endpoint.

02

Why it matters

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

Check name

Content-Security-Policy

Score

98/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

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

Result

Content-Security-Policy has a validation warning at "Review CSP reporting".

Validation steps

  1. Review CSP reporting

    CSP does not define a reporting endpoint.

Evidence log1 step · 4 lines
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.

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

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

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

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

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

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

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

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

SEOSEOBrowser audit

Links do not have descriptive text

100 Fail

Check name

Links do not have descriptive text

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 link found

Fix guidance

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).

Evidence
{
  "displayValue": "1 link found",
  "description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/)."
}

PerformancePerformanceBrowser audit

Duplicated JavaScript

11 Fail

Check name

Duplicated JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 38 KiB

Fix guidance

Remove large, [duplicate JavaScript modules](https://developer.chrome.com/docs/performance/insights/duplicated-javascript) from bundles to reduce unnecessary bytes consumed by network activity.

Evidence
{
  "displayValue": "Est savings of 38 KiB",
  "description": "Remove large, [duplicate JavaScript modules](https://developer.chrome.com/docs/performance/insights/duplicated-javascript) from bundles to reduce unnecessary bytes consumed by network activity."
}

PerformancePerformanceBrowser audit

Forced reflow

11 Fail

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.

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

PerformancePerformanceBrowser audit

Improve image delivery

11 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 169 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 169 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

PerformancePerformanceBrowser audit

Network dependency tree

11 Fail

Check name

Network dependency tree

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

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

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

PerformancePerformanceBrowser audit

Reduce unused CSS

11 Fail

Check name

Reduce unused CSS

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 199 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/).

Evidence
{
  "displayValue": "Est savings of 199 KiB",
  "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/).",
  "numericValue": 140
}

PerformancePerformanceBrowser audit

Reduce unused JavaScript

11 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 896 KiB

Fix guidance

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

Evidence
{
  "displayValue": "Est savings of 896 KiB",
  "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
  "numericValue": 680
}

PerformancePerformanceBrowser audit

Render-blocking requests

11 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 450 ms

Fix guidance

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

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

PerformancePerformanceBrowser audit

Avoid enormous network payloads

6 Warning

Check name

Avoid enormous network payloads

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Total size was 3,070 KiB

Fix guidance

Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).

Evidence
{
  "displayValue": "Total size was 3,070 KiB",
  "description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
  "numericValue": 3144138
}

PerformancePerformanceBrowser audit

Loading performance

4 Fail

Check name

Loading performance

Score

63/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 12,
      "displayValue": "2.6 s",
      "numericValue": 2592.9293682263
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 29,
      "displayValue": "3.2 s",
      "numericValue": 3223.0743168265417
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 56,
      "displayValue": "230 ms",
      "numericValue": 229.99999999999955
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 35,
      "displayValue": "2.7 s",
      "numericValue": 2711.1816849714096
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 71,
      "displayValue": "3.5 s",
      "numericValue": 3453.0981298108672
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 380 ms",
      "numericValue": 383
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "10 ms",
      "numericValue": 5.010615
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 97,
      "displayValue": "100 ms",
      "numericValue": 100.99999999999977
    }
  ]
}

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.

2 reports
Public score history report links
Scan dateScoreReadinessReport
44/100Level 2, Agent-LimitedView report
56/100Level 3, Bot-AwareCurrent report
github.com AI SEO Report: 56/100 (Level 3, Bot-Aware)