Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 44 out of 100
- Agent Ease of Use 10 out of 100
- Security & Trust 20 out of 100
- GEO, AIO and AEO 81 out of 100
- SEO 100 out of 100
- Performance and Accessibility 94 out of 100
What AI sees of your website
Customer Intelligence Platform | Uservoice
Turn customer feedback into actionable insights. Unify signals, prioritize what matters, and build products with confidence. SOC 2 & GDPR compliant.
Next step
Turn this report into a fix workflow
26 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 44 | Priority fix | 10 | 13 | 1 | View details |
| Discoverability | 67 | Needs work | 5 | 4 | 0 | View details |
| Content Readiness | 54 | Needs work | 5 | 5 | 1 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 10 | Priority fix | 6 | 29 | 1 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 0 | 7 | 0 | View details |
| MCP | 25 | Priority fix | 2 | 6 | 0 | View details |
| Skill Discovery | 5 | Priority fix | 0 | 10 | 1 | View details |
| Agent Commerce | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| GEO, AIO and AEO | 81 | Mostly ready | 7 | 0 | 10 | |
| GEO Readiness | 84 | Mostly ready | 2 | 0 | 4 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | 70 | Needs work | 1 | 0 | 6 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| Security & Trust | 20 | Priority fix | 5 | 4 | 0 | View details |
| Security & Trust | 20 | Priority fix | 1 | 4 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 94 | Strong | 20 | 4 | 1 | View details |
| Performance | 96 | Strong | 14 | 3 | 1 | View details |
| Accessibility | 90 | Strong | 6 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
40 items need attention
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
50 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
Needs attention
API Catalog
Issue
The API catalog endpoint did not return HTTP 2xx.
Why it matters
API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.
Check name
API Catalog
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated API discovery using RFC 9727.
Result
API Catalog failed at "Fetch API catalog".
Validation steps
Fetch API catalog
The API catalog endpoint did not return HTTP 2xx.
Validate RFC 9727 linkset
Response is not valid JSON.
Fetch advertised API catalog targets
API Catalog did not expose any same-origin hrefs to validate.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch API catalog",
"status": "fail",
"evidence": {
"statusCode": 404,
"contentType": "text/html; charset=utf-8"
},
"issue": "The API catalog endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/api-catalog."
},
{
"id": "validate",
"title": "Validate RFC 9727 linkset",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"issue": "Response is not valid JSON.",
"howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
},
{
"id": "target-validation",
"title": "Fetch advertised API catalog targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin API catalog hrefs were available to fetch."
}
]
},
"issue": "API Catalog did not expose any same-origin hrefs to validate.",
"howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
50 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence
{
"failedStep": "presence",
"steps": [
{
"id": "presence",
"title": "Find useful Link headers",
"status": "fail",
"evidence": {
"links": []
},
"issue": "No useful agent discovery Link headers were found.",
"howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
},
{
"id": "target-validation",
"title": "Fetch same-origin Link header targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin Link header targets were available to fetch."
}
]
},
"issue": "Link headers did not expose any same-origin targets to validate.",
"howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
}
]
}Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
50 Fail
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
Needs attention
OpenAPI discovery
Issue
OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Why it matters
OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.
Check name
OpenAPI discovery
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for API discovery.
Result
OpenAPI discovery failed at "Find valid OpenAPI document".
Validation steps
Find valid OpenAPI document
OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Find valid OpenAPI document",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/openapi.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/swagger.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
},
{
"path": "/docs/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
}
]
},
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
50 Fail
AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
Needs attention
Organization / WebSite schema
Issue
Neither Organization nor WebSite schema types were found in JSON-LD.
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
Discoverability
Maturity
Established
Goal
Identify the site owner and website entity in structured data.
Result
Organization / WebSite schema is missing or incomplete.
Evidence
{
"found": [],
"allTypes": [
"SoftwareApplication"
]
}AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
Needs attention
AI bot rules in robots.txt
Issue
No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.
Why it matters
Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.
Check name
AI bot rules in robots.txt
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.
Result
AI bot rules in robots.txt is missing or incomplete.
Evidence
{
"expectedBots": [
"GPTBot",
"ChatGPT-User",
"ClaudeBot",
"Claude-Web",
"Anthropic-AI",
"Google-Extended",
"PerplexityBot",
"CCBot",
"Applebot-Extended",
"Meta-ExternalAgent",
"Bytespider",
"Amazonbot",
"Cohere-AI"
],
"configuredBots": []
}AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
Needs attention
Content Signal
Issue
No Content Signal found in robots.txt
Why it matters
Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.
Check name
Content Signal
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences with Content Signal in robots.txt.
Result
Content Signal is missing or incomplete.
Evidence
{
"signals": [],
"ai-train": false,
"search": false,
"ai-input": false
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
33 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
Needs attention
Markdown negotiation
Issue
Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.
Why it matters
Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.
Check name
Markdown negotiation
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Return HTML responses as markdown when agents request it.
Result
Markdown negotiation failed at "Markdown content type".
Validation steps
Markdown content type
Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "accept-encoding".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html; charset=utf-8"
},
"issue": "Content-Type \"text/html; charset=utf-8\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "accept-encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"accept-encoding\".",
"howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
},
{
"id": "markdown-content",
"title": "Structured Markdown body",
"status": "fail",
"evidence": {
"valid": false,
"hasHeading": false,
"wordCount": 4017,
"excerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"695efde5fa813ad129507555\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
Needs attention
MCP Server Card
Issue
MCP Server Card was not found at the expected path.
Why it matters
MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.
Check name
MCP Server Card
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
MCP Server Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "MCP Server Card was not found at the expected path.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
Needs attention
mcp.json
Issue
mcp.json was not found at the expected path.
Why it matters
MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.
Check name
mcp.json
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.
Result
mcp.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
mcp.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "mcp.json was not found at the expected path.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
33 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: missing <main> landmark; missing <footer> landmark; skipped heading levels; 5 links missing accessible names.
Details
Why it matters
Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.
Check name
Semantic HTML
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose readable page structure through semantic HTML and accessible controls.
Result
Semantic HTML is missing or incomplete.
Evidence
{
"main": false,
"nav": true,
"footer": false,
"meaningfulH1": true,
"headingOrder": false,
"accessibleLinks": false,
"accessibleButtons": true,
"imageAltCoverage": true,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [
"<a href=\"/\" aria-current=\"page\" class=\"navbar-brand-2 w-nav-brand w--current\"><img loading=\"lazy\" src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6973b00432ddf9f3658144cc_uv-logo.svg\" alt class=\"image\" data-categories=\"unclassified\"></a>",
"<a href=\"/\" aria-current=\"page\" class=\"footer-brand w-inline-block w--current\"><img src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6973b00432ddf9f3658144cc_uv-logo.svg\" loading=\"lazy\" alt class=\"image-2\" data-categories=\"unclassified\"></a>",
"<a href=\"https://x.com/uservoiceinc?lang=en&utm_source=website_footer&utm_medium=website\" class=\"w-inline-block\"><img src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6974285d554906b552ccf1dc_x-logo.svg\" loading=\"lazy\" alt data-categories=\"unclassified\"></a>",
"<a href=\"https://www.youtube.com/@weareuservoice?utm_source=website_footer&utm_medium=website\" class=\"w-inline-block\"><img src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6974285dd345d320975e74fe_yt-logo.svg\" loading=\"lazy\" alt data-categories=\"unclassified\"></a>",
"<a href=\"https://www.linkedin.com/company/uservoice?utm_source=website_footer&utm_medium=website\" class=\"w-inline-block\"><img src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6974285d22bf4018cd58e2f1_linkedin-logo.svg\" loading=\"lazy\" alt data-categories=\"unclassified\"></a>"
],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [],
"skippedHeadingLevels": [
"h1: Get clear on what customers want. Get ahead of what it means for revenue.",
"h2: The intelligence layer your GTM stack is missing",
"h5: Ian Jackson",
"h2: Customer intelligence that speaks the language of growth",
"h4: One source of truth for customer and product insights",
"h4: Align everyone around the customer truth",
"h4: Surface risks before they hit forecast",
"h2: See what's actually driving growth",
"h4: Know what requests come from valuable accounts",
"h4: Empower decisions with data-driven insights",
"h4: Catch market shifts before your competitors do",
"h3: Uservoice helps us turn customer feedback into shared intelligence across the business. As more teams engage, we get stronger insights, better analytics, and real momentum toward embedding the customer voice into our decision-making.",
"h5: Ariana Newton",
"h3: We can quickly surface a complete, data-backed view of every client interaction—questions, feedback, and responses—and turn that into clear insights for renewals. It shows customers we’re listening and acting on what they tell us.",
"h5: Kathryn Doebler",
"h3: There are a lot of problems to solve out there, and spending time on something that isn’t the most impactful for our users is heartbreaking. Uservoice challenges me to look at the overall picture of the struggles that our customers as a whole.",
"h5: Megan Fangmeyer",
"h2: Information is safe with us (and always accessible)",
"h4: SOC 2 Type 2",
"h4: GDPR Compliant",
"h4: WCAG Compliant",
"h2: One version of the customer truth.",
"h2: Uservoice works out-of-the-box with what you already use",
"h2: Get clear on what matters"
]
},
"counts": {
"h1": 1,
"headings": 24,
"links": 51,
"inaccessibleLinks": 5,
"buttons": 1,
"inaccessibleButtons": 0,
"images": 65,
"imagesWithAlt": 65,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 0
}
}AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
33 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing was not found at the expected path.
Why it matters
Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.
Check name
Web Bot Auth request signing
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.
Result
Web Bot Auth request signing failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Web Bot Auth request signing was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "Web Bot Auth request signing was not found at the expected path.",
"howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
}
]
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
Needs attention
WebMCP manifest
Issue
WebMCP manifest was not found at the expected path.
Why it matters
A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.
Check name
WebMCP manifest
Score
0/100
Status
fail
Category
MCP
Maturity
Informational
Goal
Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.
Result
WebMCP manifest failed at "Fetch to find resource".
Validation steps
Fetch to find resource
WebMCP manifest was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
}
]
},
"issue": "WebMCP manifest was not found at the expected path.",
"howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
}
]
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
25 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
25 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
Needs attention
Frame protection
Issue
Frame protection is missing or incomplete.
Why it matters
Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.
Check name
Frame protection
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.
Result
Frame protection is missing or incomplete.
Evidence
{
"xFrameOptions": null,
"validXFrame": false,
"contentSecurityPolicy": null,
"cspFrameAncestors": false
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
25 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
25 Fail
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
Needs attention
X-Content-Type-Options
Issue
X-Content-Type-Options is missing or incomplete.
Why it matters
X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.
Check name
X-Content-Type-Options
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent MIME sniffing for browser-loaded resources.
Result
X-Content-Type-Options is missing or incomplete.
Evidence
{
"header": "x-content-type-options",
"value": null
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
25 Warning
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.
Why it matters
Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.
Check name
Content freshness signals
Score
25/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is partially implemented.
Evidence
{
"lastModified": "Tue, 09 Jun 2026 18:47:06 GMT",
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
Needs attention
A2A Agent Card
Issue
A2A Agent Card was not found at the expected path.
Why it matters
A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.
Check name
A2A Agent Card
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent card so A2A-compatible clients can discover capabilities.
Result
A2A Agent Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
A2A Agent Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
}
]
},
"issue": "A2A Agent Card was not found at the expected path.",
"howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
Needs attention
Agent Skills index
Issue
Agent Skills index was not found at the expected path.
Why it matters
An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.
Check name
Agent Skills index
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent skills discovery index.
Result
Agent Skills index failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Agent Skills index was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "Agent Skills index was not found at the expected path.",
"howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
Needs attention
agent.json
Issue
agent.json was not found at the expected path.
Why it matters
agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.
Check name
agent.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.
Result
agent.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agent.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
}
]
},
"issue": "agent.json was not found at the expected path.",
"howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
}
]
}Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
Needs attention
agents.json
Issue
agents.json was not found at the expected path.
Why it matters
agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.
Check name
agents.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Informational
Goal
Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.
Result
agents.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agents.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
}
]
},
"issue": "agents.json was not found at the expected path.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
15 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID entrypoint records were found under _agents.
Why it matters
DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.
Check name
DNS-AID Agent Discovery
Score
25/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Validation steps
Resolve DNS-AID SVCB/HTTPS records
No DNS-AID entrypoint records were found under _agents.
Validate alpn and endpoint parameters
Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.
Check DNSSEC material
DNSSEC material was not visible for the hostname or parent zone from this resolver.
Evidence
{
"failedStep": "svcb-https-records",
"steps": [
{
"id": "svcb-https-records",
"title": "Resolve DNS-AID SVCB/HTTPS records",
"status": "fail",
"evidence": {
"hostname": "uservoice.com",
"probes": [
{
"name": "_index._agents.uservoice.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.uservoice.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
}
]
},
"issue": "No DNS-AID entrypoint records were found under _agents.",
"howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
},
{
"id": "service-params",
"title": "Validate alpn and endpoint parameters",
"status": "informational",
"evidence": {
"discovered": []
},
"howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
},
{
"id": "dnssec",
"title": "Check DNSSEC material",
"status": "warning",
"evidence": {
"hasDnssecMaterial": false,
"checked": [
{
"name": "uservoice.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
}
]
},
"issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
"howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 73/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 73/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: intelligence, platform, uservoice, get, clear, customers, want, ahead, means, revenue.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Entity clarity
Score
73/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Entity clarity scored 73/100 and needs improvement.
Evidence
{
"title": "Customer Intelligence Platform | Uservoice",
"h1": "Get clear on what customers want. Get ahead of what it means for revenue.",
"description": "Turn customer feedback into actionable insights. Unify signals, prioritize what matters, and build products with confidence. SOC 2 & GDPR compliant.",
"topicOverlap": 0.09090909090909091,
"topicTerms": [
"customer",
"intelligence",
"platform",
"uservoice",
"get",
"clear",
"customers",
"want",
"ahead",
"means",
"revenue"
],
"descriptionTerms": [
"turn",
"customer",
"feedback",
"into",
"actionable",
"insights",
"unify",
"signals",
"prioritize",
"matters",
"build",
"products",
"confidence",
"soc",
"gdpr",
"compliant"
],
"missingFromDescription": [
"intelligence",
"platform",
"uservoice",
"get",
"clear",
"customers",
"want",
"ahead",
"means",
"revenue"
],
"score": 73,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
Needs attention
AEO: Answer-first sections
Issue
9 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer-first sections
Score
65/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer-first sections scored 65/100 and needs improvement.
Evidence
{
"sectionCount": 10,
"passing": 1,
"failing": [
{
"heading": "The intelligence layer your GTM stack is missing",
"headingHtml": "<h2 class=\"white bigger-picture\">The intelligence layer your GTM stack is missing</h2>",
"firstParagraph": "B2B S&T Company",
"paragraphHtml": "<p class=\"bigger-picture-sub\">B2B S&T Company</p>",
"words": 4,
"direct": false,
"issue": "First paragraph is 4 words and does not look like a concise direct answer."
},
{
"heading": "Customer intelligence that speaks the language of growth",
"headingHtml": "<h2 class=\"heading black\">Customer intelligence that speaks the language of growth</h2>",
"firstParagraph": "Ingest support tickets, NPS verbatims, product feedback, and CRM data into one place.",
"paragraphHtml": "<p>Ingest support tickets, NPS verbatims, product feedback, and CRM data into one place.</p>",
"words": 13,
"direct": false,
"issue": "First paragraph is 13 words and does not look like a concise direct answer."
},
{
"heading": "Uservoice helps us turn customer feedback into shared intelligence across the business. As more teams engage, we get stronger insights, better analytics, and real momentum toward embedding the customer voice into our decision-making.",
"headingHtml": "<h3 class=\"quote\">Uservoice helps us turn customer feedback into shared intelligence across the business. As more teams engage, we get stronger insights, better analytics, and real momentum toward embedding the customer voice into our decision-making.</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "We can quickly surface a complete, data-backed view of every client interaction—questions, feedback, and responses—and turn that into clear insights for renewals. It shows customers we’re listening and acting on what they tell us.",
"headingHtml": "<h3 class=\"quote\">We can quickly surface a complete, data-backed view of every client interaction—questions, feedback, and responses—and turn that into clear insights for renewals. It shows customers we’re listening and acting on what they tell us.</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "There are a lot of problems to solve out there, and spending time on something that isn’t the most impactful for our users is heartbreaking. Uservoice challenges me to look at the overall picture of the struggles that our customers as a whole.",
"headingHtml": "<h3 class=\"quote\">There are a lot of problems to solve out there, and spending time on something that isn’t the most impactful for our users is heartbreaking. Uservoice challenges me to look at the overall picture of the struggles that our customers as a whole.</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Information is safe with us (and always accessible)",
"headingHtml": "<h2 class=\"center\">Information is safe with us (and always accessible)</h2>",
"firstParagraph": "We're certified and follow rigorous and independently-audited security controls to keep your data safe and protected.",
"paragraphHtml": "<p>We're certified and follow rigorous and independently-audited security controls to keep your data safe and protected.</p>",
"words": 16,
"direct": false,
"issue": "First paragraph is 16 words and does not look like a concise direct answer."
},
{
"heading": "One version of the customer truth.",
"headingHtml": "<h2 class=\"heading black river-header\">One version of the customer truth.</h2>",
"firstParagraph": "Uservoice gives you the signal you need and gives sales, customer support, and product the role-specific views that make them better at their jobs.",
"paragraphHtml": "<p class=\"river-paragraph\">Uservoice gives you the signal you need and gives sales, customer support, and product the role-specific views that make them better at their jobs.</p>",
"words": 24,
"direct": false,
"issue": "First paragraph is 24 words and does not look like a concise direct answer."
},
{
"heading": "Uservoice works out-of-the-box with what you already use",
"headingHtml": "<h2 class=\"center\">Uservoice works out-of-the-box with what you already use</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Get clear on what matters",
"headingHtml": "<h2 class=\"heading-2\">Get clear on what matters</h2>",
"firstParagraph": "Turn scattered user data into meaningful customer intelligence, guiding smarter decisions and creating a better product.",
"paragraphHtml": "<p class=\"white centered\">Turn scattered user data into meaningful customer intelligence, guiding smarter decisions and creating a better product.</p>",
"words": 16,
"direct": false,
"issue": "First paragraph is 16 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
9 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 7,
"questionH2s": [],
"hasFaq": true,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
Needs attention
GEO: Explanatory content depth
Issue
No substantial explanatory paragraphs were found.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
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.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 1,
"citablePassages": 0,
"failingCandidateParagraphs": [],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": true,
"definitionPatterns": 5,
"schemaBlocks": 1,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process"
],
"score": 85,
"weight": 24
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 80/100 and needs improvement.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: freshnessDate.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer evidence and trust
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer evidence and trust scored 80/100 and needs improvement.
Evidence
{
"signals": {
"author": true,
"publisher": true,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"freshnessDate"
],
"authorMeta": "",
"schemaAuthors": [
"Ariana Newton",
"Kathryn Doebler",
"Megan Fangmeyer"
],
"schemaPublishers": [
"Uservoice"
],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [
{
"href": "https://www.linkedin.com/company/uservoice?utm_source=website_footer&utm_medium=website",
"text": "",
"html": "<a href=\"https://www.linkedin.com/company/uservoice?utm_source=website_footer&utm_medium=website\" class=\"w-inline-block\"><img src=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/6974285d22bf4018cd58e2f1_linkedin-logo.svg\" loading=\"lazy\" alt data-categories=\"unclassified\"></a>"
}
],
"contactLinks": [
{
"href": "https://help.uservoice.com/hc/en-us",
"text": "Knowledge Base",
"html": "<a href=\"https://help.uservoice.com/hc/en-us\" target=\"_blank\" class=\"nav-dropdown-link-2 w-dropdown-link\">Knowledge Base</a>"
},
{
"href": "https://help.uservoice.com/hc/en-us",
"text": "Knowledge Base",
"html": "<a href=\"https://help.uservoice.com/hc/en-us\" class=\"footer-link\">Knowledge Base</a>"
}
],
"privacyLinks": [
{
"href": "/tos",
"text": "Terms & Privacy",
"html": "<a href=\"/tos\" class=\"footer-link\">Terms & Privacy</a>"
},
{
"href": "/tos",
"text": "Terms",
"html": "<a href=\"/tos\" class=\"footer-link w-inline-block\"><div>Terms</div></a>"
},
{
"href": "/privacy",
"text": "Privacy",
"html": "<a href=\"/privacy\" class=\"footer-link w-inline-block\"><div>Privacy</div></a>"
}
],
"score": 80,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 77/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 77/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: intelligence, platform, uservoice, get, clear, customers, want, ahead, means, revenue.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Entity and definition clarity
Score
77/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Entity and definition clarity scored 77/100 and needs improvement.
Evidence
{
"title": "Customer Intelligence Platform | Uservoice",
"h1": "Get clear on what customers want. Get ahead of what it means for revenue.",
"description": "Turn customer feedback into actionable insights. Unify signals, prioritize what matters, and build products with confidence. SOC 2 & GDPR compliant.",
"topicOverlap": 0.09090909090909091,
"definitionCount": 5,
"topicTerms": [
"customer",
"intelligence",
"platform",
"uservoice",
"get",
"clear",
"customers",
"want",
"ahead",
"means",
"revenue"
],
"descriptionTerms": [
"turn",
"customer",
"feedback",
"into",
"actionable",
"insights",
"unify",
"signals",
"prioritize",
"matters",
"build",
"products",
"confidence",
"soc",
"gdpr",
"compliant"
],
"missingFromDescription": [
"intelligence",
"platform",
"uservoice",
"get",
"clear",
"customers",
"want",
"ahead",
"means",
"revenue"
],
"score": 77,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: cost, compare.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer intent coverage
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer intent coverage scored 70/100 and needs improvement.
Evidence
{
"headings": [
{
"text": "The intelligence layer your GTM stack is missing",
"html": "<h2 class=\"white bigger-picture\">The intelligence layer your GTM stack is missing</h2>"
},
{
"text": "Customer intelligence that speaks the language of growth",
"html": "<h2 class=\"heading black\">Customer intelligence that speaks the language of growth</h2>"
},
{
"text": "See what's actually driving growth",
"html": "<h2>See what's actually driving growth</h2>"
},
{
"text": "Information is safe with us (and always accessible)",
"html": "<h2 class=\"center\">Information is safe with us (and always accessible)</h2>"
},
{
"text": "One version of the customer truth.",
"html": "<h2 class=\"heading black river-header\">One version of the customer truth.</h2>"
},
{
"text": "Uservoice works out-of-the-box with what you already use",
"html": "<h2 class=\"center\">Uservoice works out-of-the-box with what you already use</h2>"
},
{
"text": "Get clear on what matters",
"html": "<h2 class=\"heading-2\">Get clear on what matters</h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Customer Intelligence Platform?",
"pattern": {}
},
{
"id": "how",
"label": "How does Customer Intelligence Platform work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Customer Intelligence Platform?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Customer Intelligence Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Customer Intelligence Platform compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "cost",
"label": "Is Customer Intelligence Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Customer Intelligence Platform compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093
}
]
},
"issue": "AI context endpoint was not found at the expected path.",
"howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
}
]
}Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Needs attention
Auth.md Agent Registration
Issue
auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.
Why it matters
Agent registration metadata lets automated clients find the registration path, supported identity types, credential types, and related claim or revocation endpoints without scraping human docs.
Check name
Auth.md Agent Registration
Score
0/100
Status
informational
Category
Auth
Maturity
Emerging recommendation
Goal
Publish Auth.md and agent_auth metadata so agents can discover registration and credential requirements.
Result
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Validation steps
Fetch and validate /auth.md
auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.
Publish protected resource metadata
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Validate agent_auth authorization metadata
OAuth authorization server metadata could not be fetched.
Evidence
{
"failedStep": "auth-md",
"steps": [
{
"id": "auth-md",
"title": "Fetch and validate /auth.md",
"status": "fail",
"evidence": {
"path": "/auth.md",
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 4093,
"validation": {
"valid": false,
"issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
"compatibleContentType": false,
"contentLength": 4043,
"hasRegisterInstructions": false,
"hasProtectedResourceLink": false,
"hasAuthorizationServerLink": false,
"mentionsIdentity": false,
"mentionsCredential": false,
"links": [
"https://cdn.prod.website-files.com\"",
"/title",
"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\"",
"/css",
"/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo",
"https://use.typekit.net/xfw3rns.js\"",
"/javascript",
"/script",
"/javascript",
"/script"
],
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Tue Jun 02 2026 00:07:11 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"uservoice.com\" data-wf-page=\"6973d6979b77fe3c31fc3d0d\" data-wf-site=\"695efde3fa813ad129507522\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><link href=\"https://cdn.prod.website-files.com/695efde3fa813ad129507522/css/uservoice-draft.shared.7357aca1e.css\" rel=\"stylesheet\" type=\"text/css\" integrity=\"sha384-c1esoeO93P9TA+YIaHmpvafD/4dZ0YINI1Rowo3cSM/vLb68YfB2TA0Mth1/A5Xo\" crossorigin=\"anonymous\"/><script "
}
},
"issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
"howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
},
{
"id": "oauth-protected-resource",
"title": "Publish protected resource metadata",
"status": "fail",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88,
"text": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
},
{
"id": "agent-auth-block",
"title": "Validate agent_auth authorization metadata",
"status": "fail",
"evidence": {
"valid": false,
"issue": "OAuth authorization server metadata could not be fetched.",
"fetch": {
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88,
"text": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
}
},
"issue": "OAuth authorization server metadata could not be fetched.",
"howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
}
]
},
"resourceFetchSucceeded": false
}AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
Why it matters
IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.
Check name
IndexNow key
Score
100/100
Status
informational
Category
Discoverability
Maturity
Established
Goal
Verify that IndexNow ownership key placement is detectable when the site advertises it.
Result
IndexNow key is informational for this page.
Validation steps
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
Fetch and validate IndexNow key file
No discoverable IndexNow key file was found.
Evidence
{
"steps": [
{
"id": "advertised-location",
"title": "Find advertised IndexNow key location",
"status": "informational",
"evidence": {
"advertised": []
},
"issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
"howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
},
{
"id": "fetch-key",
"title": "Fetch and validate IndexNow key file",
"status": "informational",
"evidence": {
"advertised": [],
"checked": []
},
"issue": "No discoverable IndexNow key file was found.",
"howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
}
]
}Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Needs attention
OAuth / OIDC discovery
Issue
OAuth / OIDC discovery was not found at the expected path.
Why it matters
OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.
Check name
OAuth / OIDC discovery
Score
0/100
Status
informational
Category
Auth
Maturity
Established
Goal
Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.
Result
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Validation steps
Fetch to find resource
OAuth / OIDC discovery was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/openid-configuration",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/oauth-authorization-server",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "OAuth / OIDC discovery was not found at the expected path.",
"howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
}
]
},
"resourceFetchSucceeded": false
}Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Needs attention
OAuth Protected Resource
Issue
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Why it matters
Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.
Check name
OAuth Protected Resource
Score
0/100
Status
informational
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.
Result
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Validation steps
Fetch protected resource metadata
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Validate protected resource metadata
Response is not valid JSON.
Validate protected resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
Probe protected API Bearer challenge
No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch protected resource metadata",
"status": "fail",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"statusCode": 404,
"contentType": "text/html; charset=utf-8"
},
"issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/oauth-protected-resource JSON."
},
{
"id": "metadata",
"title": "Validate protected resource metadata",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish resource and authorization_servers as absolute URLs."
},
{
"id": "resource-identity",
"title": "Validate protected resource identity",
"status": "fail",
"evidence": {
"expectedResource": "https://uservoice.com"
},
"issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
"howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
},
{
"id": "protected-route-challenge",
"title": "Probe protected API Bearer challenge",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/admin/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://uservoice.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://uservoice.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://uservoice.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
}
]
},
"issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
"howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
}
]
},
"resourceFetchSucceeded": false
}Performance and AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
100 Fail
Performance and AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
Check name
Background and foreground colors do not have a sufficient contrast ratio.
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}Performance and AccessibilityPerformanceBrowser audit
Font display
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Font display
Check name
Font display
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 970 ms
Fix guidance
Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 970 ms",
"description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}Performance and AccessibilityPerformanceBrowser audit
Forced reflow
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Forced reflow
Check name
Forced reflow
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
References
https://web.dev/learn/performance/Evidence
{
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}Performance and AccessibilityPerformanceBrowser audit
LCP request discovery
25 Fail
Performance and AccessibilityPerformanceBrowser audit
LCP request discovery
Check name
LCP request discovery
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
References
https://web.dev/learn/performance/Evidence
{
"description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
13 Warning
Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 16 KiB
Fix guidance
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 16 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": 0
}Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 62/100 | Level 3, Bot-Aware | Current report |