Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 26 out of 100
- Agent Ease of Use 4 out of 100
- Security & Trust 40 out of 100
- GEO, AIO and AEO 75 out of 100
- SEO 92 out of 100
- Performance and Accessibility 81 out of 100
What AI sees of your website
Secure, AI-Powered Content Management, Workflow & Collaboration
Intelligent Content Management makes it easy to automate workflows, collaborate internally and externally, and protect your sensitive data, all on one platform.
Next step
Turn this report into a fix workflow
27 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 | 26 | Priority fix | 4 | 18 | 1 | View details |
| Discoverability | 29 | Priority fix | 2 | 7 | 0 | View details |
| Content Readiness | 42 | Priority fix | 2 | 7 | 1 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 4 | Priority fix | 7 | 25 | 2 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 3 | 5 | 0 | View details |
| MCP | 13 | Priority fix | 0 | 6 | 2 | View details |
| Skill Discovery | 0 | Priority fix | 0 | 8 | 0 | View details |
| Agent Commerce | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| GEO, AIO and AEO | 75 | Mostly ready | 5 | 2 | 12 | View details |
| GEO Readiness | 86 | Mostly ready | 1 | 0 | 4 | |
| AIO Readiness | 77 | Mostly ready | 3 | 1 | 3 | View details |
| AEO Readiness | 63 | Needs work | 1 | 1 | 5 | View details |
| SEO | 92 | Strong | 10 | 1 | 0 | View details |
| SEO | 92 | Strong | 10 | 1 | 0 | View details |
| Security & Trust | 40 | Priority fix | 6 | 3 | 0 | View details |
| Security & Trust | 40 | Priority fix | 2 | 3 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 81 | Mostly ready | 19 | 4 | 3 | View details |
| Performance | 71 | Needs work | 13 | 3 | 3 | View details |
| Accessibility | 99 | Strong | 6 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
52 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"
},
"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": "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
},
"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."
}
]
}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": 403,
"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\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-v9kfGw7EWeFDgpPScqERVA' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
},
{
"path": "/openapi.yaml",
"statusCode": 403,
"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\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-2fInSwFjhHrmehml22X52H' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
},
{
"path": "/swagger.json",
"statusCode": 403,
"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\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-xbd0bDpaKK0oIzL2VHhzB5' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
},
{
"path": "/swagger.yaml",
"statusCode": 403,
"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\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-eipT6STrJ39cWe3HNaLHYQ' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": ""
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": ""
},
{
"path": "/docs/openapi.json",
"statusCode": 403,
"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\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-MFNP6q65y11aeBGPPWomU9' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
}
]
},
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
}
]
}AI 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
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
33 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": "default-src * 'self' blob: data: 'unsafe-inline'; font-src 'self' data: fonts.googleapis.com fonts.gstatic.com"
}Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
33 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
Needs attention
HSTS header
Issue
HSTS header is missing or incomplete.
Why it matters
HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade and mixed-transport risk for repeat users.
Check name
HSTS header
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat visits with Strict-Transport-Security.
Result
HSTS header is missing or incomplete.
Evidence
{
"header": "strict-transport-security",
"value": "max-age=2592000; includeSubDomains; preload"
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
33 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 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",
"length": 146
}
]
},
"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 UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
25 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",
"length": 146
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
},
{
"path": "/agent-card.json",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5490
}
]
},
"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".
25 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",
"length": 146
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
}
]
},
"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".
25 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",
"length": 146
},
{
"path": "/agent.json",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5475
}
]
},
"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".
25 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",
"length": 146
},
{
"path": "/agents.json",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5478
}
]
},
"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 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": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5447
},
{
"path": "/llms-full.txt",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5484
}
]
},
"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 "Cookie,Box-Country,X-Box-Geo-Country,X-Frame-Options,Accept-Encoding".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html; charset=UTF-8"
},
"issue": "Content-Type \"text/html; charset=UTF-8\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "Cookie,Box-Country,X-Box-Geo-Country,X-Frame-Options,Accept-Encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Cookie,Box-Country,X-Box-Geo-Country,X-Frame-Options,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": 51705,
"excerpt": "<!DOCTYPE html>\n<html lang=\"en\" dir=\"ltr\" prefix=\"og: https://ogp.me/ns#\">\n <head>\n <meta charset=\"utf-8\" />\n<script type=\"text/javascript\">/*! js-cookie v2.2.1 | MIT */\n\n!function(a){var b;if(\"function\"==typeof define&&define.amd&&(def",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
25 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",
"length": 146
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
}
]
},
"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".
25 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": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5447
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 146
}
]
},
"issue": "mcp.json was not found at the expected path.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: skipped heading levels; 1 links missing accessible names.
Details
Why it matters
Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.
Check name
Semantic HTML
Score
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": true,
"meaningfulH1": true,
"headingOrder": false,
"accessibleLinks": false,
"accessibleButtons": true,
"imageAltCoverage": true,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [
"<a id=\"main-content\" tabindex=\"-1\"></a>"
],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [],
"skippedHeadingLevels": [
"h1: Content + AI",
"h3: Intelligent content management, secure collaboration, and agentic workflow",
"h4: Collaborate easily and securely",
"h4: Get AI insights from content",
"h4: Extract critical data at scale",
"h4: Automate with AI agents",
"h4: Protect all your content",
"h4: Build with AI-native APIs",
"h4: Power seamless e-signatures",
"h3: One secure, intelligent platform with 1,500+ app integrations",
"h3: Named a Leader by independent analyst firms",
"h3: Learn more about Content + AI",
"h5: Make your content smarter",
"h5: Dive into Intelligent Content Management",
"h5: Watch the BoxWorks keynote"
]
},
"counts": {
"h1": 1,
"headings": 15,
"links": 196,
"inaccessibleLinks": 1,
"buttons": 13,
"inaccessibleButtons": 0,
"images": 112,
"imagesWithAlt": 112,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 0
}
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
25 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",
"length": 146
},
{
"path": "/webmcp.json",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5478
},
{
"path": "/mcp.json",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5447
}
]
},
"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 DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
Needs attention
FAQPage schema
Issue
FAQ content was detected but no FAQPage schema was found.
Why it matters
FAQPage schema lets agents extract visible question-and-answer content cleanly and avoid guessing which text is an answer.
Check name
FAQPage schema
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose question-and-answer content in FAQPage structured data when FAQs are present.
Result
FAQPage schema is missing or incomplete.
Evidence
{
"found": false,
"visibleFaq": true,
"allTypes": [
"Organization"
]
}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": [
"Organization"
]
}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": [
{
"url": "//assets.box.com",
"rel": "preconnect"
}
]
},
"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
robots.txt
robots.txt is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
robots.txt
robots.txt is missing or incomplete.
Needs attention
robots.txt
Issue
Failed to fetch /robots.txt (Status: 403).
Why it matters
robots.txt gives crawlers and agents a standard place to read crawl permissions, disallowed paths, and sitemap locations before requesting site content.
Check name
robots.txt
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Publish /robots.txt with clear crawl rules.
Result
robots.txt is missing or incomplete.
Evidence
{
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"parsedUserAgents": [],
"sitemapDirectives": [],
"rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-8CDndJ3szJaiIIhwEbRG18' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare."
}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.box.com/sitemap.xml, https://www.box.com/sitemap_index.xml, https://www.box.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.box.com/sitemap.xml",
"https://www.box.com/sitemap_index.xml",
"https://www.box.com/sitemap-index.xml"
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
13 Warning
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD.
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
50/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is partially implemented.
Evidence
{
"lastModified": "Fri, 05 Jun 2026 22:09:04 GMT",
"schemaDates": [],
"metaDateCount": 2,
"timeDateCount": 0
}Agent Ease of UseMCPInformational
WebMCP
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
13 Warning
Agent Ease of UseMCPInformational
WebMCP
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
Needs attention
WebMCP
Issue
WebMCP declarative annotations need fixes.
Details
Why it matters
WebMCP can expose page context and actions directly through the browser, giving agents safer structured hooks than screen scraping alone.
Check name
WebMCP
Score
50/100
Status
warning
Category
MCP
Maturity
Informational
Goal
Support WebMCP to expose site tools to AI agents via the browser.
Result
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
Validation steps
Detect data-mcp-tool annotations
No data-mcp-tool attributes were found on interactive elements.
Detect WebMCP declarative tags
No elements found with tool-name or tool-description attributes.
Validate WebMCP declarative annotation quality
WebMCP declarative annotations need fixes.
WebMCP declarative annotation issues
<select> is missing a name attribute.<select> is missing tool-param-description.
Detect WebMCP imperative API usage
navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.
Detect WebMCP browser navigator injection
navigator.modelContext was not detected in the rendered browser page.
Interactive surface coverage
Only 0% of interactive surfaces are annotated.
Evidence
{
"failedStep": "declarative-annotation-quality",
"steps": [
{
"id": "data-mcp-tool-attributes",
"title": "Detect data-mcp-tool annotations",
"status": "informational",
"evidence": {
"dataMcpToolCount": 0,
"dataMcpTools": []
},
"issue": "No data-mcp-tool attributes were found on interactive elements.",
"howToFix": "Add data-mcp-tool attributes to high-value forms, buttons, and links so generic MCP-aware tooling can identify intended actions."
},
{
"id": "declarative-tags",
"title": "Detect WebMCP declarative tags",
"status": "informational",
"evidence": {
"totalForms": 0,
"formsWithTags": 0,
"totalInteractive": 209,
"interactiveWithTags": 0,
"totalCount": 209,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<select> is missing a name attribute.",
"<select> is missing tool-param-description."
]
},
"issue": "No elements found with tool-name or tool-description attributes.",
"howToFix": "Add tool-name and tool-description attributes to forms and interactive elements."
},
{
"id": "declarative-annotation-quality",
"title": "Validate WebMCP declarative annotation quality",
"status": "warning",
"evidence": {
"issueCount": 2,
"issues": [
"<select> is missing a name attribute.",
"<select> is missing tool-param-description."
]
},
"issue": "WebMCP declarative annotations need fixes.",
"issueDetails": [
{
"title": "WebMCP declarative annotation issues",
"items": [
{
"type": "code",
"value": "<select> is missing a name attribute."
},
{
"type": "code",
"value": "<select> is missing tool-param-description."
}
]
}
],
"howToFix": "Use snake_case tool-name values, descriptive tool-description values, named and labeled fields, and tool-param-description on inputs."
},
{
"id": "imperative-api",
"title": "Detect WebMCP imperative API usage",
"status": "informational",
"evidence": {
"staticSignals": {
"detected": false,
"matched": []
},
"browser": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
},
"issue": "navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.",
"howToFix": "Use navigator.modelContext.provideContext() to register tools programmatically."
},
{
"id": "browser-navigator-injection",
"title": "Detect WebMCP browser navigator injection",
"status": "informational",
"evidence": {
"browser": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
},
"issue": "navigator.modelContext was not detected in the rendered browser page.",
"howToFix": "Expose WebMCP through navigator.modelContext in the browser runtime when the page is intended to provide in-page tools."
},
{
"id": "surface-coverage",
"title": "Interactive surface coverage",
"status": "informational",
"evidence": {
"totalForms": 0,
"formsWithTags": 0,
"totalInteractive": 209,
"interactiveWithTags": 0,
"totalCount": 209,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<select> is missing a name attribute.",
"<select> is missing tool-param-description."
]
},
"issue": "Only 0% of interactive surfaces are annotated.",
"howToFix": "Add WebMCP annotations to all forms and interactive elements to increase agent coverage."
}
],
"staticSignals": {
"detected": false,
"matched": []
},
"coverage": {
"totalForms": 0,
"formsWithTags": 0,
"totalInteractive": 209,
"interactiveWithTags": 0,
"totalCount": 209,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<select> is missing a name attribute.",
"<select> is missing tool-param-description."
]
},
"browserWebMcp": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 40/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 40/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate.
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
40/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 40/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"author",
"publisher",
"freshnessDate"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [
{
"href": "/about-us/contact-us",
"text": "Contact",
"html": "<a href=\"/about-us/contact-us\" aria-label=\"Contact\" tabindex=\"0\" class=\"main-nav--primary-item\" data-menu-id=\"556\"> Contact </a>"
},
{
"href": "/about-us",
"text": "About Us",
"html": "<a href=\"/about-us\">About Us</a>"
},
{
"href": "/about-us/leadership",
"text": "Leadership",
"html": "<a href=\"/about-us/leadership\">Leadership</a>"
},
{
"href": "/about-us/esg",
"text": "ESG",
"html": "<a href=\"/about-us/esg\">ESG</a>"
},
{
"href": "/about-us/press",
"text": "Press",
"html": "<a href=\"/about-us/press\">Press</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
}
],
"contactLinks": [
{
"href": "/customer-success/support-services",
"text": "Product SupportKeep business moving",
"html": "<a href=\"/customer-success/support-services\"><span class=\"svg-icon\"><img loading=\"lazy\" data-nav-deferred=\"1\" fetchpriority=\"low\" alt data-src=\"/sites/default/files/2026-04/nav-solutions-services-Product-Support.svg\"></span><div><span class=\"main-nav--child-item--title\">Product Support</span><span class=\"main-nav--child-item--description\"><p>Keep business moving</p></span></div></a>"
},
{
"href": "https://support.box.com/hc/en-us",
"text": "Support",
"html": "<a href=\"https://support.box.com/hc/en-us\" target=\"_blank\" rel=\"noreferrer\"><span class=\"svg-icon\"><img loading=\"lazy\" data-nav-deferred=\"1\" fetchpriority=\"low\" alt data-src=\"/sites/default/files/2026-04/nav-resources-support-Support.svg\"></span><div><span class=\"main-nav--child-item--title\">Support</span></div></a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact",
"html": "<a href=\"/about-us/contact-us\" aria-label=\"Contact\" tabindex=\"0\" class=\"main-nav--primary-item\" data-menu-id=\"556\"> Contact </a>"
},
{
"href": "/quote",
"text": "Contact us",
"html": "<a class=\"button-secondary\" href=\"/quote\"> Contact us </a>"
},
{
"href": "/customer-success/support-services",
"text": "Product Support",
"html": "<a href=\"/customer-success/support-services\">Product Support</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
},
{
"href": "/customer-success/support-services",
"text": "Service & Support",
"html": "<a href=\"/customer-success/support-services\">Service & Support</a>"
},
{
"href": "https://support.box.com/hc/en-us/requests/new",
"text": "Tech Support",
"html": "<a href=\"https://support.box.com/hc/en-us/requests/new\">Tech Support</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
}
],
"privacyLinks": [
{
"href": "/privacyineurope",
"text": "GDPR Compliance",
"html": "<a href=\"/privacyineurope\">GDPR Compliance</a>"
},
{
"href": "/legal/termsofservice",
"text": "Terms of Service",
"html": "<a href=\"/legal/termsofservice\">Terms of Service</a>"
},
{
"href": "/legal/privacypolicy",
"text": "Privacy Policy",
"html": "<a href=\"/legal/privacypolicy\">Privacy Policy</a>"
}
],
"score": 40,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 40/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 40/100 and needs a fix.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: author, publisher, freshnessDate.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer evidence and trust
Score
40/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 40/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"author",
"publisher",
"freshnessDate"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [
{
"href": "/about-us/contact-us",
"text": "Contact",
"html": "<a href=\"/about-us/contact-us\" aria-label=\"Contact\" tabindex=\"0\" class=\"main-nav--primary-item\" data-menu-id=\"556\"> Contact </a>"
},
{
"href": "/about-us",
"text": "About Us",
"html": "<a href=\"/about-us\">About Us</a>"
},
{
"href": "/about-us/leadership",
"text": "Leadership",
"html": "<a href=\"/about-us/leadership\">Leadership</a>"
},
{
"href": "/about-us/esg",
"text": "ESG",
"html": "<a href=\"/about-us/esg\">ESG</a>"
},
{
"href": "/about-us/press",
"text": "Press",
"html": "<a href=\"/about-us/press\">Press</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
}
],
"contactLinks": [
{
"href": "/customer-success/support-services",
"text": "Product SupportKeep business moving",
"html": "<a href=\"/customer-success/support-services\"><span class=\"svg-icon\"><img loading=\"lazy\" data-nav-deferred=\"1\" fetchpriority=\"low\" alt data-src=\"/sites/default/files/2026-04/nav-solutions-services-Product-Support.svg\"></span><div><span class=\"main-nav--child-item--title\">Product Support</span><span class=\"main-nav--child-item--description\"><p>Keep business moving</p></span></div></a>"
},
{
"href": "https://support.box.com/hc/en-us",
"text": "Support",
"html": "<a href=\"https://support.box.com/hc/en-us\" target=\"_blank\" rel=\"noreferrer\"><span class=\"svg-icon\"><img loading=\"lazy\" data-nav-deferred=\"1\" fetchpriority=\"low\" alt data-src=\"/sites/default/files/2026-04/nav-resources-support-Support.svg\"></span><div><span class=\"main-nav--child-item--title\">Support</span></div></a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact",
"html": "<a href=\"/about-us/contact-us\" aria-label=\"Contact\" tabindex=\"0\" class=\"main-nav--primary-item\" data-menu-id=\"556\"> Contact </a>"
},
{
"href": "/quote",
"text": "Contact us",
"html": "<a class=\"button-secondary\" href=\"/quote\"> Contact us </a>"
},
{
"href": "/customer-success/support-services",
"text": "Product Support",
"html": "<a href=\"/customer-success/support-services\">Product Support</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
},
{
"href": "/customer-success/support-services",
"text": "Service & Support",
"html": "<a href=\"/customer-success/support-services\">Service & Support</a>"
},
{
"href": "https://support.box.com/hc/en-us/requests/new",
"text": "Tech Support",
"html": "<a href=\"https://support.box.com/hc/en-us/requests/new\">Tech Support</a>"
},
{
"href": "/about-us/contact-us",
"text": "Contact Us",
"html": "<a href=\"/about-us/contact-us\">Contact Us</a>"
}
],
"privacyLinks": [
{
"href": "/privacyineurope",
"text": "GDPR Compliance",
"html": "<a href=\"/privacyineurope\">GDPR Compliance</a>"
},
{
"href": "/legal/termsofservice",
"text": "Terms of Service",
"html": "<a href=\"/legal/termsofservice\">Terms of Service</a>"
},
{
"href": "/legal/privacypolicy",
"text": "Privacy Policy",
"html": "<a href=\"/legal/privacypolicy\">Privacy Policy</a>"
}
],
"score": 40,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
Needs attention
AEO: Answer-first sections
Issue
4 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer-first sections
Score
65/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer-first sections scored 65/100 and needs improvement.
Evidence
{
"sectionCount": 4,
"passing": 0,
"failing": [
{
"heading": "Intelligent content management, secure collaboration, and agentic workflow",
"headingHtml": "<h3 style=\"--count:74\"><span class=\"gradient-text\" style=\"background-image:linear-gradient(90deg, #EA0DDC, #307CF2);\">Intelligent</span> content management, secure collaboration, and agentic workflow</h3>",
"firstParagraph": "Trusted by the world’s leading organizations. See customers",
"paragraphHtml": "<p class=\"large-type\">Trusted by the world’s leading organizations. <a href=\"/customers\">See customers</a></p>",
"words": 9,
"direct": false,
"issue": "First paragraph is 9 words and does not look like a concise direct answer."
},
{
"heading": "One secure, intelligent platform with 1,500+ app integrations",
"headingHtml": "<h3>One secure, <span class=\"gradient-text\" style=\"background-image:linear-gradient(90deg, #FE01DA, #076FEB);\">intelligent</span> platform with 1,500+ app integrations</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Named a Leader by independent analyst firms",
"headingHtml": "<h3>Named a Leader by independent analyst firms</h3>",
"firstParagraph": "Discover why Box was named a Leader based on our “Ability to Execute” and “Completeness of Vision.”",
"paragraphHtml": "<p>Discover why Box was named a Leader based on our “Ability to Execute” and “Completeness of Vision.”</p>",
"words": 17,
"direct": false,
"issue": "First paragraph is 17 words and does not look like a concise direct answer."
},
{
"heading": "Learn more about Content + AI",
"headingHtml": "<h3>Learn more about Content + AI</h3>",
"firstParagraph": "Hear from thought leaders about the power of combining AI with unstructured data.",
"paragraphHtml": "<p>Hear from thought leaders about the power of combining AI with unstructured data.</p>",
"words": 13,
"direct": false,
"issue": "First paragraph is 13 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
No question-led h2 sections or FAQ pattern was detected.
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: 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": false,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 80/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 80/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: secure, powered, workflow, collaboration.
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
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Entity clarity scored 80/100 and needs improvement.
Evidence
{
"title": "Secure, AI-Powered Content Management, Workflow & Collaboration",
"h1": "Content + AI",
"description": "Intelligent Content Management makes it easy to automate workflows, collaborate internally and externally, and protect your sensitive data, all on one platform.",
"topicOverlap": 0.3333333333333333,
"topicTerms": [
"secure",
"powered",
"content",
"management",
"workflow",
"collaboration"
],
"descriptionTerms": [
"intelligent",
"content",
"management",
"makes",
"easy",
"automate",
"workflows",
"collaborate",
"internally",
"externally",
"protect",
"sensitive",
"data",
"all",
"one",
"platform"
],
"missingFromDescription": [
"secure",
"powered",
"workflow",
"collaboration"
],
"score": 80,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
Needs attention
AIO: Google eligibility and indexability
Issue
Canonical does not self-reference the scanned page.
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
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: Google eligibility and indexability scored 80/100 and needs improvement.
Evidence
{
"status": 200,
"googlebotBlocked": false,
"metaRobotsTags": [],
"xRobotsTag": "",
"canonical": "https://www.box.com/home",
"finalUrl": "https://www.box.com/",
"canonicalScore": 60,
"score": 80,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
Needs attention
GEO: Explanatory content depth
Issue
5 explanatory paragraph(s) could be stronger for citation or AI extraction.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 5,
"citablePassages": 0,
"failingCandidateParagraphs": [
{
"index": 39,
"heading": "H4: Collaborate easily and securely",
"text": "Sales presentations, product specs, employee handbooks: Unstructured data is at the center of how you work. Access, share, edit, and co-create content with AI while accelerating productivity. Enterprise-grade security and compliance ensure sensitive data stays protected as teams work together from anywhere, inside or outside your organization.",
"words": 47,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (47 words; target 80-220)."
],
"html": "<p class=\"large-type\">Sales presentations, product specs, employee handbooks: Unstructured data is at the center of how you work. Access, share, edit, and co-create content with AI while accelerating productivity. Enterprise-grade <a href=\"/security-compliance\" data-entity-substitution=\"canonical\">security and compliance</a> ensure sensitive data stays protected as teams work together from anywhere, inside or outside your organization.</p>"
},
{
"index": 40,
"heading": "H4: Get AI insights from content",
"text": "Harness the value of unstructured data like lease agreements and finance documents, and get instant insights from any amount of content across your enterprise. Box AI lets you seamlessly tap into leading AI models from OpenAI, Anthropic, and Google for real-time summaries, deep analysis, and smart recommendations.",
"words": 47,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (47 words; target 80-220)."
],
"html": "<p class=\"large-type\">Harness the value of unstructured data like lease agreements and finance documents, and get instant insights from <a href=\"/hubs\" data-entity-substitution=\"canonical\">any amount of content</a> across your enterprise. Box AI lets you seamlessly tap into leading AI models from OpenAI, Anthropic, and Google for real-time summaries, deep analysis, and smart recommendations.</p>"
},
{
"index": 43,
"heading": "H4: Protect all your content",
"text": "Safeguard sensitive data with AI-driven security that detects and mitigates threats in real time. Get deep learning-based malware detection and timely alerts about unusual activity, plus automated classification and granular access controls that protect your data at scale. Meet requirements like GDPR, HIPAA, and FINRA with built-in compliance tools.",
"words": 49,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (49 words; target 80-220)."
],
"html": "<p class=\"large-type\">Safeguard sensitive data with AI-driven security that detects and mitigates threats in real time. Get deep learning-based malware detection and timely alerts about unusual activity, plus automated classification and granular access controls that protect your data at scale. Meet requirements like GDPR, HIPAA, and FINRA with built-in compliance tools.</p>"
},
{
"index": 44,
"heading": "H4: Build with AI-native APIs",
"text": "Our Intelligent Content Management platform provides seamless collaboration, content security, and AI capabilities that empower developers to build, customize, and integrate across their apps. Deliver AI-powered insights, along with exceptional user and agentic experiences, and customize agents to streamline workflows with Box AI Studio.",
"words": 44,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (44 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"large-type\">Our Intelligent Content Management platform provides seamless collaboration, content security, and AI capabilities that empower developers to build, customize, and integrate across their apps. Deliver AI-powered insights, along with exceptional user and agentic experiences, and customize agents to streamline workflows with Box AI Studio.</p>"
},
{
"index": 45,
"heading": "H4: Power seamless e-signatures",
"text": "Close deals and onboard talent faster. With a solution that’s built right where your content lives, you can stop jumping from emails to e-signature apps. AI-driven e-signature workflows let you sign, approve, and track documents directly within your content ecosystem. Automate requests and follow-ups, ensuring nothing falls through the cracks. Best of all, get unlimited e-signatures for free to streamline work wit...",
"words": 65,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (65 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"large-type\">Close deals and onboard talent faster. With a solution that’s built right where your content lives, you can stop jumping from emails to e-signature apps. AI-driven e-signature workflows let you sign, approve, and track documents directly within your content ecosystem. Automate requests and follow-ups, ensuring nothing falls through the cracks. Best of all, get unlimited e-signatures for free to streamline work without added costs.</p>"
}
],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 65/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 65/100 and needs improvement.
Needs attention
AIO: Answer block readiness
Issue
4 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
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: Answer block readiness
Score
65/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 65/100 and needs improvement.
Evidence
{
"sectionCount": 4,
"passing": 0,
"failing": [
{
"heading": "Intelligent content management, secure collaboration, and agentic workflow",
"headingHtml": "<h3 style=\"--count:74\"><span class=\"gradient-text\" style=\"background-image:linear-gradient(90deg, #EA0DDC, #307CF2);\">Intelligent</span> content management, secure collaboration, and agentic workflow</h3>",
"firstParagraph": "Trusted by the world’s leading organizations. See customers",
"paragraphHtml": "<p class=\"large-type\">Trusted by the world’s leading organizations. <a href=\"/customers\">See customers</a></p>",
"words": 9,
"direct": false,
"issue": "First paragraph is 9 words and does not look like a concise direct answer."
},
{
"heading": "One secure, intelligent platform with 1,500+ app integrations",
"headingHtml": "<h3>One secure, <span class=\"gradient-text\" style=\"background-image:linear-gradient(90deg, #FE01DA, #076FEB);\">intelligent</span> platform with 1,500+ app integrations</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Named a Leader by independent analyst firms",
"headingHtml": "<h3>Named a Leader by independent analyst firms</h3>",
"firstParagraph": "Discover why Box was named a Leader based on our “Ability to Execute” and “Completeness of Vision.”",
"paragraphHtml": "<p>Discover why Box was named a Leader based on our “Ability to Execute” and “Completeness of Vision.”</p>",
"words": 17,
"direct": false,
"issue": "First paragraph is 17 words and does not look like a concise direct answer."
},
{
"heading": "Learn more about Content + AI",
"headingHtml": "<h3>Learn more about Content + AI</h3>",
"firstParagraph": "Hear from thought leaders about the power of combining AI with unstructured data.",
"paragraphHtml": "<p>Hear from thought leaders about the power of combining AI with unstructured data.</p>",
"words": 13,
"direct": false,
"issue": "First paragraph is 13 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": false,
"definitionPatterns": 3,
"schemaBlocks": 1,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process",
"optional visible FAQ or FAQPage schema"
],
"score": 85,
"weight": 24
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 83/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 83/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: secure, powered, workflow, collaboration.
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
83/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Entity and definition clarity scored 83/100 and needs improvement.
Evidence
{
"title": "Secure, AI-Powered Content Management, Workflow & Collaboration",
"h1": "Content + AI",
"description": "Intelligent Content Management makes it easy to automate workflows, collaborate internally and externally, and protect your sensitive data, all on one platform.",
"topicOverlap": 0.3333333333333333,
"definitionCount": 3,
"topicTerms": [
"secure",
"powered",
"content",
"management",
"workflow",
"collaboration"
],
"descriptionTerms": [
"intelligent",
"content",
"management",
"makes",
"easy",
"automate",
"workflows",
"collaborate",
"internally",
"externally",
"protect",
"sensitive",
"data",
"all",
"one",
"platform"
],
"missingFromDescription": [
"secure",
"powered",
"workflow",
"collaboration"
],
"score": 83,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: 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 Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Secure, AI-Powered Content Management, Workfl... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Secure, AI-Powered Content Management, Workfl... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Secure, AI-Powered Content Management, Workfl... compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Secure, AI-Powered Content Management, Workfl... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Secure, AI-Powered Content Management, Workfl... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Secure, AI-Powered Content Management, Workfl... compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"length": 0
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"length": 0
},
{
"path": "/context",
"statusCode": 403,
"contentType": "text/html; charset=UTF-8",
"length": 5382
}
]
},
"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 Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Secure, AI-Powered Content Management, Workfl... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Secure, AI-Powered Content Management, Workfl... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Secure, AI-Powered Content Management, Workfl... compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Secure, AI-Powered Content Management, Workfl... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Secure, AI-Powered Content Management, Workfl...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Secure, AI-Powered Content Management, Workfl... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Secure, AI-Powered Content Management, Workfl... compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 4
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Needs attention
GEO: Q&A and FAQ opportunities
Issue
No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.
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: Q&A and FAQ opportunities
Score
75/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Q&A and FAQ opportunities is informational for this page.
Evidence
{
"h2Count": 0,
"questionH2s": 0,
"hasFaq": false,
"nonQuestionH2s": [],
"score": 75,
"weight": 4
}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 Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{"field":"jwks_uri","issue":"Missing URL."}].
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
Validate resource body
OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{"field":"jwks_uri","issue":"Missing URL."}].
Probe authorization endpoint with an authorization-code request
authorization_endpoint did not behave like an operational OAuth authorization endpoint.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/oauth-authorization-server",
"statusCode": 200,
"contentType": "application/json"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"issue": "OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{\"field\":\"jwks_uri\",\"issue\":\"Missing URL.\"}].",
"compatibleContentType": true,
"missing": [
"jwks_uri"
],
"endpointIssues": [
{
"field": "jwks_uri",
"issue": "Missing URL."
}
],
"issuer": "https://api.box.com",
"authorizationEndpoint": "https://account.box.com/api/oauth2/authorize",
"tokenEndpoint": "https://api.box.com/oauth2/token",
"responseTypesSupported": [
"code"
],
"grantTypesSupported": [
"authorization_code",
"refresh_token"
],
"idTokenSigningAlgValuesSupported": [],
"rawExcerpt": "{\n \"issuer\": \"https://api.box.com\",\n \"authorization_endpoint\": \"https://account.box.com/api/oauth2/authorize\",\n \"token_endpoint\": \"https://api.box.com/oauth2/token\",\n \"response_types_supported\": [\"code\"],\n \"grant_types_supported\": [\"authorization_code\", \"refresh_token\"],\n \"token_endpoint_auth_methods_supported\": [\n \"client_secret_basic\",\n \"client_secret_post\"\n ],\n \"revocation_endpoint\": \"https://api.box.com/oauth2/revoke\",\n \"revocation_endpoint_auth_methods_supported\": [\n \"client_secret_basic\",\n \"client_secret_post\"\n ],\n \"code_challenge_methods_supported\": [\"S256\"],\n \"service_documentation\": \"https://developer.box.com/guides/authentication/\",\n \"op_policy_uri\": \"https://www.box.com/legal/termsofservice\",\n \"op_tos_uri\": \"https://www.box.com/legal/termsofservice\"\n}"
},
"issue": "OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{\"field\":\"jwks_uri\",\"issue\":\"Missing URL.\"}].",
"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."
},
{
"id": "authorization-endpoint",
"title": "Probe authorization endpoint with an authorization-code request",
"status": "fail",
"evidence": {
"url": "https://account.box.com/api/oauth2/authorize?response_type=code&client_id=can-agent-use-scanner&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Foauth%2Fcallback&scope=openid&state=can-agent-use-probe",
"method": "GET",
"statusCode": 200,
"location": null,
"contentType": "text/html; charset=UTF-8",
"excerpt": " <!DOCTYPE html><html lang=\"en-US\" data-resin-client=\"web\"><head><meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"> <meta name=\"robots\" content=\"noindex, nofollow\"> <title>Box</title> <link rel=\"preload\" href=\"https://cdn01"
},
"issue": "authorization_endpoint did not behave like an operational OAuth authorization endpoint.",
"howToFix": "Implement an authorization endpoint that can process syntactically valid authorization requests, or remove it from discovery metadata until it exists."
},
{
"id": "authorization-redirect-safety",
"title": "Reject unregistered authorization redirects",
"status": "pass",
"evidence": {
"url": "https://account.box.com/api/oauth2/authorize?response_type=code&client_id=can-agent-use-unknown-client&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Fattacker-callback&scope=openid&state=can-agent-use-redirect-safety",
"method": "GET",
"statusCode": 200,
"location": null,
"redirectedToUntrusted": false,
"contentType": "text/html; charset=UTF-8",
"excerpt": " <!DOCTYPE html><html lang=\"en-US\" data-resin-client=\"web\"><head><meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"> <meta name=\"robots\" content=\"noindex, nofollow\"> <title>Box</title> <link rel=\"preload\" href=\"https://cdn01"
},
"howToFix": "Validate client_id and registered redirect_uri values before redirecting. Return a direct OAuth error for invalid clients or redirect URIs."
},
{
"id": "token-endpoint",
"title": "Probe token endpoint with advertised grant type",
"status": "pass",
"evidence": {
"url": "https://api.box.com/oauth2/token",
"method": "POST",
"grantType": "authorization_code",
"statusCode": 400,
"oauthError": "invalid_client",
"contentType": "application/json;charset=UTF-8",
"excerpt": "{\"error\":\"invalid_client\",\"error_description\":\"The client credentials are invalid\"}"
},
"howToFix": "Support every advertised grant type enough to return a protocol-appropriate response, or stop advertising unsupported grants."
}
],
"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": true
}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"
},
"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": "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
},
"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.box.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.box.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.box.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.box.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 AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
100 Fail
Performance and AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
Check name
Heading elements are not in a sequentially-descending order
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order)."
}SEOSEOBrowser audit
Links do not have descriptive text
100 Fail
SEOSEOBrowser audit
Links do not have descriptive text
Check name
Links do not have descriptive text
Score
0/100
Status
fail
Device
desktop
Category
SEO
Estimated savings
4 links found
Fix guidance
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).
Evidence
{
"displayValue": "4 links found",
"description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/)."
}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
Issues were logged in the `Issues` panel in Chrome Devtools
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Issues were logged in the `Issues` panel in Chrome Devtools
Check name
Issues were logged in the `Issues` panel in Chrome Devtools
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Fix guidance
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Evidence
{
"description": "Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue."
}Performance and AccessibilityPerformanceBrowser audit
Forced reflow
17 Fail
Performance and AccessibilityPerformanceBrowser audit
Forced reflow
Check name
Forced reflow
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
References
https://web.dev/learn/performance/Evidence
{
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
17 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 315 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 315 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": 380
}Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
8 Warning
Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
Check name
Avoid enormous network payloads
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Total size was 2,711 KiB
Fix guidance
Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Total size was 2,711 KiB",
"description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
"numericValue": 2775907
}Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
8 Warning
Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
Check name
Legacy JavaScript
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 9 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 9 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 CSS
8 Warning
Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 13 KiB
Fix guidance
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 13 KiB",
"description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
"numericValue": 0
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
4 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
75/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": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "50 ms",
"numericValue": 53.27406
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 14,
"displayValue": "3.7 s",
"numericValue": 3664.438035279856
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 86,
"displayValue": "170 ms",
"numericValue": 169
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 36,
"displayValue": "2.9 s",
"numericValue": 2903.122866929006
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 30 ms",
"numericValue": 28
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 71,
"displayValue": "3.4 s",
"numericValue": 3426.4151165255835
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 96,
"displayValue": "100 ms",
"numericValue": 103
},
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 99,
"displayValue": "0.6 s",
"numericValue": 603.3031749049073
}
]
}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 |
|---|---|---|---|
| 52/100 | Level 3, Bot-Aware | Current report |