Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 75 out of 100
- Agent Ease of Use 64 out of 100
- Security & Trust 91 out of 100
- GEO, AIO and AEO 69 out of 100
- SEO 100 out of 100
- Performance 87 out of 100
- Accessibility 94 out of 100
What AI sees of your website
Secure Privacy - Cookie Consent & Privacy Compliance Platform
Simplify cookie consent and privacy compliance for global teams. Consent Solution & Privacy Governance supporting 55+ privacy laws including GDPR, CCPA, LGPD. SOC2 certified.
Next step
Turn this report into a fix workflow
2 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 | 75 | Mostly ready | 40 | 1 | 1 | View details |
| Discoverability | 73 | Needs work | 6 | 0 | 0 | |
| Content Readiness | 77 | Mostly ready | 29 | 1 | 1 | View details |
| Bot Access Control | 75 | Mostly ready | 5 | 0 | 0 | |
| Agent Ease of Use | 64 | Needs work | 21 | 4 | 1 | View details |
| API | 72 | Needs work | 11 | 1 | 1 | View details |
| Auth | 37 | Priority fix | 1 | 3 | 0 | View details |
| MCP | 59 | Needs work | 3 | 0 | 0 | |
| Skill Discovery | 57 | Needs work | 3 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 69 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 91 | Strong | 25 | 0 | 0 | |
| Security & Trust | 91 | Strong | 25 | 0 | 0 | |
| Performance | 87 | Mostly ready | 18 | 0 | 0 | |
| Performance | 87 | Mostly ready | 18 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
90 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. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.
Details
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. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.
/auth.md is missing or not usable as agent registration guidance
Validate protected resource metadata
OAuth Protected Resource Metadata could not be fetched.
Auth.md protected-resource metadata is missing or incomplete
Validate Auth.md authorization metadata
OAuth authorization-server metadata could not be fetched.
Authorization-server metadata lacks Auth.md v1 fields
Evidence log3 steps · 21 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" bytes=895FAILCompare response Content-Type with expected Auth.md media type actual=true expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=853 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"WARNAuth.md validation warning warning="missing credential usage, expiry, error, or revocation guidance"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.Validate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=404 contentType="text/html; charset=utf-8" bytes=12175FAILCompare 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="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/html; charset=utf-8" bytes=12183FAILCompare 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="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
45 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.
Details
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.
Schema.org author attribution is missing or incomplete
Author identity quality
No named author or publisher identity could be extracted.
Author identity quality is incomplete
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://secureprivacy.ai/#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://secureprivacy.ai/#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://secureprivacy.ai/#organization","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
21 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.
Details
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
79/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 targets".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
API catalog HEAD Link discovery is incomplete
Validate API catalog targets
API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.
API catalog targets are unreachable or media types mismatch
Evidence log2 steps · 15 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="application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"; charset=utf-8"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 targets [fail]! API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="describedby" href="https://secureprivacy.ai/llms.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="describedby" href="https://secureprivacy.ai/llms-full.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/support" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"FAILAPI catalog target fetch failed rel="sitemap" href="https://secureprivacy.ai/sitemap.xml" error="The operation was aborted due to timeout"PASSAPI catalog target is reachable rel="alternate" href="https://secureprivacy.ai/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/support" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.
Sign in to see 27 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
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 |
|---|---|---|---|
| 78/100 | Level 4, Mostly Ready | Current report |