Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 69 out of 100
- Agent Ease of Use 74 out of 100
- Security & Trust 91 out of 100
- GEO, AIO and AEO 67 out of 100
- SEO 100 out of 100
- Performance 94 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Товары для ремонта и дома — купить в интернет-магазине Vesremont
Где купить товары для ремонта и дома? В Vesremont можно выбрать инструмент, электрику, стройматериалы и сантехнику, узнать цены, наличие, доставку и самовывоз.
Next step
Turn this report into a fix workflow
1 failed check is 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 | 69 | Needs work | 40 | 0 | 0 | |
| Discoverability | 47 | Priority fix | 6 | 0 | 0 | |
| Content Readiness | 85 | Mostly ready | 27 | 0 | 0 | |
| Bot Access Control | 74 | Needs work | 7 | 0 | 0 | |
| Agent Ease of Use | 74 | Needs work | 38 | 1 | 1 | View details |
| API | 97 | Strong | 14 | 0 | 0 | |
| Auth | 67 | Needs work | 11 | 1 | 1 | View details |
| MCP | 52 | Needs work | 3 | 0 | 0 | |
| Skill Discovery | 57 | Needs work | 3 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 7 | 0 | 0 | |
| GEO, AIO and AEO | 67 | Needs work | 9 | 1 | 3 | View details |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | 51 | Needs work | 2 | 1 | 3 | View details |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 91 | Strong | 21 | 0 | 0 | |
| Security & Trust | 91 | Strong | 21 | 0 | 0 | |
| Performance | 94 | Strong | 17 | 0 | 0 | |
| Performance | 94 | Strong | 17 | 0 | 0 | |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
6 items need attention
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
52 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 OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing agent_verified/user_claimed or claim ceremony 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
48/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 OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing agent_verified/user_claimed or claim ceremony guidance.
/auth.md is missing or not usable as agent registration guidance
Validate Auth.md authorization metadata
OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.
Authorization-server metadata lacks Auth.md v1 fields
Evidence log2 steps · 15 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata 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/markdown; charset=utf-8" bytes=4014FAILCompare 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=3911 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. missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing agent_verified/user_claimed or claim ceremony guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing agent_verified/user_claimed or claim ceremony guidance.Validate Auth.md authorization metadata [warning]! OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json; charset=utf-8" bytes=844WARNCompare response Content-Type with expected Auth.md media type actual=true expected=trueWARNCompare Auth.md/OAuth metadata validation result actual=false expected=trueWARNCompare supported credential type count actual=0 expected="> 0"WARNAuth.md validation issue issue="OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{\"field\":\"agent_registration_endpoint\",\"issue\":\"Expected an absolute HTTPS URL.\"}]; missing credential_types_supported."WARNOAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
9 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
Needs attention
AEO: Answer-first passages
Issue
11 section(s) bury or omit a concise opening answer. No direct definition pattern was 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: Answer-first passages
Score
0/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 0/100 and needs a fix.
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: publisher, sources.
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
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 80/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
No direct definition sentence was 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: Entity and definition clarity
Score
80/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 80/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 81/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 81/100 and needs improvement.
Needs attention
AEO: Extractable visible copy
Issue
Visible text has few answer-oriented terms or explanatory markers.
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: Extractable visible copy
Score
81/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: Extractable visible copy scored 81/100 and needs improvement.
AccessibilityAccessibilityBrowser audit
Accessibility audit
100 Fail
AccessibilityAccessibilityBrowser audit
Accessibility audit
Check name
Accessibility audit
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Make sure the page can load in Chrome and run Accessibility checks.
Evidence
{
"error": "Accessibility audit did not return a result."
}Sign in to see 29 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