Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 29 out of 100
- Agent Ease of Use 14 out of 100
- Security & Trust 60 out of 100
- GEO, AIO and AEO 66 out of 100
- SEO 100 out of 100
- Performance and Accessibility 50 out of 100
What AI sees of your website
Twilio Segment Customer Data Platform | Twilio
Collect, unify, and enrich customer data across any app or device with the Twilio Segment CDP, now available on Twilio.com.
Next step
Turn this report into a fix workflow
25 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 | 29 | Priority fix | 6 | 17 | 1 | View details |
| Discoverability | 33 | Priority fix | 3 | 6 | 0 | View details |
| Content Readiness | 46 | Priority fix | 3 | 7 | 1 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 14 | Priority fix | 7 | 26 | 0 | View details |
| API | 17 | Priority fix | 1 | 8 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 0 | 4 | 0 | View details |
| MCP | 25 | Priority fix | 2 | 6 | 0 | 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 | 66 | Needs work | 5 | 3 | 12 | View details |
| GEO Readiness | 77 | Mostly ready | 2 | 0 | 4 | |
| AIO Readiness | 58 | Needs work | 2 | 2 | 3 | View details |
| AEO Readiness | 61 | Needs work | 1 | 1 | 5 | View details |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| Security & Trust | 60 | Needs work | 7 | 2 | 0 | View details |
| Security & Trust | 60 | Needs work | 3 | 2 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 50 | Needs work | 23 | 2 | 2 | View details |
| Performance | 24 | Priority fix | 10 | 2 | 2 | View details |
| Accessibility | 99 | Strong | 13 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
45 items need attention
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
50 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
50 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
Needs attention
AI bot rules in robots.txt
Issue
No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.
Why it matters
Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.
Check name
AI bot rules in robots.txt
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.
Result
AI bot rules in robots.txt is missing or incomplete.
Evidence
{
"expectedBots": [
"GPTBot",
"ChatGPT-User",
"ClaudeBot",
"Claude-Web",
"Anthropic-AI",
"Google-Extended",
"PerplexityBot",
"CCBot",
"Applebot-Extended",
"Meta-ExternalAgent",
"Bytespider",
"Amazonbot",
"Cohere-AI"
],
"configuredBots": []
}Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
33 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
Needs attention
API Catalog
Issue
The API catalog endpoint did not return HTTP 2xx.
Why it matters
API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.
Check name
API Catalog
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated API discovery using RFC 9727.
Result
API Catalog failed at "Fetch API catalog".
Validation steps
Fetch API catalog
The API catalog endpoint did not return HTTP 2xx.
Validate RFC 9727 linkset
Response is not valid JSON.
Fetch advertised API catalog targets
API Catalog did not expose any same-origin hrefs to validate.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch API catalog",
"status": "fail",
"evidence": {
"statusCode": 404,
"contentType": "text/html; charset=utf-8"
},
"issue": "The API catalog endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/api-catalog."
},
{
"id": "validate",
"title": "Validate RFC 9727 linkset",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE HTML>\n<html lang=\"en\" class=\"full-width-dark\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Page not found | Twilio</title>\n \n \n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <script defer=\"defer\" type=\"text/javascript\" src=\"https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js\" data-routing=\"program=62254,environment=555373,tier=publish\" data-status=\"404\"></script>\n<link rel=\"canonical\" href=\"https://www.twilio.com/en-us/errors/404\"/>\n \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."
}
]
}AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
Needs attention
Content Signal
Issue
No Content Signal found in robots.txt
Why it matters
Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.
Check name
Content Signal
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences with Content Signal in robots.txt.
Result
Content Signal is missing or incomplete.
Evidence
{
"signals": [],
"ai-train": false,
"search": false,
"ai-input": false
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
Needs attention
MCP Server Card
Issue
MCP Server Card was not found at the expected path.
Why it matters
MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.
Check name
MCP Server Card
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
MCP Server Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"issue": "MCP Server Card was not found at the expected path.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
Needs attention
mcp.json
Issue
mcp.json was not found at the expected path.
Why it matters
MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.
Check name
mcp.json
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.
Result
mcp.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
mcp.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"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."
}
]
}Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
33 Fail
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
Needs attention
OpenAPI discovery
Issue
OpenAPI YAML document did not match the expected shape. Content-Type "text/html;charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Why it matters
OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.
Check name
OpenAPI discovery
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for API discovery.
Result
OpenAPI discovery failed at "Find valid OpenAPI document".
Validation steps
Find valid OpenAPI document
OpenAPI YAML document did not match the expected shape. Content-Type "text/html;charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Find valid OpenAPI document",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/openapi.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML>\n<html lang=\"en\" class=\"full-width-dark\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Page not found | Twilio</title>\n \n \n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <script defer=\"defer\" type=\"text/javascript\" src=\"https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js\" data-routing=\"program=62254,environment=555373,tier=publish\" data-status=\"404\"></script>\n<link rel=\"canonical\" href=\"https://www.twilio.com/en-us/errors/404\"/>\n \n "
},
{
"path": "/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/swagger.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML>\n<html lang=\"en\" class=\"full-width-dark\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Page not found | Twilio</title>\n \n \n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <script defer=\"defer\" type=\"text/javascript\" src=\"https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js\" data-routing=\"program=62254,environment=555373,tier=publish\" data-status=\"404\"></script>\n<link rel=\"canonical\" href=\"https://www.twilio.com/en-us/errors/404\"/>\n \n "
},
{
"path": "/api/openapi.json",
"statusCode": 200,
"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": "\n<!DOCTYPE HTML>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Product, services, features | Twilio</title>\n \n <meta name=\"description\" content=\"Everything you need to build intelligent and engaging customer experiences. Reach customers in 180+ countries with personalized messages across SMS, voice, email, chat, WhatsApp, RCS, and more.\"/>\n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <meta name=\"content-page-ref\" content=\"6SkxcrgzKlWWr8hKD4v8OhnBMrcC"
},
{
"path": "/api/swagger.json",
"statusCode": 200,
"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": "\n<!DOCTYPE HTML>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Product, services, features | Twilio</title>\n \n <meta name=\"description\" content=\"Everything you need to build intelligent and engaging customer experiences. Reach customers in 180+ countries with personalized messages across SMS, voice, email, chat, WhatsApp, RCS, and more.\"/>\n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <meta name=\"content-page-ref\" content=\"6SkxcrgzKlWWr8hKD4v8OhnBMrcC"
},
{
"path": "/docs/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><html lang=\"en\"><head><meta charSet=\"utf-8\" data-next-head=\"\"/><meta name=\"viewport\" content=\"width=device-width\" data-next-head=\"\"/><script async=\"\" defer=\"\" src=\"https://consent.trustarc.com/notice?domain=twilio.com&c=teconsent&gtm=1&js=nj&noticeType=bb\"></script><title data-next-head=\"\">Docs: API Reference, Tutorials, and Integration | Twilio</title><meta name=\"description\" content=\"Reference documentation for all Twilio products. Code snippets, tutorials, and sample apps for common use cases and communications solutions.\" data-next-head=\"\"/><link rel=\"canonical\" href=\"https://www.twilio.com/404\" data-next-head=\"\"/><link rel=\"alternate\" type=\"text/markdown\" title=\"Docs: API Reference, Tutorials, and Integration Markdown version\" href=\"https://www.twilio.co"
}
]
},
"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 ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
33 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing was not found at the expected path.
Why it matters
Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.
Check name
Web Bot Auth request signing
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.
Result
Web Bot Auth request signing failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Web Bot Auth request signing was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 596725
}
]
},
"issue": "Web Bot Auth request signing was not found at the expected path.",
"howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
}
]
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
Needs attention
WebMCP manifest
Issue
WebMCP manifest was not found at the expected path.
Why it matters
A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.
Check name
WebMCP manifest
Score
0/100
Status
fail
Category
MCP
Maturity
Informational
Goal
Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.
Result
WebMCP manifest failed at "Fetch to find resource".
Validation steps
Fetch to find resource
WebMCP manifest was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"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."
}
]
}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; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"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; charset=utf-8",
"length": 236
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"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; charset=utf-8",
"length": 236
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"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; charset=utf-8",
"length": 236
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 236
}
]
},
"issue": "agents.json was not found at the expected path.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
25 Fail
AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
Needs attention
High-value schema types
Issue
No high-value schema types (e.g. Article, Product, Service) were found.
Why it matters
High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.
Check name
High-value schema types
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Use schema types that describe the page's primary content or offering.
Result
High-value schema types is missing or incomplete.
Evidence
{
"found": [],
"expected": [
"Article",
"BlogPosting",
"NewsArticle",
"Product",
"SoftwareApplication",
"FAQPage",
"LocalBusiness",
"VideoObject",
"HowTo",
"Event",
"Course",
"Review",
"Service"
],
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
25 Fail
AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
Needs attention
JSON-LD present
Issue
No JSON-LD blocks found.
Why it matters
JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.
Check name
JSON-LD present
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose schema.org JSON-LD so AI search systems can parse page entities.
Result
JSON-LD present is missing or incomplete.
Evidence
{
"blocks": 0,
"validBlocks": 0,
"schemaContextBlocks": 0,
"errors": [],
"documents": [],
"nodes": []
}AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
25 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence
{
"failedStep": "presence",
"steps": [
{
"id": "presence",
"title": "Find useful Link headers",
"status": "fail",
"evidence": {
"links": []
},
"issue": "No useful agent discovery Link headers were found.",
"howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
},
{
"id": "target-validation",
"title": "Fetch same-origin Link header targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin Link header targets were available to fetch."
}
]
},
"issue": "Link headers did not expose any same-origin targets to validate.",
"howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
}
]
}AI 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 "Accept-Encoding,x-aem-variant".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html;charset=utf-8"
},
"issue": "Content-Type \"text/html;charset=utf-8\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "Accept-Encoding,x-aem-variant"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding,x-aem-variant\".",
"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": 56809,
"excerpt": "<!DOCTYPE HTML>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Twilio Segment Customer Data Platform | Twilio</title>\n <meta name=\"keywords\" content=\"Segment\"/>\n <meta name=\"description\" content=\"Collect, unify, and en",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
25 Fail
AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
Needs attention
Organization / WebSite schema
Issue
Neither Organization nor WebSite schema types were found in JSON-LD.
Why it matters
Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.
Check name
Organization / WebSite schema
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Identify the site owner and website entity in structured data.
Result
Organization / WebSite schema is missing or incomplete.
Evidence
{
"found": [],
"allTypes": []
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: missing <nav> landmark; skipped heading levels; missing alt text on >10% of images.
Details
Why it matters
Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.
Check name
Semantic HTML
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose readable page structure through semantic HTML and accessible controls.
Result
Semantic HTML is missing or incomplete.
Evidence
{
"main": true,
"nav": false,
"footer": true,
"meaningfulH1": true,
"headingOrder": false,
"accessibleLinks": true,
"accessibleButtons": true,
"imageAltCoverage": false,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [
"<img height=\"1\" width=\"1\" style=\"display:none\" src=\"https://www.facebook.com/tr?id=1040773425961662&ev=PageView&noscript=1\">",
"<img src=\"https://www.googleadservices.com/pagead/conversion/923239173/?label=2ud3CKnBgcYDEIWGnrgD&guid=ON&script=0\" height=\"1\" width=\"1\" style=\"border-style: none; display: none;\">"
],
"skippedHeadingLevels": [
"h1: Segment ❤️ Twilio. We're finally moving in together on Twilio.com!",
"h2: Same CDP, new home base.",
"h2: Collect real-time data in unified profiles—and so much more",
"h5: Customer data pipeline",
"h5: Customer Data Platform",
"h2: Resources to learn, build, or troubleshoot"
]
},
"counts": {
"h1": 1,
"headings": 6,
"links": 87,
"inaccessibleLinks": 0,
"buttons": 6,
"inaccessibleButtons": 0,
"images": 9,
"imagesWithAlt": 7,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 0
}
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
19 Warning
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.
Why it matters
Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.
Check name
Content freshness signals
Score
25/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is partially implemented.
Evidence
{
"lastModified": "Sat, 06 Jun 2026 12:00:32 GMT",
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint failed at "Validate resource body".
17 Fail
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint failed at "Validate resource body".
Needs attention
AI context endpoint
Issue
Content-Type "text/html;charset=utf-8" is not JSON, Markdown, or text/plain.
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
50/100
Status
fail
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 failed at "Validate resource body".
Validation steps
Validate resource body
Content-Type "text/html;charset=utf-8" is not JSON, Markdown, or text/plain.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/api/ai/context",
"statusCode": 200,
"contentType": "text/html;charset=utf-8"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Content-Type \"text/html;charset=utf-8\" is not JSON, Markdown, or text/plain.",
"rawExcerpt": "\n<!DOCTYPE HTML>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Product, services, features | Twilio</title>\n \n <meta name=\"description\" content=\"Everything you need to build intelligent and engaging customer experiences. Reach customers in 180+ countries with personalized messages across SMS, voice, email, chat, WhatsApp, RCS, and more.\"/>\n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/products\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <meta name=\"content-page-ref\" content=\"6SkxcrgzKlWWr8hKD4v8OhnBMrcC"
},
"issue": "Content-Type \"text/html;charset=utf-8\" is not JSON, Markdown, or text/plain.",
"howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
}
]
}AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate resource body".
13 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate resource body".
Needs attention
llms.txt
Issue
llms.txt response did not match the expected shape. missing h1 title (e.g. # Site Name).
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
50/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish llms.txt to summarize agent-readable site guidance.
Result
llms.txt failed at "Validate resource body".
Validation steps
Validate resource body
llms.txt response did not match the expected shape. missing h1 title (e.g. # Site Name).
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/llms.txt",
"statusCode": 200,
"contentType": "text/markdown; charset=utf-8"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"issue": "llms.txt response did not match the expected shape. missing h1 title (e.g. # Site Name).",
"compatibleContentType": true,
"hasTitle": false,
"contentLength": 2196781,
"linkCount": 10182,
"links": [
"https://www.twilio.com/en-us.md",
"https://www.twilio.com/en-us/ai.md",
"https://www.twilio.com/en-us/ai-strategy-search-retail-experiences.md",
"https://www.twilio.com/en-us/blog.md",
"/en-us/blog",
"https://www.twilio.com/en-us/blog/interconnect-is-now-global-new-exchanges-in-europe-and-asia-html.md",
"https://www.twilio.com/en-us/blog/introducing-the-pricing-api-html.md",
"https://www.twilio.com/en-us/blog/jsconf-2012-bull-rides-bacon-in-scottsdale-html.md",
"https://www.twilio.com/en-us/blog/new-webhooks-and-reporting-for-twilio-authy-2fa-and-verify-phone-verification-apis-html.md",
"https://www.twilio.com/en-us/blog/pcaps-html.md"
],
"rawExcerpt": "## [Communications APIs with AI and data for SMS, Voice, Email | Twilio]\n\n* [Communications APIs with AI and data for SMS, Voice, Email | Twilio](https://www.twilio.com/en-us.md): Create amazing customer experiences with our Customer Engagement Platform (CEP) that combines communication APIs with AI. Build solutions for SMS, WhatsApp, voice, and email.\n\n## [AI for personalized customer engagement | Twilio]\n\n* [AI for personalized customer engagement | Twilio](https://www.twilio.com/en-us/ai.md): Twilio joins artificial intelligence (AI) with contextual data and trusted communications to drive personalized customer engagement at scale.\n\n## [AI Alchemy: In Search of an AI Strategy to Reshape Retail Experiences]\n\n* [AI Alchemy: In Search of an AI Strategy to Reshape Retail Experiences](https:"
},
"issue": "llms.txt response did not match the expected shape. missing h1 title (e.g. # Site Name).",
"howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
10 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
Needs attention
AIO: Visible structured data match
Issue
No JSON-LD structured data was detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Visible structured data match
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Visible structured data match scored 0/100 and needs a fix.
Evidence
{
"schemaCount": 0,
"mismatches": [],
"score": 0,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 40/100 and needs a fix.
6 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": "https://www.linkedin.com/company/twilio-inc-",
"text": "LinkedIn logo",
"html": "<a href=\"https://www.linkedin.com/company/twilio-inc-\" target=\"_blank\" title=\"Twilio on LinkedIn\" aria-label=\"Twilio on LinkedIn\" class=\"m-share-button js-share-linkedin\"> <span class=\"name twilio-icon \"> <svg xmlns=\"http://www.w3.org/2000/svg\" fill=\"currentColor\" viewBox=\"0 0 72 72\" class=\"icon--decorative\" role=\"presentation\"> <title>LinkedIn logo</title> <g class=\"social_linkedin-alt\"> <path d=\"M17.436 68.5V24.645H2.86V68.5h14.576ZM10.15 18.653c5.083 0 8.247-3.367 8.247-7.575-.095-4.304-3...."
},
{
"href": "/en-us/company",
"text": "About Twilio",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/company\" data-uuid=\"bd9560a2-8d46-3576-a0ad-7f6fd032de60\" target=\"_self\"> <span>About Twilio</span> </a>"
}
],
"contactLinks": [
{
"href": "https://help.twilio.com/",
"text": "Help Center",
"html": "<a href=\"https://help.twilio.com/\" class=\"utility-nav__link utility-nav__link--dropdown paragraph-small-medium\" aria-label=\"Help Center\" target=\"_self\">Help Center</a>"
},
{
"href": "https://www.twilio.com/en-us/support-plans",
"text": "Support Plans",
"html": "<a href=\"https://www.twilio.com/en-us/support-plans\" class=\"utility-nav__link utility-nav__link--dropdown paragraph-small-medium\" aria-label=\"Support Plans\" target=\"_self\">Support Plans</a>"
},
{
"href": "https://www.twilio.com/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"button button-secondary right\" href=\"https://www.twilio.com/en-us/help/sales\" target=\"_self\" data-uuid=\"2a106cbe-6c59-3a55-a37f-c78fc4a50779\" aria-label=\"Contact sales\"> <span class=\"button-text\"> Contact sales </span> </a>"
},
{
"href": "https://www.twilio.com/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"button button-secondary right\" href=\"https://www.twilio.com/en-us/help/sales\" target=\"_self\" data-uuid=\"2a106cbe-6c59-3a55-a37f-c78fc4a50779\" aria-label=\"Contact sales\"> <span class=\"button-text\"> Contact sales </span> </a>"
},
{
"href": "https://help.twilio.com/",
"text": "Help Center",
"html": "<a href=\"https://help.twilio.com/\" target=\"_self\"> Help Center </a>"
},
{
"href": "/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/help/sales\" data-uuid=\"0bcd96f3-a4b2-3300-a894-a9c4d8a91382\" target=\"_self\"> <span>Contact sales</span> </a>"
},
{
"href": "/en-us/support-plans",
"text": "Support plans",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/support-plans\" data-uuid=\"58133ac5-52c8-33dd-879a-6c59cef0729e\" target=\"_self\"> <span>Support plans</span> </a>"
},
{
"href": "/en-us/flex/use-cases/contact-center",
"text": "Contact center",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/flex/use-cases/contact-center\" data-uuid=\"f7680993-4f5d-34bc-b494-5263749dfa2f\" target=\"_self\"> <span>Contact center</span> </a>"
}
],
"privacyLinks": [
{
"href": "/en-us/legal/privacy",
"text": "Privacy",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/legal/privacy\" data-uuid=\"4bc2df01-aa18-3156-b2e7-5c60e263a77c\" target=\"_self\"> <span>Privacy</span> </a>"
}
],
"score": 40,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 50/100 and needs improvement.
6 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 50/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, clear definition sentence using "is", "means", or "refers to" where natural, JSON-LD structured data.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 50/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": true,
"definitionPatterns": 0,
"schemaBlocks": 0,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process",
"clear definition sentence using \"is\", \"means\", or \"refers to\" where natural",
"JSON-LD structured data"
],
"score": 50,
"weight": 24
}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": "https://www.linkedin.com/company/twilio-inc-",
"text": "LinkedIn logo",
"html": "<a href=\"https://www.linkedin.com/company/twilio-inc-\" target=\"_blank\" title=\"Twilio on LinkedIn\" aria-label=\"Twilio on LinkedIn\" class=\"m-share-button js-share-linkedin\"> <span class=\"name twilio-icon \"> <svg xmlns=\"http://www.w3.org/2000/svg\" fill=\"currentColor\" viewBox=\"0 0 72 72\" class=\"icon--decorative\" role=\"presentation\"> <title>LinkedIn logo</title> <g class=\"social_linkedin-alt\"> <path d=\"M17.436 68.5V24.645H2.86V68.5h14.576ZM10.15 18.653c5.083 0 8.247-3.367 8.247-7.575-.095-4.304-3...."
},
{
"href": "/en-us/company",
"text": "About Twilio",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/company\" data-uuid=\"bd9560a2-8d46-3576-a0ad-7f6fd032de60\" target=\"_self\"> <span>About Twilio</span> </a>"
}
],
"contactLinks": [
{
"href": "https://help.twilio.com/",
"text": "Help Center",
"html": "<a href=\"https://help.twilio.com/\" class=\"utility-nav__link utility-nav__link--dropdown paragraph-small-medium\" aria-label=\"Help Center\" target=\"_self\">Help Center</a>"
},
{
"href": "https://www.twilio.com/en-us/support-plans",
"text": "Support Plans",
"html": "<a href=\"https://www.twilio.com/en-us/support-plans\" class=\"utility-nav__link utility-nav__link--dropdown paragraph-small-medium\" aria-label=\"Support Plans\" target=\"_self\">Support Plans</a>"
},
{
"href": "https://www.twilio.com/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"button button-secondary right\" href=\"https://www.twilio.com/en-us/help/sales\" target=\"_self\" data-uuid=\"2a106cbe-6c59-3a55-a37f-c78fc4a50779\" aria-label=\"Contact sales\"> <span class=\"button-text\"> Contact sales </span> </a>"
},
{
"href": "https://www.twilio.com/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"button button-secondary right\" href=\"https://www.twilio.com/en-us/help/sales\" target=\"_self\" data-uuid=\"2a106cbe-6c59-3a55-a37f-c78fc4a50779\" aria-label=\"Contact sales\"> <span class=\"button-text\"> Contact sales </span> </a>"
},
{
"href": "https://help.twilio.com/",
"text": "Help Center",
"html": "<a href=\"https://help.twilio.com/\" target=\"_self\"> Help Center </a>"
},
{
"href": "/en-us/help/sales",
"text": "Contact sales",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/help/sales\" data-uuid=\"0bcd96f3-a4b2-3300-a894-a9c4d8a91382\" target=\"_self\"> <span>Contact sales</span> </a>"
},
{
"href": "/en-us/support-plans",
"text": "Support plans",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/support-plans\" data-uuid=\"58133ac5-52c8-33dd-879a-6c59cef0729e\" target=\"_self\"> <span>Support plans</span> </a>"
},
{
"href": "/en-us/flex/use-cases/contact-center",
"text": "Contact center",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/flex/use-cases/contact-center\" data-uuid=\"f7680993-4f5d-34bc-b494-5263749dfa2f\" target=\"_self\"> <span>Contact center</span> </a>"
}
],
"privacyLinks": [
{
"href": "/en-us/legal/privacy",
"text": "Privacy",
"html": "<a class=\"cmp-linklist__container__item__anchor cmp-linklist__container__item__anchor--link paragraph-small\" href=\"/en-us/legal/privacy\" data-uuid=\"4bc2df01-aa18-3156-b2e7-5c60e263a77c\" target=\"_self\"> <span>Privacy</span> </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
2 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": 3,
"passing": 1,
"failing": [
{
"heading": "Collect real-time data in unified profiles—and so much more",
"headingHtml": "<h2 class=\"h2 \"> Collect real-time data in unified profiles—and so much more </h2>",
"firstParagraph": "Collect, clean and activate your customer data in any tool to create context-driven experiences. Then explore the rest of the Twilio Platform for a complete solution that combines your data, communications, and AI.",
"paragraphHtml": "<p style=\" text-align: center; \">Collect, clean and activate your customer data in any tool to create context-driven experiences. Then explore the rest of the Twilio Platform for a complete solution that combines your data, communications, and AI.</p>",
"words": 33,
"direct": false,
"issue": "First paragraph is 33 words and does not look like a concise direct answer."
},
{
"heading": "Resources to learn, build, or troubleshoot",
"headingHtml": "<h2 class=\"h2 \"> Resources to learn, build, or troubleshoot </h2>",
"firstParagraph": "Integrations catalog",
"paragraphHtml": "<p class=\"paragraph-extra-large-semibold\"> <a href=\"https://www.twilio.com/en-us/catalog\" target=\"_self\"> Integrations catalog </a> </p>",
"words": 2,
"direct": false,
"issue": "First paragraph is 2 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
2 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 3,
"questionH2s": [],
"hasFaq": true,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
Needs attention
GEO: Explanatory content depth
Issue
No substantial explanatory paragraphs were found.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 1,
"citablePassages": 0,
"failingCandidateParagraphs": [],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 87/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 87/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: platform, finally, moving, together.
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
87/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 87/100 and needs improvement.
Evidence
{
"title": "Twilio Segment Customer Data Platform | Twilio",
"h1": "Segment ❤️ Twilio. We're finally moving in together on Twilio.com!",
"description": "Collect, unify, and enrich customer data across any app or device with the Twilio Segment CDP, now available on Twilio.com.",
"topicOverlap": 0.5555555555555556,
"topicTerms": [
"twilio",
"segment",
"customer",
"data",
"platform",
"finally",
"moving",
"together",
"com"
],
"descriptionTerms": [
"collect",
"unify",
"enrich",
"customer",
"data",
"across",
"any",
"app",
"device",
"twilio",
"segment",
"cdp",
"now",
"available",
"com"
],
"missingFromDescription": [
"platform",
"finally",
"moving",
"together"
],
"score": 87,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 74/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 74/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: platform, finally, moving, together.
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
74/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 74/100 and needs improvement.
Evidence
{
"title": "Twilio Segment Customer Data Platform | Twilio",
"h1": "Segment ❤️ Twilio. We're finally moving in together on Twilio.com!",
"description": "Collect, unify, and enrich customer data across any app or device with the Twilio Segment CDP, now available on Twilio.com.",
"topicOverlap": 0.5555555555555556,
"definitionCount": 0,
"topicTerms": [
"twilio",
"segment",
"customer",
"data",
"platform",
"finally",
"moving",
"together",
"com"
],
"descriptionTerms": [
"collect",
"unify",
"enrich",
"customer",
"data",
"across",
"any",
"app",
"device",
"twilio",
"segment",
"cdp",
"now",
"available",
"com"
],
"missingFromDescription": [
"platform",
"finally",
"moving",
"together"
],
"score": 74,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 70/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 70/100 and needs improvement.
Needs attention
AIO: Page experience for AIO
Issue
6 image(s) are missing width/height attributes. 6 possible modal/interstitial element(s) detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Page experience for AIO
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Page experience for AIO scored 70/100 and needs improvement.
Evidence
{
"viewportContent": "width=device-width, initial-scale=1",
"visibleWords": 432,
"htmlBytes": 724902,
"imagesMissingDimensions": [
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_hero_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_hero_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Four interlocking puzzle pieces with icons of a message, speech bubble, lock, and user profile.\" title=\"Puzzle Pieces Representing Communication and Security Concepts\" class=\" \" loading=\"lazy\">"
},
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_hero_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_hero_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Four interlocking puzzle pieces with icons of a message, speech bubble, lock, and user profile.\" title=\"Puzzle Pieces Representing Communication and Security Concepts\" loading=\"lazy\">"
},
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_customer-pipeline_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_customer-pipeline_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Diagram showing a central Connections node linking to sources like Braze, Node.js, SQL Database and destinations such as Analytics.\" title=\"Connection Map for Integration with Various Services.\" class=\" \" loading=\"lazy\">"
},
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_customer-pipeline_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_customer-pipeline_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Diagram showing a central Connections node linking to sources like Braze, Node.js, SQL Database and destinations such as Analytics.\" title=\"Connection Map for Integration with Various Services.\" loading=\"lazy\">"
},
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_cdp_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_cdp_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Diagram showing data sources, customer profile, and engagement channels for streamlined customer interaction.\" title=\"Data Integration Flow for Customer Engagement\" class=\" \" loading=\"lazy\">"
},
{
"src": "/content/dam/segment/global/en/Home-page/rebrand/Segment_cdp_twilio.png/_jcr_content/renditions/compressed-original.webp",
"width": "",
"height": "",
"loading": "lazy",
"html": "<img src=\"/content/dam/segment/global/en/Home-page/rebrand/Segment_cdp_twilio.png/_jcr_content/renditions/compressed-original.webp\" alt=\"Diagram showing data sources, customer profile, and engagement channels for streamlined customer interaction.\" title=\"Data Integration Flow for Customer Engagement\" loading=\"lazy\">"
}
],
"possibleDialogs": [
"<template id=\"cmp-popup-template\"> <div class=\"cmp-popup\" role=\"dialog\" aria-modal=\"true\" tabindex=\"-1\" aria-label=\"Popup\"> <div class=\"cmp-popup__overlay\"></div> <div class=\"cmp-popup__content\"> <button class=\"cmp-popup__content__close\" aria-label=\"Close popup\"></button> <div class=\"cmp-popup__content__body\"></div> </div> </div> </template>",
"<div class=\"cmp-popup\" role=\"dialog\" aria-modal=\"true\" tabindex=\"-1\" aria-label=\"Popup\"> <div class=\"cmp-popup__overlay\"></div> <div class=\"cmp-popup__content\"> <button class=\"cmp-popup__content__close\" aria-label=\"Close popup\"></button> <div class=\"cmp-popup__content__body\"></div> </div> </div>",
"<div class=\"cmp-popup__overlay\"></div>",
"<div class=\"cmp-popup__content\"> <button class=\"cmp-popup__content__close\" aria-label=\"Close popup\"></button> <div class=\"cmp-popup__content__body\"></div> </div>",
"<button class=\"cmp-popup__content__close\" aria-label=\"Close popup\"></button>",
"<div class=\"cmp-popup__content__body\"></div>"
],
"score": 70,
"weight": 10
}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
2 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": 3,
"passing": 1,
"failing": [
{
"heading": "Collect real-time data in unified profiles—and so much more",
"headingHtml": "<h2 class=\"h2 \"> Collect real-time data in unified profiles—and so much more </h2>",
"firstParagraph": "Collect, clean and activate your customer data in any tool to create context-driven experiences. Then explore the rest of the Twilio Platform for a complete solution that combines your data, communications, and AI.",
"paragraphHtml": "<p style=\" text-align: center; \">Collect, clean and activate your customer data in any tool to create context-driven experiences. Then explore the rest of the Twilio Platform for a complete solution that combines your data, communications, and AI.</p>",
"words": 33,
"direct": false,
"issue": "First paragraph is 33 words and does not look like a concise direct answer."
},
{
"heading": "Resources to learn, build, or troubleshoot",
"headingHtml": "<h2 class=\"h2 \"> Resources to learn, build, or troubleshoot </h2>",
"firstParagraph": "Integrations catalog",
"paragraphHtml": "<p class=\"paragraph-extra-large-semibold\"> <a href=\"https://www.twilio.com/en-us/catalog\" target=\"_self\"> Integrations catalog </a> </p>",
"words": 2,
"direct": false,
"issue": "First paragraph is 2 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 8
}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": [
{
"text": "Same CDP, new home base.",
"html": "<h2 class=\"h2 \"> Same CDP, new home base. </h2>"
},
{
"text": "Collect real-time data in unified profiles—and so much more",
"html": "<h2 class=\"h2 \"> Collect real-time data in unified profiles—and so much more </h2>"
},
{
"text": "Resources to learn, build, or troubleshoot",
"html": "<h2 class=\"h2 \"> Resources to learn, build, or troubleshoot </h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "how",
"label": "How does Twilio Segment Customer Data Platform work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Twilio Segment Customer Data Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Twilio Segment Customer Data Platform compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "how",
"label": "How does Twilio Segment Customer Data Platform work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Twilio Segment Customer Data Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Twilio Segment Customer Data Platform compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}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": [
{
"text": "Same CDP, new home base.",
"html": "<h2 class=\"h2 \"> Same CDP, new home base. </h2>"
},
{
"text": "Collect real-time data in unified profiles—and so much more",
"html": "<h2 class=\"h2 \"> Collect real-time data in unified profiles—and so much more </h2>"
},
{
"text": "Resources to learn, build, or troubleshoot",
"html": "<h2 class=\"h2 \"> Resources to learn, build, or troubleshoot </h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "how",
"label": "How does Twilio Segment Customer Data Platform work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Twilio Segment Customer Data Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Twilio Segment Customer Data Platform compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "how",
"label": "How does Twilio Segment Customer Data Platform work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Twilio Segment Customer Data Platform?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Twilio Segment Customer Data Platform free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Twilio Segment Customer Data Platform compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"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 / OIDC discovery was not found at the expected path.
Why it matters
OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.
Check name
OAuth / OIDC discovery
Score
0/100
Status
informational
Category
Auth
Maturity
Established
Goal
Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.
Result
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Validation steps
Fetch to find resource
OAuth / OIDC discovery was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/openid-configuration",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 596725
},
{
"path": "/.well-known/oauth-authorization-server",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 596725
}
]
},
"issue": "OAuth / OIDC discovery was not found at the expected path.",
"howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 9,
"signals": [
{
"source": "link:href",
"weight": 3,
"match": "auth link"
},
{
"source": "visible-text",
"weight": 3,
"match": "log in"
},
{
"source": "visible-text",
"weight": 3,
"match": "login"
}
]
},
"resourceFetchSucceeded": false
}Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Needs attention
OAuth Protected Resource
Issue
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Why it matters
Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.
Check name
OAuth Protected Resource
Score
0/100
Status
informational
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.
Result
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Validation steps
Fetch protected resource metadata
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Validate protected resource metadata
Response is not valid JSON.
Validate protected resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
Probe protected API Bearer challenge
No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch protected resource metadata",
"status": "fail",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"statusCode": 404,
"contentType": "text/html; charset=utf-8"
},
"issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/oauth-protected-resource JSON."
},
{
"id": "metadata",
"title": "Validate protected resource metadata",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE HTML>\n<html lang=\"en\" class=\"full-width-dark\">\n<head>\n <meta charset=\"UTF-8\"/>\n <title>Page not found | Twilio</title>\n \n \n <meta name=\"template\" content=\"base-page\"/>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/>\n <meta name=\"robots\" content=\"index\"/>\n <meta property=\"og:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"twitter:url\" content=\"https://www.twilio.com/en-us/errors/404\"/>\n <meta name=\"brand\" content=\"twilio\"/>\n\n <script defer=\"defer\" type=\"text/javascript\" src=\"https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js\" data-routing=\"program=62254,environment=555373,tier=publish\" data-status=\"404\"></script>\n<link rel=\"canonical\" href=\"https://www.twilio.com/en-us/errors/404\"/>\n \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.twilio.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": 200,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.twilio.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 200,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.twilio.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 200,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.twilio.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": "login"
}
]
},
"resourceFetchSucceeded": false
}Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
Check name
Browser errors were logged to the console
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Fix guidance
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)
Evidence
{
"description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
Check name
Uses deprecated APIs
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Estimated savings
1 warning found
Fix guidance
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).
Evidence
{
"displayValue": "1 warning found",
"description": "Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/)."
}Performance and AccessibilityPerformanceBrowser audit
Reduce JavaScript execution time
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce JavaScript execution time
Check name
Reduce JavaScript execution time
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
64.0Â s
Fix guidance
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "64.0Â s",
"description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
"numericValue": 64048.707999999904
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
18 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
27/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": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 1,
"displayValue": "3.8Â s",
"numericValue": 3819.8568999999993
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 0,
"displayValue": "31.7Â s",
"numericValue": 31707.149650000003
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 0,
"displayValue": "30.6Â s",
"numericValue": 30587.28110565746
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 0,
"displayValue": "65,500Â ms",
"numericValue": 65495.22059999998
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 0,
"displayValue": "5,550Â ms",
"numericValue": 5548.999999999993
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 20Â ms",
"numericValue": 19.83
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 0,
"displayValue": "86.8Â s",
"numericValue": 86789.57749999998
},
{
"id": "uses-rel-preconnect",
"title": "Preconnect to required origins",
"score": 100,
"displayValue": "",
"numericValue": 0
},
{
"id": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "150Â ms",
"numericValue": 149.072
},
{
"id": "third-party-summary",
"title": "Reduce the impact of third-party code",
"score": 0,
"displayValue": "Third-party code blocked the main thread for 43,960Â ms"
},
{
"id": "largest-contentful-paint-element",
"title": "Largest Contentful Paint element",
"score": 0,
"displayValue": "31,710Â ms"
}
]
}Performance and AccessibilityPerformanceBrowser audit
Ensure text remains visible during webfont load
13 Warning
Performance and AccessibilityPerformanceBrowser audit
Ensure text remains visible during webfont load
Check name
Ensure text remains visible during webfont load
Score
50/100
Status
warning
Device
desktop
Category
Performance
Fix guidance
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. [Learn more about `font-display`](https://developer.chrome.com/docs/lighthouse/performance/font-display/).
References
https://web.dev/learn/performance/Evidence
{
"description": "Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. [Learn more about `font-display`](https://developer.chrome.com/docs/lighthouse/performance/font-display/)."
}Performance and AccessibilityPerformanceBrowser audit
Image elements do not have explicit `width` and `height`
13 Warning
Performance and AccessibilityPerformanceBrowser audit
Image elements do not have explicit `width` and `height`
Check name
Image elements do not have explicit `width` and `height`
Score
50/100
Status
warning
Device
desktop
Category
Performance
Fix guidance
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)
References
https://web.dev/learn/performance/Evidence
{
"description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)"
}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 |
|---|---|---|---|
| 48/100 | Level 2, Agent-Limited | View report | |
| 41/100 | Level 2, Agent-Limited | View report | |
| 42/100 | Level 2, Agent-Limited | Current report |