Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 41 out of 100
- Agent Ease of Use 56 out of 100
- Security & Trust 84 out of 100
- GEO, AIO and AEO 57 out of 100
- SEO 75 out of 100
- Performance 77 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Home | DrayTek
DrayTek Corporation is a Taiwan-based manufacturer of SMB networking equipment, including VPN Routers, managed Switches, wireless AP, and management systems.
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 | 41 | Priority fix | 14 | 1 | 0 | View details |
| Discoverability | 35 | Priority fix | 3 | 0 | 0 | |
| Content Readiness | 25 | Priority fix | 8 | 0 | 0 | |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 56 | Needs work | 11 | 2 | 2 | View details |
| API | 70 | Needs work | 6 | 1 | 2 | View details |
| Auth | 57 | Needs work | 4 | 0 | 0 | |
| Google Agentic Browsing | 49 | Priority fix | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 57 | 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 | 75 | Mostly ready | 6 | 0 | 0 | |
| SEO | 75 | Mostly ready | 6 | 0 | 0 | |
| Security & Trust | 84 | Mostly ready | 21 | 0 | 0 | |
| Security & Trust | 84 | Mostly ready | 21 | 0 | 0 | |
| Performance | 77 | Mostly ready | 11 | 0 | 0 | |
| Performance | 77 | Mostly ready | 11 | 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.
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
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.
robots.txt lacks explicit AI crawler rules
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=0Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
27 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://www.draytek.com/api/v1/resources (service-doc) returned HTTP 403 instead of a 2xx/3xx response.
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
73/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 media type
The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.
API catalog media type is not application/linkset+json
Validate API catalog targets
API catalog target https://www.draytek.com/api/v1/resources (service-doc) returned HTTP 403 instead of a 2xx/3xx response.
API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 14 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; 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 media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json; charset=UTF-8" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://www.draytek.com/api/v1/resources (service-doc) returned HTTP 403 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="service-doc" href="https://www.draytek.com/api/v1/resources" statusCode=403 contentType="text/html; charset=UTF-8" advertisedType="text/html" typeMatches=trueFAILAPI catalog target failed validation rel="service-desc" href="https://www.draytek.com/api/v1/knowledgebase.json" statusCode=403 contentType="text/html; charset=UTF-8" advertisedType="application/json" typeMatches=falseFAILCompare API catalog target failure count actual=3 expected=0FAILAPI catalog target https://www.draytek.com/api/v1/resources (service-doc) returned HTTP 403 instead of a 2xx/3xx response.
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
Check name
Accessibility tree is not well-formed
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
Evidence
{
"description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}Sign in to see 53 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