Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 20 out of 100
- Agent Ease of Use 39 out of 100
- Security & Trust 0 out of 100
- GEO, AIO and AEO 58 out of 100
- SEO 83 out of 100
- Performance and Accessibility 76 out of 100
What AI sees of your website
Estimote UWB Tags
Estimote UWB Tags estimote UWB Tags programmable in JavaScript track valuable assets automate team work prototype innovations Buy dev kit with 3 tags for $199 Contact us How does it work? UWB Tags are handy little gadgets that can detect other nearby tags wit...
Next step
Turn this report into a fix workflow
33 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 | 20 | Priority fix | 4 | 20 | 1 | View details |
| Discoverability | 14 | Priority fix | 1 | 8 | 0 | View details |
| Content Readiness | 29 | Priority fix | 2 | 8 | 1 | View details |
| Bot Access Control | 17 | Priority fix | 1 | 4 | 0 | View details |
| Agent Ease of Use | 39 | Priority fix | 21 | 33 | 2 | View details |
| API | 28 | Priority fix | 2 | 7 | 0 | View details |
| Auth | 27 | Priority fix | 6 | 8 | 0 | View details |
| MCP | 60 | Needs work | 5 | 7 | 1 | View details |
| Skill Discovery | 42 | Priority fix | 4 | 11 | 1 | View details |
| Agent Commerce | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| GEO, AIO and AEO | 58 | Needs work | 3 | 3 | 13 | View details |
| GEO Readiness | 68 | Needs work | 1 | 0 | 4 | |
| AIO Readiness | 51 | Needs work | 1 | 2 | 4 | View details |
| AEO Readiness | 53 | Needs work | 1 | 1 | 5 | View details |
| SEO | 83 | Mostly ready | 9 | 2 | 0 | View details |
| SEO | 83 | Mostly ready | 9 | 2 | 0 | View details |
| Security & Trust | 20 | Priority fix | 3 | 7 | 0 | View details |
| Security & Trust | 0 | Priority fix | 0 | 5 | 0 | View details |
| AI Training Exposure | 50 | Needs work | 3 | 2 | 0 | View details |
| Performance and Accessibility | 76 | Mostly ready | 19 | 6 | 1 | View details |
| Performance | 75 | Mostly ready | 17 | 4 | 1 | View details |
| Accessibility | 79 | Mostly ready | 2 | 2 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
58 items need attention
Security & TrustAI Training ExposureEmerging recommendation
TDMRep declaration
TDMRep declaration is missing or incomplete.
100 Fail
Security & TrustAI Training ExposureEmerging recommendation
TDMRep declaration
TDMRep declaration is missing or incomplete.
Needs attention
TDMRep declaration
Issue
Response is not valid JSON.
Why it matters
TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.
Check name
TDMRep declaration
Score
0/100
Status
fail
Category
AI Training Exposure
Maturity
Emerging recommendation
Goal
Publish a machine-readable text and data mining reservation declaration when the site needs one.
Result
TDMRep declaration is missing or incomplete.
Validation steps
Validate TDMRep rules
Response is not valid JSON.
Evidence
{
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t ",
"steps": [
{
"id": "fetch",
"title": "Fetch /.well-known/tdmrep.json",
"status": "pass",
"evidence": {
"statusCode": 200,
"contentType": "text/html",
"length": 28141
}
},
{
"id": "validate",
"title": "Validate TDMRep rules",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish /.well-known/tdmrep.json as an array of TDMRep rule objects with location and tdm-reservation values of 0 or 1."
}
]
}Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate resource body".
40 Fail
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate resource body".
Needs attention
OAuth / OIDC discovery
Issue
Response is not valid JSON.
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
20/100
Status
fail
Category
Auth
Maturity
Established
Goal
Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.
Result
OAuth / OIDC discovery failed at "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Probe authorization endpoint with an authorization-code request
authorization_endpoint is missing from discovery metadata.
Reject unregistered authorization redirects
authorization_endpoint is missing from discovery metadata.
Probe token endpoint with advertised grant type
token_endpoint is missing from discovery metadata.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/openid-configuration",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
},
{
"id": "authorization-endpoint",
"title": "Probe authorization endpoint with an authorization-code request",
"status": "fail",
"evidence": {
"url": ""
},
"issue": "authorization_endpoint is missing from discovery metadata.",
"howToFix": "Advertise only implemented OAuth/OIDC endpoints."
},
{
"id": "authorization-redirect-safety",
"title": "Reject unregistered authorization redirects",
"status": "fail",
"evidence": {
"url": ""
},
"issue": "authorization_endpoint is missing from discovery metadata.",
"howToFix": "Validate clients and redirect_uri values before redirecting."
},
{
"id": "token-endpoint",
"title": "Probe token endpoint with advertised grant type",
"status": "fail",
"evidence": {
"url": ""
},
"issue": "token_endpoint is missing from discovery metadata.",
"howToFix": "Advertise only implemented OAuth/OIDC endpoints."
}
],
"authApplicability": {
"supportsAuth": false,
"score": 0,
"signals": []
},
"resourceFetchSucceeded": true
}Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate protected resource metadata".
34 Fail
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate protected resource metadata".
Needs attention
OAuth Protected Resource
Issue
Response is not valid JSON.
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
33/100
Status
fail
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.
Result
OAuth Protected Resource failed at "Validate protected resource metadata".
Validation steps
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": "metadata",
"steps": [
{
"id": "fetch",
"title": "Fetch protected resource metadata",
"status": "pass",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"statusCode": 200,
"contentType": "text/html"
},
"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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"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://estimote.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://estimote.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 200,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://estimote.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 200,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://estimote.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": false,
"score": 0,
"signals": []
},
"resourceFetchSucceeded": true
}AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
Needs attention
AI bot rules in robots.txt
Issue
No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.
Why it matters
Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.
Check name
AI bot rules in robots.txt
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.
Result
AI bot rules in robots.txt is missing or incomplete.
Evidence
{
"expectedBots": [
"GPTBot",
"ChatGPT-User",
"ClaudeBot",
"Claude-Web",
"Anthropic-AI",
"Google-Extended",
"PerplexityBot",
"CCBot",
"Applebot-Extended",
"Meta-ExternalAgent",
"Bytespider",
"Amazonbot",
"Cohere-AI"
],
"configuredBots": []
}AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
Needs attention
Content Signal
Issue
No Content Signal found in robots.txt
Why it matters
Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.
Check name
Content Signal
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences with Content Signal in robots.txt.
Result
Content Signal is missing or incomplete.
Evidence
{
"signals": [],
"ai-train": false,
"search": false,
"ai-input": false
}Agent Ease of 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" 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" 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": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/openapi.yaml",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/swagger.json",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/swagger.yaml",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/api/openapi.json",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/api/swagger.json",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
{
"path": "/docs/openapi.json",
"statusCode": 200,
"contentType": "text/html",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
}
]
},
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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."
}
]
}Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate RFC 9727 linkset".
22 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate RFC 9727 linkset".
Needs attention
API Catalog
Issue
Response is not valid JSON.
Why it matters
API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.
Check name
API Catalog
Score
33/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated API discovery using RFC 9727.
Result
API Catalog failed at "Validate RFC 9727 linkset".
Validation steps
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": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch API catalog",
"status": "pass",
"evidence": {
"statusCode": 200,
"contentType": "text/html"
},
"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\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
},
{
"id": "target-validation",
"title": "Fetch advertised API catalog targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin API catalog hrefs were available to fetch."
}
]
},
"issue": "API Catalog did not expose any same-origin hrefs to validate.",
"howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
}
]
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate resource body".
21 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate resource body".
Needs attention
MCP Server Card
Issue
Response is not valid JSON.
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
38/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Verify advertised MCP transport endpoints
At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.
Verify advertised MCP tool execution
MCP discovery passed, but no advertised tool could be safely executed by this scanner.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/mcp/server-card.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
},
{
"id": "endpoint-verification",
"title": "Verify advertised MCP transport endpoints",
"status": "fail",
"evidence": {
"probes": []
},
"issue": "At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.",
"howToFix": "Expose a real MCP endpoint for advertised transports, or remove transports that point to ordinary HTTP APIs."
},
{
"id": "tool-execution",
"title": "Verify advertised MCP tool execution",
"status": "warning",
"evidence": {
"probes": []
},
"issue": "MCP discovery passed, but no advertised tool could be safely executed by this scanner.",
"howToFix": "Implement tools/call for advertised tools, or report the MCP card as discovery-only until tools are executable."
}
]
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
Needs attention
Frame protection
Issue
Frame protection is missing or incomplete.
Why it matters
Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.
Check name
Frame protection
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.
Result
Frame protection is missing or incomplete.
Evidence
{
"xFrameOptions": null,
"validXFrame": false,
"contentSecurityPolicy": null,
"cspFrameAncestors": false
}Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
Needs attention
HSTS header
Issue
HSTS header is missing or incomplete.
Why it matters
HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade and mixed-transport risk for repeat users.
Check name
HSTS header
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat visits with Strict-Transport-Security.
Result
HSTS header is missing or incomplete.
Evidence
{
"header": "strict-transport-security",
"value": null
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
20 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
Needs attention
Markdown negotiation
Issue
Content-Type "text/html" 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" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "Accept-Encoding".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html"
},
"issue": "Content-Type \"text/html\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "Accept-Encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding\".",
"howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
},
{
"id": "markdown-content",
"title": "Structured Markdown body",
"status": "fail",
"evidence": {
"valid": false,
"hasHeading": false,
"wordCount": 3548,
"excerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n",
"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."
}
]
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
20 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 DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
20 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: missing <main> landmark; missing <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": false,
"nav": false,
"footer": true,
"meaningfulH1": true,
"headingOrder": false,
"accessibleLinks": true,
"accessibleButtons": true,
"imageAltCoverage": false,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [
"<img src=\"uwb-wearable.png\">",
"<img class=\"Initiator\" src=\"single-uwb-wearable.png\">",
"<img class=\"Responder\" src=\"single-uwb-wearable.png\">",
"<img src=\"workplace.png\">",
"<img src=\"health-care.png\">",
"<img src=\"panic-button.png\">",
"<img src=\"workplace.png\">",
"<img src=\"health-care.png\">",
"<img src=\"panic-button.png\">",
"<img class=\"Teardown\" src=\"uwb-teardown.png\">",
"<img src=\"uwb-devkit.png\">",
"<img class=\"IDE\" src=\"uwb-programming.png\">",
"<img class=\"IDE\" src=\"uwb-map.png\">",
"<img class=\"IDE\" src=\"uwb-cloud-lambda.png\">",
"<img src=\"workplace.png\">",
"<img src=\"health-care.png\">",
"<img src=\"panic-button.png\">",
"<img src=\"workplace.png\">",
"<img src=\"health-care.png\">",
"<img src=\"panic-button.png\">",
"<img class=\"Customizations\" src=\"estimote-products.png\">",
"<img src=\"estimote-logo.png\">"
],
"skippedHeadingLevels": [
"h3: estimote",
"h1: UWB Tags",
"h2: programmable in JavaScript",
"h4: How does it work?",
"h4: What are they used for?",
"h4: How do they work technically?",
"h4: How is UWB different from Bluetooth?",
"h4: How to get started?",
"h4: How can they be programmed?",
"h4: Can they push data directly to my cloud?",
"h4: Why JavaScript?",
"h4: Why I should buy this dev kit?",
"h4: What is the battery life of a UWB tag?",
"h4: How accurate are the tags?",
"h4: Do they work in any environment?",
"h4: What industries are they suited for?",
"h4: Can smartphones detect UWB tags?",
"h4: Is location tracking better with smartphones or UWB tags?",
"h4: How many UWB tags can range with each other?",
"h4: Can UWB tags be used for RTLS?",
"h4: What are the security features?",
"h4: Do you offer support?",
"h4: How about custom form-factors?",
"h4: How can I contact you?",
"h4: Why should we work with you?",
"h5: Estimote, Inc",
"h5: Estimote Polska Sp. z o.o."
]
},
"counts": {
"h1": 1,
"headings": 27,
"links": 9,
"inaccessibleLinks": 0,
"buttons": 2,
"inaccessibleButtons": 0,
"images": 22,
"imagesWithAlt": 0,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 0
}
}AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data is missing or incomplete.
20 Fail
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data is missing or incomplete.
Needs attention
Structured data
Issue
No structured data (JSON-LD, Microdata, or RDFa) found on page.
Why it matters
Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.
Check name
Structured data
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose machine-readable page entities and relationships.
Result
Structured data is missing or incomplete.
Evidence
{
"jsonLdBlocks": 0,
"microdata": false,
"rdfa": false
}Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
Needs attention
X-Content-Type-Options
Issue
X-Content-Type-Options is missing or incomplete.
Why it matters
X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.
Check name
X-Content-Type-Options
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent MIME sniffing for browser-loaded resources.
Result
X-Content-Type-Options is missing or incomplete.
Evidence
{
"header": "x-content-type-options",
"value": null
}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" 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" 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"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Content-Type \"text/html\" is not JSON, Markdown, or text/plain.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Content-Type \"text/html\" 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 DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
17 Fail
AI DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
Needs attention
FAQPage schema
Issue
FAQ content was detected but no FAQPage schema was found.
Why it matters
FAQPage schema lets agents extract visible question-and-answer content cleanly and avoid guessing which text is an answer.
Check name
FAQPage schema
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose question-and-answer content in FAQPage structured data when FAQs are present.
Result
FAQPage schema is missing or incomplete.
Evidence
{
"found": false,
"visibleFaq": true,
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
17 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.
17 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".
17 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence
{
"failedStep": "presence",
"steps": [
{
"id": "presence",
"title": "Find useful Link headers",
"status": "fail",
"evidence": {
"links": []
},
"issue": "No useful agent discovery Link headers were found.",
"howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
},
{
"id": "target-validation",
"title": "Fetch same-origin Link header targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin Link header targets were available to fetch."
}
]
},
"issue": "Link headers did not expose any same-origin targets to validate.",
"howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Validate resource body".
17 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Validate resource body".
Needs attention
mcp.json
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/mcp.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
17 Fail
AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
Needs attention
Organization / WebSite schema
Issue
Neither Organization nor WebSite schema types were found in JSON-LD.
Why it matters
Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.
Check name
Organization / WebSite schema
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Identify the site owner and website entity in structured data.
Result
Organization / WebSite schema is missing or incomplete.
Evidence
{
"found": [],
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
Sitemap
Sitemap is missing or incomplete.
17 Fail
AI DiscoverabilityDiscoverabilityEstablished
Sitemap
Sitemap is missing or incomplete.
Needs attention
Sitemap
Issue
No valid XML sitemap found at checked locations: https://estimote.com/sitemap.xml, https://estimote.com/sitemap_index.xml, https://estimote.com/sitemap-index.xml.
Why it matters
Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.
Check name
Sitemap
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Publish a sitemap and reference it from robots.txt.
Result
Sitemap is missing or incomplete.
Evidence
{
"checked": [
"https://estimote.com/sitemap.xml",
"https://estimote.com/sitemap_index.xml",
"https://estimote.com/sitemap-index.xml"
]
}AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Validate resource body".
17 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Validate resource body".
Needs attention
Web Bot Auth request signing
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"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 "Validate resource body".
17 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Validate resource body".
Needs attention
WebMCP manifest
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/webmcp.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
15 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID entrypoint records were found under _agents.
Why it matters
DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.
Check name
DNS-AID Agent Discovery
Score
25/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Validation steps
Resolve DNS-AID SVCB/HTTPS records
No DNS-AID entrypoint records were found under _agents.
Validate alpn and endpoint parameters
Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.
Check DNSSEC material
DNSSEC material was not visible for the hostname or parent zone from this resolver.
Evidence
{
"failedStep": "svcb-https-records",
"steps": [
{
"id": "svcb-https-records",
"title": "Resolve DNS-AID SVCB/HTTPS records",
"status": "fail",
"evidence": {
"hostname": "estimote.com",
"probes": [
{
"name": "_index._agents.estimote.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.estimote.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
}
]
},
"issue": "No DNS-AID entrypoint records were found under _agents.",
"howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
},
{
"id": "service-params",
"title": "Validate alpn and endpoint parameters",
"status": "informational",
"evidence": {
"discovered": []
},
"howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
},
{
"id": "dnssec",
"title": "Check DNSSEC material",
"status": "warning",
"evidence": {
"hasDnssecMaterial": false,
"checked": [
{
"name": "estimote.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
}
]
},
"issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
"howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
15 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": "Mon, 29 Jul 2024 08:51:09 GMT",
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate resource body".
13 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate resource body".
Needs attention
Agent Skills index
Issue
Response is not valid JSON.
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
33/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent skills discovery index.
Result
Agent Skills index failed at "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Fetch advertised SKILL.md files
One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/agent-skills/index.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
},
{
"id": "skill-documents",
"title": "Fetch advertised SKILL.md files",
"status": "fail",
"evidence": {
"checkedCount": 0,
"totalCount": 0,
"checked": []
},
"issue": "One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.",
"howToFix": "Make every advertised skill URL return Markdown with a top-level heading and a matching sha256 digest, or remove broken entries from the index."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate resource body".
10 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate resource body".
Needs attention
A2A Agent Card
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/agent-card.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"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.json
agent.json failed at "Validate resource body".
10 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Validate resource body".
Needs attention
agent.json
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/agent.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"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 "Validate resource body".
10 Fail
Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Validate resource body".
Needs attention
agents.json
Issue
Response is not valid JSON.
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
50/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 "Validate resource body".
Validation steps
Validate resource body
Response is not valid JSON.
Evidence
{
"failedStep": "validate",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/agents.json",
"statusCode": 200,
"contentType": "text/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"validJson": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "Response is not valid JSON.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate resource body".
10 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. Content-Type "text/html" is not Markdown or text/plain; 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. Content-Type "text/html" is not Markdown or text/plain; 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/html"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "fail",
"evidence": {
"valid": false,
"issue": "llms.txt response did not match the expected shape. Content-Type \"text/html\" is not Markdown or text/plain; missing h1 title (e.g. # Site Name).",
"compatibleContentType": false,
"hasTitle": false,
"contentLength": 24984,
"linkCount": 269,
"links": [
"/title",
"/favicon.ico",
"/x-icon",
"//",
"/2.5+",
"//",
"//",
"//",
"//",
"//"
],
"rawExcerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"UTF-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Estimote UWB Tags</title>\n\t<link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\">\n\t\n\t\n\t<script>\n\t\t// Animate UWB distance measurements\n\t function animateTextContent(spanId, startValue, endValue, duration, callback) {\n\t const spanElement = document.getElementById(spanId);\n\t let currentValue = startValue;\n\t const increment = (endValue - startValue) / (duration / 100);\n\t const interval = setInterval(() => {\n\t currentValue += increment;\n\t if ((increment > 0 && currentValue >= endValue) || (increment < 0 && currentValue <= endValue)) {\n\t "
},
"issue": "llms.txt response did not match the expected shape. Content-Type \"text/html\" is not Markdown or text/plain; 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.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
Needs attention
AIO: Visible structured data match
Issue
No JSON-LD structured data was detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Visible structured data match
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Visible structured data match scored 0/100 and needs a fix.
Evidence
{
"schemaCount": 0,
"mismatches": [],
"score": 0,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 50/100 and needs improvement.
7 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 50/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: estimote, uwb, tags.
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
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: Entity clarity scored 50/100 and needs improvement.
Evidence
{
"title": "Estimote UWB Tags",
"h1": "UWB Tags",
"description": "",
"topicOverlap": 0,
"topicTerms": [
"estimote",
"uwb",
"tags"
],
"descriptionTerms": [],
"missingFromDescription": [
"estimote",
"uwb",
"tags"
],
"score": 50,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 20/100 and needs a fix.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 20/100 and needs a fix.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: author, publisher, freshnessDate, policyLinks.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer evidence and trust
Score
20/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 20/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": false
},
"missing": [
"author",
"publisher",
"freshnessDate",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [
{
"href": "mailto:[email protected]",
"text": "Contact us",
"html": "<a href=\"mailto:[email protected]\">Contact us</a>"
}
],
"privacyLinks": [],
"score": 20,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 20/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 20/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate, policyLinks.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Source and trust signals
Score
20/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 20/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": false
},
"missing": [
"author",
"publisher",
"freshnessDate",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [
{
"href": "mailto:[email protected]",
"text": "Contact us",
"html": "<a href=\"mailto:[email protected]\">Contact us</a>"
}
],
"privacyLinks": [],
"score": 20,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
5 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, JSON-LD structured data.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
60/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": false,
"definitionPatterns": 25,
"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",
"optional visible FAQ or FAQPage schema",
"JSON-LD structured data"
],
"score": 60,
"weight": 24
}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
1 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": 2,
"passing": 1,
"failing": [
{
"heading": "estimote",
"headingHtml": "<h3>estimote</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
No question-led h2 sections or FAQ pattern was detected.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 1,
"questionH2s": [],
"hasFaq": false,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 55/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 55/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: estimote, uwb, tags.
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
55/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 55/100 and needs improvement.
Evidence
{
"title": "Estimote UWB Tags",
"h1": "UWB Tags",
"description": "",
"topicOverlap": 0,
"definitionCount": 25,
"topicTerms": [
"estimote",
"uwb",
"tags"
],
"descriptionTerms": [],
"missingFromDescription": [
"estimote",
"uwb",
"tags"
],
"score": 55,
"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
18 explanatory paragraph(s) could be stronger for citation or AI extraction.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 20,
"citablePassages": 2,
"failingCandidateParagraphs": [
{
"index": 1,
"heading": "H4: How does it work?",
"text": "UWB Tags are handy little gadgets that can detect other nearby tags with inch-level precision. They can trigger actions based on how close they are to each other. With built-in IMU and pressure sensors, they can also track movement and elevation. They can send real-time location and other data over LTE directly to your endpoints, making them a perfect platform for asset tracking, productivity and safety applications.",
"words": 67,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (67 words; target 80-220)."
],
"html": "<p> UWB Tags are handy little gadgets that can detect other nearby tags with inch-level precision. They can trigger actions based on how close they are to each other. With built-in IMU and pressure sensors, they can also track movement and elevation. They can send real-time location and other data over LTE directly to your endpoints, making them a perfect platform for asset tracking, productivity and safety applications. </p>"
},
{
"index": 2,
"heading": "H4: What are they used for?",
"text": "They are used to easily and precisely locate things both indoors and outdoors. Since they are programmable and have connectivity, they are often used for automation. For example, team members can wear them and things can happen automatically just by entering different rooms or approaching equipment.",
"words": 46,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (46 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> They are used to easily and precisely locate things both indoors and outdoors. Since they are programmable and have connectivity, they are often used for automation. For example, team members can wear them and things can happen automatically just by entering different rooms or approaching equipment. </p>"
},
{
"index": 3,
"heading": "H4: How do they work technically?",
"text": "Each UWB Tag has a very precise clock and an ultra wideband transmitter. When they communicate, they measure the time these radio signals travel from one to another. By multiplying this time by the speed of light, they estimate distances to each other with inch-level accuracy. This precision allows them to deliver magical experiences or automations.",
"words": 56,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (56 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Each UWB Tag has a very precise clock and an ultra wideband transmitter. When they communicate, they measure the time these radio signals travel from one to another. By multiplying this time by the speed of light, they estimate distances to each other with inch-level accuracy. This precision allows them to deliver magical experiences or automations. </p>"
},
{
"index": 6,
"heading": "H4: How can they be programmed?",
"text": "UWB Tags can be programmed directly from your computer using Bluetooth. By using the Chrome browser and our Web IDE, you simply connect with a nearby UWB Tag via Web Bluetooth. You can write JavaScript code and upload it directly to your tag. It will act as you programmed it to.",
"words": 51,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (51 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> UWB Tags can be programmed directly from your computer using Bluetooth. By using the Chrome browser and our Web IDE, you simply connect with a nearby UWB Tag via Web Bluetooth. You can write JavaScript code and upload it directly to your tag. It will act as you programmed it to. </p>"
},
{
"index": 9,
"heading": "H4: Can they push data directly to my cloud?",
"text": "Yes, UWB Tags have a built-in modem, just like your smartphone. They connect to the nearest cell tower using LTE-M or NB-IoT and can send data directly to your own cloud. In our Web IDE, there is a section called \"Cloud code\" which is executed as a serverless Lambda. You can program it to structure and send data to your own end-points.",
"words": 62,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (62 words; target 80-220)."
],
"html": "<p> Yes, UWB Tags have a built-in modem, just like your smartphone. They connect to the nearest cell tower using LTE-M or NB-IoT and can send data directly to your own cloud. In our Web IDE, there is a section called "Cloud code" which is executed as a serverless Lambda. You can program it to structure and send data to your own end-points. </p>"
},
{
"index": 11,
"heading": "H4: Why JavaScript?",
"text": "Because it is the most popular language among developers. There are milions of web developers who are fluent in JS, working on client or server-side. This is far more than embedded engineers who are typically required to program IoT devices. JavaScript has native support for events, and in the modern IoT it's all about events and reactions to things that happen in the physical world. JavaScript can also be generat...",
"words": 85,
"hasEvidence": false,
"reasons": [
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Because it is the most popular language among developers. There are milions of web developers who are fluent in JS, working on client or server-side. This is far more than embedded engineers who are typically required to program IoT devices. JavaScript has native support for events, and in the modern IoT it's all about events and reactions to things that happen in the physical world. JavaScript can also be generated with modern AI tools, allowing you to come up with any real-world ap..."
},
{
"index": 12,
"heading": "H4: Why I should buy this dev kit?",
"text": "It is simply the best way to learn and evaluate UWB technology. You don't need embedded engineering skills since you can program UWB tags in JavaScript direcly from your laptop. You can use them to prototype various use cases, from asset tracking to smart badges. Since they have LTE, you can also use them to pilot your solution and collect data or update remotely. It is the best IoT prototyping platform on the mar...",
"words": 74,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (74 words; target 80-220)."
],
"html": "<p> It is simply the best way to learn and evaluate UWB technology. You don't need embedded engineering skills since you can program UWB tags in JavaScript direcly from your laptop. You can use them to prototype various use cases, from asset tracking to smart badges. Since they have LTE, you can also use them to pilot your solution and collect data or update remotely. It is the best IoT prototyping platform on the market. </p>"
},
{
"index": 13,
"heading": "H4: What is the battery life of a UWB tag?",
"text": "Each tag has a 400 mAh rechargeable battery. Battery life depends on the configuration. For simple UWB or BLE beaconing, they can last years on a single charge. When programmed to act as wearables detecting proximity and sending data, they can last a few weeks. For continuous scanning and real-time asset tracking, they require permanent power via USB-C.",
"words": 58,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (58 words; target 80-220)."
],
"html": "<p> Each tag has a 400 mAh rechargeable battery. Battery life depends on the configuration. For simple UWB or BLE beaconing, they can last years on a single charge. When programmed to act as wearables detecting proximity and sending data, they can last a few weeks. For continuous scanning and real-time asset tracking, they require permanent power via USB-C. </p>"
},
{
"index": 14,
"heading": "H4: How accurate are the tags?",
"text": "It depends on tag orientation, but on average, without any filtering, you should expect approx. 20cm. With sensor fusion including the IMU, accuracy could improve to sub-10cm. Their responsiveness can be as low as 10ms, and the range is up to 30-40m, extendable to 100-200m with an LNA amplifier.",
"words": 49,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (49 words; target 80-220)."
],
"html": "<p> It depends on tag orientation, but on average, without any filtering, you should expect approx. 20cm. With sensor fusion including the IMU, accuracy could improve to sub-10cm. Their responsiveness can be as low as 10ms, and the range is up to 30-40m, extendable to 100-200m with an LNA amplifier. </p>"
},
{
"index": 15,
"heading": "H4: Do they work in any environment?",
"text": "UWB signals are 3-9 GHz frequency and can easily go through concrete, wood or glass. As every radio wave it might be blocked by metal structures so in a complex industrial environments it is important to install more of them to ensure line of sight. They be deployed indoor or outdoor and they survive from -40°C up to +40°C.",
"words": 61,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (61 words; target 80-220)."
],
"html": "<p>UWB signals are 3-9 GHz frequency and can easily go through concrete, wood or glass. As every radio wave it might be blocked by metal structures so in a complex industrial environments it is important to install more of them to ensure line of sight. They be deployed indoor or outdoor and they survive from -40°C up to +40°C.</p>"
},
{
"index": 16,
"heading": "H4: What industries are they suited for?",
"text": "Our tags are used in warehousing, logistics, healthcare, retail, and hospitality. They enhance safety, improve asset tracking, and provide precise location data where GPS is insufficient. During the pandemic, they were used for contact tracing and social distancing. In hospitality, they can serve as panic buttons for cleaning personnel.",
"words": 49,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (49 words; target 80-220)."
],
"html": "<p> Our tags are used in warehousing, logistics, healthcare, retail, and hospitality. They enhance safety, improve asset tracking, and provide precise location data where GPS is insufficient. During the pandemic, they were used for contact tracing and social distancing. In hospitality, they can serve as panic buttons for cleaning personnel. </p>"
},
{
"index": 17,
"heading": "H4: Can smartphones detect UWB tags?",
"text": "Yes, UWB Tags can be configured in JavaScript to act as BLE beacons, broadcasting for example, iBeacon packets. Smartphones can detect these packets and react to the presence of tags. They can also range with UWB-enabled iPhones or Androids with high precision, but that requires using non-JavaScript firmware since the interoperability standard defined by FiRa requires strict configuration.",
"words": 58,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (58 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Yes, UWB Tags can be configured in JavaScript to act as BLE beacons, broadcasting for example, iBeacon packets. Smartphones can detect these packets and react to the presence of tags. They can also range with UWB-enabled iPhones or Androids with high precision, but that requires using non-JavaScript firmware since the interoperability standard defined by FiRa requires strict configuration. </p>"
},
{
"index": 18,
"heading": "H4: Is location tracking better with smartphones or UWB tags?",
"text": "Well, it really depends on your objectives. If you are working on a consumer solution and need to provide indoor location or proximity experiences to hundreds of thousands of users, it would be easier to build a smartphone app. Although it might take time and might be a significant investment, it might also require the users to download an app compatible with their device, grant all the permissions, etc. On the ot...",
"words": 119,
"hasEvidence": false,
"reasons": [
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Well, it really depends on your objectives. If you are working on a consumer solution and need to provide indoor location or proximity experiences to hundreds of thousands of users, it would be easier to build a smartphone app. Although it might take time and might be a significant investment, it might also require the users to download an app compatible with their device, grant all the permissions, etc. On the other hand, if you are building a solution for a workplace of hundreds or even..."
},
{
"index": 19,
"heading": "H4: How many UWB tags can range with each other?",
"text": "When it comes to BLE, there is actually no limit and a tag can detect hundreds of other tags nearby. With UWB, it is also possible to range with 100 tags or so. Since ranging requires exchanging some packets, it might be less responsive for 100 tags compared to 10 tags.",
"words": 51,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (51 words; target 80-220)."
],
"html": "<p> When it comes to BLE, there is actually no limit and a tag can detect hundreds of other tags nearby. With UWB, it is also possible to range with 100 tags or so. Since ranging requires exchanging some packets, it might be less responsive for 100 tags compared to 10 tags. </p>"
},
{
"index": 20,
"heading": "H4: Can UWB tags be used for RTLS?",
"text": "Yes, UWB Tags can be programmed for Real-Time Location Systems (RTLS). Some will act as tags, broadcasting their presence and others will be anchors scanning for tags and computing their precise (X,Y) location using a technique called time difference of arrival (TDoA).",
"words": 43,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (43 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Yes, UWB Tags can be programmed for Real-Time Location Systems (RTLS). Some will act as tags, broadcasting their presence and others will be anchors scanning for tags and computing their precise (X,Y) location using a technique called time difference of arrival (TDoA). </p>"
},
{
"index": 21,
"heading": "H4: What are the security features?",
"text": "Our tags are protected by industry standard encryption to ensure only authorized users who own them can program and communicate with them. We also offer private cloud deployments in your AWS, GCP or Azure to ensure data are end-to-end encrypted and securely stored for your most sensitive applications.",
"words": 48,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (48 words; target 80-220)."
],
"html": "<p> Our tags are protected by industry standard encryption to ensure only authorized users who own them can program and communicate with them. We also offer private cloud deployments in your AWS, GCP or Azure to ensure data are end-to-end encrypted and securely stored for your most sensitive applications. </p>"
},
{
"index": 22,
"heading": "H4: Do you offer support?",
"text": "Yes, we offer comprehensive online API documentation, templates, demos and best practices. Additionally, we provide paid technical support to assist customers with integrating our tags into existing systems. We have deployed millions of tags globally for various applications and are always more than happy to share our experience.",
"words": 48,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (48 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Yes, we offer comprehensive online API documentation, templates, demos and best practices. Additionally, we provide paid technical support to assist customers with integrating our tags into existing systems. We have deployed millions of tags globally for various applications and are always more than happy to share our experience. </p>"
},
{
"index": 24,
"heading": "H4: How can I contact you?",
"text": "Simply shoot us a note to document.write(NoteToEstimote());[email protected] and our team will get back to arrange a discovery call. Once we know more about your vision and your use-case, we will recommend the best hardware and software and provide bulk pricing.",
"words": 45,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (45 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p> Simply shoot us a note to <span class=\"Note\"><script type=\"text/javascript\">document.write(NoteToEstimote());</script>[email protected]</span> and our team will get back to arrange a discovery call. Once we know more about your vision and your use-case, we will recommend the best hardware and software and provide bulk pricing. </p>"
}
],
"citableParagraphs": [
{
"index": 4,
"heading": "H4: How is UWB different from Bluetooth?",
"text": "UWB is a popular emerging technology for positioning. Every Apple iPhone since 2019 has a UWB chip that is used for precision finding, and there are 300+ million of them. Cars like Tesla and BMW use them for keyless car entry and hands-free experiences. If you are already familiar with Bluetooth Low Energy and its applications for IoT, beacons and proximity use-cases, you should think about UWB as the next-gen pos...",
"words": 91,
"hasEvidence": true,
"reasons": [],
"html": "<p> UWB is a popular emerging technology for positioning. Every Apple iPhone since 2019 has a UWB chip that is used for precision finding, and there are 300+ million of them. Cars like Tesla and BMW use them for keyless car entry and hands-free experiences. If you are already familiar with Bluetooth Low Energy and its applications for IoT, beacons and proximity use-cases, you should think about UWB as the next-gen positioning technology. It is far more accurate, equally low power, relatively..."
},
{
"index": 25,
"heading": "H4: Why should we work with you?",
"text": "Estimote, Inc. has been a market leader in location and proximity technologies for over a decade, developing cutting-edge solutions for a wide range of applications. Founded in 2012, Estimote has revolutionized the way businesses interact with physical spaces through the use of small, wireless sensors that leverage modern IoT radio technologies like Bluetooth, Ultra Wideband (UWB), and LTE/NB-IoT​. The company has...",
"words": 99,
"hasEvidence": true,
"reasons": [],
"html": "<p> Estimote, Inc. has been a market leader in location and proximity technologies for over a decade, developing cutting-edge solutions for a wide range of applications. Founded in 2012, Estimote has revolutionized the way businesses interact with physical spaces through the use of small, wireless sensors that leverage modern IoT radio technologies like Bluetooth, Ultra Wideband (UWB), and LTE/NB-IoT​. The company has successfully deployed millions of sensors worldwide for the most pro..."
}
],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
Needs attention
AIO: Google eligibility and indexability
Issue
Canonical tag is missing.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Google eligibility and indexability
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
Evidence
{
"status": 200,
"googlebotBlocked": false,
"metaRobotsTags": [],
"xRobotsTag": "",
"canonical": "",
"finalUrl": "https://estimote.com/",
"canonicalScore": 0,
"score": 80,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 65/100 and needs improvement.
1 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
1 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": 2,
"passing": 1,
"failing": [
{
"heading": "estimote",
"headingHtml": "<h3>estimote</h3>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
}
],
"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": "programmable in JavaScript",
"html": "<h2>programmable in JavaScript</h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Estimote UWB Tags?",
"pattern": {}
},
{
"id": "how",
"label": "How does Estimote UWB Tags work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Estimote UWB Tags?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Estimote UWB Tags free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Estimote UWB Tags compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Estimote UWB Tags?",
"pattern": {}
},
{
"id": "how",
"label": "How does Estimote UWB Tags work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Estimote UWB Tags?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Estimote UWB Tags free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Estimote UWB Tags compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 80/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 80/100 and needs improvement.
Needs attention
AIO: Page experience for AIO
Issue
22 image(s) are missing width/height attributes.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Page experience for AIO
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Page experience for AIO scored 80/100 and needs improvement.
Evidence
{
"viewportContent": "width=device-width, initial-scale=1.0",
"visibleWords": 1803,
"htmlBytes": 28151,
"imagesMissingDimensions": [
{
"src": "uwb-wearable.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"uwb-wearable.png\">"
},
{
"src": "single-uwb-wearable.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"Initiator\" src=\"single-uwb-wearable.png\">"
},
{
"src": "single-uwb-wearable.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"Responder\" src=\"single-uwb-wearable.png\">"
},
{
"src": "workplace.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"workplace.png\">"
},
{
"src": "health-care.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"health-care.png\">"
},
{
"src": "panic-button.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"panic-button.png\">"
},
{
"src": "workplace.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"workplace.png\">"
},
{
"src": "health-care.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"health-care.png\">"
},
{
"src": "panic-button.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"panic-button.png\">"
},
{
"src": "uwb-teardown.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"Teardown\" src=\"uwb-teardown.png\">"
},
{
"src": "uwb-devkit.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"uwb-devkit.png\">"
},
{
"src": "uwb-programming.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"IDE\" src=\"uwb-programming.png\">"
},
{
"src": "uwb-map.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"IDE\" src=\"uwb-map.png\">"
},
{
"src": "uwb-cloud-lambda.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"IDE\" src=\"uwb-cloud-lambda.png\">"
},
{
"src": "workplace.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"workplace.png\">"
},
{
"src": "health-care.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"health-care.png\">"
},
{
"src": "panic-button.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"panic-button.png\">"
},
{
"src": "workplace.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"workplace.png\">"
},
{
"src": "health-care.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"health-care.png\">"
},
{
"src": "panic-button.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"panic-button.png\">"
},
{
"src": "estimote-products.png",
"width": "",
"height": "",
"loading": "",
"html": "<img class=\"Customizations\" src=\"estimote-products.png\">"
},
{
"src": "estimote-logo.png",
"width": "",
"height": "",
"loading": "",
"html": "<img src=\"estimote-logo.png\">"
}
],
"possibleDialogs": [],
"score": 80,
"weight": 10
}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": "programmable in JavaScript",
"html": "<h2>programmable in JavaScript</h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Estimote UWB Tags?",
"pattern": {}
},
{
"id": "how",
"label": "How does Estimote UWB Tags work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Estimote UWB Tags?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Estimote UWB Tags free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Estimote UWB Tags compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Estimote UWB Tags?",
"pattern": {}
},
{
"id": "how",
"label": "How does Estimote UWB Tags work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Estimote UWB Tags?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Estimote UWB Tags free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Estimote UWB Tags compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 4
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Needs attention
GEO: Q&A and FAQ opportunities
Issue
1 h2 heading(s) are not phrased as questions; this is optional and only useful where Q&A wording is natural. No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Q&A and FAQ opportunities
Score
75/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Q&A and FAQ opportunities is informational for this page.
Evidence
{
"h2Count": 1,
"questionH2s": 0,
"hasFaq": false,
"nonQuestionH2s": [
{
"index": 1,
"text": "programmable in JavaScript",
"isQuestion": false,
"html": "<h2>programmable in JavaScript</h2>"
}
],
"score": 75,
"weight": 4
}AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
Why it matters
IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.
Check name
IndexNow key
Score
100/100
Status
informational
Category
Discoverability
Maturity
Established
Goal
Verify that IndexNow ownership key placement is detectable when the site advertises it.
Result
IndexNow key is informational for this page.
Validation steps
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
Fetch and validate IndexNow key file
No discoverable IndexNow key file was found.
Evidence
{
"steps": [
{
"id": "advertised-location",
"title": "Find advertised IndexNow key location",
"status": "informational",
"evidence": {
"advertised": []
},
"issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
"howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
},
{
"id": "fetch-key",
"title": "Fetch and validate IndexNow key file",
"status": "informational",
"evidence": {
"advertised": [],
"checked": []
},
"issue": "No discoverable IndexNow key file was found.",
"howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
}
]
}SEOSEOBrowser audit
Document does not have a meta description
50 Fail
SEOSEOBrowser audit
Document does not have a meta description
Check name
Document does not have a meta description
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).
Evidence
{
"description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}Performance and AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
50 Fail
Performance and AccessibilityAccessibilityBrowser audit
Heading elements are not in a sequentially-descending order
Check name
Heading elements are not in a sequentially-descending order
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order)."
}Performance and AccessibilityAccessibilityBrowser audit
Image elements do not have `[alt]` attributes
50 Fail
Performance and AccessibilityAccessibilityBrowser audit
Image elements do not have `[alt]` attributes
Check name
Image elements do not have `[alt]` attributes
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}SEOSEOBrowser audit
Image elements do not have `[alt]` attributes
50 Fail
SEOSEOBrowser audit
Image elements do not have `[alt]` attributes
Check name
Image elements do not have `[alt]` attributes
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).
Evidence
{
"description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}Performance and AccessibilityPerformanceBrowser audit
Avoid large layout shifts
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Avoid large layout shifts
Check name
Avoid large layout shifts
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
15 layout shifts found
Fix guidance
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "15 layout shifts found",
"description": "These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)"
}Performance and AccessibilityPerformanceBrowser audit
Document does not have a main landmark.
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Document does not have a main landmark.
Check name
Document does not have a main landmark.
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
One main landmark helps screen reader users navigate a web page. [Learn more about landmarks](https://dequeuniversity.com/rules/axe/4.11/landmark-one-main).
References
https://web.dev/learn/performance/Evidence
{
"description": "One main landmark helps screen reader users navigate a web page. [Learn more about landmarks](https://dequeuniversity.com/rules/axe/4.11/landmark-one-main)."
}Performance and AccessibilityPerformanceBrowser audit
LCP request discovery
20 Fail
Performance and AccessibilityPerformanceBrowser audit
LCP request discovery
Check name
LCP request discovery
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
References
https://web.dev/learn/performance/Evidence
{
"description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}Performance and AccessibilityPerformanceBrowser audit
Network dependency tree
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Network dependency tree
Check name
Network dependency tree
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
References
https://web.dev/learn/performance/Evidence
{
"description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load."
}Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
10 Warning
Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
Check name
Avoid enormous network payloads
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Total size was 6,337Â KiB
Fix guidance
Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Total size was 6,337Â KiB",
"description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
"numericValue": 6488810
}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 | Current report |