Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 26 out of 100
- Agent Ease of Use 6 out of 100
- Security & Trust 60 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 100 out of 100
- Performance and Accessibility 95 out of 100
What AI sees of your website
Apache Airflow
Platform created by the community to programmatically author, schedule and monitor workflows.
Next step
Turn this report into a fix workflow
25 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 26 | Priority fix | 4 | 18 | 1 | View details |
| Discoverability | 29 | Priority fix | 2 | 7 | 0 | View details |
| Content Readiness | 42 | 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 | 15 | 22 | 3 | View details |
| API | 0 | Priority fix | 0 | 6 | 0 | View details |
| Auth | Not Applicable | Not Applicable | 11 | 0 | 0 | |
| 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 | 68 | Needs work | 4 | 1 | 14 | View details |
| GEO Readiness | 74 | Needs work | 1 | 0 | 4 | |
| AIO Readiness | 62 | Needs work | 2 | 1 | 4 | View details |
| AEO Readiness | 66 | Needs work | 1 | 0 | 6 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| SEO | 100 | Strong | 11 | 0 | 0 | |
| Security & Trust | 60 | Needs work | 7 | 2 | 0 | View details |
| Security & Trust | 60 | Needs work | 3 | 2 | 0 | View details |
| AI Training Exposure | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| Performance and Accessibility | 95 | Strong | 23 | 3 | 0 | View details |
| Performance | 93 | Strong | 16 | 3 | 0 | View details |
| Accessibility | 100 | Strong | 7 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
44 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=iso-8859-1"
},
"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 PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
"issue": "Response is not valid JSON.",
"howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
},
{
"id": "target-validation",
"title": "Fetch advertised API catalog targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin API catalog hrefs were available to fetch."
}
]
},
"issue": "API Catalog did not expose any same-origin hrefs to validate.",
"howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
}
]
}Agent Ease of 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=iso-8859-1" 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=iso-8859-1" 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=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/openapi.yaml",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/swagger.yaml",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/api/openapi.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/api/swagger.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"valid": false,
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
"compatibleContentType": false,
"format": "yaml",
"version": "",
"pathCount": 0,
"operationCount": 0,
"rawExcerpt": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n</body></html>\n"
},
{
"path": "/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": "<html>\n<head><title>404 Not Found</title></head>\n<body>\n<h1>404 Not Found</h1>\n<ul>\n<li>Code: NoSuchKey</li>\n<li>Message: The specified key does not exist.</li>\n<li>Key: docs/openapi.json</li>\n<li>RequestId: TBKDJ9PWWC43A45R</li>\n<li>HostId: UZAeFKkdb6cc+wmieip1cMVqCG/Q3IP92gNpyCviVxraCmf80hi8ZA2o5krdUQgkobeg+/bLwrWP5Fm3MJSmK5NzBOZA5Dko</li>\n</ul>\n<hr/>\n</body>\n</html>\n"
}
]
},
"issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=iso-8859-1\" 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."
}
]
}Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
50 Fail
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy is missing or incomplete.
Needs attention
Referrer-Policy
Issue
Referrer-Policy is missing or incomplete.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
0/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site.
Result
Referrer-Policy is missing or incomplete.
Evidence
{
"header": "referrer-policy",
"value": null
}Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options is missing or incomplete.
50 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 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=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/llms-full.txt",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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" does not indicate Markdown when requested with Accept: text/markdown.
Why it matters
Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.
Check name
Markdown negotiation
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Return HTML responses as markdown when agents request it.
Result
Markdown negotiation failed at "Markdown content type".
Validation steps
Markdown content type
Content-Type "text/html" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "Accept-Encoding".
Structured Markdown body
Markdown response is missing a heading.
Evidence
{
"failedStep": "content-type",
"steps": [
{
"id": "content-type",
"title": "Markdown content type",
"status": "fail",
"evidence": {
"statusCode": 200,
"contentType": "text/html"
},
"issue": "Content-Type \"text/html\" does not indicate Markdown when requested with Accept: text/markdown.",
"howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
},
{
"id": "vary-accept",
"title": "Vary: Accept header",
"status": "fail",
"evidence": {
"vary": "Accept-Encoding"
},
"issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding\".",
"howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
},
{
"id": "markdown-content",
"title": "Structured Markdown body",
"status": "fail",
"evidence": {
"valid": false,
"hasHeading": false,
"wordCount": 16591,
"excerpt": "<!doctype html>\n<html lang=\"en\" class=\"no-js\">\n<head>\n \n<meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, shrink-to-fit=no\">\n<meta name=\"generator\" content=\"Hugo 0.146.0\">\n\n<META NAME=\"ROBOTS\" CON",
"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=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/mcp/server-cards.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/mcp/server-card.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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: 0/1 applicable form inputs have autocomplete attributes (1 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": true,
"headingOrder": true,
"accessibleLinks": true,
"accessibleButtons": true,
"imageAltCoverage": true,
"formAutocompleteCoverage": false,
"details": {
"inaccessibleLinks": [],
"inaccessibleButtons": [],
"missingAutocompleteInputs": [
"<input id=\"integrations-search\" class=\"search-form__input\" placeholder=\"Search\" name=\"q\" type=\"search\" size=\"16\" aria-label=\"Search integrations\">"
],
"imagesMissingAlt": [],
"skippedHeadingLevels": []
},
"counts": {
"h1": 1,
"headings": 17,
"links": 40,
"inaccessibleLinks": 0,
"buttons": 10,
"inaccessibleButtons": 0,
"images": 0,
"imagesWithAlt": 0,
"autocompleteInputs": 1,
"inputsWithAutocomplete": 0,
"missingAutocompleteInputs": 1
}
}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=iso-8859-1",
"length": 196
},
{
"path": "/webmcp.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/mcp.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/a2a/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/agent-card.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/.well-known/skills/index.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/agent.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"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=iso-8859-1",
"length": 196
},
{
"path": "/agents.json",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"issue": "agents.json was not found at the expected path.",
"howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
FAQPage schema
FAQPage schema is missing or incomplete.
Needs attention
FAQPage schema
Issue
FAQ content was detected but no FAQPage schema was found.
Why it matters
FAQPage schema lets agents extract visible question-and-answer content cleanly and avoid guessing which text is an answer.
Check name
FAQPage schema
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose question-and-answer content in FAQPage structured data when FAQs are present.
Result
FAQPage schema is missing or incomplete.
Evidence
{
"found": false,
"visibleFaq": true,
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
High-value schema types
High-value schema types is missing or incomplete.
Needs attention
High-value schema types
Issue
No high-value schema types (e.g. Article, Product, Service) were found.
Why it matters
High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.
Check name
High-value schema types
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Use schema types that describe the page's primary content or offering.
Result
High-value schema types is missing or incomplete.
Evidence
{
"found": [],
"expected": [
"Article",
"BlogPosting",
"NewsArticle",
"Product",
"SoftwareApplication",
"FAQPage",
"LocalBusiness",
"VideoObject",
"HowTo",
"Event",
"Course",
"Review",
"Service"
],
"allTypes": []
}AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
JSON-LD present
JSON-LD present is missing or incomplete.
Needs attention
JSON-LD present
Issue
No JSON-LD blocks found.
Why it matters
JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.
Check name
JSON-LD present
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Expose schema.org JSON-LD so AI search systems can parse page entities.
Result
JSON-LD present is missing or incomplete.
Evidence
{
"blocks": 0,
"validBlocks": 0,
"schemaContextBlocks": 0,
"errors": [],
"documents": [],
"nodes": []
}AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
20 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence
{
"failedStep": "presence",
"steps": [
{
"id": "presence",
"title": "Find useful Link headers",
"status": "fail",
"evidence": {
"links": []
},
"issue": "No useful agent discovery Link headers were found.",
"howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
},
{
"id": "target-validation",
"title": "Fetch same-origin Link header targets",
"status": "fail",
"evidence": {
"checked": [],
"failures": [
{
"reason": "No same-origin Link header targets were available to fetch."
}
]
},
"issue": "Link headers did not expose any same-origin targets to validate.",
"howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
}
]
}AI DiscoverabilityDiscoverabilityEstablished
Organization / WebSite schema
Organization / WebSite schema is missing or incomplete.
20 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": []
}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": "airflow.apache.org",
"probes": [
{
"name": "_index._agents.airflow.apache.org",
"found": false,
"recordCount": 1,
"records": [],
"hasAlpn": false,
"hasEndpoint": false
},
{
"name": "_a2a._agents.airflow.apache.org",
"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": "airflow.apache.org",
"dnssecTypes": [],
"dnssecRecordCount": 0
},
{
"name": "apache.org",
"dnssecTypes": [],
"dnssecRecordCount": 0
}
]
},
"issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
"howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
}
]
}AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is partially implemented.
13 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.
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
50/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 19:37:19 GMT",
"schemaDates": [],
"metaDateCount": 1,
"timeDateCount": 3
}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="q"> 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": 1,
"formsWithTags": 0,
"totalInteractive": 51,
"interactiveWithTags": 0,
"totalCount": 52,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"q\"> 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": 1,
"issues": [
"<input name=\"q\"> is missing tool-param-description."
]
},
"issue": "WebMCP declarative annotations need fixes.",
"issueDetails": [
{
"title": "WebMCP declarative annotation issues",
"items": [
{
"type": "code",
"value": "<input name=\"q\"> 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": 1,
"formsWithTags": 0,
"totalInteractive": 51,
"interactiveWithTags": 0,
"totalCount": 52,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"q\"> 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": 1,
"formsWithTags": 0,
"totalInteractive": 51,
"interactiveWithTags": 0,
"totalCount": 52,
"taggedCount": 0,
"dataMcpToolCount": 0,
"dataMcpTools": [],
"coverage": 0,
"annotationIssues": [
"<input name=\"q\"> 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
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible structured data match
AIO: Visible structured data match scored 0/100 and needs a fix.
Needs attention
AIO: Visible structured data match
Issue
No JSON-LD structured data was detected.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Visible structured data match
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Visible structured data match scored 0/100 and needs a fix.
Evidence
{
"schemaCount": 0,
"mismatches": [],
"score": 0,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
5 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extraction-friendly structure
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
Needs attention
GEO: Extraction-friendly structure
Issue
Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, JSON-LD structured data.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Extraction-friendly structure
Score
60/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Extraction-friendly structure scored 60/100 and needs improvement.
Evidence
{
"hasSummary": false,
"tableCount": 0,
"tablesWithHead": 0,
"tablesMissingThead": [],
"orderedLists": 0,
"hasFaq": false,
"definitionPatterns": 3,
"schemaBlocks": 0,
"missingSignals": [
"optional top summary / TL;DR / key takeaways block",
"table with <thead> only if the page already has tabular/comparative data",
"ordered list only if the page explains a workflow/process",
"optional visible FAQ or FAQPage schema",
"JSON-LD structured data"
],
"score": 60,
"weight": 24
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 70/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 70/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: apache, airflow.
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
70/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 70/100 and needs improvement.
Evidence
{
"title": "Apache Airflow",
"h1": "Apache Airflow®",
"description": "Platform created by the community to programmatically author, schedule and monitor workflows.",
"topicOverlap": 0,
"topicTerms": [
"apache",
"airflow"
],
"descriptionTerms": [
"platform",
"created",
"community",
"programmatically",
"author",
"schedule",
"monitor",
"workflows"
],
"missingFromDescription": [
"apache",
"airflow"
],
"score": 70,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 60/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 60/100 and needs improvement.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Source and trust signals
Score
60/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Source and trust signals scored 60/100 and needs improvement.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": true,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"author",
"publisher"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [
"2026-04-15 00:00:00 +0000 UTC",
"2026-04-15 00:00:00 +0000 UTC",
"2026-04-14 00:00:00 +0000 UTC"
],
"aboutLinks": [],
"contactLinks": [
{
"href": "/blog/common-ai-provider/",
"text": "Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow",
"html": "<a href=\"/blog/common-ai-provider/\">Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow</a>"
}
],
"privacyLinks": [
{
"href": "https://privacy.apache.org/policies/privacy-policy-public.html",
"text": "Privacy",
"html": "<a href=\"https://privacy.apache.org/policies/privacy-policy-public.html\" class=\"footer-section__policies-section--policy-item\"> <span>Privacy</span> </a>"
}
],
"score": 60,
"weight": 20
}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
11 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": 16,
"passing": 5,
"failing": [
{
"heading": "Principles",
"headingHtml": "<h2 class=\"page-header home-section-header\">Principles</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Extensible",
"headingHtml": "<h3 class=\"text-with-icon-item--header\">Extensible</h3>",
"firstParagraph": "Easily define your own operators and extend libraries to fit the level of abstraction that suits your environment.",
"paragraphHtml": "<p class=\"text-with-icon-item--text\">Easily define your own operators and extend libraries to fit the level of abstraction that suits your environment.</p>",
"words": 18,
"direct": false,
"issue": "First paragraph is 18 words and does not look like a concise direct answer."
},
{
"heading": "Features",
"headingHtml": "<h2 class=\"page-header home-section-header\">Features</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Useful UI",
"headingHtml": "<h3 class=\"feature-item--header\">Useful UI</h3>",
"firstParagraph": "Monitor, schedule and manage your workflows via a robust and modern web application. No need to learn old, cron-like interfaces. You always have full insight into the status and logs of completed and ongoing tasks.",
"paragraphHtml": "<p class=\"feature-item--text\">Monitor, schedule and manage your workflows via a robust and modern web application. No need to learn old, cron-like interfaces. You always have full insight into the status and logs of completed and ongoing tasks.</p>",
"words": 35,
"direct": false,
"issue": "First paragraph is 35 words and does not look like a concise direct answer."
},
{
"heading": "Easy to Use",
"headingHtml": "<h3 class=\"feature-item--header\">Easy to Use</h3>",
"firstParagraph": "Anyone with Python knowledge can deploy a workflow. Apache Airflow® does not limit the scope of your pipelines; you can use it to build ML models, transfer data, manage your infrastructure, and more.",
"paragraphHtml": "<p class=\"feature-item--text\">Anyone with Python knowledge can deploy a workflow. Apache Airflow® does not limit the scope of your pipelines; you can use it to build ML models, transfer data, manage your infrastructure, and more.</p>",
"words": 33,
"direct": false,
"issue": "First paragraph is 33 words and does not look like a concise direct answer."
},
{
"heading": "Open Source",
"headingHtml": "<h3 class=\"feature-item--header\">Open Source</h3>",
"firstParagraph": "Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.",
"paragraphHtml": "<p class=\"feature-item--text\">Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.</p>",
"words": 43,
"direct": false,
"issue": "First paragraph is 43 words and does not look like a concise direct answer."
},
{
"heading": "Integrations",
"headingHtml": "<h2 class=\"page-header home-section-header\">Integrations</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "From the Blog",
"headingHtml": "<h2 class=\"page-header home-section-header\">From the Blog</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Agentic Workloads on Airflow: Observable, Retryable, and Auditable by Design",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/agentic-workloads-airflow-3/\">Agentic Workloads on Airflow: Observable, Retryable, and Auditable by Design</a> </h3>",
"firstParagraph": "A question like “How does AI tool usage vary across Airflow versions?” has a natural SQL shape: one cross-tabulation, one …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> A question like “How does AI tool usage vary across Airflow versions?” has a natural SQL shape: one cross-tabulation, one … </p>",
"words": 20,
"direct": false,
"issue": "First paragraph is 20 words and does not look like a concise direct answer."
},
{
"heading": "Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/ai-survey-analysis-pipelines/\">Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3</a> </h3>",
"firstParagraph": "The 2025 Airflow Community Survey collected responses from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> The 2025 Airflow Community Survey collected responses from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and … </p>",
"words": 21,
"direct": false,
"issue": "First paragraph is 21 words and does not look like a concise direct answer."
},
{
"heading": "Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/common-ai-provider/\">Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow</a> </h3>",
"firstParagraph": "At Airflow Summit 2025, we previewed what native AI integration in Apache Airflow could look like. Today we’re shipping it. …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> At Airflow Summit 2025, we previewed what native AI integration in Apache Airflow could look like. Today we’re shipping it. … </p>",
"words": 21,
"direct": false,
"issue": "First paragraph is 21 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 28
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question-led structure
AEO: Question-led structure scored 50/100 and needs improvement.
Needs attention
AEO: Question-led structure
Issue
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": 4,
"questionH2s": [],
"hasFaq": false,
"score": 50,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 60/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer evidence and trust
AEO: Answer evidence and trust scored 60/100 and needs improvement.
Needs attention
AEO: Answer evidence and trust
Issue
Missing AIO trust signals: author, publisher.
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
60/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 60/100 and needs improvement.
Evidence
{
"signals": {
"author": false,
"publisher": false,
"freshnessDate": true,
"aboutOrContact": true,
"policyLinks": true
},
"missing": [
"author",
"publisher"
],
"authorMeta": "",
"schemaAuthors": [],
"schemaPublishers": [],
"schemaDates": [],
"visibleDates": [
"2026-04-15 00:00:00 +0000 UTC",
"2026-04-15 00:00:00 +0000 UTC",
"2026-04-14 00:00:00 +0000 UTC"
],
"aboutLinks": [],
"contactLinks": [
{
"href": "/blog/common-ai-provider/",
"text": "Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow",
"html": "<a href=\"/blog/common-ai-provider/\">Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow</a>"
}
],
"privacyLinks": [
{
"href": "https://privacy.apache.org/policies/privacy-policy-public.html",
"text": "Privacy",
"html": "<a href=\"https://privacy.apache.org/policies/privacy-policy-public.html\" class=\"footer-section__policies-section--policy-item\"> <span>Privacy</span> </a>"
}
],
"score": 60,
"weight": 22
}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
2 explanatory paragraph(s) could be stronger for citation or AI extraction.
Details
Why it matters
Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.
Check name
GEO: Explanatory content depth
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute.
Result
GEO: Explanatory content depth scored 75/100 and needs improvement.
Evidence
{
"candidatePassages": 2,
"citablePassages": 0,
"failingCandidateParagraphs": [
{
"index": 8,
"heading": "H3: Robust Integrations",
"text": "Apache Airflow® provides many plug-and-play operators that are ready to execute your tasks on Google Cloud Platform, Amazon Web Services, Microsoft Azure and many other third-party services. This makes Airflow easy to apply to current infrastructure and extend to next-gen technologies.",
"words": 41,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (41 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"feature-item--text\">Apache Airflow® provides many plug-and-play operators that are ready to execute your tasks on Google Cloud Platform, Amazon Web Services, Microsoft Azure and many other third-party services. This makes Airflow easy to apply to current infrastructure and extend to next-gen technologies.</p>"
},
{
"index": 10,
"heading": "H3: Open Source",
"text": "Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.",
"words": 43,
"hasEvidence": false,
"reasons": [
"Too short for a citation-ready passage (43 words; target 80-220).",
"Missing a named source, statistic, date, percentage, report, or other evidence signal."
],
"html": "<p class=\"feature-item--text\">Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.</p>"
}
],
"citableParagraphs": [],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google eligibility and indexability
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
Needs attention
AIO: Google eligibility and indexability
Issue
Canonical tag is missing.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Google eligibility and indexability
Score
80/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Google eligibility and indexability scored 80/100 and needs improvement.
Evidence
{
"status": 200,
"googlebotBlocked": false,
"metaRobotsTags": [
"INDEX, FOLLOW"
],
"xRobotsTag": "",
"canonical": "",
"finalUrl": "https://airflow.apache.org/",
"canonicalScore": 0,
"score": 80,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 75/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Entity or definition gaps: apache, airflow.
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
75/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 75/100 and needs improvement.
Evidence
{
"title": "Apache Airflow",
"h1": "Apache Airflow®",
"description": "Platform created by the community to programmatically author, schedule and monitor workflows.",
"topicOverlap": 0,
"definitionCount": 3,
"topicTerms": [
"apache",
"airflow"
],
"descriptionTerms": [
"platform",
"created",
"community",
"programmatically",
"author",
"schedule",
"monitor",
"workflows"
],
"missingFromDescription": [
"apache",
"airflow"
],
"score": 75,
"weight": 18
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 65/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Answer block readiness
AIO: Answer block readiness scored 65/100 and needs improvement.
Needs attention
AIO: Answer block readiness
Issue
11 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Answer block readiness
Score
65/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Answer block readiness scored 65/100 and needs improvement.
Evidence
{
"sectionCount": 16,
"passing": 5,
"failing": [
{
"heading": "Principles",
"headingHtml": "<h2 class=\"page-header home-section-header\">Principles</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Extensible",
"headingHtml": "<h3 class=\"text-with-icon-item--header\">Extensible</h3>",
"firstParagraph": "Easily define your own operators and extend libraries to fit the level of abstraction that suits your environment.",
"paragraphHtml": "<p class=\"text-with-icon-item--text\">Easily define your own operators and extend libraries to fit the level of abstraction that suits your environment.</p>",
"words": 18,
"direct": false,
"issue": "First paragraph is 18 words and does not look like a concise direct answer."
},
{
"heading": "Features",
"headingHtml": "<h2 class=\"page-header home-section-header\">Features</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Useful UI",
"headingHtml": "<h3 class=\"feature-item--header\">Useful UI</h3>",
"firstParagraph": "Monitor, schedule and manage your workflows via a robust and modern web application. No need to learn old, cron-like interfaces. You always have full insight into the status and logs of completed and ongoing tasks.",
"paragraphHtml": "<p class=\"feature-item--text\">Monitor, schedule and manage your workflows via a robust and modern web application. No need to learn old, cron-like interfaces. You always have full insight into the status and logs of completed and ongoing tasks.</p>",
"words": 35,
"direct": false,
"issue": "First paragraph is 35 words and does not look like a concise direct answer."
},
{
"heading": "Easy to Use",
"headingHtml": "<h3 class=\"feature-item--header\">Easy to Use</h3>",
"firstParagraph": "Anyone with Python knowledge can deploy a workflow. Apache Airflow® does not limit the scope of your pipelines; you can use it to build ML models, transfer data, manage your infrastructure, and more.",
"paragraphHtml": "<p class=\"feature-item--text\">Anyone with Python knowledge can deploy a workflow. Apache Airflow® does not limit the scope of your pipelines; you can use it to build ML models, transfer data, manage your infrastructure, and more.</p>",
"words": 33,
"direct": false,
"issue": "First paragraph is 33 words and does not look like a concise direct answer."
},
{
"heading": "Open Source",
"headingHtml": "<h3 class=\"feature-item--header\">Open Source</h3>",
"firstParagraph": "Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.",
"paragraphHtml": "<p class=\"feature-item--text\">Wherever you want to share your improvement you can do this by opening a PR. It’s simple as that, no barriers, no prolonged procedures. Airflow has many active users who willingly share their experiences. Have any questions? Check out our buzzing slack.</p>",
"words": 43,
"direct": false,
"issue": "First paragraph is 43 words and does not look like a concise direct answer."
},
{
"heading": "Integrations",
"headingHtml": "<h2 class=\"page-header home-section-header\">Integrations</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "From the Blog",
"headingHtml": "<h2 class=\"page-header home-section-header\">From the Blog</h2>",
"firstParagraph": "",
"paragraphHtml": "",
"words": 0,
"direct": false,
"issue": "No paragraph follows this heading."
},
{
"heading": "Agentic Workloads on Airflow: Observable, Retryable, and Auditable by Design",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/agentic-workloads-airflow-3/\">Agentic Workloads on Airflow: Observable, Retryable, and Auditable by Design</a> </h3>",
"firstParagraph": "A question like “How does AI tool usage vary across Airflow versions?” has a natural SQL shape: one cross-tabulation, one …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> A question like “How does AI tool usage vary across Airflow versions?” has a natural SQL shape: one cross-tabulation, one … </p>",
"words": 20,
"direct": false,
"issue": "First paragraph is 20 words and does not look like a concise direct answer."
},
{
"heading": "Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/ai-survey-analysis-pipelines/\">Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3</a> </h3>",
"firstParagraph": "The 2025 Airflow Community Survey collected responses from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> The 2025 Airflow Community Survey collected responses from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and … </p>",
"words": 21,
"direct": false,
"issue": "First paragraph is 21 words and does not look like a concise direct answer."
},
{
"heading": "Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow",
"headingHtml": "<h3 class=\"blog-snippet-title\"> <a href=\"/blog/common-ai-provider/\">Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow</a> </h3>",
"firstParagraph": "At Airflow Summit 2025, we previewed what native AI integration in Apache Airflow could look like. Today we’re shipping it. …",
"paragraphHtml": "<p class=\"blog-snippet-excerpt\"> At Airflow Summit 2025, we previewed what native AI integration in Apache Airflow could look like. Today we’re shipping it. … </p>",
"words": 21,
"direct": false,
"issue": "First paragraph is 21 words and does not look like a concise direct answer."
}
],
"score": 65,
"weight": 8
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer intent coverage
AEO: Answer intent coverage scored 70/100 and needs improvement.
Needs attention
AEO: Answer intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.
Check name
AEO: Answer intent coverage
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to answer from directly.
Result
AEO: Answer intent coverage scored 70/100 and needs improvement.
Evidence
{
"headings": [
{
"text": "Principles",
"html": "<h2 class=\"page-header home-section-header\">Principles</h2>"
},
{
"text": "Features",
"html": "<h2 class=\"page-header home-section-header\">Features</h2>"
},
{
"text": "Integrations",
"html": "<h2 class=\"page-header home-section-header\">Integrations</h2>"
},
{
"text": "From the Blog",
"html": "<h2 class=\"page-header home-section-header\">From the Blog</h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Apache Airflow?",
"pattern": {}
},
{
"id": "how",
"label": "How does Apache Airflow work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Apache Airflow?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Apache Airflow free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Apache Airflow compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Apache Airflow?",
"pattern": {}
},
{
"id": "how",
"label": "How does Apache Airflow work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Apache Airflow?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Apache Airflow free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Apache Airflow compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 8
}Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Informational
Agent Ease of UseAPIEmerging recommendation
AI context endpoint
AI context endpoint is informational for this page.
Needs attention
AI context endpoint
Issue
AI context endpoint is informational for this page.
Why it matters
A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.
Check name
AI context endpoint
Score
100/100
Status
informational
Category
API
Maturity
Emerging recommendation
Goal
Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.
Result
AI context endpoint is informational for this page.
Validation steps
Fetch to find resource
AI context endpoint was not found at the expected path.
Evidence
{
"steps": [
{
"id": "fetch",
"title": "Fetch to find resource",
"status": "informational",
"evidence": {
"checked": [
{
"path": "/api/ai/context",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/api/context",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
},
{
"path": "/context",
"statusCode": 404,
"contentType": "text/html; charset=iso-8859-1",
"length": 196
}
]
},
"issue": "AI context endpoint was not found at the expected path.",
"howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
}
]
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Query intent coverage
AIO: Query intent coverage is informational for this page.
Needs attention
AIO: Query intent coverage
Issue
Missing likely AI Overview intent sections: what, how, benefits, cost, compare.
Details
Why it matters
AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.
Check name
AIO: Query intent coverage
Score
70/100
Status
informational
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible and useful for Google AI Overviews and AI Mode extraction.
Result
AIO: Query intent coverage is informational for this page.
Evidence
{
"headings": [
{
"text": "Principles",
"html": "<h2 class=\"page-header home-section-header\">Principles</h2>"
},
{
"text": "Features",
"html": "<h2 class=\"page-header home-section-header\">Features</h2>"
},
{
"text": "Integrations",
"html": "<h2 class=\"page-header home-section-header\">Integrations</h2>"
},
{
"text": "From the Blog",
"html": "<h2 class=\"page-header home-section-header\">From the Blog</h2>"
}
],
"expected": [
{
"id": "what",
"label": "What is Apache Airflow?",
"pattern": {}
},
{
"id": "how",
"label": "How does Apache Airflow work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Apache Airflow?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Apache Airflow free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Apache Airflow compare with alternatives?",
"pattern": {}
}
],
"missing": [
{
"id": "what",
"label": "What is Apache Airflow?",
"pattern": {}
},
{
"id": "how",
"label": "How does Apache Airflow work?",
"pattern": {}
},
{
"id": "benefits",
"label": "Why use Apache Airflow?",
"pattern": {}
},
{
"id": "cost",
"label": "Is Apache Airflow free or paid?",
"pattern": {}
},
{
"id": "compare",
"label": "How does Apache Airflow compare with alternatives?",
"pattern": {}
}
],
"score": 70,
"weight": 4
}GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Informational
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Q&A and FAQ opportunities
GEO: Q&A and FAQ opportunities is informational for this page.
Needs attention
GEO: Q&A and FAQ opportunities
Issue
4 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": 4,
"questionH2s": 0,
"hasFaq": false,
"nonQuestionH2s": [
{
"index": 1,
"text": "Principles",
"isQuestion": false,
"html": "<h2 class=\"page-header home-section-header\">Principles</h2>"
},
{
"index": 2,
"text": "Features",
"isQuestion": false,
"html": "<h2 class=\"page-header home-section-header\">Features</h2>"
},
{
"index": 3,
"text": "Integrations",
"isQuestion": false,
"html": "<h2 class=\"page-header home-section-header\">Integrations</h2>"
},
{
"index": 4,
"text": "From the Blog",
"isQuestion": false,
"html": "<h2 class=\"page-header home-section-header\">From the Blog</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."
}
]
}Performance and AccessibilityPerformanceBrowser audit
Font display
33 Fail
Performance and AccessibilityPerformanceBrowser audit
Font display
Check name
Font display
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 50 ms
Fix guidance
Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 50 ms",
"description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
33 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 73 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 73 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": 80
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused JavaScript
33 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 298 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 298 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": 40
}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 |
|---|---|---|---|
| 58/100 | Level 3, Bot-Aware | Current report |