Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 67 out of 100
- Agent Ease of Use 61 out of 100
- Security & Trust 85 out of 100
- GEO, AIO and AEO 59 out of 100
- SEO 100 out of 100
- Performance 72 out of 100
- Accessibility 91 out of 100
What AI sees of your website
Free PDF Editor Online - No Sign Up, No Watermarks | SimplePDF
Edit, fill, and sign PDFs in your browser - no account, no watermarks, no uploads. Add text, checkboxes, images, and signatures in seconds. HIPAA-friendly, GDPR compliant.
Next step
Turn this report into a fix workflow
3 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 | 67 | Needs work | 30 | 3 | 2 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 73 | Needs work | 19 | 1 | 2 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 61 | Needs work | 8 | 0 | 0 | |
| API | 100 | Strong | 7 | 0 | 0 | |
| MCP | 43 | Priority fix | 1 | 0 | 0 | |
| GEO, AIO and AEO | 59 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 85 | Mostly ready | 20 | 2 | 2 | View details |
| Security & Trust | 85 | Mostly ready | 20 | 2 | 2 | View details |
| Performance | 72 | Needs work | 15 | 0 | 0 | |
| Performance | 72 | Needs work | 15 | 0 | 0 | |
| Accessibility | 91 | Strong | 7 | 0 | 0 | |
| Accessibility | 91 | Strong | 7 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 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.
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Validate Markdown discovery shape".
55 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
45/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
- Missing H1 title, such as '# Example Docs'.
Score llms.txt structure and usefulness
llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.
Findings
- Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
Probe sampled linked resources
Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.
Findings
- 1/25 probed links were broken or unreachable.
- 1/25 probed links did not look agent-readable.
Inspect optional llms-full.txt
Passed.
Evidence log4 steps · 27 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 linksPASSCheck content type is Markdown-compatible text actual="text/plain; charset=UTF-8" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"PASSCheck response is not HTML actual=false expected=falseFAILCheck H1 title is present actual=false expected=truePASSCheck minimum text length actual=18988 expected=">= 160"PASSCheck at least one usable public link actual=77 expected="> 0" linkCount=77FAILMarkdown discovery shape validation failedScore llms.txt structure and usefulness [warning]! llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.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=truePASSCheck H2 section count actual=8 expected="> 0"PASSCheck Markdown-formatted links actual=62 expected="> 0"PASSCheck unsafe/private link count actual=0 expected=0WARNllms.txt structure-quality validation completed with warnings reason="llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples."Probe sampled linked resources [warning]! Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=25PASSCheck probed links were attempted actual=25 expected="> 0"WARNCheck broken probed link count actual=1 expected=0PASSCheck agent-readable probed links actual=24 expected="> 0"WARNLinked resource probe validation completed with warnings reason="Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://simplepdf.com/llms-full.txt"PASS/llms-full.txt returned HTTP 2xx statusCode=200 contentType="text/plain; charset=UTF-8" length=184023PASSCheck llms-full.txt content type is Markdown-compatible text actual="text/plain; charset=UTF-8" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"PASSCheck llms-full.txt looks like supplemental full corpus content actual=true expected=truePASSOptional llms-full.txt inspection recorded
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
50 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
default-src is present but not meaningfully restrictive.
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
default-src is present but not meaningfully restrictive.
Evaluate script execution
script-src leaves script execution broadly unrestricted.
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri.
Review CSP reporting
CSP does not define a reporting endpoint.
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["'self'","http:","https:","ws:","wss:","data:","blob:","'unsafe-inline'"] explicitFetchDirectives=["script-src"]FAILCompare fetch baseline actual=["'self'","http:","https:","ws:","wss:","data:","blob:","'unsafe-inline'"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [fail]! script-src leaves script execution broadly unrestricted.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","http:","https:","blob:","'unsafe-inline'","'wasm-unsafe-eval'"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":true,"dangerousSchemes":["blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src leaves script execution broadly unrestricted."FAILscript-src leaves script execution broadly unrestricted.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","http:","https:","ws:","wss:","data:","blob:","'unsafe-inline'"] frameAncestors=["'self'"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.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.
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