Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 46 out of 100
- Agent Ease of Use 10 out of 100
- Security & Trust 40 out of 100
- GEO, AIO and AEO 71 out of 100
- SEO 100 out of 100
- Performance and Accessibility 92 out of 100
What AI sees of your website
Mountain View Staffing - Silicon Valley/Bay Area Staffing
Silicon Valley's most trusted recruiting and staffing agency for full-time and contract hiring for technical and business roles at funded startups- Mountain View, Palo Alto, Sunnyvale, Santa Clara, San Jose, Menlo Park, Redwood City
Next step
Turn this report into a fix workflow
22 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 | 46 | Priority fix | 11 | 13 | 0 | View details |
| Discoverability | 67 | Needs work | 5 | 4 | 0 | View details |
| Content Readiness | 60 | Needs work | 6 | 5 | 0 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 10 | Priority fix | 17 | 22 | 1 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 11 | 0 | 0 | |
| MCP | 25 | Priority fix | 2 | 6 | 0 | View details |
| Skill Discovery | 5 | Priority fix | 0 | 10 | 1 | View details |
| Agent Commerce | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| GEO, AIO and AEO | 71 | Needs work | 7 | 3 | 10 | View details |
| GEO Readiness | 89 | Mostly ready | 2 | 0 | 4 | |
| AIO Readiness | 59 | Needs work | 3 | 2 | 2 | View details |
| AEO Readiness | 64 | Needs work | 2 | 1 | 4 | View details |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| Security & Trust | 40 | Priority fix | 6 | 3 | 0 | View details |
| Security & Trust | 40 | Priority fix | 2 | 3 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 92 | Strong | 21 | 4 | 1 | View details |
| Performance | 90 | Strong | 14 | 4 | 1 | View details |
| Accessibility | 96 | Strong | 7 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
38 items need attention
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
50 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
Needs attention
API Catalog
Issue
The API catalog endpoint did not return HTTP 2xx.
Why it matters
API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.
Check name
API Catalog
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated API discovery using RFC 9727.
Result
API Catalog failed at "Fetch API catalog".
Validation steps
Fetch API catalog
The API catalog endpoint did not return HTTP 2xx.
Validate RFC 9727 linkset
Response is not valid JSON.
Fetch advertised API catalog targets
API Catalog did not expose any same-origin hrefs to validate.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch API catalog",
"status": "fail",
"evidence": {
"statusCode": 400,
"contentType": "text/html; charset=UTF-8"
},
"issue": "The API catalog endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/api-catalog."
},
{
"id": "validate",
"title": "Validate RFC 9727 linkset",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>400 Error: Bad Request</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/unpk"
},
"issue": "Response is not valid JSON.",
"howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
},
{
"id": "target-validation",
"title": "Fetch advertised API catalog targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin API catalog hrefs were available to fetch."
}
]
},
"issue": "API Catalog did not expose any same-origin hrefs to validate.",
"howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
50 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing Last-Modified HTTP header; missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.
Why it matters
Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.
Check name
Content freshness signals
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is missing or incomplete.
Evidence
{
"lastModified": null,
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
50 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": [
"WebSite"
]
}AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
50 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence
{
"failedStep": "presence",
"steps": [
{
"id": "presence",
"title": "Find useful Link headers",
"status": "fail",
"evidence": {
"links": [
{
"url": "https://static.parastorage.com/",
"rel": "preconnect"
},
{
"url": "https://static.parastorage.com/",
"rel": "preconnect"
},
{
"url": "https://static.wixstatic.com/",
"rel": "preconnect"
},
{
"url": "https://static.wixstatic.com/",
"rel": "preconnect"
},
{
"url": "https://siteassets.parastorage.com",
"rel": "preconnect"
}
]
},
"issue": "No useful agent discovery Link headers were found.",
"howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
},
{
"id": "target-validation",
"title": "Fetch same-origin Link header targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin Link header targets were available to fetch."
}
]
},
"issue": "Link headers did not expose any same-origin targets to validate.",
"howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
50 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
Needs attention
Markdown negotiation
Issue
Content-Type "text/html; charset=UTF-8" does not indicate Markdown when requested with Accept: text/markdown.
Why it matters
Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.
Check name
Markdown negotiation
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Return HTML responses as markdown when agents request it.
Result
Markdown negotiation failed at "Markdown content type".
Validation steps
Markdown content type
Content-Type "text/html; charset=UTF-8" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "Accept-Encoding".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html; charset=UTF-8"
},
"issue": "Content-Type \"text/html; charset=UTF-8\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "Accept-Encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding\".",
"howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
},
{
"id": "markdown-content",
"title": "Structured Markdown body",
"status": "fail",
"evidence": {
"valid": false,
"hasHeading": false,
"wordCount": 26629,
"excerpt": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n \n <meta charset='utf-8'>\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" id=\"wixDesktopViewport\" />\n <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\">\n <meta name=\"gener",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
50 Fail
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Find valid OpenAPI document".
Needs attention
OpenAPI discovery
Issue
OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=UTF-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Why it matters
OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.
Check name
OpenAPI discovery
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for API discovery.
Result
OpenAPI discovery failed at "Find valid OpenAPI document".
Validation steps
Find valid OpenAPI document
OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=UTF-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Find valid OpenAPI document",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/openapi.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>400 Error: Bad Request</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/unpk"
},
{
"path": "/openapi.yaml",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>400 Error: Bad Request</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/unpk"
},
{
"path": "/swagger.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>400 Error: Bad Request</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/unpk"
},
{
"path": "/swagger.yaml",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>400 Error: Bad Request</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/unpk"
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>404 Error: Page Not Found</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/u"
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>404 Error: Page Not Found</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/u"
},
{
"path": "/docs/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "\n <!DOCTYPE html>\n<!--\n \n\n \n\n \n \n \n-->\n<html>\n<head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <meta name=\"robots\" content=\"noindex\">\n <title>404 Error: Page Not Found</title>\n\n \n <script async src=\"https://static.parastorage.com/polyfill/v2/polyfill.min.js?features=default,es6,es7,es2017&flags=gated&unknown=polyfill&rum=0\"></script>\n <script src=\"https://static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js\"></script>\n <script>fedopsLogger.reportAppLoadStarted(\"classic-error-pages-statics\");</script>\n <script src=\"https://static.parastorage.com/unpkg-semver/header-footer-provider/app.bundle.min.js\"></script>\n <script crossorigin src=\"https://static.parastorage.com/u"
}
]
},
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
}
]
}AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
Needs attention
AI bot rules in robots.txt
Issue
No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.
Why it matters
Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.
Check name
AI bot rules in robots.txt
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.
Result
AI bot rules in robots.txt is missing or incomplete.
Evidence
{
"expectedBots": [
"GPTBot",
"ChatGPT-User",
"ClaudeBot",
"Claude-Web",
"Anthropic-AI",
"Google-Extended",
"PerplexityBot",
"CCBot",
"Applebot-Extended",
"Meta-ExternalAgent",
"Bytespider",
"Amazonbot",
"Cohere-AI"
],
"configuredBots": []
}AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
Needs attention
Content Signal
Issue
No Content Signal found in robots.txt
Why it matters
Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.
Check name
Content Signal
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences with Content Signal in robots.txt.
Result
Content Signal is missing or incomplete.
Evidence
{
"signals": [],
"ai-train": false,
"search": false,
"ai-input": false
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
33 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
33 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
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
Needs attention
MCP Server Card
Issue
MCP Server Card was not found at the expected path.
Why it matters
MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.
Check name
MCP Server Card
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
MCP Server Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/.well-known/mcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "MCP Server Card was not found at the expected path.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
Needs attention
mcp.json
Issue
mcp.json was not found at the expected path.
Why it matters
MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.
Check name
mcp.json
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.
Result
mcp.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
mcp.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/mcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/.well-known/mcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "mcp.json was not found at the expected path.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
33 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
33 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing was not found at the expected path.
Why it matters
Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.
Check name
Web Bot Auth request signing
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.
Result
Web Bot Auth request signing failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Web Bot Auth request signing was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "Web Bot Auth request signing was not found at the expected path.",
"howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
}
]
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
Needs attention
WebMCP manifest
Issue
WebMCP manifest was not found at the expected path.
Why it matters
A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.
Check name
WebMCP manifest
Score
0/100
Status
fail
Category
MCP
Maturity
Informational
Goal
Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.
Result
WebMCP manifest failed at "Fetch to find resource".
Validation steps
Fetch to find resource
WebMCP manifest was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/webmcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/webmcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/mcp.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "WebMCP manifest was not found at the expected path.",
"howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
Needs attention
A2A Agent Card
Issue
A2A Agent Card was not found at the expected path.
Why it matters
A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.
Check name
A2A Agent Card
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent card so A2A-compatible clients can discover capabilities.
Result
A2A Agent Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
A2A Agent Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-card.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2206
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/agent-card.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "A2A Agent Card was not found at the expected path.",
"howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
Needs attention
Agent Skills index
Issue
Agent Skills index was not found at the expected path.
Why it matters
An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.
Check name
Agent Skills index
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent skills discovery index.
Result
Agent Skills index failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Agent Skills index was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-skills/index.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "Agent Skills index was not found at the expected path.",
"howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
Needs attention
agent.json
Issue
agent.json was not found at the expected path.
Why it matters
agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.
Check name
agent.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.
Result
agent.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agent.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/agent.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "agent.json was not found at the expected path.",
"howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
}
]
}Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
20 Fail
Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
Needs attention
agents.json
Issue
agents.json was not found at the expected path.
Why it matters
agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.
Check name
agents.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Informational
Goal
Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.
Result
agents.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agents.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agents.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
},
{
"path": "/agents.json",
"statusCode": 400,
"contentType": "text/html; charset=UTF-8",
"length": 2205
}
]
},
"issue": "agents.json was not found at the expected path.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
15 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID entrypoint records were found under _agents.
Why it matters
DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.
Check name
DNS-AID Agent Discovery
Score
25/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".
Validation steps
Resolve DNS-AID SVCB/HTTPS records
No DNS-AID entrypoint records were found under _agents.
Validate alpn and endpoint parameters
Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.
Check DNSSEC material
DNSSEC material was not visible for the hostname or parent zone from this resolver.
Evidence
{
"failedStep": "svcb-https-records",
"steps": [
{
"id": "svcb-https-records",
"title": "Resolve DNS-AID SVCB/HTTPS records",
"status": "fail",
"evidence": {
"hostname": "www.mountainviewstaffing.com",
"probes": [
{
"name": "_index._agents.www.mountainviewstaffing.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.www.mountainviewstaffing.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
}
]
},
"issue": "No DNS-AID entrypoint records were found under _agents.",
"howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
},
{
"id": "service-params",
"title": "Validate alpn and endpoint parameters",
"status": "informational",
"evidence": {
"discovered": []
},
"howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
},
{
"id": "dnssec",
"title": "Check DNSSEC material",
"status": "warning",
"evidence": {
"hasDnssecMaterial": false,
"checked": [
{
"name": "www.mountainviewstaffing.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
},
{
"name": "mountainviewstaffing.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
}
]
},
"issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
"howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
12 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
1 structured-data value(s) were not found in visible page text.
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": 1,
"checkedFields": [
{
"path": "$[0].name",
"value": "mountainviewstaffing"
}
],
"mismatches": [
{
"path": "$[0].name",
"value": "mountainviewstaffing"
}
],
"score": 0,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 20/100 and needs a fix.
10 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": "https://www.mountainviewstaffing.com/contact",
"text": "Contact Us",
"html": "<a data-testid=\"linkElement\" href=\"https://www.mountainviewstaffing.com/contact\" class=\"wNTNML\"><div class=\"MKZTGU\"><div class><p class=\"VhM8Ji\" id=\"DrpDwnMn0-hwd2label\" style=\"line-height: 25px;\">Contact Us</p></div></div></a>"
}
],
"privacyLinks": [],
"score": 20,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 20/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 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": "https://www.mountainviewstaffing.com/contact",
"text": "Contact Us",
"html": "<a data-testid=\"linkElement\" href=\"https://www.mountainviewstaffing.com/contact\" class=\"wNTNML\"><div class=\"MKZTGU\"><div class><p class=\"VhM8Ji\" id=\"DrpDwnMn0-hwd2label\" style=\"line-height: 25px;\">Contact Us</p></div></div></a>"
}
],
"privacyLinks": [],
"score": 20,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
AEO readiness is incomplete.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 0,
"questionH2s": [],
"hasFaq": true,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 80/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 80/100 and needs improvement.
Needs attention
AEO: Answer-first sections
Issue
AEO readiness is incomplete.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer-first sections
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer-first sections scored 80/100 and needs improvement.
Evidence
{
"sectionCount": 0,
"passing": 0,
"failing": [],
"score": 80,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 75/100 and needs improvement.
Needs attention
GEO: Explanatory content depth
Issue
5 explanatory paragraph(s) could be stronger for citation or AI extraction.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 5,
"citablePassages": 0,
"failingCandidateParagraphs": [
{
"index": 6,
"heading": "Before first heading",
"text": "Mountain View Staffing is the trusted recruiting and staffing agency of Silicon Valley based companies. We help startups to Fortune 500 companies hire full-time employees. We specialize in Engineering, Software, Marketing, Business and Administrative roles. We are local and understand the local market- companies, talent bar-hiring bar, motivations, benefits packages, salaries, commute, etc. when trying to match ca...",
"words": 62,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (62 words; target 80-220)."
],
"html": "<p class=\"font_8 wixui-rich-text__text\" style=\"font-size:16px; line-height:1.6em;\"><span style=\"letter-spacing:normal;\" class=\"wixui-rich-text__text\"><span style=\"font-size:16px;\" class=\"wixui-rich-text__text\">Mountain View Staffing is the trusted recruiting and staffing agency of Silicon Valley based companies. We help startups to Fortune 500 companies hire full-time employees. We specialize in Engineering, Software, Marketing, Business and Administrative roles. We are local and understand t..."
},
{
"index": 11,
"heading": "Before first heading",
"text": "Some positions we are often recruiting for. List is not updated frequently, so best way to apply is to email your resume to [email protected]. If there's a match we'll call you back asap. If we don't, you can be sure we read your resume but don't have anything right now. Sorry, but its impossible for us to respond, meet or give feedback to every applicant.",
"words": 67,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (67 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"font_8 wixui-rich-text__text\" style=\"font-size:16px; line-height:1.6em;\"><span style=\"letter-spacing:normal;\" class=\"wixui-rich-text__text\"><span style=\"font-size:16px;\" class=\"wixui-rich-text__text\">Some positions we are often recruiting for. </span></span><span style=\"letter-spacing:normal;\" class=\"wixui-rich-text__text\"><span style=\"font-size:16px;\" class=\"wixui-rich-text__text\">List is not updated frequently, so best way to apply is to email your resume to <a data-auto-reco..."
},
{
"index": 27,
"heading": "H1: Testimonials",
"text": "\"I can't dream going back to my full-time job now that I've discovered this new future of work. No pressure to impress anyone, worry about my colleagues outperforming me, working overtime to get a promotion, and other nonsense that come with the percieved illusion of a stable full-time job.",
"words": 49,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (49 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"font_8 wixui-rich-text__text\" style=\"line-height:1.6em; font-size:14px;\"><span class=\"wixui-rich-text__text\">"I can't dream going back to my full-time job now that I've discovered this new future of work. No pressure to impress anyone, worry about my colleagues outperforming me, working overtime to get a promotion, and other nonsense that come with the percieved illusion of a stable full-time job. </span></p>"
},
{
"index": 29,
"heading": "H1: Testimonials",
"text": "I've been working with Mountain View Tech Staffing for the last 18 months years and love the job, client, pay rate, flexibility and benefits. I decide when and where and how much I work for and the kind of projects I want to be involved in. MountainView Tech Staffing is the best talent agent in Silicon Valley\"",
"words": 57,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (57 words; target 80-220)."
],
"html": "<p class=\"font_8 wixui-rich-text__text\" style=\"line-height:1.6em; font-size:14px;\">I've been working with Mountain View Tech Staffing for the last 18 months years and love the job, client, pay rate, flexibility and benefits. I decide when and where and how much I work for and the kind of projects I want to be involved in. <span class=\"wixui-rich-text__text\">MountainView Tech Staffing is the best talent agent in Silicon Valley"</span></p>"
},
{
"index": 33,
"heading": "H1: Testimonials",
"text": "\"I have been working for Mountain View Tech Staffing for 2 years and appreciate the ease of doing business with them. They let me work, do what they are supposed to and never require me to follow up on anything. I just got converted to Full time and they didn't have any problem with that\"",
"words": 55,
"hasEvidence": true,
"reasons": [
"Too short for a citation-ready passage (55 words; target 80-220)."
],
"html": "<p class=\"font_8 wixui-rich-text__text\" style=\"line-height:1.6em; font-size:14px;\"><span class=\"wixui-rich-text__text\">"I have been working for Mountain View Tech Staffing</span> for 2 years and appreciate the ease of doing business with them. They let me work, do what they are supposed to and  never require me to follow up on anything. I just got converted to Full time and they didn't have any problem with that"</p>"
}
],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": true,
"definitionPatterns": 5,
"schemaBlocks": 1,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process"
],
"score": 85,
"weight": 24
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 89/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 89/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: bay, area, testimonials.
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
89/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 89/100 and needs improvement.
Evidence
{
"title": "Mountain View Staffing - Silicon Valley/Bay Area Staffing",
"h1": "Testimonials",
"description": "Silicon Valley's most trusted recruiting and staffing agency for full-time and contract hiring for technical and business roles at funded startups- Mountain View, Palo Alto, Sunnyvale, Santa Clara, San Jose, Menlo Park, Redwood City",
"topicOverlap": 0.625,
"topicTerms": [
"mountain",
"view",
"staffing",
"silicon",
"valley",
"bay",
"area",
"testimonials"
],
"descriptionTerms": [
"silicon",
"valley",
"most",
"trusted",
"recruiting",
"staffing",
"agency",
"full",
"time",
"contract",
"hiring",
"technical",
"business",
"roles",
"funded",
"startups",
"mountain",
"view",
"palo",
"alto"
],
"missingFromDescription": [
"bay",
"area",
"testimonials"
],
"score": 89,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer intent coverage
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer intent coverage scored 70/100 and needs improvement.
Evidence
{
"headings": [],
"expected": [
{
"id": "what",
"label": "What is Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Mountain View Staffing - Silicon Valley/Bay A... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Mountain View Staffing - Silicon Valley/Bay A... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 80/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 80/100 and needs improvement.
Needs attention
AIO: Answer block readiness
Issue
1 structured-data value(s) were not found in visible page text.
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Answer block readiness
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Answer block readiness scored 80/100 and needs improvement.
Evidence
{
"sectionCount": 0,
"passing": 0,
"failing": [],
"score": 80,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"length": 2208
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"length": 2208
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html; charset=UTF-8",
"length": 2208
}
]
},
"issue": "AI context endpoint was not found at the expected path.",
"howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Needs attention
AIO: Query intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Query intent coverage
Score
70/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Query intent coverage is informational for this page.
Evidence
{
"headings": [],
"expected": [
{
"id": "what",
"label": "What is Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Mountain View Staffing - Silicon Valley/Bay A... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "how",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Mountain View Staffing - Silicon Valley/Bay A...?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Mountain View Staffing - Silicon Valley/Bay A... free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Mountain View Staffing - Silicon Valley/Bay A... compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 4
}AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
Why it matters
IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.
Check name
IndexNow key
Score
100/100
Status
informational
Category
Discoverability
Maturity
Established
Goal
Verify that IndexNow ownership key placement is detectable when the site advertises it.
Result
IndexNow key is informational for this page.
Validation steps
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
Fetch and validate IndexNow key file
No discoverable IndexNow key file was found.
Evidence
{
"steps": [
{
"id": "advertised-location",
"title": "Find advertised IndexNow key location",
"status": "informational",
"evidence": {
"advertised": []
},
"issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
"howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
},
{
"id": "fetch-key",
"title": "Fetch and validate IndexNow key file",
"status": "informational",
"evidence": {
"advertised": [],
"checked": []
},
"issue": "No discoverable IndexNow key file was found.",
"howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
}
]
}Performance and AccessibilityPerformanceBrowser audit
`<frame>` or `<iframe>` elements do not have a title
20 Fail
Performance and AccessibilityPerformanceBrowser audit
`<frame>` or `<iframe>` elements do not have a title
Check name
`<frame>` or `<iframe>` elements do not have a title
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Screen reader users rely on frame titles to describe the contents of frames. [Learn more about frame titles](https://dequeuniversity.com/rules/axe/4.11/frame-title).
References
https://web.dev/learn/performance/Evidence
{
"description": "Screen reader users rely on frame titles to describe the contents of frames. [Learn more about frame titles](https://dequeuniversity.com/rules/axe/4.11/frame-title)."
}Performance and AccessibilityPerformanceBrowser audit
Image optimization
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Image optimization
Check name
Image optimization
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped image optimization checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "image-aspect-ratio",
"title": "Displays images with incorrect aspect ratio",
"score": 0
}
]
}Performance and AccessibilityPerformanceBrowser audit
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
Reduce unused JavaScript
10 Warning
Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
Check name
Reduce unused JavaScript
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 128Â KiB
Fix guidance
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 128Â KiB",
"description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
"numericValue": 0
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
2 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
88/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 10Â ms",
"numericValue": 12
},
{
"id": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "20Â ms",
"numericValue": 17.200289999999995
},
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 100,
"displayValue": "0.5Â s",
"numericValue": 490.69685650115997
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 68,
"displayValue": "260Â ms",
"numericValue": 255
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 41,
"displayValue": "280Â ms",
"numericValue": 279
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 96,
"displayValue": "2.0Â s",
"numericValue": 1997.575863439441
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 99,
"displayValue": "0.8Â s",
"numericValue": 832.0732860688433
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 99,
"displayValue": "0.7Â s",
"numericValue": 695.1916173364266
}
]
}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 |
|---|---|---|---|
| 63/100 | Level 3, Bot-Aware | Current report |