Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 22 out of 100
- Agent Ease of Use 59 out of 100
- Security & Trust 48 out of 100
- GEO, AIO and AEO 24 out of 100
- SEO 45 out of 100
- Performance 99 out of 100
- Accessibility 67 out of 100
What AI sees of your website
403 Forbidden.
No page metadata or readable excerpt was captured.
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 | 22 | Priority fix | 8 | 2 | 0 | View details |
| Discoverability | 7 | Priority fix | 1 | 0 | 0 | |
| Content Readiness | 18 | Priority fix | 7 | 0 | 0 | |
| Bot Access Control | 38 | Priority fix | 0 | 2 | 0 | View details |
| Agent Ease of Use | 59 | Needs work | 2 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 24 | Priority fix | 3 | 3 | 1 | View details |
| AIO Readiness | 37 | Priority fix | 2 | 3 | 1 | View details |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 45 | Priority fix | 5 | 0 | 0 | |
| SEO | 45 | Priority fix | 5 | 0 | 0 | |
| Security & Trust | 48 | Priority fix | 8 | 1 | 1 | View details |
| Security & Trust | 48 | Priority fix | 8 | 1 | 1 | View details |
| Performance | 99 | Strong | 20 | 0 | 0 | |
| Performance | 99 | Strong | 20 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
6 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Fetch robots.txt".
100 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Fetch robots.txt".
Needs attention
AI bot rules in robots.txt
Issue
No robots.txt content was available to inspect for AI bot rules.
Details
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
0/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 "Fetch robots.txt".
Validation steps
Fetch robots.txt
No robots.txt content was available to inspect for AI bot rules.
robots.txt is missing for AI crawler policy inspection
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
80 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
Needs attention
Content-Security-Policy
Issue
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Details
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
20/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 "Find enforcing CSP delivery".
Validation steps
Validate CSP applicability
The response is an error page, so it may not represent the browser application.
CSP applicability could not be confirmed for a browser-rendered page
Find enforcing CSP delivery
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Enforcing Content-Security-Policy header is missing
Evidence log2 steps · 8 lines
Validate CSP applicability [warning]! The response is an error page, so it may not represent the browser application.INFOValidate CSP applicabilityINFOInspect scanned response finalUrl="https://sevencloud.ru/" status=403 contentType="text/html; charset=UTF-8" htmlBytes=740WARNCompare response type actual="HTML document" expected="browser-rendered HTML document" reason="The response is an error page, so it may not represent the browser application."WARNThe response is an error page, so it may not represent the browser application.Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google Search eligibility
AIO: Google Search eligibility scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google Search eligibility
AIO: Google Search eligibility scored 0/100 and needs a fix.
Needs attention
AIO: Google Search eligibility
Issue
HTTP status is 403; Google Search AI features require an indexable 2xx page. Noindex directive found: noindex. Canonical tag is missing. Only 5 visible words 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: Google Search eligibility
Score
0/100
Status
fail
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: Google Search eligibility scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 17/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 17/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks.
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
17/100
Status
fail
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 17/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 42/100 and needs a fix.
4 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 42/100 and needs a fix.
Needs attention
AIO: Visible content clarity
Issue
Expected exactly one h1, found 0. Missing meta description or Open Graph description. Only 5 visible words were detected. 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
42/100
Status
fail
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 42/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 50/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
Missing viewport meta tag. Only 5 words of visible rendered text 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: Page experience proxy
Score
50/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 50/100 and needs improvement.
Sign in to see 35 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