Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 49 out of 100
- Agent Ease of Use 23 out of 100
- Security & Trust 60 out of 100
- GEO, AIO and AEO 58 out of 100
- SEO 100 out of 100
- Performance and Accessibility 48 out of 100
What AI sees of your website
An error occurred | Teamwork.com
Teamwork.com offers complete operations control and powerful project management in one place. Drive efficiency, improve profits, and scale in confidence.
Next step
Turn this report into a fix workflow
21 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 | 49 | Priority fix | 10 | 13 | 1 | View details |
| Discoverability | 71 | Needs work | 5 | 4 | 0 | View details |
| Content Readiness | 63 | Needs work | 5 | 5 | 1 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 23 | Priority fix | 15 | 23 | 0 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | 67 | Needs work | 9 | 3 | 0 | View details |
| MCP | 25 | Priority fix | 2 | 6 | 0 | View details |
| Skill Discovery | 0 | Priority fix | 0 | 8 | 0 | View details |
| Agent Commerce | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| GEO, AIO and AEO | 58 | Needs work | 2 | 5 | 13 | View details |
| GEO Readiness | 60 | Needs work | 1 | 1 | 4 | View details |
| AIO Readiness | 60 | Needs work | 1 | 2 | 4 | View details |
| AEO Readiness | 53 | Needs work | 0 | 2 | 5 | View details |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| Security & Trust | 60 | Needs work | 7 | 2 | 0 | View details |
| Security & Trust | 60 | Needs work | 3 | 2 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 48 | Priority fix | 21 | 3 | 2 | View details |
| Performance | 25 | Priority fix | 15 | 2 | 2 | View details |
| Accessibility | 91 | Strong | 6 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
45 items need attention
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
50 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Fetch API catalog".
Needs attention
API Catalog
Issue
The API catalog endpoint did not return HTTP 2xx.
Why it matters
API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.
Check name
API Catalog
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated API discovery using RFC 9727.
Result
API Catalog failed at "Fetch API catalog".
Validation steps
Fetch API catalog
The API catalog endpoint did not return HTTP 2xx.
Validate RFC 9727 linkset
Response is not valid JSON.
Fetch advertised API catalog targets
API Catalog did not expose any same-origin hrefs to validate.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch API catalog",
"status": "fail",
"evidence": {
"statusCode": 404,
"contentType": "text/html"
},
"issue": "The API catalog endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/api-catalog."
},
{
"id": "validate",
"title": "Validate RFC 9727 linkset",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
"issue": "Response is not valid JSON.",
"howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
},
{
"id": "target-validation",
"title": "Fetch advertised API catalog targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin API catalog hrefs were available to fetch."
}
]
},
"issue": "API Catalog did not expose any same-origin hrefs to validate.",
"howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
}
]
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
50 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": "frame-ancestors 'self' localhost *.teamwork.com *.teamworkpm.net *.helpdocsite.com teams.microsoft.com *.teams.microsoft.com *.skype.com teamworkintegrations.ngrok.io *.us.teamworkops.com teams.cloud.microsoft outlook.cloud.microsoft m365.cloud.microsoft app.hubspot.com app-eu1.hubspot.com *.canva.com;"
}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": []
},
"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 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" 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": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/openapi.yaml",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/swagger.json",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/swagger.yaml",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
},
{
"path": "/docs/openapi.json",
"statusCode": 404,
"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><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project and Team Management Software | Teamwork</title>\n<link rel=\"preconnect\" href=\"//a.storyblok.com\">\n<link rel=\"preconnect\" href=\"https://dev.visualwebsiteoptimizer.com\">\n<link rel=\"preconnect\" href=\"https://cdn-website.teamwork.com\">\n<style>.d-none{display:none!important}.d-inline{display:inline!important}.d-inline-block{display:inline-block!important}.d-block{display:block!important}.d-table{display:table!important}.d-table-row{display:table-row!important}.d-table-cell{display:table-cell!important}.d-flex{display:flex!important}.d-inline-flex{display:inline-flex!important}@media(min-width:576px){.d-sm-none{display"
}
]
},
"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."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
50 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": [
"FAQPage",
"VideoObject"
]
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
50 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt is missing or incomplete.
Needs attention
AI bot rules in robots.txt
Issue
No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.
Why it matters
Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.
Check name
AI bot rules in robots.txt
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.
Result
AI bot rules in robots.txt is missing or incomplete.
Evidence
{
"expectedBots": [
"GPTBot",
"ChatGPT-User",
"ClaudeBot",
"Claude-Web",
"Anthropic-AI",
"Google-Extended",
"PerplexityBot",
"CCBot",
"Applebot-Extended",
"Meta-ExternalAgent",
"Bytespider",
"Amazonbot",
"Cohere-AI"
],
"configuredBots": []
}AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
33 Fail
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal is missing or incomplete.
Needs attention
Content Signal
Issue
No Content Signal found in robots.txt
Why it matters
Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.
Check name
Content Signal
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences with Content Signal in robots.txt.
Result
Content Signal is missing or incomplete.
Evidence
{
"signals": [],
"ai-train": false,
"search": false,
"ai-input": false
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
33 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, Origin".
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, Origin"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding, Origin\".",
"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": 65118,
"excerpt": "<!DOCTYPE html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, interactive-widget=resizes-content\">\n<title>Project, Resource & Financial Management Software for Busy Team",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
Needs attention
MCP Server Card
Issue
MCP Server Card was not found at the expected path.
Why it matters
MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.
Check name
MCP Server Card
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
MCP Server Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "MCP Server Card was not found at the expected path.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
Needs attention
mcp.json
Issue
mcp.json was not found at the expected path.
Why it matters
MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.
Check name
mcp.json
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.
Result
mcp.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
mcp.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "mcp.json was not found at the expected path.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
33 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; missing <footer> landmark; invalid h1 (found 0).
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": false,
"meaningfulH1": false,
"headingOrder": true,
"accessibleLinks": true,
"accessibleButtons": true,
"imageAltCoverage": true,
"formAutocompleteCoverage": true,
"details": {
"inaccessibleLinks": [],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [],
"imagesMissingAlt": [],
"skippedHeadingLevels": []
},
"counts": {
"h1": 0,
"headings": 1,
"links": 2,
"inaccessibleLinks": 0,
"buttons": 0,
"inaccessibleButtons": 0,
"images": 2,
"imagesWithAlt": 2,
"autocompleteInputs": 0,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 0
}
}AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
33 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing was not found at the expected path.
Why it matters
Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.
Check name
Web Bot Auth request signing
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.
Result
Web Bot Auth request signing failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Web Bot Auth request signing was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "Web Bot Auth request signing was not found at the expected path.",
"howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
}
]
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
33 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
Needs attention
WebMCP manifest
Issue
WebMCP manifest was not found at the expected path.
Why it matters
A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.
Check name
WebMCP manifest
Score
0/100
Status
fail
Category
MCP
Maturity
Informational
Goal
Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.
Result
WebMCP manifest failed at "Fetch to find resource".
Validation steps
Fetch to find resource
WebMCP manifest was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/webmcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"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 UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Probe authorization endpoint with an authorization-code request".
33 Fail
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Probe authorization endpoint with an authorization-code request".
Needs attention
OAuth / OIDC discovery
Issue
authorization_endpoint did not behave like an operational OAuth authorization endpoint.
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
67/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 "Probe authorization endpoint with an authorization-code request".
Validation steps
Probe authorization endpoint with an authorization-code request
authorization_endpoint did not behave like an operational OAuth authorization endpoint.
Fetch and validate jwks_uri
jwks_uri did not return usable JWK entries for the advertised signing algorithms.
Evidence
{
"failedStep": "authorization-endpoint",
"steps": [
{
"id": "fetch",
"title": "Fetch discovery resource",
"status": "pass",
"evidence": {
"path": "/.well-known/openid-configuration",
"statusCode": 200,
"contentType": "application/json; charset=UTF-8"
}
},
{
"id": "validate",
"title": "Validate resource body",
"status": "pass",
"evidence": {
"valid": true,
"compatibleContentType": true,
"missing": [],
"endpointIssues": [],
"issuer": "https://www.teamwork.com/launchpad",
"authorizationEndpoint": "https://www.teamwork.com/launchpad/login",
"tokenEndpoint": "https://www.teamwork.com/launchpad/v1/token.json",
"jwksUri": "https://www.teamwork.com/launchpad/v1/certs.json",
"responseTypesSupported": [
"code"
],
"grantTypesSupported": [
"authorization_code"
],
"idTokenSigningAlgValuesSupported": [
"RS256"
],
"rawExcerpt": "{\"authorization_endpoint\":\"https://www.teamwork.com/launchpad/login\",\"claims_supported\":[\"email\",\"family_name\",\"given_name\",\"picture\",\"user_id\",\"installation_id\",\"url\"],\"code_challenge_methods_supported\":[\"S256\"],\"grant_types_supported\":[\"authorization_code\"],\"id_token_signing_alg_values_supported\":[\"RS256\"],\"issuer\":\"https://www.teamwork.com/launchpad\",\"jwks_uri\":\"https://www.teamwork.com/launchpad/v1/certs.json\",\"response_types_supported\":[\"code\"],\"scopes_supported\":[\"openid\",\"projects\"],\"subject_types_supported\":[\"public\"],\"token_endpoint\":\"https://www.teamwork.com/launchpad/v1/token.json\",\"token_endpoint_auth_methods_supported\":[\"client_secret_post\"],\"userinfo_endpoint\":\"https://www.teamwork.com/launchpad/v1/userinfo.json\"}\n"
},
"howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
},
{
"id": "authorization-endpoint",
"title": "Probe authorization endpoint with an authorization-code request",
"status": "fail",
"evidence": {
"url": "https://www.teamwork.com/launchpad/login?response_type=code&client_id=can-agent-use-scanner&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Foauth%2Fcallback&scope=openid&state=can-agent-use-probe",
"method": "GET",
"statusCode": 405,
"location": null,
"contentType": "text/html; charset=UTF-8",
"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\">\n <title>Human Verification</title>\n <style>\n body {\n font-family: \"Arial\";\n }\n </style>\n <script type=\"text/javascript\">\n "
},
"issue": "authorization_endpoint did not behave like an operational OAuth authorization endpoint.",
"howToFix": "Implement an authorization endpoint that can process syntactically valid authorization requests, or remove it from discovery metadata until it exists."
},
{
"id": "authorization-redirect-safety",
"title": "Reject unregistered authorization redirects",
"status": "pass",
"evidence": {
"url": "https://www.teamwork.com/launchpad/login?response_type=code&client_id=can-agent-use-unknown-client&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Fattacker-callback&scope=openid&state=can-agent-use-redirect-safety",
"method": "GET",
"statusCode": 405,
"location": null,
"redirectedToUntrusted": false,
"contentType": "text/html; charset=UTF-8",
"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\">\n <title>Human Verification</title>\n <style>\n body {\n font-family: \"Arial\";\n }\n </style>\n <script type=\"text/javascript\">\n "
},
"howToFix": "Validate client_id and registered redirect_uri values before redirecting. Return a direct OAuth error for invalid clients or redirect URIs."
},
{
"id": "token-endpoint",
"title": "Probe token endpoint with advertised grant type",
"status": "pass",
"evidence": {
"url": "https://www.teamwork.com/launchpad/v1/token.json",
"method": "POST",
"grantType": "authorization_code",
"statusCode": 400,
"oauthError": "invalid_request",
"contentType": "application/json; charset=UTF-8",
"excerpt": "{\"error\":\"invalid_request\",\"error_description\":\"Missing client credentials\"}\n"
},
"howToFix": "Support every advertised grant type enough to return a protocol-appropriate response, or stop advertising unsupported grants."
},
{
"id": "jwks",
"title": "Fetch and validate jwks_uri",
"status": "fail",
"evidence": {
"jwksUri": "https://www.teamwork.com/launchpad/v1/certs.json",
"statusCode": 405,
"contentType": "text/html; charset=UTF-8"
},
"issue": "jwks_uri did not return usable JWK entries for the advertised signing algorithms.",
"howToFix": "Implement the advertised jwks_uri route with usable JWK metadata or remove it from discovery metadata until it exists."
}
],
"authApplicability": {
"supportsAuth": false,
"score": 0,
"signals": []
},
"resourceFetchSucceeded": true
}Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
25 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Fetch to find resource".
Needs attention
A2A Agent Card
Issue
A2A Agent Card was not found at the expected path.
Why it matters
A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.
Check name
A2A Agent Card
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent card so A2A-compatible clients can discover capabilities.
Result
A2A Agent Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
A2A Agent Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "A2A Agent Card was not found at the expected path.",
"howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
25 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Fetch to find resource".
Needs attention
Agent Skills index
Issue
Agent Skills index was not found at the expected path.
Why it matters
An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.
Check name
Agent Skills index
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an agent skills discovery index.
Result
Agent Skills index failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Agent Skills index was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent-skills/index.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "Agent Skills index was not found at the expected path.",
"howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
}
]
}Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
25 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agent.json
agent.json failed at "Fetch to find resource".
Needs attention
agent.json
Issue
agent.json was not found at the expected path.
Why it matters
agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.
Check name
agent.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.
Result
agent.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agent.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agent.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "agent.json was not found at the expected path.",
"howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
}
]
}Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
25 Fail
Agent Ease of UseSkill DiscoveryInformational
agents.json
agents.json failed at "Fetch to find resource".
Needs attention
agents.json
Issue
agents.json was not found at the expected path.
Why it matters
agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.
Check name
agents.json
Score
0/100
Status
fail
Category
Skill Discovery
Maturity
Informational
Goal
Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.
Result
agents.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
agents.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/agents.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"issue": "agents.json was not found at the expected path.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
8 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 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
75/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": "Thu, 04 Jun 2026 17:13:25 GMT",
"schemaDates": [
"2025-06-19T16:06:53+00:00",
"2025-10-30T10:55:40+00:00",
"2023-07-05T11:45:35+00:00",
"2024-08-09T15:56:25+00:00",
"2022-11-11T11:42:54+00:00"
],
"metaDateCount": 0,
"timeDateCount": 0
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 29/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 29/100 and needs a fix.
Needs attention
AIO: Visible structured data match
Issue
12 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
29/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 29/100 and needs a fix.
Evidence
{
"schemaCount": 6,
"checkedFields": [
{
"path": "$[0].mainEntity[0].name",
"value": "How is Teamwork.com different from other project management tools?"
},
{
"path": "$[0].mainEntity[1].name",
"value": "What types of businesses use Teamwork.com to manage projects?"
},
{
"path": "$[0].mainEntity[2].name",
"value": "I’m looking for resource management software – why should I choose Teamwork.com?"
},
{
"path": "$[0].mainEntity[3].name",
"value": "How does Teamwork.com help with resource allocation and planning?"
},
{
"path": "$[0].mainEntity[4].name",
"value": "Does Teamwork.com offer onboarding and implementation support?"
},
{
"path": "$[0].mainEntity[5].name",
"value": "Does Teamwork.com support teams globally?"
},
{
"path": "$[1].name",
"value": "Invanity Marketing"
},
{
"path": "$[1].publisher.name",
"value": "Teamwork.com"
},
{
"path": "$[2].name",
"value": "How to Build Client Projects Fast Using AI"
},
{
"path": "$[2].description",
"value": "<p>Agencies and PSAs can streamline client work and boost profitability by using AI-powered tools like Teamwork.com to automate project setup, optimize resource scheduling, and ensure accurate Time Tracking and budget management.\nAre you tired of excessive admin tasks slowing down your client delivery? This demo shows how professional services firms and agencies can use Teamwork.com to connect projects, resources, time, and profitability, making client work more efficient. The platform uses the AI Project Wizard to turn scattered briefs into fully built projects in clicks, drastically reducing setup time. The Smart Scheduler and Resource Planner ensure optimal staff allocation based on availability, improving billable utilization. Key features for successful agency operations include: - Streamlined Time Tracking with automated reminders. - Proactive Budget Management with instant spending alerts. - Powerful Utilization and Project Health Reports. - AI Forecaster for instant profitability predictions. Find out more about AI-powered agency operations here: https://www.teamwork.com/product/ai/</p>"
},
{
"path": "$[2].publisher.name",
"value": "Teamwork.com"
},
{
"path": "$[3].name",
"value": "Kyle Duford - The Brand Leader"
},
{
"path": "$[3].publisher.name",
"value": "Teamwork.com"
},
{
"path": "$[4].name",
"value": "OIC Advisors"
},
{
"path": "$[4].publisher.name",
"value": "Teamwork.com"
},
{
"path": "$[5].name",
"value": "ThreeSixtyEight Testimonial 4K"
},
{
"path": "$[5].publisher.name",
"value": "Teamwork.com"
}
],
"mismatches": [
{
"path": "$[0].mainEntity[0].name",
"value": "How is Teamwork.com different from other project management tools?"
},
{
"path": "$[0].mainEntity[1].name",
"value": "What types of businesses use Teamwork.com to manage projects?"
},
{
"path": "$[0].mainEntity[2].name",
"value": "I’m looking for resource management software – why should I choose Teamwork.com?"
},
{
"path": "$[0].mainEntity[3].name",
"value": "How does Teamwork.com help with resource allocation and planning?"
},
{
"path": "$[0].mainEntity[4].name",
"value": "Does Teamwork.com offer onboarding and implementation support?"
},
{
"path": "$[0].mainEntity[5].name",
"value": "Does Teamwork.com support teams globally?"
},
{
"path": "$[1].name",
"value": "Invanity Marketing"
},
{
"path": "$[2].name",
"value": "How to Build Client Projects Fast Using AI"
},
{
"path": "$[2].description",
"value": "<p>Agencies and PSAs can streamline client work and boost profitability by using AI-powered tools like Teamwork.com to automate project setup, optimize resource scheduling, and ensure accurate Time Tracking and budget management.\nAre you tired of excessive admin tasks slowing down your client delivery? This demo shows how professional services firms and agencies can use Teamwork.com to connect projects, resources, time, and profitability, making client work more efficient. The platform uses the AI Project Wizard to turn scattered briefs into fully built projects in clicks, drastically reducing setup time. The Smart Scheduler and Resource Planner ensure optimal staff allocation based on availability, improving billable utilization. Key features for successful agency operations include: - Streamlined Time Tracking with automated reminders. - Proactive Budget Management with instant spending alerts. - Powerful Utilization and Project Health Reports. - AI Forecaster for instant profitability predictions. Find out more about AI-powered agency operations here: https://www.teamwork.com/product/ai/</p>"
},
{
"path": "$[3].name",
"value": "Kyle Duford - The Brand Leader"
},
{
"path": "$[4].name",
"value": "OIC Advisors"
},
{
"path": "$[5].name",
"value": "ThreeSixtyEight Testimonial 4K"
}
],
"score": 29,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 25/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Explanatory content depth
GEO: Explanatory content depth scored 25/100 and needs a fix.
Needs attention
GEO: Explanatory content depth
Issue
No substantial explanatory paragraphs were found.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
25/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 25/100 and needs a fix.
Evidence
{
"candidatePassages": 1,
"citablePassages": 0,
"failingCandidateParagraphs": [],
"citableParagraphs": [],
"score": 25,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 40/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 40/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, aboutOrContact, policyLinks.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Source and trust signals
Score
40/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Source and trust signals scored 40/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": true,
"freshnessDate": true,
"aboutOrContact": false,
"policyLinks": false
},
"missing": [
"author",
"aboutOrContact",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [
"Teamwork.com"
],
"schemaDates": [
"2025-06-19T16:06:53+00:00",
"2025-10-30T10:55:40+00:00",
"2023-07-05T11:45:35+00:00",
"2024-08-09T15:56:25+00:00",
"2022-11-11T11:42:54+00:00"
],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [],
"privacyLinks": [],
"score": 40,
"weight": 20
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 40/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 40/100 and needs a fix.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: author, aboutOrContact, policyLinks.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer evidence and trust
Score
40/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer evidence and trust scored 40/100 and needs a fix.
Evidence
{
"signals": {
"author": false,
"publisher": true,
"freshnessDate": true,
"aboutOrContact": false,
"policyLinks": false
},
"missing": [
"author",
"aboutOrContact",
"policyLinks"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [
"Teamwork.com"
],
"schemaDates": [
"2025-06-19T16:06:53+00:00",
"2025-10-30T10:55:40+00:00",
"2023-07-05T11:45:35+00:00",
"2024-08-09T15:56:25+00:00",
"2022-11-11T11:42:54+00:00"
],
"visibleDates": [],
"aboutLinks": [],
"contactLinks": [],
"privacyLinks": [],
"score": 40,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 60/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 60/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: error, occurred.
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
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: Entity clarity scored 60/100 and needs improvement.
Evidence
{
"title": "An error occurred | Teamwork.com",
"h1": "",
"description": "Teamwork.com offers complete operations control and powerful project management in one place. Drive efficiency, improve profits, and scale in confidence.",
"topicOverlap": 0.5,
"topicTerms": [
"error",
"occurred",
"teamwork",
"com"
],
"descriptionTerms": [
"teamwork",
"com",
"offers",
"complete",
"operations",
"control",
"powerful",
"project",
"management",
"one",
"place",
"drive",
"efficiency",
"improve",
"profits",
"scale",
"confidence"
],
"missingFromDescription": [
"error",
"occurred"
],
"score": 60,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
3 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": 1,
"passing": 0,
"failing": [
{
"heading": "An error occurred",
"headingHtml": "<h3 data-v-6db2a4da class=\"tw-heading tw-heading--large tw-heading--bold error-page__title\">An error occurred</h3>",
"firstParagraph": "Sorry, we can't find that page. It might be an old link or maybe it was moved. Why not check out our Resource Center in the meantime?",
"paragraphHtml": "<p data-v-6db2a4da class=\"tw-paragraph tw-paragraph--large error-page__description\"> Sorry, we can't find that page. It might be an old link or maybe it was moved. Why not check out our Resource Center in the meantime? </p>",
"words": 27,
"direct": false,
"issue": "First paragraph is 27 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI crawler accessibility
GEO: AI crawler accessibility scored 65/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI crawler accessibility
GEO: AI crawler accessibility scored 65/100 and needs improvement.
Needs attention
GEO: AI crawler accessibility
Issue
Only 40 words of Chrome-rendered body text were detected.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: AI crawler accessibility
Score
65/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: AI crawler accessibility scored 65/100 and needs improvement.
Evidence
{
"textWords": 40,
"htmlBytes": 916586,
"robots": {
"checkedCrawlers": [
"gptbot",
"chatgpt-user",
"claudebot",
"perplexitybot",
"google-extended"
],
"blocked": [],
"allows": true
},
"schemaBlocks": 6,
"finalUrl": "https://www.teamwork.com/",
"robotsExcerpt": "User-agent: *\nSitemap: https://www.teamwork.com/sitemap.xml\n\nDisallow: /launchpad/*\nAllow: /launchpad/*js\nAllow: /launchpad/*css\nAllow: /launchpad/login\nAllow: *js\nAllow: *css\n",
"score": 65,
"weight": 26
}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
1 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 0,
"questionH2s": [],
"hasFaq": true,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 53/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 53/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: error, occurred.
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
53/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 53/100 and needs improvement.
Evidence
{
"title": "An error occurred | Teamwork.com",
"h1": "",
"description": "Teamwork.com offers complete operations control and powerful project management in one place. Drive efficiency, improve profits, and scale in confidence.",
"topicOverlap": 0.5,
"definitionCount": 0,
"topicTerms": [
"error",
"occurred",
"teamwork",
"com"
],
"descriptionTerms": [
"teamwork",
"com",
"offers",
"complete",
"operations",
"control",
"powerful",
"project",
"management",
"one",
"place",
"drive",
"efficiency",
"improve",
"profits",
"scale",
"confidence"
],
"missingFromDescription": [
"error",
"occurred"
],
"score": 53,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 75/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, clear definition sentence using "is", "means", or "refers to" where natural.
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
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: Extraction-friendly structure scored 75/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": true,
"definitionPatterns": 0,
"schemaBlocks": 6,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process",
"clear definition sentence using \"is\", \"means\", or \"refers to\" where natural"
],
"score": 75,
"weight": 24
}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://www.teamwork.com/",
"canonicalScore": 0,
"score": 80,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 65/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience for AIO
AIO: Page experience for AIO scored 65/100 and needs improvement.
Needs attention
AIO: Page experience for AIO
Issue
Only 40 words of visible rendered text were detected. 2 possible modal/interstitial element(s) detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Page experience for AIO
Score
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: Page experience for AIO scored 65/100 and needs improvement.
Evidence
{
"viewportContent": "width=device-width, initial-scale=1, interactive-widget=resizes-content",
"visibleWords": 40,
"htmlBytes": 916586,
"imagesMissingDimensions": [],
"possibleDialogs": [
"<div id=\"hs-interactives-modal-overlay\" class=\"go1632949049\"></div>",
"<div id=\"hs-overlay-cta-262297335017\" class=\"go3064412225\" role=\"dialog\" aria-modal=\"true\" style=\"width: 950px; height: 580.266px;\"><iframe src=\"https://26079973.hs-sites-eu1.com/hs-web-interactive-26079973-262297335017?utk=c72eb7e6487aa8d5870b3c8e0de0c7dd&enableResponsiveStyles=true\" aria-label=\"Popup CTA\" title=\"Popup CTA\" allow=\"autoplay; fullscreen; clipboard-write\" data-test-id=\"interactive-frame\" class=\"go812842568\" style=\"border-width: medium; border-style: none; border-color: curr..."
],
"score": 65,
"weight": 10
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 35/100 and needs a fix.
1 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 35/100 and needs a fix.
Needs attention
AEO: Extractable visible copy
Issue
Only 40 visible words were detected for answer extraction.
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Extractable visible copy
Score
35/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: Extractable visible copy scored 35/100 and needs a fix.
Evidence
{
"visibleWords": 40,
"schemaCount": 6,
"score": 35,
"weight": 6
}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": 1,
"passing": 0,
"failing": [
{
"heading": "An error occurred",
"headingHtml": "<h3 data-v-6db2a4da class=\"tw-heading tw-heading--large tw-heading--bold error-page__title\">An error occurred</h3>",
"firstParagraph": "Sorry, we can't find that page. It might be an old link or maybe it was moved. Why not check out our Resource Center in the meantime?",
"paragraphHtml": "<p data-v-6db2a4da class=\"tw-paragraph tw-paragraph--large error-page__description\"> Sorry, we can't find that page. It might be an old link or maybe it was moved. Why not check out our Resource Center in the meantime? </p>",
"words": 27,
"direct": false,
"issue": "First paragraph is 27 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer intent coverage
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer intent coverage scored 70/100 and needs improvement.
Evidence
{
"headings": [],
"expected": [
{
"id": "what",
"label": "What is An error occurred?",
"pattern": {}
},
{
"id": "how",
"label": "How does An error occurred work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use An error occurred?",
"pattern": {}
},
{
"id": "cost",
"label": "Is An error occurred free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does An error occurred compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is An error occurred?",
"pattern": {}
},
{
"id": "how",
"label": "How does An error occurred work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use An error occurred?",
"pattern": {}
},
{
"id": "cost",
"label": "Is An error occurred free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does An error occurred compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html",
"length": 112234
}
]
},
"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 An error occurred?",
"pattern": {}
},
{
"id": "how",
"label": "How does An error occurred work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use An error occurred?",
"pattern": {}
},
{
"id": "cost",
"label": "Is An error occurred free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does An error occurred compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is An error occurred?",
"pattern": {}
},
{
"id": "how",
"label": "How does An error occurred work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use An error occurred?",
"pattern": {}
},
{
"id": "cost",
"label": "Is An error occurred free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does An error occurred 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 AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
100 Fail
Performance and AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
Check name
Background and foreground colors do not have a sufficient contrast ratio.
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.10/color-contrast).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.10/color-contrast)."
}Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
Check name
Browser errors were logged to the console
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Fix guidance
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)
Evidence
{
"description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
50 Fail
Performance and AccessibilityBest PracticesBrowser audit
Uses deprecated APIs
Check name
Uses deprecated APIs
Score
0/100
Status
fail
Device
desktop
Category
Best Practices
Estimated savings
1 warning found
Fix guidance
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).
Evidence
{
"displayValue": "1 warning found",
"description": "Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/)."
}Performance and AccessibilityPerformanceBrowser audit
Reduce JavaScript execution time
25 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce JavaScript execution time
Check name
Reduce JavaScript execution time
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
40.2Â s
Fix guidance
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "40.2Â s",
"description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
"numericValue": 40215.84399999786
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
18 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
27/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 0,
"displayValue": "4.3Â s",
"numericValue": 4251.2333
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 0,
"displayValue": "30.6Â s",
"numericValue": 30606.528299999998
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 0,
"displayValue": "21.3Â s",
"numericValue": 21267.523058242725
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 0,
"displayValue": "37,730Â ms",
"numericValue": 37732.203299999994
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 0,
"displayValue": "2,320Â ms",
"numericValue": 2319
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 290Â ms",
"numericValue": 291.18600000000004
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 0,
"displayValue": "56.2Â s",
"numericValue": 56172.5399
},
{
"id": "uses-rel-preconnect",
"title": "Preconnect to required origins",
"score": 100
},
{
"id": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "10Â ms",
"numericValue": 14.65668
},
{
"id": "third-party-summary",
"title": "Reduce the impact of third-party code",
"score": 0,
"displayValue": "Third-party code blocked the main thread for 17,490Â ms"
},
{
"id": "largest-contentful-paint-element",
"title": "Largest Contentful Paint element",
"score": 0,
"displayValue": "30,610Â ms"
}
]
}Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
13 Warning
Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
Check name
Avoid enormous network payloads
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Total size was 2,727Â KiB
Fix guidance
Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Total size was 2,727Â 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": 2792661
}Performance and AccessibilityPerformanceBrowser audit
Serve static assets with an efficient cache policy
13 Warning
Performance and AccessibilityPerformanceBrowser audit
Serve static assets with an efficient cache policy
Check name
Serve static assets with an efficient cache policy
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
14 resources found
Fix guidance
A long cache lifetime can speed up repeat visits to your page. [Learn more about efficient cache policies](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "14 resources found",
"description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about efficient cache policies](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/).",
"numericValue": 296251.5758845438
}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 |
|---|---|---|---|
| 47/100 | Level 2, Agent-Limited | Current report |