Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 13 out of 100
- Agent Ease of Use 10 out of 100
- Security & Trust 60 out of 100
- GEO, AIO and AEO 38 out of 100
- SEO 33 out of 100
- Performance and Accessibility 74 out of 100
What AI sees of your website
No page title captured
Create a business account Add your restaurant Sign up to deliver Get a ride Skip to content Log in Sign up Uber Eats is not available in your area We do not operate Uber Eats in your region. Try Uber instead for affordable rides and hassle free package delive...
Next step
Turn this report into a fix workflow
32 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 | 13 | Priority fix | 4 | 19 | 0 | View details |
| Discoverability | 17 | Priority fix | 2 | 7 | 0 | View details |
| Content Readiness | 20 | Priority fix | 2 | 8 | 0 | 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 | 38 | Priority fix | 2 | 10 | 8 | View details |
| GEO Readiness | 37 | Priority fix | 1 | 3 | 2 | View details |
| AIO Readiness | 32 | Priority fix | 1 | 4 | 2 | View details |
| AEO Readiness | 44 | Priority fix | 0 | 3 | 4 | View details |
| SEO | 33 | Priority fix | 6 | 5 | 0 | View details |
| SEO | 33 | Priority fix | 6 | 5 | 0 | View details |
| Security & Trust | 60 | Needs work | 7 | 2 | 0 | View details |
| Security & Trust | 60 | Needs work | 3 | 2 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 74 | Needs work | 20 | 4 | 0 | View details |
| Performance | 65 | Needs work | 14 | 4 | 0 | View details |
| Accessibility | 91 | Strong | 6 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
56 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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"24119637-bd5e-4289-bf69-0c2093771cc2\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"24119637-bd5e-4289-bf69-0c2093771cc2\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"24119637-bd5e-4289-bf69-0c2093771cc2\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"24119637-bd5e-4289-bf69-0c2093771cc2\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"24119637-bd5e-4289-bf69-0c2093771cc2\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
"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."
}
]
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
50 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": "frame-ancestors 'self' https://www.nimblerx.com https://static-team-ops.nimbleandsimple.com https://pharma.uber.com https://voalzira.online/ https://voalzira.online/minhaloja https://medmate.com.au https://order.manoosh.com.au https://test.expresskfc.com/ https://expresskfc.com/ https://www.test.expresskfc.com/ https://www.expresskfc.com/ https://kfccostarica.cr/ https://www.kfccostarica.cr/ https://express.dospinos.com/ https://mcstaging.dospinos.com/ https://shopuat.pxpay.com.tw/ https://shop.pxpay.com.tw/ https://app.cocinasocultas.com https://app.foodstarsuk.com https://app.pruebehubster.com https://app.pruebehubster.com.mx https://app.tryhubster.co.uk https://app.tryhubster.com https://app.tryhubster.com.au https://app.tryotter.com https://catalogs.uberinternal.com https://catalogs-staging.uberinternal.com https://payments.uber.com https://payments-guest.uber.com https://payments.ubereats.com https://payments.postmates.com https://payments.order.store https://wpe-breeze.uberinternal.com https://payments-orchid.uber.com https://payments-otchs.uber.com https://payments-staging.uberinternal.com https://payments-staging.uber.com *.appspaces.ca *.paidshipping.com *.shiptime.com https://dev-bk-web.co.uk.rbi.tools https://staging-bk-web.co.uk.rbi.tools https://qa-bk-web.co.uk.rbi.tools https://www.burgerking.co.uk https://burgerking.co.uk capacitor://burgerking.co.uk capacitor://www.burgerking.co.uk capacitor://dev-bk-web.co.uk.rbi.tools capacitor://staging-bk-web.co.uk.rbi.tools capacitor://qa-bk-web.co.uk.rbi.tools report-uri https://csp.uber.com/csp?a=web-eats-v2&ro=false"
}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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"e35e9e80-a6bd-49aa-93b6-c45249d05ec8\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"e35e9e80-a6bd-49aa-93b6-c45249d05ec8\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"e35e9e80-a6bd-49aa-93b6-c45249d05ec8\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"e35e9e80-a6bd-49aa-93b6-c45249d05ec8\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"e35e9e80-a6bd-49aa-93b6-c45249d05ec8\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
{
"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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"1cde468e-f09c-4f44-8a79-0be636d3d4ea\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"1cde468e-f09c-4f44-8a79-0be636d3d4ea\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"1cde468e-f09c-4f44-8a79-0be636d3d4ea\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"1cde468e-f09c-4f44-8a79-0be636d3d4ea\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"1cde468e-f09c-4f44-8a79-0be636d3d4ea\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
{
"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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"23c546ec-29a3-4e1a-a48c-cf2127f91d99\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"23c546ec-29a3-4e1a-a48c-cf2127f91d99\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"23c546ec-29a3-4e1a-a48c-cf2127f91d99\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"23c546ec-29a3-4e1a-a48c-cf2127f91d99\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"23c546ec-29a3-4e1a-a48c-cf2127f91d99\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
{
"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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"c5db81a3-8c2e-486c-8eb2-0d8e592a6738\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"c5db81a3-8c2e-486c-8eb2-0d8e592a6738\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"c5db81a3-8c2e-486c-8eb2-0d8e592a6738\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"c5db81a3-8c2e-486c-8eb2-0d8e592a6738\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"c5db81a3-8c2e-486c-8eb2-0d8e592a6738\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"contentType": "text/plain; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": true,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "Not Found"
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"contentType": "text/plain; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": true,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "Not Found"
},
{
"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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"44d28746-cd3f-470f-96f3-f688c65399cc\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"44d28746-cd3f-470f-96f3-f688c65399cc\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"44d28746-cd3f-470f-96f3-f688c65399cc\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"44d28746-cd3f-470f-96f3-f688c65399cc\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"44d28746-cd3f-470f-96f3-f688c65399cc\" as=\"script\"/><link rel=\"preload\" href=\"/"
}
]
},
"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."
}
]
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
50 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
}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
}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": 655194
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655242
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655123
}
]
},
"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": 661544
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655152
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655242
}
]
},
"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 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": 654633
}
]
},
"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": 655133
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 661755
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 661491
}
]
},
"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."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing Last-Modified HTTP header; 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
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is missing or incomplete.
Evidence
{
"lastModified": null,
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch to find resource".
25 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch to find resource".
Needs attention
llms.txt
Issue
llms.txt was not found at the expected path.
Why it matters
llms.txt gives language-model clients a concise, curated summary of important site context and links before they crawl broadly.
Check name
llms.txt
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish llms.txt to summarize agent-readable site guidance.
Result
llms.txt failed at "Fetch to find resource".
Validation steps
Fetch to find resource
llms.txt was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/llms.txt",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 660598
},
{
"path": "/llms-full.txt",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 660943
}
]
},
"issue": "llms.txt was not found at the expected path.",
"howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
25 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 "Sec-CH-Prefers-Color-Scheme, 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": 410,
"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": "Sec-CH-Prefers-Color-Scheme, Accept-Encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Sec-CH-Prefers-Color-Scheme, 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": 49027,
"excerpt": "<!doctype html><html lang=\"en-IN\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"c98b1b72-9a6e-45cc-84cf-c4992e8694ff\" as=\"script\"/><link rel=\"preload\" href=\"/_sta",
"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."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: missing <footer> landmark; invalid h1 (found 0); missing alt text on >10% of images.
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": true,
"nav": true,
"footer": false,
"meaningfulH1": false,
"headingOrder": true,
"accessibleLinks": true,
"accessibleButtons": true,
"imageAltCoverage": false,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [
"<img src=\"https://d4p17acsd5wyj.cloudfront.net/static/third-party-shutdown.png\" width=\"263\" height=\"96\" class=\"_es\">"
],
"skippedHeadingLevels": []
},
"counts": {
"h1": 0,
"headings": 0,
"links": 9,
"inaccessibleLinks": 0,
"buttons": 1,
"inaccessibleButtons": 0,
"images": 3,
"imagesWithAlt": 2,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 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": 655168
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655245
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 662038
}
]
},
"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": 655246
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655172
}
]
},
"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": 655122
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 661639
}
]
},
"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": 654490
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 661744
}
]
},
"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."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
Needs attention
High-value schema types
Issue
No high-value schema types (e.g. Article, Product, Service) were found.
Why it matters
High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.
Check name
High-value schema types
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Use schema types that describe the page's primary content or offering.
Result
High-value schema types is missing or incomplete.
Evidence
{
"found": [],
"expected": [
"Article",
"BlogPosting",
"NewsArticle",
"Product",
"SoftwareApplication",
"FAQPage",
"LocalBusiness",
"VideoObject",
"HowTo",
"Event",
"Course",
"Review",
"Service"
],
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
Needs attention
JSON-LD present
Issue
No JSON-LD blocks found.
Why it matters
JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.
Check name
JSON-LD present
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose schema.org JSON-LD so AI search systems can parse page entities.
Result
JSON-LD present is missing or incomplete.
Evidence
{
"blocks": 0,
"validBlocks": 0,
"schemaContextBlocks": 0,
"errors": [],
"documents": [],
"nodes": []
}AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
20 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."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
20 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": []
}AI DiscoverabilityDiscoverabilityEstablished
Sitemap
Sitemap is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
Sitemap
Sitemap is missing or incomplete.
Needs attention
Sitemap
Issue
No valid XML sitemap found at checked locations: https://www.ubereats.com/sitemap-index-771af823.xml.gz, https://www.ubereats.com/sitemap-store-771af823-025.xml.gz, https://www.ubereats.com/sitemap-store-771af823-024.xml.gz, https://www.ubereats.com/sitemap-store-771af823-023.xml.gz, https://www.ubereats.com/sitemap-store-771af823-022.xml.gz, https://www.ubereats.com/sitemap-store-771af823-021.xml.gz, https://www.ubereats.com/sitemap-store-771af823-020.xml.gz, https://www.ubereats.com/sitemap-store-771af823-019.xml.gz, https://www.ubereats.com/sitemap-store-771af823-018.xml.gz, https://www.ubereats.com/sitemap-store-771af823-017.xml.gz, https://www.ubereats.com/sitemap-store-771af823-016.xml.gz, https://www.ubereats.com/sitemap-store-771af823-015.xml.gz, https://www.ubereats.com/sitemap-store-771af823-014.xml.gz, https://www.ubereats.com/sitemap-store-771af823-013.xml.gz, https://www.ubereats.com/sitemap-store-771af823-012.xml.gz, https://www.ubereats.com/sitemap-store-771af823-011.xml.gz, https://www.ubereats.com/sitemap-store-771af823-010.xml.gz, https://www.ubereats.com/sitemap-store-771af823-009.xml.gz, https://www.ubereats.com/sitemap-store-771af823-008.xml.gz, https://www.ubereats.com/sitemap-store-771af823-007.xml.gz, https://www.ubereats.com/sitemap-store-771af823-006.xml.gz, https://www.ubereats.com/sitemap-store-771af823-005.xml.gz, https://www.ubereats.com/sitemap-store-771af823-004.xml.gz, https://www.ubereats.com/sitemap-store-771af823-003.xml.gz, https://www.ubereats.com/sitemap-store-771af823-002.xml.gz, https://www.ubereats.com/sitemap-store-771af823-001.xml.gz, https://www.ubereats.com/sitemap-store-771af823-000.xml.gz, https://www.ubereats.com/sitemap.xml, https://www.ubereats.com/sitemap_index.xml, https://www.ubereats.com/sitemap-index.xml.
Why it matters
Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.
Check name
Sitemap
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Publish a sitemap and reference it from robots.txt.
Result
Sitemap is missing or incomplete.
Evidence
{
"checked": [
"https://www.ubereats.com/sitemap-index-771af823.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-025.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-024.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-023.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-022.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-021.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-020.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-019.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-018.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-017.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-016.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-015.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-014.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-013.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-012.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-011.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-010.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-009.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-008.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-007.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-006.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-005.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-004.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-003.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-002.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-001.xml.gz",
"https://www.ubereats.com/sitemap-store-771af823-000.xml.gz",
"https://www.ubereats.com/sitemap.xml",
"https://www.ubereats.com/sitemap_index.xml",
"https://www.ubereats.com/sitemap-index.xml"
]
}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": "www.ubereats.com",
"probes": [
{
"name": "_index._agents.www.ubereats.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.www.ubereats.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": "www.ubereats.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
},
{
"name": "ubereats.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 0/100 and needs a fix.
10 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 0/100 and needs a fix.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: none.
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
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.
Result
GEO: Entity clarity scored 0/100 and needs a fix.
Evidence
{
"title": "",
"h1": "",
"description": "",
"topicOverlap": 0,
"topicTerms": [],
"descriptionTerms": [],
"missingFromDescription": [],
"score": 0,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 0/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Source and trust signals
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Source and trust signals scored 0/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": false,
"policyLinks": false
},
"missing": [
"author",
"publisher",
"freshnessDate",
"aboutOrContact",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [],
"privacyLinks": [],
"score": 0,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 0/100 and needs a fix.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks.
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
0/100
Status
fail
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 0/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": false,
"policyLinks": false
},
"missing": [
"author",
"publisher",
"freshnessDate",
"aboutOrContact",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [],
"privacyLinks": [],
"score": 0,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
Needs attention
AIO: Visible structured data match
Issue
No JSON-LD structured data was detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Visible structured data match
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Visible structured data match scored 0/100 and needs a fix.
Evidence
{
"schemaCount": 0,
"mismatches": [],
"score": 0,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 10/100 and needs a fix.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 10/100 and needs a fix.
Needs attention
AIO: Google eligibility and indexability
Issue
HTTP status is 410; Google AI features need an indexable 2xx page. Noindex directive found: noindex, nofollow. Canonical tag is missing.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Google eligibility and indexability
Score
10/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Google eligibility and indexability scored 10/100 and needs a fix.
Evidence
{
"status": 410,
"googlebotBlocked": false,
"metaRobotsTags": [
"noindex, nofollow"
],
"xRobotsTag": "",
"canonical": "",
"finalUrl": "https://www.ubereats.com/in",
"canonicalScore": 0,
"score": 10,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 15/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 15/100 and needs a fix.
Needs attention
AEO: Entity and definition clarity
Issue
AEO readiness is incomplete.
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
15/100
Status
fail
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 15/100 and needs a fix.
Evidence
{
"title": "",
"h1": "",
"description": "",
"topicOverlap": 0,
"definitionCount": 2,
"topicTerms": [],
"descriptionTerms": [],
"missingFromDescription": [],
"score": 15,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 25/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 25/100 and needs a fix.
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
25/100
Status
fail
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 25/100 and needs a fix.
Evidence
{
"candidatePassages": 1,
"citablePassages": 0,
"failingCandidateParagraphs": [],
"citableParagraphs": [],
"score": 25,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI crawler accessibility
GEO: AI crawler accessibility scored 55/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI crawler accessibility
GEO: AI crawler accessibility scored 55/100 and needs improvement.
Needs attention
GEO: AI crawler accessibility
Issue
Only 76 words of Chrome-rendered body text were detected. No rendered JSON-LD schema block was detected.
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: AI crawler accessibility
Score
55/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: AI crawler accessibility scored 55/100 and needs improvement.
Evidence
{
"textWords": 76,
"htmlBytes": 655592,
"robots": {
"checkedCrawlers": [
"gptbot",
"chatgpt-user",
"claudebot",
"perplexitybot",
"google-extended"
],
"blocked": [],
"allows": true
},
"schemaBlocks": 0,
"finalUrl": "https://www.ubereats.com/in",
"robotsExcerpt": "User-agent: *\nDisallow: */delivery-details\nDisallow: */search?\nDisallow: */select-language\n\nUser-agent: googlebot\nDisallow: */blog\nDisallow: */checkout\nDisallow: */closest\nDisallow: */delivery-details\nDisallow: */feed\nDisallow: */login-redirect/\nDisallow: */order\nDisallow: *恒博国际app下载*\nDisallow: /DC/\nDisallow: /JP-JP/\nDisallow: /_/defaults\nDisallow: /_/diagnostics\nDisallow: /_errors\nDisallow: /_events\nDisallow: /_p/api/getInstructionForLocationV1\nDisallow: /_p/api/getOrderEntitiesV1\nDisallow: /_p/api/getSessionElapseV1\nDisallow: /_p/api/setNupEventsV1\nDisallow: /_translations?\nDisallow: /ae/\nDisallow: /ar-AE/\nDisallow: /ar-AT/\nDisallow: /ar-AU/\nDisallow: /ar-AZ/\nDisallow: /ar-BE/\nDisallow: /ar-BG/\nDisallow: /ar-BR/\nDisallow: /ar-BY/\nDisallow: /ar-CA/\nDisallow: /ar-CL/\nDisallow: /ar-CN/\nDisa",
"score": 55,
"weight": 26
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/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, JSON-LD structured data.
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
60/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 60/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": true,
"definitionPatterns": 2,
"schemaBlocks": 0,
"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",
"JSON-LD structured data"
],
"score": 60,
"weight": 24
}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
AEO readiness is incomplete.
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": 0,
"questionH2s": [],
"hasFaq": true,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 80/100 and needs improvement.
Needs attention
AEO: Answer-first sections
Issue
AEO readiness is incomplete.
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
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-first sections scored 80/100 and needs improvement.
Evidence
{
"sectionCount": 0,
"passing": 0,
"failing": [],
"score": 80,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 70/100 and needs improvement.
Needs attention
AIO: Page experience for AIO
Issue
Only 76 words of visible rendered text were detected. 1 image(s) are missing width/height attributes.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Page experience for AIO
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Page experience for AIO scored 70/100 and needs improvement.
Evidence
{
"viewportContent": "width=device-width, initial-scale=1.0, maximum-scale=2.0",
"visibleWords": 76,
"htmlBytes": 655592,
"imagesMissingDimensions": [
{
"src": "/_static/29ed4bc0793fd578.svg",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"_bh _ae\" alt=\"Javascript disabled\" src=\"/_static/29ed4bc0793fd578.svg\">"
}
],
"possibleDialogs": [],
"score": 70,
"weight": 10
}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: what, how, benefits, 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": [],
"expected": [
{
"id": "what",
"label": "What is this page?",
"pattern": {}
},
{
"id": "how",
"label": "How does this page work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use this page?",
"pattern": {}
},
{
"id": "cost",
"label": "Is this page free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does this page compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is this page?",
"pattern": {}
},
{
"id": "how",
"label": "How does this page work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use this page?",
"pattern": {}
},
{
"id": "cost",
"label": "Is this page free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does this page compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 80/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 80/100 and needs improvement.
Needs attention
AIO: Answer block readiness
Issue
HTTP status is 410; Google AI features need an indexable 2xx page. Noindex directive found: noindex, nofollow. Canonical tag is missing.
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Answer block readiness
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Answer block readiness scored 80/100 and needs improvement.
Evidence
{
"sectionCount": 0,
"passing": 0,
"failing": [],
"score": 80,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 70/100 and needs improvement.
Needs attention
AEO: Extractable visible copy
Issue
Only 76 visible words were detected for answer extraction.
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: Extractable visible copy
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: Extractable visible copy scored 70/100 and needs improvement.
Evidence
{
"visibleWords": 76,
"schemaCount": 0,
"score": 70,
"weight": 6
}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/plain; charset=utf-8",
"length": 9
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/plain; charset=utf-8",
"length": 9
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 661464
}
]
},
"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."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Needs attention
AIO: Query intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Query intent coverage
Score
70/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Query intent coverage is informational for this page.
Evidence
{
"headings": [],
"expected": [
{
"id": "what",
"label": "What is this page?",
"pattern": {}
},
{
"id": "how",
"label": "How does this page work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use this page?",
"pattern": {}
},
{
"id": "cost",
"label": "Is this page free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does this page compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is this page?",
"pattern": {}
},
{
"id": "how",
"label": "How does this page work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use this page?",
"pattern": {}
},
{
"id": "cost",
"label": "Is this page free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does this page compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 4
}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 /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.
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 /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.
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": 661472,
"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 /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.",
"compatibleContentType": false,
"contentLength": 659065,
"hasRegisterInstructions": true,
"hasProtectedResourceLink": false,
"hasAuthorizationServerLink": false,
"mentionsIdentity": true,
"mentionsCredential": true,
"links": [
"/_static/client-legacy-main-003efd7b8601033e.js",
"/_static/client-legacy-main-f153b7fc5a17947c.css",
"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js",
"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js",
"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js",
"/_static/client-legacy-vendor-web-vitals-4772cf164a2ec700.js",
"/_static/client-legacy-vendor-url-6a4386ccabfd09bd.js",
"/_static/client-legacy-vendor-fusion-0b7793d1447a7ccb.js",
"/_static/client-legacy-vendor-styletron-react-8e45c05e35b2e23c.js",
"/_static/client-legacy-vendor-history-4770146359a90a0b.js"
],
"rawExcerpt": "<!doctype html><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"51a6fc9e-9eaa-4c6d-821a-4b8169da7f27\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"51a6fc9e-9eaa-4c6d-821a-4b8169da7f27\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"51a6fc9e-9eaa-4c6d-821a-4b8169da7f27\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"51a6fc9e-9eaa-4c6d-821a-4b8169da7f27\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"51a6fc9e-9eaa-4c6d-821a-4b8169da7f27\" as=\"script\"/><link rel=\"preload\" href=\"/"
}
},
"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 /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.",
"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": 655313,
"text": "<!doctype html><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-web-vitals-4772cf164a2ec700.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-url-6a4386ccabfd09bd.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-fusion-0b7793d1447a7ccb.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-styletron-react-8e45c05e35b2e23c.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-history-4770146359a90a0b.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-85233-1957accd76c55744.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-main-f153b7fc5a17947c.css\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-66392-b540f303c66e30c7.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-89933-37647b0f3579e525.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-10324-9383ff2273a08ef9.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-11061-4abed162abfe15cf.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-13068-a5ca8c1d6bb4c429.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-13102-0c366ec8e8531946.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-14364-c16976ba361ed5c5.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-15752-d3894dada04fff2f.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-16687-b336fbb6d3fd897e.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17083-f71be4adacb57f4d.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17288-e23ba5b3ce68ac07.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17662-a8a9d3a7ed42db78.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-18127-5e883e95fee037b3.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-25099-4312f9dabc0570bd.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-26147-1f7dafec15964032.js\" nonce=\"4658be19-79f3-4478-94a1-cf41f49c0dff\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-28844-b586980d9e06f244.j"
},
"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": 655273,
"text": "<!doctype html><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-web-vitals-4772cf164a2ec700.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-url-6a4386ccabfd09bd.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-fusion-0b7793d1447a7ccb.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-styletron-react-8e45c05e35b2e23c.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-history-4770146359a90a0b.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-85233-1957accd76c55744.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-main-f153b7fc5a17947c.css\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-66392-b540f303c66e30c7.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-89933-37647b0f3579e525.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-10324-9383ff2273a08ef9.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-11061-4abed162abfe15cf.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-13068-a5ca8c1d6bb4c429.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-13102-0c366ec8e8531946.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-14364-c16976ba361ed5c5.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-15752-d3894dada04fff2f.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-16687-b336fbb6d3fd897e.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17083-f71be4adacb57f4d.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17288-e23ba5b3ce68ac07.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-17662-a8a9d3a7ed42db78.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-18127-5e883e95fee037b3.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-25099-4312f9dabc0570bd.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-26147-1f7dafec15964032.js\" nonce=\"50366846-19a4-4b5f-a1d0-0e5bb4bce929\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-legacy-28844-b586980d9e06f244.j"
}
},
"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": 9,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "log in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"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": 655234
},
{
"path": "/.well-known/oauth-authorization-server",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 655279
}
]
},
"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": 9,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "log in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"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><html lang=\"en-US\" dir=\"ltr\"><head><meta charset=\"utf-8\" /><link rel=\"preload\" href=\"/_static/client-legacy-main-003efd7b8601033e.js\" nonce=\"31a8758c-a413-4d5d-a7ba-16b74b0a5f46\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-main-f153b7fc5a17947c.css\" nonce=\"31a8758c-a413-4d5d-a7ba-16b74b0a5f46\" as=\"style\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-core-1c2aea1bf8693e3c.js\" nonce=\"31a8758c-a413-4d5d-a7ba-16b74b0a5f46\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-lodash-2093cf5c472e9b0c.js\" nonce=\"31a8758c-a413-4d5d-a7ba-16b74b0a5f46\" as=\"script\"/><link rel=\"preload\" href=\"/_static/client-legacy-vendor-react-cdf2919afe9cc6c4.js\" nonce=\"31a8758c-a413-4d5d-a7ba-16b74b0a5f46\" as=\"script\"/><link rel=\"preload\" href=\"/"
},
"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://www.ubereats.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://www.ubereats.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.ubereats.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.ubereats.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": 9,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "log in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"resourceFetchSucceeded": false
}Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
Check name
Browser errors were logged to the console
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Fix guidance
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)
Evidence
{
"description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
Check name
Uses deprecated APIs
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Estimated savings
1 warning found
Fix guidance
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).
Evidence
{
"displayValue": "1 warning found",
"description": "Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/)."
}Performance and AccessibilityPerformanceBrowser audit
Image optimization
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Image optimization
Check name
Image optimization
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped image optimization checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "image-aspect-ratio",
"title": "Displays images with incorrect aspect ratio",
"score": 0
}
]
}Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
Check name
Legacy JavaScript
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 13 KiB
Fix guidance
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 13 KiB",
"description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
Check name
Reduce unused JavaScript
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 651 KiB
Fix guidance
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 651 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": 480
}SEOSEOBrowser audit
Document does not have a meta description
20 Fail
SEOSEOBrowser audit
Document does not have a meta description
Check name
Document does not have a meta description
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).
Evidence
{
"description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}SEOSEOBrowser audit
Document doesn't have a `<title>` element
20 Fail
SEOSEOBrowser audit
Document doesn't have a `<title>` element
Check name
Document doesn't have a `<title>` element
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. [Learn more about document titles](https://dequeuniversity.com/rules/axe/4.11/document-title).
Evidence
{
"description": "The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. [Learn more about document titles](https://dequeuniversity.com/rules/axe/4.11/document-title)."
}SEOSEOBrowser audit
Image elements do not have `[alt]` attributes
20 Fail
SEOSEOBrowser audit
Image elements do not have `[alt]` attributes
Check name
Image elements do not have `[alt]` attributes
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).
Evidence
{
"description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}SEOSEOBrowser audit
Page has unsuccessful HTTP status code
20 Fail
SEOSEOBrowser audit
Page has unsuccessful HTTP status code
Check name
Page has unsuccessful HTTP status code
Score
0/100
Status
fail
Device
desktop
Category
SEO
Estimated savings
410
Fix guidance
Pages with unsuccessful HTTP status codes may not be indexed properly. [Learn more about HTTP status codes](https://developer.chrome.com/docs/lighthouse/seo/http-status-code/).
Evidence
{
"displayValue": "410",
"description": "Pages with unsuccessful HTTP status codes may not be indexed properly. [Learn more about HTTP status codes](https://developer.chrome.com/docs/lighthouse/seo/http-status-code/)."
}SEOSEOBrowser audit
Page is blocked from indexing
20 Fail
SEOSEOBrowser audit
Page is blocked from indexing
Check name
Page is blocked from indexing
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Search engines are unable to include your pages in search results if they don't have permission to crawl them. [Learn more about crawler directives](https://developer.chrome.com/docs/lighthouse/seo/is-crawlable/).
Evidence
{
"description": "Search engines are unable to include your pages in search results if they don't have permission to crawl them. [Learn more about crawler directives](https://developer.chrome.com/docs/lighthouse/seo/is-crawlable/)."
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
8 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
67/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 27,
"displayValue": "520 ms",
"numericValue": 516.5
},
{
"id": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "0 ms",
"numericValue": 0.8999999999999999
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 30 ms",
"numericValue": 32
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 81,
"displayValue": "1.6 s",
"numericValue": 1561
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 10,
"displayValue": "470 ms",
"numericValue": 468
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 75,
"displayValue": "1.6 s",
"numericValue": 1641
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 91,
"displayValue": "2.3 s",
"numericValue": 2346
},
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 52,
"displayValue": "1.6 s",
"numericValue": 1561
}
]
}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 |
|---|---|---|---|
| 43/100 | Level 2, Agent-Limited | Current report |