Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 72 out of 100
- Agent Ease of Use 65 out of 100
- Security & Trust 96 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 100 out of 100
- Performance 99 out of 100
- Accessibility 95 out of 100
What AI sees of your website
anon.li - Privacy-First Email Aliases, Encrypted File Sharing & Forms
Protect your identity with private email aliases, end-to-end encrypted file sharing, and confidential forms. Sign up free, forward email without exposing your personal address, share files with client-side encryption, and collect responses...
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 | 72 | Needs work | 35 | 2 | 1 | View details |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 63 | Needs work | 22 | 1 | 1 | View details |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 65 | Needs work | 27 | 1 | 1 | View details |
| API | 72 | Needs work | 11 | 1 | 1 | View details |
| Auth | 68 | Needs work | 9 | 0 | 0 | |
| MCP | 62 | Needs work | 3 | 0 | 0 | |
| Skill Discovery | 59 | Needs work | 4 | 0 | 0 | |
| GEO, AIO and AEO | 68 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| Security & Trust | 96 | Strong | 27 | 0 | 0 | |
| Security & Trust | 96 | Strong | 27 | 0 | 0 | |
| Performance | 99 | Strong | 14 | 0 | 0 | |
| Performance | 99 | Strong | 14 | 0 | 0 | |
| Accessibility | 95 | Strong | 9 | 0 | 0 | |
| Accessibility | 95 | Strong | 9 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 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=0AI 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.
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=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]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=[]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://anon.li/api/v1/alias (item) returned HTTP 401 instead of a 2xx/3xx response.
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".
Validate API catalog targets
API catalog target https://anon.li/api/v1/alias (item) returned HTTP 401 instead of a 2xx/3xx response.
Evidence log2 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="application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\""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://anon.li/api/v1/alias (item) returned HTTP 401 instead of a 2xx/3xx response.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/v1/alias" statusCode=401 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/v1/drop" statusCode=401 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/v1/form" statusCode=401 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/v1/domain" statusCode=401 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/v1/recipient" statusCode=401 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://anon.li/api/mcp" statusCode=401 contentType="application/json" typeMatches=truePASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/alias" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/drop" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/form" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/domain" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/recipient" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://anon.li/docs/api/mcp" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-meta" href="https://anon.li/.well-known/mcp/server-card.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-meta" href="https://anon.li/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-meta" href="https://anon.li/.well-known/oauth-protected-resource" statusCode=200 contentType="application/json" advertisedType="application/json"FAILCompare API catalog target failure count actual=6 expected=0FAILAPI catalog target https://anon.li/api/v1/alias (item) returned HTTP 401 instead of a 2xx/3xx response.
Sign in to see 25 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