Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 38 out of 100
- Agent Ease of Use 6 out of 100
- Security & Trust 0 out of 100
- GEO, AIO and AEO 83 out of 100
- SEO 92 out of 100
- Performance and Accessibility 62 out of 100
What AI sees of your website
Greenhouse | Applicant tracking software & hiring platform
Greenhouse is more than your typical ATS recruiting software, powered by built-in AI recruiting tools to streamline sourcing, hiring and talent management.
Next step
Turn this report into a fix workflow
28 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 | 38 | Priority fix | 7 | 15 | 1 | View details |
| Discoverability | 67 | Needs work | 5 | 4 | 0 | View details |
| Content Readiness | 38 | Priority fix | 2 | 7 | 1 | View details |
| Bot Access Control | 0 | Priority fix | 0 | 4 | 0 | View details |
| Agent Ease of Use | 6 | Priority fix | 4 | 29 | 3 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 0 | 7 | 0 | View details |
| MCP | 13 | Priority fix | 0 | 6 | 2 | 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 | 83 | Mostly ready | 6 | 0 | 10 | |
| GEO Readiness | 87 | Mostly ready | 1 | 0 | 4 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | 72 | Needs work | 1 | 0 | 6 | |
| SEO | 92 | Strong | 10 | 1 | 0 | View details |
| SEO | 92 | Strong | 10 | 1 | 0 | View details |
| Security & Trust | 0 | Priority fix | 4 | 5 | 0 | View details |
| Security & Trust | 0 | Priority fix | 0 | 5 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 62 | Needs work | 18 | 6 | 2 | View details |
| Performance | 45 | Priority fix | 14 | 4 | 2 | View details |
| Accessibility | 94 | Strong | 4 | 2 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
49 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; charset=utf-8"
},
"issue": "The API catalog endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/api-catalog."
},
{
"id": "validate",
"title": "Validate RFC 9727 linkset",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"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 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; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Why it matters
OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.
Check name
OpenAPI discovery
Score
0/100
Status
fail
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for API discovery.
Result
OpenAPI discovery failed at "Find valid OpenAPI document".
Validation steps
Find valid OpenAPI document
OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Find valid OpenAPI document",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"path": "/openapi.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"path": "/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"path": "/swagger.yaml",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"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": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"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": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
},
{
"path": "/docs/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
}
]
},
"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 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": [
"SoftwareApplication"
]
}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 DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
33 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Fetch to find resource".
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing was not found at the expected path.
Why it matters
Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.
Check name
Web Bot Auth request signing
Score
0/100
Status
fail
Category
Bot Access Control
Maturity
Informational
Goal
Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.
Result
Web Bot Auth request signing failed at "Fetch to find resource".
Validation steps
Fetch to find resource
Web Bot Auth request signing was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/http-message-signatures-directory",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"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."
}
]
}AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch to find resource".
25 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch to find resource".
Needs attention
llms.txt
Issue
llms.txt was not found at the expected path.
Why it matters
llms.txt gives language-model clients a concise, curated summary of important site context and links before they crawl broadly.
Check name
llms.txt
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish llms.txt to summarize agent-readable site guidance.
Result
llms.txt failed at "Fetch to find resource".
Validation steps
Fetch to find resource
llms.txt was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/llms.txt",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
},
{
"path": "/llms-full.txt",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"issue": "llms.txt was not found at the expected path.",
"howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation failed at "Markdown content type".
Needs attention
Markdown negotiation
Issue
Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.
Why it matters
Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.
Check name
Markdown negotiation
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Return HTML responses as markdown when agents request it.
Result
Markdown negotiation failed at "Markdown content type".
Validation steps
Markdown content type
Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "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": 18928,
"excerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"6668a687e71e2722fccb8366\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellim",
"issue": "Markdown response is missing a heading."
},
"issue": "Markdown response is missing a heading.",
"howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
}
]
}Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
25 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Fetch to find resource".
Needs attention
MCP Server Card
Issue
MCP Server Card was not found at the expected path.
Why it matters
MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.
Check name
MCP Server Card
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card for agent discovery.
Result
MCP Server Card failed at "Fetch to find resource".
Validation steps
Fetch to find resource
MCP Server Card was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "MCP Server Card was not found at the expected path.",
"howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
}
]
}Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
25 Fail
Agent Ease of UseMCPEmerging recommendation
mcp.json
mcp.json failed at "Fetch to find resource".
Needs attention
mcp.json
Issue
mcp.json was not found at the expected path.
Why it matters
MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.
Check name
mcp.json
Score
0/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.
Result
mcp.json failed at "Fetch to find resource".
Validation steps
Fetch to find resource
mcp.json was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "mcp.json was not found at the expected path.",
"howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is missing or incomplete.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: invalid h1 (found 2); skipped heading levels; 5 links missing accessible names; 0/2 applicable form inputs have autocomplete attributes (2 missing).
Details
Why it matters
Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.
Check name
Semantic HTML
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose readable page structure through semantic HTML and accessible controls.
Result
Semantic HTML is missing or incomplete.
Evidence
{
"main": true,
"nav": true,
"footer": true,
"meaningfulH1": false,
"headingOrder": false,
"accessibleLinks": false,
"accessibleButtons": true,
"imageAltCoverage": true,
"formAutocompleteCoverage": false,
"details": {
"inaccessibleLinks": [
"<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb056f\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb056f\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220e99",
"<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0571\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0571\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220e99",
"<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0573\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0573\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220e99",
"<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0575\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0575\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220e99",
"<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0577\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0577\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220e99"
],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [
"<input class=\"navigation-search w-input\" maxlength=\"256\" name=\"query\" placeholder type=\"search\" id=\"search-3\" required aria-hidden=\"false\" tabindex=\"0\">",
"<input id=\"Email\" name=\"Email\" maxlength=\"255\" aria-labelledby=\"LblEmail InstructEmail\" type=\"email\" class=\"mktoField mktoEmailField mktoHasWidth mktoRequired\" aria-required=\"true\" style=\"width: 400px;\">"
],
"imagesMissingAlt": [],
"skippedHeadingLevels": [
"h1: The only hiring platform you’ll",
"h1: ever need",
"h3: Greenhouse has entered into a definitive agreement to acquire Ezra AI Labs, bringing conversational AI to the hiring process.",
"h3: Real Talent",
"h2: See who’s hiring with Greenhouse",
"h2: Great companies hire with Greenhouse",
"h2: The best teams start with hiring – and the best hiring starts with Greenhouse",
"h3: Flex and scale with ease",
"h2: Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.",
"h2: Everything you need to get better at hiring"
]
},
"counts": {
"h1": 2,
"headings": 10,
"links": 136,
"inaccessibleLinks": 5,
"buttons": 7,
"inaccessibleButtons": 0,
"images": 40,
"imagesWithAlt": 40,
"autocompleteInputs": 2,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 2
}
}Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
25 Fail
Agent Ease of UseMCPInformational
WebMCP manifest
WebMCP manifest failed at "Fetch to find resource".
Needs attention
WebMCP manifest
Issue
WebMCP manifest was not found at the expected path.
Why it matters
A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.
Check name
WebMCP manifest
Score
0/100
Status
fail
Category
MCP
Maturity
Informational
Goal
Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.
Result
WebMCP manifest failed at "Fetch to find resource".
Validation steps
Fetch to find resource
WebMCP manifest was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"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": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"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": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"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": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"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": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"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."
}
]
}Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy is missing or incomplete.
Needs attention
Content-Security-Policy
Issue
Content-Security-Policy is missing or incomplete.
Why it matters
Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.
Check name
Content-Security-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain script, style, frame, and resource loading with a Content-Security-Policy header.
Result
Content-Security-Policy is missing or incomplete.
Evidence
{
"header": "content-security-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection is missing or incomplete.
Needs attention
Frame protection
Issue
Frame protection is missing or incomplete.
Why it matters
Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.
Check name
Frame protection
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.
Result
Frame protection is missing or incomplete.
Evidence
{
"xFrameOptions": null,
"validXFrame": false,
"contentSecurityPolicy": null,
"cspFrameAncestors": false
}Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header is missing or incomplete.
Needs attention
HSTS header
Issue
HSTS header is missing or incomplete.
Why it matters
HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade and mixed-transport risk for repeat users.
Check name
HSTS header
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat visits with Strict-Transport-Security.
Result
HSTS header is missing or incomplete.
Evidence
{
"header": "strict-transport-security",
"value": null
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
20 Fail
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
Needs attention
X-Content-Type-Options
Issue
X-Content-Type-Options is missing or incomplete.
Why it matters
X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.
Check name
X-Content-Type-Options
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent MIME sniffing for browser-loaded resources.
Result
X-Content-Type-Options is missing or incomplete.
Evidence
{
"header": "x-content-type-options",
"value": null
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
19 Warning
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.
Why it matters
Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.
Check name
Content freshness signals
Score
25/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval and ranking.
Result
Content freshness signals is partially implemented.
Evidence
{
"lastModified": "Fri, 05 Jun 2026 20:43:16 GMT",
"schemaDates": [],
"metaDateCount": 0,
"timeDateCount": 0
}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.greenhouse.com",
"probes": [
{
"name": "_index._agents.www.greenhouse.com",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.www.greenhouse.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.greenhouse.com",
"dnssecTypes": [],
"dnssecRecordCount": 0
},
{
"name": "greenhouse.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."
}
]
}Agent Ease of UseMCPInformational
WebMCP
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
13 Warning
Agent Ease of UseMCPInformational
WebMCP
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
Needs attention
WebMCP
Issue
WebMCP declarative annotations need fixes.
Details
Why it matters
WebMCP can expose page context and actions directly through the browser, giving agents safer structured hooks than screen scraping alone.
Check name
WebMCP
Score
50/100
Status
warning
Category
MCP
Maturity
Informational
Goal
Support WebMCP to expose site tools to AI agents via the browser.
Result
WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".
Validation steps
Detect data-mcp-tool annotations
No data-mcp-tool attributes were found on interactive elements.
Detect WebMCP declarative tags
No elements found with tool-name or tool-description attributes.
Validate WebMCP declarative annotation quality
WebMCP declarative annotations need fixes.
WebMCP declarative annotation issues
<input name="query"> is missing tool-param-description.<input> is missing a name attribute.<input> is missing a label.<input> is missing tool-param-description.<input name="Email"> is missing tool-param-description.
Detect WebMCP imperative API usage
navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.
Detect WebMCP browser navigator injection
navigator.modelContext was not detected in the rendered browser page.
Interactive surface coverage
Only 0% of interactive surfaces are annotated.
Evidence
{
"failedStep": "declarative-annotation-quality",
"steps": [
{
"id": "data-mcp-tool-attributes",
"title": "Detect data-mcp-tool annotations",
"status": "informational",
"evidence": {
"dataMcpToolCount": 0,
"dataMcpTools": []
},
"issue": "No data-mcp-tool attributes were found on interactive elements.",
"howToFix": "Add data-mcp-tool attributes to high-value forms, buttons, and links so generic MCP-aware tooling can identify intended actions."
},
{
"id": "declarative-tags",
"title": "Detect WebMCP declarative tags",
"status": "informational",
"evidence": {
"totalForms": 3,
"formsWithTags": 0,
"totalInteractive": 146,
"interactiveWithTags": 0,
"totalCount": 149,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"query\"> is missing tool-param-description.",
"<input> is missing a name attribute.",
"<input> is missing a label.",
"<input> is missing tool-param-description.",
"<input name=\"Email\"> is missing tool-param-description."
]
},
"issue": "No elements found with tool-name or tool-description attributes.",
"howToFix": "Add tool-name and tool-description attributes to forms and interactive elements."
},
{
"id": "declarative-annotation-quality",
"title": "Validate WebMCP declarative annotation quality",
"status": "warning",
"evidence": {
"issueCount": 5,
"issues": [
"<input name=\"query\"> is missing tool-param-description.",
"<input> is missing a name attribute.",
"<input> is missing a label.",
"<input> is missing tool-param-description.",
"<input name=\"Email\"> is missing tool-param-description."
]
},
"issue": "WebMCP declarative annotations need fixes.",
"issueDetails": [
{
"title": "WebMCP declarative annotation issues",
"items": [
{
"type": "code",
"value": "<input name=\"query\"> is missing tool-param-description."
},
{
"type": "code",
"value": "<input> is missing a name attribute."
},
{
"type": "code",
"value": "<input> is missing a label."
},
{
"type": "code",
"value": "<input> is missing tool-param-description."
},
{
"type": "code",
"value": "<input name=\"Email\"> is missing tool-param-description."
}
]
}
],
"howToFix": "Use snake_case tool-name values, descriptive tool-description values, named and labeled fields, and tool-param-description on inputs."
},
{
"id": "imperative-api",
"title": "Detect WebMCP imperative API usage",
"status": "informational",
"evidence": {
"staticSignals": {
"detected": false,
"matched": []
},
"browser": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
},
"issue": "navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.",
"howToFix": "Use navigator.modelContext.provideContext() to register tools programmatically."
},
{
"id": "browser-navigator-injection",
"title": "Detect WebMCP browser navigator injection",
"status": "informational",
"evidence": {
"browser": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
},
"issue": "navigator.modelContext was not detected in the rendered browser page.",
"howToFix": "Expose WebMCP through navigator.modelContext in the browser runtime when the page is intended to provide in-page tools."
},
{
"id": "surface-coverage",
"title": "Interactive surface coverage",
"status": "informational",
"evidence": {
"totalForms": 3,
"formsWithTags": 0,
"totalInteractive": 146,
"interactiveWithTags": 0,
"totalCount": 149,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"query\"> is missing tool-param-description.",
"<input> is missing a name attribute.",
"<input> is missing a label.",
"<input> is missing tool-param-description.",
"<input name=\"Email\"> is missing tool-param-description."
]
},
"issue": "Only 0% of interactive surfaces are annotated.",
"howToFix": "Add WebMCP annotations to all forms and interactive elements to increase agent coverage."
}
],
"staticSignals": {
"detected": false,
"matched": []
},
"coverage": {
"totalForms": 3,
"formsWithTags": 0,
"totalInteractive": 146,
"interactiveWithTags": 0,
"totalCount": 149,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"query\"> is missing tool-param-description.",
"<input> is missing a name attribute.",
"<input> is missing a label.",
"<input> is missing tool-param-description.",
"<input name=\"Email\"> is missing tool-param-description."
]
},
"browserWebMcp": {
"checked": true,
"detected": false,
"hasNavigatorModelContext": false,
"modelContextType": "undefined",
"hasProvideContext": false,
"hasRegisterTool": false
}
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first sections
AEO: Answer-first sections scored 65/100 and needs improvement.
Needs attention
AEO: Answer-first sections
Issue
8 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": 8,
"passing": 0,
"failing": [
{
"heading": "Greenhouse has entered into a definitive agreement to acquire Ezra AI Labs, bringing conversational AI to the hiring process.",
"headingHtml": "<h3 class=\"heading-medium promo\"><strong>Greenhouse has entered into a definitive agreement to acquire Ezra AI Labs</strong>, bringing conversational AI to the hiring process.</h3>",
"firstParagraph": "Greenhouse AI",
"paragraphHtml": "<p><strong>Greenhouse AI</strong></p>",
"words": 2,
"direct": false,
"issue": "First paragraph is 2 words and does not look like a concise direct answer."
},
{
"heading": "Real Talent",
"headingHtml": "<h3><strong>Real Talent</strong></h3>",
"firstParagraph": "Greenhouse Real Talent™ brings triple layers of trust to hiring with candidate fraud detection, identity verification and candidate matching software, so you can make more confident hiring decisions.",
"paragraphHtml": "<p>Greenhouse Real Talent™ brings triple layers of trust to hiring with candidate fraud detection, identity verification and candidate matching software, so you can make more confident hiring decisions. </p>",
"words": 28,
"direct": false,
"issue": "First paragraph is 28 words and does not look like a concise direct answer."
},
{
"heading": "See who’s hiring with Greenhouse",
"headingHtml": "<h2>See who’s hiring with Greenhouse</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Great companies hire with Greenhouse",
"headingHtml": "<h2>Great companies hire with Greenhouse</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "The best teams start with hiring – and the best hiring starts with Greenhouse",
"headingHtml": "<h2>The best teams start with hiring – and the best hiring starts with Greenhouse</h2>",
"firstParagraph": "Everything you need to hire, in one platform",
"paragraphHtml": "<p><strong>Everything you need to hire, in one platform</strong></p>",
"words": 8,
"direct": false,
"issue": "First paragraph is 8 words and does not look like a concise direct answer."
},
{
"heading": "Flex and scale with ease",
"headingHtml": "<h3><strong>Flex and scale with ease</strong></h3>",
"firstParagraph": "Greenhouse has everything you need for great hiring in one easy-to-use platform. Plus, you can connect with business tools you already use and customize a tech stack with our hundreds of pre-built integrations.",
"paragraphHtml": "<p>Greenhouse has everything you need for great hiring in one easy-to-use platform. Plus, you can connect with business tools you already use and customize a tech stack with our hundreds of pre-built integrations. </p>",
"words": 33,
"direct": false,
"issue": "First paragraph is 33 words and does not look like a concise direct answer."
},
{
"heading": "Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.",
"headingHtml": "<h2>Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.</h2>",
"firstParagraph": "Peter Tam",
"paragraphHtml": "<p><strong>Peter Tam</strong></p>",
"words": 2,
"direct": false,
"issue": "First paragraph is 2 words and does not look like a concise direct answer."
},
{
"heading": "Everything you need to get better at hiring",
"headingHtml": "<h2>Everything you need to get better at hiring </h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
No question-led h2 sections or FAQ pattern was detected.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Question-led structure
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Question-led structure scored 50/100 and needs improvement.
Evidence
{
"h2Count": 5,
"questionH2s": [],
"hasFaq": false,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 83/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 83/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: applicant, tracking, platform, only.
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
83/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 83/100 and needs improvement.
Evidence
{
"title": "Greenhouse | Applicant tracking software & hiring platform",
"h1": "The only hiring platform you’ll",
"description": "Greenhouse is more than your typical ATS recruiting software, powered by built-in AI recruiting tools to streamline sourcing, hiring and talent management.",
"topicOverlap": 0.42857142857142855,
"topicTerms": [
"greenhouse",
"applicant",
"tracking",
"software",
"hiring",
"platform",
"only"
],
"descriptionTerms": [
"greenhouse",
"more",
"than",
"typical",
"ats",
"recruiting",
"software",
"powered",
"built",
"tools",
"streamline",
"sourcing",
"hiring",
"talent",
"management"
],
"missingFromDescription": [
"applicant",
"tracking",
"platform",
"only"
],
"score": 83,
"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
No substantial explanatory paragraphs were found.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 1,
"citablePassages": 0,
"failingCandidateParagraphs": [],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 85/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": false,
"definitionPatterns": 3,
"schemaBlocks": 1,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process",
"optional visible FAQ or FAQPage schema"
],
"score": 85,
"weight": 24
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 80/100 and needs improvement.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: freshnessDate.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer evidence and trust
Score
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 evidence and trust scored 80/100 and needs improvement.
Evidence
{
"signals": {
"author": true,
"publisher": true,
"freshnessDate": false,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"freshnessDate"
],
"authorMeta": "",
"schemaAuthors": [
"Peter Tam"
],
"schemaPublishers": [
"Greenhouse",
"Ocado Group"
],
"schemaDates": [],
"visibleDates": [],
"aboutLinks": [
{
"href": "/scaling-company",
"text": "Scaling company",
"html": "<a tabindex=\"-1\" aria-hidden=\"true\" data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb04aa\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb04aa\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb..."
},
{
"href": "/company",
"text": "Company",
"html": "<a tabindex=\"-1\" aria-hidden=\"true\" data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0520\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0520\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb..."
},
{
"href": "https://www.linkedin.com/company/greenhouse-inc-/",
"text": "",
"html": "<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb0571\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb0571\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220..."
},
{
"href": "/ai-recruiting",
"text": "Learn about AI recruiting",
"html": "<a data-wf-native-id-path=\"e6905b18-3e83-656b-9ad2-b4e3bfa24037:335c73ce-c38b-e546-07d8-e3dcf8e04bfa\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"335c73ce-c38b-e546-07d8-e3dcf8e04bfa\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22335c73ce-c38b-e546-07d8-e3dcf8e04bf9%22%2C%22instanceId%22%3A%22e6905b18-3e83-656b-9ad2-b4e3bfa24037%22%7D%5D\" href=\"/ai-recruiting\" data-wf-event-ids class=\"buttonnew w-button button-text-green\">Learn about AI recruiting</a>"
},
{
"href": "/scaling-company",
"text": "Scaling company",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df310117ba\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df310117ba\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"/scaling-company\" class=\"link-block-7 w-inline-block\"><span>Scaling company</span></a>"
},
{
"href": "/company",
"text": "Company",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df310117da\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df310117da\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"/company\" class=\"link-block-7 w-inline-block\"><span>Company</span></a>"
},
{
"href": "https://www.linkedin.com/company/greenhouse-inc-/",
"text": "",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df3101182d\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df3101182d\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"https://www.linkedin.com/company/greenhouse-inc-/\" target=\"_blank\" class=\"social footer-social-link w-inline-block\"><img..."
}
],
"contactLinks": [
{
"href": "https://support.greenhouse.io/hc/en-us",
"text": "Get support",
"html": "<a tabindex=\"-1\" aria-hidden=\"true\" data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb050f\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb050f\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb..."
},
{
"href": "/contact",
"text": "Contact",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df310117e6\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df310117e6\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"/contact\" class=\"link-block-7 w-inline-block\"><span>Contact</span></a>"
},
{
"href": "https://support.greenhouse.io/hc/en-us",
"text": "Customer support",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df31011806\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df31011806\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"https://support.greenhouse.io/hc/en-us\" class=\"link-block-7 w-inline-block\"><span>Customer support</span></a>"
}
],
"privacyLinks": [
{
"href": "/privacy-policy",
"text": "Privacy Policy",
"html": "<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb057c\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb057c\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220..."
},
{
"href": "/legal",
"text": "Terms of service",
"html": "<a data-wf-native-id-path=\"3b734924-cc69-d1ca-3453-c5c466798999:0e99f551-0381-5516-4c05-fc9a1638250d:70c70397-29a5-0c0d-bf2c-deadb5cb057f\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"70c70397-29a5-0c0d-bf2c-deadb5cb057f\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22333c0404-1247-5dc2-252d-f5f1275de9e9%22%2C%22instanceId%22%3A%223b734924-cc69-d1ca-3453-c5c466798999%22%7D%2C%7B%22componentId%22%3A%2270c70397-29a5-0c0d-bf2c-deadb5cb046d%22%2C%22instanceId%22%3A%220..."
},
{
"href": "/privacy-policy",
"text": "Privacy policy",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df31011842\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df31011842\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"/privacy-policy\" class=\"link-10\">Privacy policy</a>"
},
{
"href": "/legal",
"text": "Terms of service",
"html": "<a data-wf-native-id-path=\"0e084c62-0e64-becc-4b50-cb2156b22037:d8f601bd-30a9-0371-7f2b-42df31011845\" data-wf-ao-click-engagement-tracking=\"true\" data-wf-element-id=\"d8f601bd-30a9-0371-7f2b-42df31011845\" data-wf-component-context=\"%5B%7B%22componentId%22%3A%22d8f601bd-30a9-0371-7f2b-42df3101175f%22%2C%22instanceId%22%3A%220e084c62-0e64-becc-4b50-cb2156b22037%22%7D%5D\" href=\"/legal\" class=\"link-10\">Terms of service</a>"
}
],
"score": 80,
"weight": 22
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 86/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 86/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: applicant, tracking, platform, only.
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
86/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 86/100 and needs improvement.
Evidence
{
"title": "Greenhouse | Applicant tracking software & hiring platform",
"h1": "The only hiring platform you’ll",
"description": "Greenhouse is more than your typical ATS recruiting software, powered by built-in AI recruiting tools to streamline sourcing, hiring and talent management.",
"topicOverlap": 0.42857142857142855,
"definitionCount": 3,
"topicTerms": [
"greenhouse",
"applicant",
"tracking",
"software",
"hiring",
"platform",
"only"
],
"descriptionTerms": [
"greenhouse",
"more",
"than",
"typical",
"ats",
"recruiting",
"software",
"powered",
"built",
"tools",
"streamline",
"sourcing",
"hiring",
"talent",
"management"
],
"missingFromDescription": [
"applicant",
"tracking",
"platform",
"only"
],
"score": 86,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: what, cost.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer intent coverage
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer intent coverage scored 70/100 and needs improvement.
Evidence
{
"headings": [
{
"text": "See who’s hiring with Greenhouse",
"html": "<h2>See who’s hiring with Greenhouse</h2>"
},
{
"text": "Great companies hire with Greenhouse",
"html": "<h2>Great companies hire with Greenhouse</h2>"
},
{
"text": "The best teams start with hiring – and the best hiring starts with Greenhouse",
"html": "<h2>The best teams start with hiring – and the best hiring starts with Greenhouse</h2>"
},
{
"text": "Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.",
"html": "<h2>Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.</h2>"
},
{
"text": "Everything you need to get better at hiring",
"html": "<h2>Everything you need to get better at hiring </h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Greenhouse?",
"pattern": {}
},
{
"id": "how",
"label": "How does Greenhouse work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Greenhouse?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Greenhouse free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Greenhouse compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Greenhouse?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Greenhouse free or paid?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851
}
]
},
"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."
}
]
}Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Needs attention
Auth.md Agent Registration
Issue
auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.
Why it matters
Agent registration metadata lets automated clients find the registration path, supported identity types, credential types, and related claim or revocation endpoints without scraping human docs.
Check name
Auth.md Agent Registration
Score
0/100
Status
informational
Category
Auth
Maturity
Emerging recommendation
Goal
Publish Auth.md and agent_auth metadata so agents can discover registration and credential requirements.
Result
Auth.md Agent Registration has an informational finding because the page appears to support authentication.
Validation steps
Fetch and validate /auth.md
auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.
Publish protected resource metadata
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Validate agent_auth authorization metadata
OAuth authorization server metadata could not be fetched.
Evidence
{
"failedStep": "auth-md",
"steps": [
{
"id": "auth-md",
"title": "Fetch and validate /auth.md",
"status": "fail",
"evidence": {
"path": "/auth.md",
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 156851,
"validation": {
"valid": false,
"issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
"compatibleContentType": false,
"contentLength": 144244,
"hasRegisterInstructions": true,
"hasProtectedResourceLink": false,
"hasAuthorizationServerLink": false,
"mentionsIdentity": false,
"mentionsCredential": false,
"links": [
"https://cdn.prod.website-files.com\"",
"/title",
"https://www.greenhouse.com/404\"/><link",
"https://www.greenhouse.com/404\"/><link",
"https://www.greenhouse.com/uk/404\"/><link",
"https://www.greenhouse.com/de/404\"/><meta",
"https://cdn.prod.website-files.com/6668a687e71e2722fccb8357/6a0e4a6604e53c65d24dc379_SEO_404_Onboarding-tasks-and-office-workers.png\"",
"https://cdn.prod.website-files.com/6668a687e71e2722fccb8357/6a0e4a6604e53c65d24dc379_SEO_404_Onboarding-tasks-and-office-workers.png\"",
"https://cdn.prod.website-files.com/6668a687e71e2722fccb8357/css/www-greenhouse-com.shared.f6d112cfe.min.css\"",
"/css"
],
"rawExcerpt": "<!DOCTYPE html><!-- Last Published: Fri Jun 05 2026 19:17:49 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.greenhouse.com\" data-wf-page=\"67378fc42b0b210ac499256a\" data-wf-site=\"6668a687e71e2722fccb8357\" data-wf-intellimize-customer-id=\"117853634\" lang=\"en-US\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><link rel=\"alternate\" hrefLang=\"x-default\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-US\" href=\"https://www.greenhouse.com/404\"/><link rel=\"alternate\" hrefLang=\"en-GB\" href=\"https://www.greenhouse.com/uk/404\"/><link rel=\"alternate\" hrefLang=\"de-DE\" href=\"https://www.greenhouse.com/de/404\"/><meta content=\"Not Found\" property=\"og:title\"/><meta c"
}
},
"issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
"howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
},
{
"id": "oauth-protected-resource",
"title": "Publish protected resource metadata",
"status": "fail",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88,
"text": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
},
{
"id": "agent-auth-block",
"title": "Validate agent_auth authorization metadata",
"status": "fail",
"evidence": {
"valid": false,
"issue": "OAuth authorization server metadata could not be fetched.",
"fetch": {
"ok": false,
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88,
"text": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
}
},
"issue": "OAuth authorization server metadata could not be fetched.",
"howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"resourceFetchSucceeded": false
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Needs attention
GEO: Q&A and FAQ opportunities
Issue
5 h2 heading(s) are not phrased as questions; this is optional and only useful where Q&A wording is natural. No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Q&A and FAQ opportunities
Score
75/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Q&A and FAQ opportunities is informational for this page.
Evidence
{
"h2Count": 5,
"questionH2s": 0,
"hasFaq": false,
"nonQuestionH2s": [
{
"index": 1,
"text": "See who’s hiring with Greenhouse",
"isQuestion": false,
"html": "<h2>See who’s hiring with Greenhouse</h2>"
},
{
"index": 2,
"text": "Great companies hire with Greenhouse",
"isQuestion": false,
"html": "<h2>Great companies hire with Greenhouse</h2>"
},
{
"index": 3,
"text": "The best teams start with hiring – and the best hiring starts with Greenhouse",
"isQuestion": false,
"html": "<h2>The best teams start with hiring – and the best hiring starts with Greenhouse</h2>"
},
{
"index": 4,
"text": "Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.",
"isQuestion": false,
"html": "<h2>Greenhouse has made a real difference to how we hire at Ocado Group. It’s helped us simplify our recruitment processes, cutting our time-to-hire by nearly 30%.</h2>"
},
{
"index": 5,
"text": "Everything you need to get better at hiring",
"isQuestion": false,
"html": "<h2>Everything you need to get better at hiring </h2>"
}
],
"score": 75,
"weight": 4
}AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
Why it matters
IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.
Check name
IndexNow key
Score
100/100
Status
informational
Category
Discoverability
Maturity
Established
Goal
Verify that IndexNow ownership key placement is detectable when the site advertises it.
Result
IndexNow key is informational for this page.
Validation steps
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
Fetch and validate IndexNow key file
No discoverable IndexNow key file was found.
Evidence
{
"steps": [
{
"id": "advertised-location",
"title": "Find advertised IndexNow key location",
"status": "informational",
"evidence": {
"advertised": []
},
"issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
"howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
},
{
"id": "fetch-key",
"title": "Fetch and validate IndexNow key file",
"status": "informational",
"evidence": {
"advertised": [],
"checked": []
},
"issue": "No discoverable IndexNow key file was found.",
"howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
}
]
}Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Needs attention
OAuth / OIDC discovery
Issue
OAuth / OIDC discovery was not found at the expected path.
Why it matters
OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.
Check name
OAuth / OIDC discovery
Score
0/100
Status
informational
Category
Auth
Maturity
Established
Goal
Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.
Result
OAuth / OIDC discovery has an informational finding because the page appears to support authentication.
Validation steps
Fetch to find resource
OAuth / OIDC discovery was not found at the expected path.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "fail",
"evidence": {
"checked": [
{
"path": "/.well-known/openid-configuration",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
},
{
"path": "/.well-known/oauth-authorization-server",
"statusCode": 404,
"contentType": "text/html; charset=utf-8",
"length": 88
}
]
},
"issue": "OAuth / OIDC discovery was not found at the expected path.",
"howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"resourceFetchSucceeded": false
}Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Informational
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Needs attention
OAuth Protected Resource
Issue
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Why it matters
Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.
Check name
OAuth Protected Resource
Score
0/100
Status
informational
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.
Result
OAuth Protected Resource has an informational finding because the page appears to support authentication.
Validation steps
Fetch protected resource metadata
The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.
Validate protected resource metadata
Response is not valid JSON.
Validate protected resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
Probe protected API Bearer challenge
No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.
Evidence
{
"failedStep": "fetch",
"steps": [
{
"id": "fetch",
"title": "Fetch protected resource metadata",
"status": "fail",
"evidence": {
"path": "/.well-known/oauth-protected-resource",
"statusCode": 404,
"contentType": "text/html; charset=utf-8"
},
"issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
"howToFix": "Publish /.well-known/oauth-protected-resource JSON."
},
{
"id": "metadata",
"title": "Validate protected resource metadata",
"status": "fail",
"evidence": {
"valid": false,
"compatibleContentType": false,
"issue": "Response is not valid JSON.",
"rawExcerpt": "<!DOCTYPE html>\n<html>\n <body>\n <p>Invalid .well-known request</p>\n </body>\n</html>"
},
"issue": "Response is not valid JSON.",
"howToFix": "Publish resource and authorization_servers as absolute URLs."
},
{
"id": "resource-identity",
"title": "Validate protected resource identity",
"status": "fail",
"evidence": {
"expectedResource": "https://www.greenhouse.com"
},
"issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
"howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
},
{
"id": "protected-route-challenge",
"title": "Probe protected API Bearer challenge",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/admin/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.greenhouse.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/admin/summary",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.greenhouse.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
},
{
"path": "/api/scans",
"statusCode": 404,
"wwwAuthenticate": {
"valid": false,
"present": false
},
"expectedMetadataUrl": "https://www.greenhouse.com/.well-known/oauth-protected-resource",
"metadataUrlMatches": true,
"resourceMatchesRequestContext": true
}
]
},
"issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
"howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
}
],
"authApplicability": {
"supportsAuth": true,
"score": 6,
"signals": [
{
"source": "visible-text",
"weight": 3,
"match": "sign in"
},
{
"source": "visible-text",
"weight": 3,
"match": "sign up"
}
]
},
"resourceFetchSucceeded": false
}Performance and AccessibilityBest PracticesBrowser audit
Browser errors were logged to the console
100 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/)"
}SEOSEOBrowser audit
Links do not have descriptive text
100 Fail
SEOSEOBrowser audit
Links do not have descriptive text
Check name
Links do not have descriptive text
Score
0/100
Status
fail
Device
desktop
Category
SEO
Estimated savings
5 links found
Fix guidance
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).
Evidence
{
"displayValue": "5 links found",
"description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/)."
}Performance and AccessibilityAccessibilityBrowser audit
Elements use prohibited ARIA attributes
50 Fail
Performance and AccessibilityAccessibilityBrowser audit
Elements use prohibited ARIA attributes
Check name
Elements use prohibited ARIA attributes
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. [Learn more about prohibited ARIA roles](https://dequeuniversity.com/rules/axe/4.11/aria-prohibited-attr).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. [Learn more about prohibited ARIA roles](https://dequeuniversity.com/rules/axe/4.11/aria-prohibited-attr)."
}Performance and AccessibilityAccessibilityBrowser audit
Elements with visible text labels do not have matching accessible names.
50 Fail
Performance and AccessibilityAccessibilityBrowser audit
Elements with visible text labels do not have matching accessible names.
Check name
Elements with visible text labels do not have matching accessible names.
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. [Learn more about accessible names](https://dequeuniversity.com/rules/axe/4.11/label-content-name-mismatch).
References
https://web.dev/learn/accessibility/Evidence
{
"description": "Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. [Learn more about accessible names](https://dequeuniversity.com/rules/axe/4.11/label-content-name-mismatch)."
}Performance and AccessibilityPerformanceBrowser audit
Network dependency tree
17 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 CSS
17 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 130 KiB
Fix guidance
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 130 KiB",
"description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
"numericValue": 120
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
17 Fail
Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
Check name
Reduce unused JavaScript
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 569 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 569 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": 480
}Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
8 Warning
Performance and AccessibilityPerformanceBrowser audit
Avoid enormous network payloads
Check name
Avoid enormous network payloads
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Total size was 4,737 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 4,737 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": 4850890
}Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
8 Warning
Performance and AccessibilityPerformanceBrowser audit
Legacy JavaScript
Check name
Legacy JavaScript
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 31 KiB
Fix guidance
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 31 KiB",
"description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
8 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
53/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "network-rtt",
"title": "Network Round Trip Times",
"score": 100,
"displayValue": "20 ms",
"numericValue": 18.93312
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 23,
"displayValue": "3.2 s",
"numericValue": 3176.048063555216
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 9,
"displayValue": "4.8 s",
"numericValue": 4825.055541379057
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 25,
"displayValue": "540 ms",
"numericValue": 539.9999999999989
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 39,
"displayValue": "5.1 s",
"numericValue": 5105.458619806603
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 10 ms",
"numericValue": 5
},
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 79,
"displayValue": "1.1 s",
"numericValue": 1124.0099183726961
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 45,
"displayValue": "270 ms",
"numericValue": 265.9999999999982
}
]
}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 |
|---|---|---|---|
| 45/100 | Level 2, Agent-Limited | Current report |