Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 44 out of 100
- Agent Ease of Use 53 out of 100
- Security & Trust 47 out of 100
- GEO, AIO and AEO 56 out of 100
- SEO 83 out of 100
- Performance 45 out of 100
- Accessibility 58 out of 100
What AI sees of your website
OrionVM – Wholesale IaaS Cloud Platform
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 | 44 | Priority fix | 19 | 3 | 1 | View details |
| Discoverability | 33 | Priority fix | 5 | 0 | 0 | |
| Content Readiness | 62 | Needs work | 14 | 1 | 1 | View details |
| Bot Access Control | 38 | Priority fix | 0 | 2 | 0 | View details |
| Agent Ease of Use | 53 | Needs work | 2 | 0 | 0 | |
| Google Agentic Browsing | 66 | Needs work | 2 | 0 | 0 | |
| GEO, AIO and AEO | 56 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 83 | Mostly ready | 7 | 0 | 0 | |
| SEO | 83 | Mostly ready | 7 | 0 | 0 | |
| Security & Trust | 47 | Priority fix | 9 | 2 | 2 | View details |
| Security & Trust | 47 | Priority fix | 9 | 2 | 2 | View details |
| Performance | 45 | Priority fix | 10 | 0 | 0 | |
| Performance | 45 | Priority fix | 10 | 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 "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 "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
CSP does not define default-src; several fetch directives may have no restrictive fallback.
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
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
CSP does not define default-src; several fetch directives may have no restrictive fallback.
CSP fetch baseline is too broad or missing
Evaluate script execution
No script-src or default-src directive constrains script execution.
CSP script execution policy is unsafe
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri, form-action.
CSP hardening directives are missing or weak
Review CSP reporting
CSP does not define a reporting endpoint.
CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=["frame-src"]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives formCount=1WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.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.
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
0 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are invalid: dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2025-01-28T09:17:51+11:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2024-11-23T05:30:00+11:00)..
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
100/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Sitemap lastmod corroboration is missing
Check date validity and consistency
dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2025-01-28T09:17:51+11:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2024-11-23T05:30:00+11:00).
Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=3WARNCheck matching sitemap lastmod actual="invalid match" expected="valid match when available" sitemapUrl="https://www.orionvm.com/wp-sitemap-posts-page-1.xml" robotsStatusCode=404WARNNo matching sitemap lastmod found after sitemap attempts attempts=3Check date validity and consistency [fail]! dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-13T06:08:46+10:00).; dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-12T16:30:13+10:00).; dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-04-29T07:42:28+10:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2025-01-28T09:17:51+11:00).; dateModified (2024-10-02 15:32:14) is earlier than datePublished (2024-11-23T05:30:00+11:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=13 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-13T06:08:46+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-13T06:08:46+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-13T06:08:46+10:00)."},{"severity":"fail","message":"dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-13T06:08:46+10:00)."},{"severity":"fail","message":"dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-12T16:30:13+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-12T16:30:13+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-12T16:30:13+10:00)."},{"severity":"fail","message":"dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-12T16:30:13+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-04-29T07:42:28+10:00)."},{"severity":"fail","message":"dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-04-29T07:42:28+10:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-13T06:08:46+10:00).","dateModified (2025-01-29 20:50:47) is earlier than datePublished (2026-05-13T06:08:46+10:00).","dateModified (2025-01-29 07:13:39) is earlier than datePublished (2026-05-13T06:08:46+10:00).","dateModified (2024-10-02 15:32:14) is earlier than datePublished (2026-05-13T06:08:46+10:00).","dateModified (2026-05-12 03:29:54) is earlier than datePublished (2026-05-12T16:30:13+10:00)."]
Sign in to see 45 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