Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 58 out of 100
- Agent Ease of Use 45 out of 100
- Security & Trust 75 out of 100
- GEO, AIO and AEO 61 out of 100
- SEO 92 out of 100
- Performance 20 out of 100
- Accessibility 0 out of 100
What AI sees of your website

Home - Collabora Online and Collabora Office
CollaborativeOpen-SourceDocumentEditing Controlled by You Collabora Online is a powerful online document editing suite. Integrate into your own infrastructure or access via one of our trusted hosting partners. Try the FREE Demo https://www...
Next step
Turn this report into a fix workflow
23 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 | 58 | Needs work | 33 | 17 | 8 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 65 | Needs work | 23 | 12 | 4 | View details |
| Bot Access Control | 44 | Priority fix | 2 | 3 | 4 | View details |
| Agent Ease of Use | 45 | Priority fix | 30 | 29 | 18 | View details |
| API | 44 | Priority fix | 7 | 7 | 1 | View details |
| Auth | 41 | Priority fix | 6 | 6 | 3 | View details |
| MCP | 42 | Priority fix | 4 | 5 | 2 | View details |
| Skill Discovery | 47 | Priority fix | 6 | 6 | 8 | View details |
| Agent Commerce | 45 | Priority fix | 7 | 5 | 4 | View details |
| GEO, AIO and AEO | 61 | Needs work | 7 | 2 | 9 | View details |
| GEO Readiness | 52 | Needs work | 2 | 1 | 3 | View details |
| AIO Readiness | 80 | Mostly ready | 3 | 0 | 3 | |
| AEO Readiness | 51 | Needs work | 2 | 1 | 3 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| SEO | 92 | Strong | 9 | 1 | 0 | View details |
| Security & Trust | 75 | Mostly ready | 17 | 3 | 5 | View details |
| Security & Trust | 75 | Mostly ready | 17 | 3 | 5 | View details |
| Performance | 20 | Priority fix | 10 | 10 | 4 | View details |
| Performance | 20 | Priority fix | 10 | 10 | 4 | View details |
| Accessibility | 0 | Priority fix | 0 | 5 | 7 | View details |
| Accessibility | 0 | Priority fix | 0 | 5 | 7 | View details |
Prioritized recommendations
Issues ranked by score impact
69 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 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 log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
32 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
Needs attention
API Catalog
Issue
Content-Type "text/html" is not valid for an RFC 9727 API catalog.
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
37/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog media type".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
Validate API catalog media type
Content-Type "text/html" is not valid for an RFC 9727 API catalog.
Validate Linkset shape
Unexpected token '<', "<!DOCTYPE "... is not valid JSON
Unexpected token '<', "<!DOCTYPE "... is not valid JSON
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
Validate API catalog targets
API catalog did not expose any href targets to validate.
Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="text/html"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [fail]! Content-Type "text/html" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', "<!DOCTYPE "... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILUnexpected token '<', "<!DOCTYPE "... is not valid JSONClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
30 Fail
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
Needs attention
Auth.md Agent Registration
Issue
auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.
Why it matters
Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.
Check name
Auth.md Agent Registration
Score
10/100
Status
fail
Category
Auth
Maturity
Emerging recommendation
Goal
Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.
Result
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
Validation steps
Fetch and validate /auth.md
auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.
Validate protected resource metadata
Response is not valid JSON.
Validate Auth.md authorization metadata
Response is not valid JSON.
Evidence log3 steps · 20 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/html" bytes=467808FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=443650 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. Content-Type \"text/html\" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.Validate protected resource metadata [fail]! Response is not valid JSON.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=200 contentType="text/html" bytes=467808FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="Response is not valid JSON."FAILResponse is not valid JSON.Validate Auth.md authorization metadata [fail]! Response is not valid JSON.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=200 contentType="text/html" bytes=467808FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="Response is not valid JSON."FAILResponse is not valid JSON.
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
30 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
Needs attention
MCP Server Card
Issue
MCP Server Card response is not valid JSON.
Why it matters
MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.
Check name
MCP Server Card
Score
40/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Publish an MCP Server Card that helps agents discover remote MCP server transports before opening a session.
Result
MCP Server Card failed at "Validate server-card shape".
Validation steps
Validate server-card shape
MCP Server Card response is not valid JSON.
Validate MCP remotes
No usable MCP remote transport was declared.
Validate HTTP delivery
Content-Type "text/html" is not JSON.
Probe same-origin MCP endpoint
No MCP remote endpoint could be probed.
Evidence log4 steps · 23 lines
Validate server-card shape [fail]! MCP Server Card response is not valid JSON.INFOValidate server-card shape profile="unknown-json"FAILCheck response body parsed as JSON actual=false expected=trueFAILCheck Content-Type is JSON-compatible actual=false expected=trueFAILCheck recognized MCP server-card profile actual="unknown-json" expected="sep-2127-draft"PASSCheck required card fields are present actual=0 expected=0 missing=[]PASSCheck MCP server-card uses the current remotes[] profile without legacy compatibility warnings actual="no compatibility warnings" expected="current sep-2127-draft card shape with no legacy compatibility warnings" warnings=[]FAILMCP server-card shape validation failed reason="MCP Server Card response is not valid JSON."Validate MCP remotes [fail]! No usable MCP remote transport was declared.INFOValidate MCP remotes remoteCount=0FAILCheck at least one MCP remote is declared actual=0 expected="> 0"PASSCheck invalid remote count actual=0 expected=0 invalidRemotes=[]PASSCheck same-origin remote coverage actual=0 expected=0FAILMCP remote validation failed reason="No usable MCP remote transport was declared."Validate HTTP delivery [fail]! Content-Type "text/html" is not JSON.INFOValidate HTTP delivery finalUrl="https://www.collaboraonline.com/.well-known/mcp-server-card"PASSCheck server card returned HTTP 2xx actual=200 expected="200-299"FAILCheck card is served as JSON actual="text/html" expected="application/json or +json"PASSCheck card is served over HTTPS actual="https:" expected="https:"WARNCheck browser-readable CORS header actual="missing" expected="Access-Control-Allow-Origin present"WARNCheck cache header is present actual="missing" expected="Cache-Control present"FAILMCP server-card HTTP delivery failed issues=["Content-Type \"text/html\" is not JSON.","CORS header Access-Control-Allow-Origin is absent.","Cache-Control is absent."] reason="Content-Type \"text/html\" is not JSON."Probe same-origin MCP endpoint [warning]! No MCP remote endpoint could be probed.INFOProbe same-origin MCP endpoint probeCount=0INFOSelecting same-origin unauthenticated MCP remotes for a bounded initialize probeWARNCheck successful initialize probe count actual=0 expected="> 0 when a safe same-origin unauthenticated remote exists" activeProbeCount=0 authBlocked=0WARNMCP endpoint probe could not fully confirm operability reason="No MCP remote endpoint could be probed."
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP failed at "Probe WebMCP operability".
28 Fail
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP failed at "Probe WebMCP operability".
Needs attention
WebMCP
Issue
Discovered WebMCP static metadata was fetchable but invalid.
Details
Why it matters
WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.
Check name
WebMCP
Score
44/100
Status
fail
Category
MCP
Maturity
Emerging recommendation
Goal
Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.
Result
WebMCP failed at "Probe WebMCP operability".
Validation steps
Detect WebMCP runtime API
WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.
Probe WebMCP operability
Discovered WebMCP static metadata was fetchable but invalid.
WebMCP operability findings
- Discovered WebMCP static metadata was fetchable but invalid.
Validate declarative WebMCP form tools
No W3C-style declarative WebMCP form attributes were found.
Validate MCP-aware HTML annotations
No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.
Validate static WebMCP JSON compatibility
A discovered WebMCP static manifest or WMCP interaction graph was invalid.
Body is not valid JSON.
Body is not valid JSON.
Evidence log5 steps · 23 lines
Detect WebMCP runtime API [warning]! WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.INFODetect WebMCP runtime API status="warning"INFOProbe rendered browser for WebMCP runtime objects WARNCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"WARNWebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.Probe WebMCP operability [fail]! Discovered WebMCP static metadata was fetchable but invalid.INFOProbe WebMCP operability status="fail"INFORun safe WebMCP operability checks safeProbeOnly=trueFAILCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"FAILWebMCP operability failure issue="Discovered WebMCP static metadata was fetchable but invalid."FAILDiscovered WebMCP static metadata was fetchable but invalid.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [fail]! A discovered WebMCP static manifest or WMCP interaction graph was invalid.INFOValidate static WebMCP JSON compatibility status="fail"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={"unknown-webmcp-json":2}PASSWebMCP manifest candidate found source="path" path="/.well-known/webmcp.json" url="https://www.collaboraonline.com/.well-known/webmcp.json" statusCode=200 contentType="text/html"PASSWebMCP manifest candidate found source="path" path="/webmcp.json" url="https://www.collaboraonline.com/webmcp.json" statusCode=200 contentType="text/html"FAILValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":2,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"FAILA discovered WebMCP static manifest or WMCP interaction graph was invalid.
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Parse OpenAPI document".
25 Fail
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery failed at "Parse OpenAPI document".
Needs attention
OpenAPI discovery
Issue
OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.
Why it matters
OpenAPI documents let agents understand operations, schemas, authentication, servers, and request/response formats before calling an API.
Check name
OpenAPI discovery
Score
50/100
Status
fail
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.
Result
OpenAPI discovery failed at "Parse OpenAPI document".
Validation steps
Parse OpenAPI document
OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.
Validate OpenAPI shape
Response is not valid JSON and does not match baseline OpenAPI YAML shape.
Check machine-usable details
Add servers, parameters, request bodies, response schemas, operation IDs, tags, examples, and security or explicit no-auth declarations where they apply.
Evidence log3 steps · 14 lines
Parse OpenAPI document [fail]! OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.INFOParse OpenAPI document status="fail"INFOParse selected document as JSON first, then YAML-like OpenAPI parsed=false format="unknown" versionFamily="missing"FAILCheck parse result actual="not parseable" expected="parseable OpenAPI 3.x or Swagger 2.0 document" compatibleContentType=falseFAILOpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.Validate OpenAPI shape [fail]! Response is not valid JSON and does not match baseline OpenAPI YAML shape.INFOValidate OpenAPI shape status="fail"INFOValidate required OpenAPI shape versionFamily="missing" pathCount=0 webhookCount=0 operationCount=0PASSCheck operations define responses actual=0 expected="every operation should define responses"FAILCheck info metadata actual={"hasInfoTitle":false,"hasInfoVersion":false} expected="info.title and info.version present"FAILOpenAPI shape issue issue="Response is not valid JSON and does not match baseline OpenAPI YAML shape."FAILResponse is not valid JSON and does not match baseline OpenAPI YAML shape.Check machine-usable details [fail]INFOCheck machine-usable details status="fail"INFOInspect machine-usable operation details hasServers=false hasSecuritySchemes=false hasExplicitNoAuth=false requestBodyOperationCount=0 parameterOperationCount=0 responseSchemaOperationCount=0 operationIdCount=0 taggedOperationCount=0 exampleOperationCount=0PASSCheck OpenAPI operations include enough detail for agents to call them safely actual="no machine-usability warnings" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"FAILOpenAPI discovery validation failed.
Agent Ease of UseAgent CommerceInformational
Universal Commerce Protocol
Universal Commerce Protocol failed at "Fetch UCP profile".
21 Fail
Agent Ease of UseAgent CommerceInformational
Universal Commerce Protocol
Universal Commerce Protocol failed at "Fetch UCP profile".
Needs attention
Universal Commerce Protocol
Issue
UCP profile content type "text/html" is not JSON-compatible.
Why it matters
UCP discovery lets agents identify commerce capabilities, service transports, payment handlers, and signing keys without scraping human checkout flows.
Check name
Universal Commerce Protocol
Score
36/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose a valid Universal Commerce Protocol business profile when this origin supports agentic commerce workflows.
Result
Universal Commerce Protocol failed at "Fetch UCP profile".
Validation steps
Fetch UCP profile
UCP profile content type "text/html" is not JSON-compatible.
Validate UCP profile shape
UCP profile could not be parsed.
Evidence log2 steps · 11 lines
Fetch UCP profile [fail]! UCP profile content type "text/html" is not JSON-compatible.INFOFetch UCP profile status="fail"INFOFetch /.well-known/ucp statusCode=200 contentType="text/html" error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILCheck UCP profile availability actual=true expected=trueFAILCheck JSON-compatible profile response actual=false expected=true jsonCompatible=false parsed=falseFAILUCP profile content type "text/html" is not JSON-compatible.Validate UCP profile shape [fail]! UCP profile could not be parsed.INFOValidate UCP profile shape status="fail"INFOValidate top-level ucp object, version, services, payment handlers, and supported versionsFAILCheck top-level ucp object actual=false expected=trueFAILCheck production-friendly version actual=false expected=true stableVersion=false draftVersion=falseFAILCheck required UCP sections actual={"services":false,"paymentHandlers":false,"supportedVersionCount":0} expected="services, payment_handlers, and supported versions"FAILUCP profile could not be parsed.
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
19 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery content type "text/html" is not JSON-compatible.
Why it matters
ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.
Check name
ACP - Agentic Commerce Protocol
Score
42/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.
Result
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
Validation steps
Fetch ACP discovery
ACP discovery content type "text/html" is not JSON-compatible.
Validate ACP discovery shape
ACP discovery could not be parsed.
Review ACP cache and retry metadata
ACP discovery is missing Cache-Control guidance.
Evidence log3 steps · 14 lines
Fetch ACP discovery [fail]! ACP discovery content type "text/html" is not JSON-compatible.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=200 contentType="text/html" parsed=false error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery content type "text/html" is not JSON-compatible.Validate ACP discovery shape [fail]! ACP discovery could not be parsed.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":false,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery could not be parsed.Review ACP cache and retry metadata [warning]! ACP discovery is missing Cache-Control guidance.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=200 cacheControl=null retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"WARNCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"WARNACP discovery is missing Cache-Control guidance.
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
18 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Best candidate returned Content-Type "text/html" instead of text/markdown.
Why it matters
Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.
Check name
Markdown negotiation
Score
10/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose a useful Markdown representation through negotiation or an explicit alternate URL.
Result
Markdown negotiation is missing or incomplete.
Validation steps
Markdown representation
No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.
Same-URL negotiation
Same-URL Accept: text/markdown did not return a valid Markdown representation.
Markdown format validation
Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.
Advertised Markdown alternate
No Link or HTML rel=alternate text/markdown URL was advertised.
Conventional .md mirror
Conventional .md mirror candidates did not return valid Markdown.
Evidence log5 steps · 15 lines
Markdown representation [fail]! No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.INFOMarkdown representationFAILCheck usable Markdown representation was selected actual={"source":"negotiated","url":"https://www.collaboraonline.com/","statusCode":200,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":54134,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":4,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":3968,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en-US\">\n\n<head>\n\t<meta charset=\"UTF-8\">\n\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t\t<meta name=\"robots\" content=\"index, follow, max-image-preview:large, max-snippet:-1, max-video-pre","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://www.collaboraonline.com/","statusCode":200,"contentType":"text/html","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":54134,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":4,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":3968,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html>\n<html lang=\"en-US\">\n\n<head>\n\t<meta charset=\"UTF-8\">\n\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t\t<meta name=\"robots\" content=\"index, follow, max-image-preview:large, max-snippet:-1, max-video-pre","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} candidatesChecked=2FAILMarkdown representation failed issue="No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks."Same-URL negotiation [fail]! Same-URL Accept: text/markdown did not return a valid Markdown representation.INFOSame-URL negotiationFAILCheck negotiated Markdown response actual={"statusCode":200,"mediaType":"text/html","vary":""} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://www.collaboraonline.com/" statusCode=200 mediaType="text/html"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":54134,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=54134 headingCount=0FAILMarkdown format validation failed issue="Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."Advertised Markdown alternate [warning]! No Link or HTML rel=alternate text/markdown URL was advertised.INFOAdvertised Markdown alternateWARNCheck advertised Markdown alternate candidates actual=0 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=[] candidateCount=0WARNAdvertised Markdown alternate has a warning issue="No Link or HTML rel=alternate text/markdown URL was advertised."Conventional .md mirror [fail]! Conventional .md mirror candidates did not return valid Markdown.INFOConventional .md mirrorFAILCheck conventional Markdown mirror candidates actual=1 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://www.collaboraonline.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
16 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json response is not valid JSON.
Why it matters
Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.
Check name
agents.json
Score
35/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.
Result
agents.json failed at "Validate Wildcard schema shape".
Validation steps
Validate Wildcard schema shape
agents.json response is not valid JSON.
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
Validate flows and links
No executable flows were found.
Review examples and LLM usability
Examples or descriptions are too thin for reliable agent argument generation.
Evidence log4 steps · 17 lines
Validate Wildcard schema shape [fail]! agents.json response is not valid JSON.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=false expected=trueFAILagents.json response is not valid JSON.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNExamples or descriptions are too thin for reliable agent argument generation.
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate Markdown discovery shape".
16 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate Markdown discovery shape".
Needs attention
llms.txt
Issue
llms.txt did not provide the minimum expected Markdown discovery shape.
Details
Why it matters
llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.
Check name
llms.txt
Score
21/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish a concise llms.txt index that helps agents discover useful public site context.
Result
llms.txt failed at "Validate Markdown discovery shape".
Validation steps
Validate Markdown discovery shape
llms.txt did not provide the minimum expected Markdown discovery shape.
Findings
- Content-Type "text/html" is not text/markdown, another Markdown type, or text/plain.
- Response looks like an HTML page rather than a Markdown/text llms.txt file.
- Missing H1 title, such as '# Example Docs'.
Score llms.txt structure and usefulness
llms.txt includes unsafe or private links that should not be advertised to agents.
Findings
- Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
- Missing H2 sections for grouping important links.
- No Markdown-formatted links were found.
- Several links have vague labels or raw URL labels.
{ "truncated": true, "omittedCount": 2, "originalCount": 6 }
Probe sampled linked resources
Most sampled llms.txt links were broken or none returned agent-readable content.
Findings
- 22/24 probed links were broken or unreachable.
- 22/24 probed links did not look agent-readable.
Inspect optional llms-full.txt
Passed.
Evidence log4 steps · 34 lines
Validate Markdown discovery shape [fail]! llms.txt did not provide the minimum expected Markdown discovery shape.INFOValidate Markdown discovery shapeINFOChecking response compatibility, title, content length, and usable linksFAILCheck content type is Markdown-compatible text actual="text/html" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"FAILCheck response is not HTML actual=true expected=falseFAILCheck H1 title is present actual=false expected=truePASSCheck minimum text length actual=443574 expected=">= 160"PASSCheck at least one usable public link actual=172 expected="> 0" linkCount=173FAILMarkdown discovery shape validation failedScore llms.txt structure and usefulness [fail]! llms.txt includes unsafe or private links that should not be advertised to agents.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsWARNCheck blockquote summary is present actual=false expected=trueWARNCheck H2 section count actual=0 expected="> 0"WARNCheck Markdown-formatted links actual=0 expected="> 0"FAILCheck unsafe/private link count actual=1 expected=0FAILllms.txt structure-quality validation failed reason="llms.txt includes unsafe or private links that should not be advertised to agents."Probe sampled linked resources [fail]! Most sampled llms.txt links were broken or none returned agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=24PASSCheck probed links were attempted actual=24 expected="> 0"FAILCheck broken probed link count actual=22 expected=0WARNBroken sampled llms.txt link url="https://www.collaboraonline.com/wp-content/uploads/2025/04/Writer-Overview-005-720p.mp4" label="https://www.collaboraonline.com/wp-content/uploads/2025/04/Writer-Overview-005-720p.mp4" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/*#" label="/*#" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/style" label="/style" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/head" label="/head" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/a" label="/a" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/wp-content/uploads/2025/02/collabora-online-white-300x113.png" label="https://www.collaboraonline.com/wp-content/uploads/2025/02/collabora-online-white-300x113.png" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/div" label="/div" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/span" label="/span" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/button" label="/button" error="TypeError: fetch failed" agentReadable=falseWARNBroken sampled llms.txt link url="https://www.collaboraonline.com/i" label="/i" error="TypeError: fetch failed" agentReadable=falsePASSCheck agent-readable probed links actual=2 expected="> 0"FAILLinked resource probe validation failed reason="Most sampled llms.txt links were broken or none returned agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://www.collaboraonline.com/llms-full.txt"SKIP/llms-full.txt is not present error="TypeError: fetch failed"
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate metadata shape".
15 Fail
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource failed at "Validate metadata shape".
Needs attention
OAuth Protected Resource
Issue
Response is not valid JSON.
Why it matters
Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.
Check name
OAuth Protected Resource
Score
55/100
Status
fail
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.
Result
OAuth Protected Resource failed at "Validate metadata shape".
Validation steps
Validate metadata shape
Response is not valid JSON.
Validate resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
Validate authorization servers
authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.
Validate protected resource challenge
No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.
Evidence log4 steps · 27 lines
Validate metadata shape [fail]! Response is not valid JSON.INFOValidate metadata shapeINFOParsing and validating RFC 9728 protected-resource metadata valid=false compatibleContentType=false issue="Response is not valid JSON." warningsCount=0 resourceIssuesCount=0 authorizationServersCount=0 authorizationServerIssuesCount=0 scopesSupportedCount=0 bearerMethodsSupportedCount=0 optionalFieldIssuesCount=0FAILCheck metadata resource field is present actual="missing" expected="absolute protected resource identifier"PASSCheck required metadata field failures actual=0 expected=0 missing=[]PASSCheck protected-resource metadata is browser-readable and complete for OAuth clients actual="no client-usage warnings" expected="no CORS, authorization-server, or compatibility warnings" warnings=[]FAILValidate metadata shape failed issue="Response is not valid JSON."Validate resource identity [fail]! Protected resource metadata `resource` did not match the resource identifier used to retrieve it.INFOValidate resource identityINFOComparing metadata resource identifier with the candidate resource expectedResource="https://www.collaboraonline.com" candidatePresent=trueFAILCheck protected resource identity matches expected="https://www.collaboraonline.com"FAILValidate resource identity failed issue="Protected resource metadata `resource` did not match the resource identifier used to retrieve it."Validate authorization servers [warning]! authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.INFOValidate authorization serversINFOValidating advertised authorization server issuer URLs authorizationServerCount=0PASSCheck authorization server count actual=0 expected="> 0 when required"PASSCheck authorization server URL issue count actual=0 expected=0 issues=[]WARNValidate authorization servers completed with warnings issue="authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery."Validate protected resource challenge [warning]! No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.INFOValidate protected resource challengeINFOProbing protected routes for WWW-Authenticate resource_metadata linkage checkedCount=8INFOChecked protected route challenge url="https://www.collaboraonline.com/wp-content/plugins/elementor/assets/lib/swiper/v8/css/swiper.min.css?ver=1781741591" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/wp-json/wp/v2/pages/42160" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/wp-content/plugins/elementor/assets/lib/swiper/v8/css/swiper.min.css?ver=8.4.5" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper.min.js" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/api/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/api/admin/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/api/admin/summary" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://www.collaboraonline.com/mcp" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://www.collaboraonline.com/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://www.collaboraonline.com" resourceMatches=true scopePresent=falseWARNCheck challenge includes resource_metadata linkage actual=8 expected="> 0 matching protected route challenges"WARNValidate protected resource challenge completed with warnings issue="No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven."
Agent Ease of UseAgent CommerceEmerging recommendation
x402 Protocol
x402 Protocol failed at "Probe x402 runtime response".
15 Fail
Agent Ease of UseAgent CommerceEmerging recommendation
x402 Protocol
x402 Protocol failed at "Probe x402 runtime response".
Needs attention
x402 Protocol
Issue
x402 candidate routes were found, but none returned HTTP 402 before payment.
Why it matters
x402 lets agents discover paid HTTP resources through ordinary 402 responses, understand accepted schemes and networks, and retry with a signed payment payload without scraping checkout flows.
Check name
x402 Protocol
Score
56/100
Status
fail
Category
Agent Commerce
Maturity
Emerging recommendation
Goal
Expose x402 V2 payment requirements on payable HTTP resources so agents can recognize and satisfy payment requirements programmatically.
Result
x402 Protocol failed at "Probe x402 runtime response".
Validation steps
Probe x402 runtime response
x402 candidate routes were found, but none returned HTTP 402 before payment.
Validate x402 V2 headers
No x402 runtime response was available for header validation.
Validate x402 payment requirement payload
No x402 runtime response was available for payload validation.
Compare x402 metadata consistency
x402 metadata was found, but no probed candidate returned HTTP 402.
Evidence log4 steps · 20 lines
Probe x402 runtime response [fail]! x402 candidate routes were found, but none returned HTTP 402 before payment.INFOProbe x402 runtime response status="fail"INFOProbe candidate GET routes without sending payment credentials checkedCount=1INFOProbe x402 candidate route path="/" source="well-known" statusCode=200 contentType="text/html" finalUrl="https://www.collaboraonline.com/" headers={} textSample="<!DOCTYPE html> <html lang=\"en-US\"> <head> <meta charset=\"UTF-8\"> <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"> <meta name=\"robots\" content=\"index, follow,"FAILCheck pre-payment runtime response actual="none" expected=402 best={}FAILx402 candidate routes were found, but none returned HTTP 402 before payment.Validate x402 V2 headers [warning]! No x402 runtime response was available for header validation.INFOValidate x402 V2 headers status="warning"INFOInspect payment headers on the best HTTP 402 response observedHeaders={}WARNCheck PAYMENT-REQUIRED header actual=false expected=true hasLegacyOnly=falseWARNCheck legacy-only x402 header usage actual=false expected=falseWARNNo x402 runtime response was available for header validation.Validate x402 payment requirement payload [warning]! No x402 runtime response was available for payload validation.INFOValidate x402 payment requirement payload status="warning"INFODecode PAYMENT-REQUIRED as Base64 JSON and inspect accepted payment optionsWARNCheck PAYMENT-REQUIRED decoding actual={} expected={"decoded":true,"parsed":true}WARNCheck x402 payment option shape actual={} expected="x402Version 2 with accepted options containing payee and amount"INFOSummarize decoded payment requirement WARNNo x402 runtime response was available for payload validation.Compare x402 metadata consistency [warning]! x402 metadata was found, but no probed candidate returned HTTP 402.INFOCompare x402 metadata consistency status="warning"INFOCompare metadata-declared payable routes with observed runtime 402 behavior openApiSignals=[] wellKnown={"found":true,"statusCode":200,"contentType":"text/html","markers":[],"candidateCount":1} runtime402=falseWARNCheck runtime 402 evidence against metadata actual={"openApiSignals":[],"wellKnown":{"found":true,"statusCode":200,"contentType":"text/html","markers":[],"candidateCount":1},"runtime402":false} expected="metadata and runtime agree on payable resources"WARNx402 metadata was found, but no probed candidate returned HTTP 402.
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate metadata profile".
14 Fail
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate metadata profile".
Needs attention
OAuth / OIDC discovery
Issue
Response is not valid JSON.
Why it matters
OAuth and OIDC discovery let agents and API clients find authorization, token, and key endpoints programmatically instead of scraping login pages or guessing provider setup.
Check name
OAuth / OIDC discovery
Score
58/100
Status
fail
Category
Auth
Maturity
Established
Goal
Publish OAuth/OIDC discovery metadata only when the site operates or advertises a real OAuth/OIDC authorization server.
Result
OAuth / OIDC discovery failed at "Validate metadata profile".
Validation steps
Validate metadata profile
Response is not valid JSON.
Validate discovery CORS
Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin.
Evidence log2 steps · 10 lines
Validate metadata profile [fail]! Response is not valid JSON.INFOValidate metadata profileINFOParsing and validating OAuth/OIDC metadata profile valid=false compatibleContentType=false profile="unknown" issue="Response is not valid JSON." missingCount=0 warningsCount=0 endpointIssuesCount=0 responseTypesSupportedCount=0 grantTypesSupportedCount=0 inferredGrantTypes=falsePASSCheck metadata profile was recognized actual="unknown" expected="oauth-authorization-server, oidc, or hybrid"PASSCheck required metadata fields are present actual=0 expected=0 missing=[]PASSCheck OAuth metadata is fully usable by browser and agent clients actual="no client-usage warnings" expected="no CORS, endpoint, or compatibility warnings" warnings=[]FAILValidate metadata profile failed issue="Response is not valid JSON."Validate discovery CORS [warning]! Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin.INFOValidate discovery CORSINFOChecking whether browser clients can read the public discovery document profile="unknown" corsPresent=trueWARNCheck Access-Control-Allow-Origin header actual="missing" expected="present or wildcard for browser-readable discovery"WARNValidate discovery CORS completed with warnings issue="Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin."
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
14 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
13 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
Needs attention
A2A Agent Card
Issue
The discovered JSON document does not match a supported A2A Agent Card version family.
Why it matters
A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.
Check name
A2A Agent Card
Score
48/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.
Result
A2A Agent Card failed at "Detect A2A card version".
Validation steps
Detect A2A card version
The discovered JSON document does not match a supported A2A Agent Card version family.
Validate version-specific card shape
A2A Agent Card response is not valid JSON.
Validate HTTP delivery
The card was parseable JSON but was not served with a JSON-compatible content type.
Probe same-origin A2A endpoint
A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.
Evidence log4 steps · 17 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
13 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
CSP does not define default-src; several fetch directives may have no restrictive fallback.
Why it matters
Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.
Check name
Content-Security-Policy
Score
50/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Evaluate fetch baseline".
Validation steps
Evaluate fetch baseline
CSP does not define default-src; several fetch directives may have no restrictive fallback.
Evaluate script execution
No script-src or default-src directive constrains script execution.
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri, form-action.
Review CSP reporting
CSP does not define a reporting endpoint.
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'self'","https://support.collaboraoffice.com","https://mautic.collaboraoffice.com","https://www.collaboraonline.com"] formCount=1WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
13 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
Needs attention
HSTS header
Issue
HTTPS response is missing Strict-Transport-Security.
Why it matters
HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.
Check name
HSTS header
Score
50/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.
Result
HSTS header failed at "Find Strict-Transport-Security".
Validation steps
Find Strict-Transport-Security
HTTPS response is missing Strict-Transport-Security.
Evidence log1 step · 4 lines
Find Strict-Transport-Security [fail]! HTTPS response is missing Strict-Transport-Security.INFOFind Strict-Transport-SecurityINFORead Strict-Transport-Security header header="strict-transport-security" value="missing" effectiveValue=null duplicateHeaderValueCount=0FAILRequire HSTS header on HTTPS response actual="missing" expected="present" issue="HTTPS response is missing Strict-Transport-Security."FAILHTTPS response is missing Strict-Transport-Security.Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
13 Warning
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID HTTPS/SVCB records were found under _agents.
Why it matters
DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.
Check name
DNS-AID Agent Discovery
Score
50/100
Status
warning
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
Validation steps
Query DNS-AID records
No DNS-AID HTTPS/SVCB records were found under _agents.
Check DNSSEC authentication evidence
DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
Evidence log2 steps · 24 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="www.collaboraonline.com" labels=["_index._agents.www.collaboraonline.com","_a2a._agents.www.collaboraonline.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.www.collaboraonline.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.collaboraonline.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.www.collaboraonline.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.www.collaboraonline.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.collaboraonline.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.collaboraonline.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.www.collaboraonline.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.www.collaboraonline.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.collaboraonline.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.collaboraonline.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.collaboraonline.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.collaboraonline.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.collaboraonline.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.collaboraonline.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.collaboraonline.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.collaboraonline.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="www.collaboraonline.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="collaboraonline.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
12 Fail
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
Needs attention
ai.txt policy
Issue
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Why it matters
ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.
Check name
ai.txt policy
Score
38/100
Status
fail
Category
Bot Access Control
Maturity
Emerging recommendation
Goal
Publish an advisory human-readable AI usage policy only when the site intentionally needs one.
Result
ai.txt policy failed at "Validate transport".
Validation steps
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
Validate policy content
ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
Evidence log3 steps · 14 lines
Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html" length=467808 lineCount=3824FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="generic-markdown" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="generic-markdown"INFODetected policy signals hasPermissionLanguage=true hasRestrictionLanguage=false hasTrainingLanguage=true hasAttributionLanguage=true hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
12 Warning
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: expected exactly one visible main landmark, found 0; invalid h1 structure (visible h1 count 0); skipped or empty headings; 56 links missing accessible names; 26 image alt text quality issues.
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
42/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Expose readable page structure through semantic HTML and accessible controls.
Result
Semantic HTML is partially implemented.
Validation steps
Page landmarks
Expected exactly one visible main landmark; found 0.
Heading structure
Expected one meaningful visible h1; found 0.
Links
56 links are missing accessible names.
Image text alternatives
26 image alt text issues were found.
Evidence log4 steps · 12 lines
Page landmarks [fail]! Expected exactly one visible main landmark; found 0.INFOPage landmarksFAILCheck page landmarks evidence actual={"counts":{"main":0,"roleMain":0,"nav":3,"roleNavigation":1,"header":0,"roleBanner":0,"footer":1,"pageFooter":1,"roleContentinfo":0},"main":false} expected="semantic HTML evidence for this step"FAILPage landmarks failed issue="Expected exactly one visible main landmark; found 0."Heading structure [fail]! Expected one meaningful visible h1; found 0.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":0,"visibleH1":0,"headings":128,"emptyHeadings":0},"meaningfulH1":false} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Expected one meaningful visible h1; found 0."Links [fail]! 56 links are missing accessible names.INFOLinksFAILCheck links evidence actual={"counts":{"links":194,"inaccessibleLinks":56,"nonCrawlableLinks":0,"genericLinks":0},"accessibleLinks":false} expected="semantic HTML evidence for this step"FAILLinks failed issue="56 links are missing accessible names."Image text alternatives [warning]! 26 image alt text issues were found.INFOImage text alternativesWARNCheck image text alternatives evidence actual={"counts":{"images":112,"imagesWithAlt":112,"imageAltIssues":26},"imageAltCoverage":true} expected="semantic HTML evidence for this step"WARNImage text alternatives has a warning issue="26 image alt text issues were found."
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
11 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
Needs attention
Agent Skills index
Issue
Agent Skills index was not served with a JSON-compatible Content-Type.
Details
Why it matters
An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.
Check name
Agent Skills index
Score
55/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.
Result
Agent Skills index failed at "Validate discovery index schema".
Validation steps
Validate discovery index schema
Agent Skills index was not served with a JSON-compatible Content-Type.
Response is not valid JSON.
Verify advertised artifacts
No valid skill artifacts were available to verify.
Validate skill content
For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.
Review skill artifact security
Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.
Evidence log4 steps · 14 lines
Validate discovery index schema [fail]! Agent Skills index was not served with a JSON-compatible Content-Type.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=false contentTypeCompatible=falseFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index was not served with a JSON-compatible Content-Type.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
10 Warning
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
Needs attention
Content Signal
Issue
No Content-Usage or Content-Signal declarations were found.
Why it matters
Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.
Check name
Content Signal
Score
50/100
Status
warning
Category
Bot Access Control
Maturity
Informational
Goal
Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.
Result
Content Signal has a validation warning at "Validate declared usage preferences".
Validation steps
Validate declared usage preferences
No Content-Usage or Content-Signal declarations were found.
Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! No Content-Usage or Content-Signal declarations were found.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=0SKIPSkipping declaration validation because no Content-Usage or Content-Signal records were declared.SKIPCompare declared records to validation requirement actual=0 expected="No validation needed when no records are declared"WARNNo Content-Usage or Content-Signal declarations were present.AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
10 Warning
AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
Needs attention
RSL license signal
Issue
No RSL declarations were found.
Why it matters
Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.
Check name
RSL license signal
Score
50/100
Status
warning
Category
Bot Access Control
Maturity
Emerging recommendation
Goal
Declare machine-readable content licensing terms for compliant AI and crawler systems when the site needs them.
Result
No RSL declarations were found.
Validation steps
Discover RSL declarations
No RSL declarations were found.
Evidence log1 step · 4 lines
Discover RSL declarations [warning]! No RSL declarations were found.INFODiscover RSL declarationsINFOChecking robots.txt License records, HTTP Link rel=license headers, HTML license links, and inline RSL XML robotsFound=trueSKIPCount discovered RSL declarations actual=0 expected=">= 1 when RSL licensing terms are published" sources={}WARNNo RSL declarations were found on any supported discovery surface.AI DiscoverabilityBot Access ControlEmerging recommendation
TDMRep declaration
No TDMRep declaration was found.
10 Warning
AI DiscoverabilityBot Access ControlEmerging recommendation
TDMRep declaration
No TDMRep declaration was found.
Needs attention
TDMRep declaration
Issue
No TDMRep declaration was found at /.well-known/tdmrep.json.
Why it matters
TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.
Check name
TDMRep declaration
Score
50/100
Status
warning
Category
Bot Access Control
Maturity
Emerging recommendation
Goal
Publish a machine-readable text and data mining reservation declaration and verifiable ODRL policy when the site needs one.
Result
No TDMRep declaration was found.
Validation steps
Fetch /.well-known/tdmrep.json
No TDMRep declaration was found at /.well-known/tdmrep.json.
Evidence log1 step · 4 lines
Fetch /.well-known/tdmrep.json [warning]! No TDMRep declaration was found at /.well-known/tdmrep.json.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonINFOThe TDMRep request did not return an HTTP response error="TypeError: fetch failed"WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. error="TypeError: fetch failed"AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
9 Warning
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
No named author or publisher identity could be extracted.
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
55/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Schema.org attribution is incomplete or relies only on publisher/fallback evidence.
Author identity quality
No named author or publisher identity could be extracted.
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=1 namedContributors=0 authors=[] publishers=[{"role":"publisher","id":"https://www.collaboraonline.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=1 authors=[] publishers=[{"role":"publisher","id":"https://www.collaboraonline.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[{"role":"publisher","id":"https://www.collaboraonline.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
9 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
Needs attention
GEO: Citable passages
Issue
No evidence-backed, citation-length explanatory paragraph was found.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Citable passages
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Citable passages scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 22/100 and needs a fix.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 22/100 and needs a fix.
Needs attention
AEO: Answer-first passages
Issue
117 section(s) bury or omit a concise opening answer.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Answer-first passages
Score
22/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Answer-first passages scored 22/100 and needs a fix.
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection has a validation warning at "Validate X-Frame-Options".
4 Warning
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection has a validation warning at "Validate X-Frame-Options".
Needs attention
Frame protection
Issue
X-Frame-Options is not DENY or SAMEORIGIN. Modern browsers can still use the enforcing frame-ancestors policy.
Why it matters
Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.
Check name
Frame protection
Score
83/100
Status
warning
Category
Security & Trust
Maturity
Established
Goal
Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.
Result
Frame protection has a validation warning at "Validate X-Frame-Options".
Validation steps
Validate X-Frame-Options
X-Frame-Options is not DENY or SAMEORIGIN. Modern browsers can still use the enforcing frame-ancestors policy.
Review CSP and XFO interaction
CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.
Evidence log2 steps · 8 lines
Validate X-Frame-Options [warning]! X-Frame-Options is not DENY or SAMEORIGIN. Modern browsers can still use the enforcing frame-ancestors policy.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="SAMEORIGIN ALLOW-FROM https://support.collaboraoffice.com https://mautic.collaboraoffice.com https://www.collaboraonline.com" parsedValues=["SAMEORIGIN ALLOW-FROM https://support.collaboraoffice.com https://mautic.collaboraoffice.com https://www.collaboraonline.com"] normalizedValues=["sameorigin allow-from https://support.collaboraoffice.com https://mautic.collaboraoffice.com https://www.collaboraonline.com"]WARNCompare X-Frame-Options value actual="invalid" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="X-Frame-Options is not DENY or SAMEORIGIN. Modern browsers can still use the enforcing frame-ancestors policy."WARNX-Frame-Options is not DENY or SAMEORIGIN. Modern browsers can still use the enforcing frame-ancestors policy.Review CSP and XFO interaction [warning]! CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.INFOReview CSP and XFO interactionINFOCompare modern CSP and legacy XFO behavior modernBrowserMechanism="csp-frame-ancestors" cspOverridesXfo=true cspMode="explicit"WARNCheck CSP/XFO policy alignment actual="aligned or single mechanism" expected="no conflicting framing policy" issue="CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting."WARNCSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 67/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 67/100 and needs improvement.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Source and trust signals
Score
67/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Source and trust signals scored 67/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 63/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 63/100 and needs improvement.
Needs attention
GEO: Structured extraction
Issue
Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, FAQ or question-answer section where appropriate.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Structured extraction
Score
63/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Structured extraction scored 63/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 70/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 70/100 and needs improvement.
Needs attention
AIO: Visible content clarity
Issue
Expected exactly one h1, found 0. 117 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Visible content clarity
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Visible content clarity scored 70/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 67/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 67/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Expected exactly one h1, found 0. Title/H1 terms missing from description: office.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Entity clarity
Score
67/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Entity clarity scored 67/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 69/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 69/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Expected exactly one h1, found 0.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Entity and definition clarity
Score
69/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Entity and definition clarity scored 69/100 and needs improvement.
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Page-relevant schema family".
3 Fail
AI DiscoverabilityContent ReadinessEstablished
Structured data
Structured data failed at "Page-relevant schema family".
Needs attention
Structured data
Issue
The page has specific visible content intent, but structured data does not include a matching primary schema family.
Why it matters
Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.
Check name
Structured data
Score
87/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose machine-readable page entities and relationships through a recognized structured-data syntax.
Result
Structured data failed at "Page-relevant schema family".
Validation steps
Page-relevant schema family
The page has specific visible content intent, but structured data does not include a matching primary schema family.
Evidence log1 step · 4 lines
Page-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["software","local-business","discussion"] expectedTypes=["SoftwareApplication","WebApplication","MobileApplication","LocalBusiness","DiscussionForumPosting"] matchingTypes=[] observedTypes=["BreadcrumbList","ImageObject","Organization","WebPage","WebSite"]FAILNo primary schema family matches the inferred page intent expectedTypes=["SoftwareApplication","WebApplication","MobileApplication","LocalBusiness","DiscussionForumPosting"] primaryTypes=["BreadcrumbList"]GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 71/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 71/100 and needs improvement.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: author, publisher.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Evidence and trust
Score
71/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Evidence and trust scored 71/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 75/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 75/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
40 image(s) are missing width/height attributes. 1 possible modal/interstitial element(s) detected.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Page experience proxy
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Page experience proxy scored 75/100 and needs improvement.
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options has a validation warning at "Review observed browser responses".
2 Warning
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options has a validation warning at "Review observed browser responses".
Needs attention
X-Content-Type-Options
Issue
One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
Why it matters
X-Content-Type-Options tells browsers to trust declared media types instead of sniffing content, reducing the risk that mislabeled files execute as active content.
Check name
X-Content-Type-Options
Score
93/100
Status
warning
Category
Security & Trust
Maturity
Established
Goal
Prevent browser MIME sniffing for browser-loadable responses with X-Content-Type-Options: nosniff.
Result
X-Content-Type-Options has a validation warning at "Review observed browser responses".
Validation steps
Review observed browser responses
One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
Evidence log1 step · 4 lines
Review observed browser responses [warning]! One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.INFOReview observed browser responsesINFOSample Chrome-observed same-origin resources observedResponseCount=120 sameOriginCount=116 eligibleCount=115WARNCompare observed nosniff coverage actual={"missingNosniffCount":100,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":60,"affected":[{"url":"https://www.collaboraonline.com/wp-content/plugins/podlove-podcasting-plugin-for-wordpress/css/frontend.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/podlove-podcasting-plugin-for-wordpress/css/admin-font.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/uploads/elementor/css/custom-frontend.min.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/uploads/elementor/css/post-28384.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/common-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/profile-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/testimonial-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/post-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/tour-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/listing-card-style.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/card-elements-for-elementor/assets/css/font-awesome.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"},{"url":"https://www.collaboraonline.com/wp-content/plugins/elementor/assets/lib/font-awesome/css/all.min.css?ver=1781741591","status":200,"resourceType":"stylesheet","contentType":"text/css text/css"}]} expected="0 missing or malformed eligible same-origin responses" issue="One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff."WARNOne or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 83/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 83/100 and needs improvement.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: authorOrOwner.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Source and trust signals
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 without promising inclusion in any proprietary answer surface.
Result
GEO: Source and trust signals scored 83/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 87/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 87/100 and needs improvement.
Needs attention
AEO: Question and answer structure
Issue
Heading structure issues were detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Question and answer structure
Score
87/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Question and answer structure scored 87/100 and needs improvement.
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 log2 steps · 10 lines
Find advertised IndexNow key location [informational]! No IndexNow key location was advertised in HTML, Link headers, or robots.txt.INFOFind advertised IndexNow key locationINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"WARNNo IndexNow key location was advertised in HTML, Link headers, or robots.txt.Fetch and validate IndexNow key file [informational]! No discoverable IndexNow key file was found.INFOFetch and validate IndexNow key fileINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"INFOFetch each advertised same-origin key file and validate filename/body matchFAILCompare valid IndexNow key file count actual=0 expected="> 0"WARNNo discoverable IndexNow key file was found.
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing is informational for this page.
Informational
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing is informational for this page.
Needs attention
Web Bot Auth request signing
Issue
Web Bot Auth request signing is informational for this page.
Why it matters
Web Bot Auth lets bot and agent operators publish HTTP Message Signatures keys so receiving websites can verify signed automated requests without relying only on user-agent strings, IP lists, or reverse DNS.
Check name
Web Bot Auth request signing
Score
100/100
Status
informational
Category
Bot Access Control
Maturity
Informational
Goal
Validate public signing-key discovery when this origin operates signed bots or agents whose requests other sites can verify.
Result
Web Bot Auth request signing is informational for this page.
Validation steps
Discover signing key directory
The Web Bot Auth directory could not be checked reliably.
Evidence log1 step · 5 lines
Discover signing key directory [informational]! The Web Bot Auth directory could not be checked reliably.INFODiscover signing key directory status="informational"INFOCheck homepage and headers for Web Bot Auth claims matches=[] homepageHtmlBytes=483694 homepageHeaderCount=11INFOFetch signing key directory url="https://www.collaboraonline.com/.well-known/http-message-signatures-directory"WARNDirectory fetch could not be completed error="fetch failed"INFOThe Web Bot Auth directory could not be checked reliably. status="informational"SEOSEOBrowser audit
Document does not have a meta description
100 Fail
SEOSEOBrowser audit
Document does not have a meta description
Check name
Document does not have a meta description
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).
Evidence
{
"description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}AccessibilityAccessibilityBrowser audit
ARIA attributes must conform to valid values
8 Fail
AccessibilityAccessibilityBrowser audit
ARIA attributes must conform to valid values
Check name
ARIA attributes must conform to valid values
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
ARIA attributes must conform to valid values
Evidence
{
"ruleId": "aria-valid-attr-value",
"impact": "critical",
"description": "Ensure all ARIA attributes have valid values",
"tags": [
"cat.aria",
"wcag2a",
"wcag412",
"EN-301-549",
"EN-9.4.1.2",
"RGAAv4",
"RGAA-7.1.1"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".e-floating-bars__close-button"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 163
},
"failureSummary": "Fix all of the following:\n Invalid ARIA attribute value: aria-controls=\"e-floating-bars\""
}
]
}AccessibilityAccessibilityBrowser audit
Certain ARIA roles must contain particular children
8 Fail
AccessibilityAccessibilityBrowser audit
Certain ARIA roles must contain particular children
Check name
Certain ARIA roles must contain particular children
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Certain ARIA roles must contain particular children
Evidence
{
"ruleId": "aria-required-children",
"impact": "critical",
"description": "Ensure elements with an ARIA role that require child roles contain them",
"tags": [
"cat.aria",
"wcag2a",
"wcag131",
"EN-301-549",
"EN-9.1.3.1",
"RGAAv4",
"RGAA-9.3.1"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".elementor-element-cef3cfa > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 65
},
"failureSummary": "Fix any of the following:\n Element has children which are not allowed: a"
}
]
}PerformancePerformanceBrowser audit
Font display
7 Fail
PerformancePerformanceBrowser audit
Font display
Check name
Font display
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 3,000Â 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 3,000Â 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)."
}PerformancePerformanceBrowser audit
Forced reflow
7 Fail
PerformancePerformanceBrowser audit
Forced reflow
Check name
Forced reflow
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
References
https://web.dev/learn/performance/Evidence
{
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}PerformancePerformanceBrowser audit
Layout shift culprits
7 Fail
PerformancePerformanceBrowser audit
Layout shift culprits
Check name
Layout shift culprits
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.
References
https://web.dev/learn/performance/Evidence
{
"description": "Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads."
}PerformancePerformanceBrowser audit
LCP breakdown
7 Fail
PerformancePerformanceBrowser audit
LCP breakdown
Check name
LCP breakdown
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
References
https://web.dev/learn/performance/Evidence
{
"description": "Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays."
}PerformancePerformanceBrowser audit
Minify CSS
7 Fail
PerformancePerformanceBrowser audit
Minify CSS
Check name
Minify CSS
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 21Â KiB
Fix guidance
Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 21Â KiB",
"description": "Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).",
"numericValue": 40
}PerformancePerformanceBrowser audit
Network dependency tree
7 Fail
PerformancePerformanceBrowser 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."
}PerformancePerformanceBrowser audit
Reduce unused CSS
7 Fail
PerformancePerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 1,336Â 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 1,336Â 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": 1020
}PerformancePerformanceBrowser audit
Reduce unused JavaScript
7 Fail
PerformancePerformanceBrowser audit
Reduce unused JavaScript
Check name
Reduce unused JavaScript
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 3,598Â 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 3,598Â 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": 160
}PerformancePerformanceBrowser audit
Render-blocking requests
7 Fail
PerformancePerformanceBrowser audit
Render-blocking requests
Check name
Render-blocking requests
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 7,890Â ms
Fix guidance
Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 7,890Â ms",
"description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}AccessibilityAccessibilityBrowser audit
ARIA dialog and alertdialog nodes should have an accessible name
6 Fail
AccessibilityAccessibilityBrowser audit
ARIA dialog and alertdialog nodes should have an accessible name
Check name
ARIA dialog and alertdialog nodes should have an accessible name
Score
25/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
ARIA dialog and alertdialog nodes should have an accessible name
Evidence
{
"ruleId": "aria-dialog-name",
"impact": "serious",
"description": "Ensure every ARIA dialog and alertdialog node has an accessible name",
"tags": [
"cat.aria",
"best-practice"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".e-floating-bars"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 170
},
"failureSummary": "Fix any of the following:\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
}
]
}AccessibilityAccessibilityBrowser audit
ARIA hidden element must not be focusable or contain focusable elements
6 Fail
AccessibilityAccessibilityBrowser audit
ARIA hidden element must not be focusable or contain focusable elements
Check name
ARIA hidden element must not be focusable or contain focusable elements
Score
25/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
ARIA hidden element must not be focusable or contain focusable elements
Evidence
{
"ruleId": "aria-hidden-focus",
"impact": "serious",
"description": "Ensure aria-hidden elements are not focusable nor contain focusable elements",
"tags": [
"cat.name-role-value",
"wcag2a",
"wcag412",
"TTv5",
"TT6.a",
"EN-301-549",
"EN-9.4.1.2",
"RGAAv4",
{
"truncated": true,
"omittedCount": 1,
"originalCount": 9
}
],
"affectedNodeCount": 8,
"nodes": [
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(2)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(3)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(4)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(5)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(6)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(7)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner:nth-child(1) > .e-floating-bars__headline--clone.e-floating-bars__headline[aria-hidden=\"true\"]:nth-child(8)"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 151
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
},
{
"target": [
".e-floating-bars__headlines-inner--clone"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 105
},
"failureSummary": "Fix all of the following:\n Focusable content should have tabindex=\"-1\" or be removed from the DOM"
}
]
}AccessibilityAccessibilityBrowser audit
Links must have discernible text
6 Fail
AccessibilityAccessibilityBrowser audit
Links must have discernible text
Check name
Links must have discernible text
Score
25/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Links must have discernible text
Evidence
{
"ruleId": "link-name",
"impact": "serious",
"description": "Ensure links have discernible text",
"tags": [
"cat.name-role-value",
"wcag2a",
"wcag244",
"wcag412",
"section508",
"section508.22.a",
"TTv5",
"TT6.a",
{
"truncated": true,
"omittedCount": 6,
"originalCount": 14
}
],
"affectedNodeCount": 39,
"nodes": [
{
"target": [
".elementor-sticky--active > .e-con-inner > .elementor-element-efe8a34[data-id=\"efe8a34\"][data-widget_type=\"image.default\"] > .elementor-widget-container > a"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 43
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".elementor-element-ec261ac > .elementor-widget-container > a[data-elementor-open-lightbox=\"yes\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 159
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-56993 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 190
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-56952 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 193
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-55616 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 200
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-54786 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 191
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-54030 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 194
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"target": [
".e-loop-item-53300 > .elementor-element-e82b82b.e-parent[data-id=\"e82b82b\"]"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 197
},
"failureSummary": "Fix all of the following:\n Element is in tab order and does not have accessible text\n\nFix any of the following:\n Element does not have text that is visible to screen readers\n aria-label attribute does not exist or is empty\n aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n Element has no title attribute"
},
{
"truncated": true,
"omittedCount": 2,
"originalCount": 10
}
]
}PerformancePerformanceBrowser audit
Loading performance
4 Fail
PerformancePerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
41/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": "50Â ms",
"numericValue": 45.05566499999999
},
{
"id": "largest-contentful-paint",
"title": "Largest Contentful Paint",
"score": 47,
"displayValue": "2.5Â s",
"numericValue": 2490
},
{
"id": "max-potential-fid",
"title": "Max Potential First Input Delay",
"score": 58,
"displayValue": "230Â ms",
"numericValue": 225.00000000000182
},
{
"id": "server-response-time",
"title": "Initial server response time was short",
"score": 100,
"displayValue": "Root document took 280Â ms",
"numericValue": 282
},
{
"id": "speed-index",
"title": "Speed Index",
"score": 1,
"displayValue": "6.3Â s",
"numericValue": 6339.4170221025615
},
{
"id": "interactive",
"title": "Time to Interactive",
"score": 1,
"displayValue": "12.9Â s",
"numericValue": 12851.45358562763
},
{
"id": "first-contentful-paint",
"title": "First Contentful Paint",
"score": 16,
"displayValue": "2.4Â s",
"numericValue": 2410
},
{
"id": "total-blocking-time",
"title": "Total Blocking Time",
"score": 2,
"displayValue": "1,260Â ms",
"numericValue": 1259.0000000000064
}
]
}AccessibilityAccessibilityBrowser audit
All page content should be contained by landmarks
4 Warning
AccessibilityAccessibilityBrowser audit
All page content should be contained by landmarks
Check name
All page content should be contained by landmarks
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
All page content should be contained by landmarks
Evidence
{
"ruleId": "region",
"impact": "moderate",
"description": "Ensure all page content is contained by landmarks",
"tags": [
"cat.keyboard",
"best-practice",
"RGAAv4",
"RGAA-9.2.1"
],
"affectedNodeCount": 48,
"nodes": [
{
"target": [
".skip-link"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 81
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-b9c36c0"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 211
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-b66f9f3"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 179
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-a0dafe3"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 187
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-b04a655"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 137
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-5d53a8b"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 137
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-7516504"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 179
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"target": [
".elementor-element-17b9bab > .elementor-widget-container > .elementor-icon-box-wrapper > .elementor-icon-box-content"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 300
},
"failureSummary": "Fix any of the following:\n Some page content is not contained by landmarks"
},
{
"truncated": true,
"omittedCount": 2,
"originalCount": 10
}
]
}AccessibilityAccessibilityBrowser audit
Document should have one main landmark
4 Warning
AccessibilityAccessibilityBrowser audit
Document should have one main landmark
Check name
Document should have one main landmark
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
Document should have one main landmark
Evidence
{
"ruleId": "landmark-one-main",
"impact": "moderate",
"description": "Ensure the document has a main landmark",
"tags": [
"cat.semantics",
"best-practice"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
"html"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 19
},
"failureSummary": "Fix all of the following:\n Document does not have a main landmark"
}
]
}AccessibilityAccessibilityBrowser audit
Heading levels should only increase by one
4 Warning
AccessibilityAccessibilityBrowser audit
Heading levels should only increase by one
Check name
Heading levels should only increase by one
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
Heading levels should only increase by one
Evidence
{
"ruleId": "heading-order",
"impact": "moderate",
"description": "Ensure the order of headings is semantically correct",
"tags": [
"cat.semantics",
"best-practice"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".elementor-element-17b9bab > .elementor-widget-container > .elementor-icon-box-wrapper > .elementor-icon-box-content > h4"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 104
},
"failureSummary": "Fix any of the following:\n Heading order invalid"
}
]
}AccessibilityAccessibilityBrowser audit
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
4 Warning
AccessibilityAccessibilityBrowser audit
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Check name
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Evidence
{
"ruleId": "landmark-unique",
"impact": "moderate",
"description": "Ensure landmarks are unique",
"tags": [
"cat.semantics",
"best-practice"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".elementor-element-72fbf80 > .elementor-widget-container > .elementor-nav-menu--main.elementor-nav-menu--layout-vertical.e--pointer-text"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 157
},
"failureSummary": "Fix any of the following:\n The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable"
}
]
}AccessibilityAccessibilityBrowser audit
Page should contain a level-one heading
4 Warning
AccessibilityAccessibilityBrowser audit
Page should contain a level-one heading
Check name
Page should contain a level-one heading
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
Page should contain a level-one heading
Evidence
{
"ruleId": "page-has-heading-one",
"impact": "moderate",
"description": "Ensure that the page, or at least one of its frames contains a level-one heading",
"tags": [
"cat.semantics",
"best-practice"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
"html"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 19
},
"failureSummary": "Fix all of the following:\n Page must have a level-one heading"
}
]
}AccessibilityAccessibilityBrowser audit
The skip-link target should exist and be focusable
4 Warning
AccessibilityAccessibilityBrowser audit
The skip-link target should exist and be focusable
Check name
The skip-link target should exist and be focusable
Score
55/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
The skip-link target should exist and be focusable
Evidence
{
"ruleId": "skip-link",
"impact": "moderate",
"description": "Ensure all skip links have a focusable target",
"tags": [
"cat.keyboard",
"best-practice",
"RGAAv4",
"RGAA-12.7.1"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".skip-link"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 81
},
"failureSummary": "Fix any of the following:\n No skip link target"
}
]
}PerformancePerformanceBrowser audit
Avoid enormous network payloads
4 Warning
PerformancePerformanceBrowser 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 13,808Â 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 13,808Â 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": 14139635
}PerformancePerformanceBrowser audit
Image elements do not have explicit `width` and `height`
4 Warning
PerformancePerformanceBrowser audit
Image elements do not have explicit `width` and `height`
Check name
Image elements do not have explicit `width` and `height`
Score
50/100
Status
warning
Device
desktop
Category
Performance
Fix guidance
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)
References
https://web.dev/learn/performance/Evidence
{
"description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)"
}PerformancePerformanceBrowser audit
Improve image delivery
4 Warning
PerformancePerformanceBrowser audit
Improve image delivery
Check name
Improve image delivery
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 1,575Â KiB
Fix guidance
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 1,575Â KiB",
"description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}PerformancePerformanceBrowser audit
Legacy JavaScript
4 Warning
PerformancePerformanceBrowser audit
Legacy JavaScript
Check name
Legacy JavaScript
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 61Â 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 61Â 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)"
}AccessibilityAccessibilityBrowser audit
ARIA role should be appropriate for the element
2 Warning
AccessibilityAccessibilityBrowser audit
ARIA role should be appropriate for the element
Check name
ARIA role should be appropriate for the element
Score
75/100
Status
warning
Device
desktop
Category
Accessibility
Fix guidance
ARIA role should be appropriate for the element
Evidence
{
"ruleId": "aria-allowed-role",
"impact": "minor",
"description": "Ensure role attribute has an appropriate value for the element",
"tags": [
"cat.aria",
"best-practice"
],
"affectedNodeCount": 5,
"nodes": [
{
"target": [
".post-59689"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 198
},
"failureSummary": "Fix any of the following:\n ARIA role listitem is not allowed for given element"
},
{
"target": [
".post-59746"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 254
},
"failureSummary": "Fix any of the following:\n ARIA role listitem is not allowed for given element"
},
{
"target": [
".post-59037"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 201
},
"failureSummary": "Fix any of the following:\n ARIA role listitem is not allowed for given element"
},
{
"target": [
".post-59498"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 198
},
"failureSummary": "Fix any of the following:\n ARIA role listitem is not allowed for given element"
},
{
"target": [
".post-58411"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 168
},
"failureSummary": "Fix any of the following:\n ARIA role listitem is not allowed for given element"
}
]
}Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 47/100 | Level 2, Agent-Limited | Current report |