CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 7, 2026, 3:41 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
72/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability55%Agent Easeof Use57%Security& Trust90%GEO, AIO, AEO60%SEO100%Performance95%Accessibility100%
  • AI Discoverability 55 out of 100
  • Agent Ease of Use 57 out of 100
  • Security & Trust 90 out of 100
  • GEO, AIO and AEO 60 out of 100
  • SEO 100 out of 100
  • Performance 95 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

vidIQ: Get More Subscribers & Views on YouTube | YouTube Tools favicon

vidIQ: Get More Subscribers & Views on YouTube | YouTube Tools

Unlock faster YouTube growth with vidIQ. AI keyword research, video SEO, thumbnails, and daily content ideas trusted by millions of creators. Free to start.

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
55
Needs work2830View details
Discoverability
47
Priority fix620View details
Content Readiness
68
Needs work1900
Bot Access Control
50
Needs work310View details
Agent Ease of Use
57
Needs work400
MCP
43
Priority fix100
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
60
Needs work700
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable100
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
90
Strong2311View details
Security & Trust
90
Strong2311View details
Performance
95
Strong1600
Performance
95
Strong1600

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

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

Details

02

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

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

    Link header lacks useful discovery relations
  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

    Link header targets are unreachable or media types mismatch
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 DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

02

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

  1. 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=0

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate script execution".

32 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

script-src allows dangerous script schemes: blob:.

Details

02

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

68/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 script execution".

Validation steps

  1. Evaluate script execution

    script-src allows dangerous script schemes: blob:.

    CSP script execution policy is unsafe
  2. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri.

    CSP hardening directives are missing or weak
Evidence log2 steps · 8 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","blob:","https://recaptcha.net","https://google.com","https://js-na2.hsforms.net","https://static.hsappstatic.net","https://cdn-cookieyes.com","https://global.localizecdn.com/","https://www.redditstatic.com","https://*.intercomcdn.com","https://*.vidiq.com","https://polyfill.io","https://*.googleapis.com","https://*.paddle.com","https://*.cloudflare.com","https://*.sentry-cdn.com","https://*.profitwell.com","https://js.stripe.com","https://*.framer.com","https://framerusercontent.com","https://*.churnbuster.io","https://vidiq-generate-minitools-db6d800hy-vidiq.vercel.app","https://www.youtube.com","https://www.youtube-nocookie.com","https://*.intercom.io","https://*.iframe.ly","https://infird.com","https://www.google-analytics.com","https://www.gstatic.com","https://cdn.debugbear.com","https://www.googleadservices.com","https://*.omappapi.com","https://*.cookieyes.com","https://*.google.com","https://www.googletagmanager.com","https://*.amplitude.com","https://js.go2sdk.com","https://static.ads-twitter.com","https://bat.bing.com","https://*.facebook.net","https://analytics.tiktok.com","https://snap.licdn.com","https://platform.twitter.com","https://*.g.doubleclick.net","https://assets.apollo.io","https://va.vercel-scripts.com","https://*.vercel-scripts.com","https://bzrcdn.openai.com","https://*.clarity.ms","https://stapecdn.com"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":["blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows dangerous script schemes: blob:."FAILscript-src allows dangerous script schemes: blob:.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","https://*.paddle.com"] frameAncestors=["'self'","https://dna8twue3dlxq.cloudfront.net","https://vidiq-marketing-cms.now.sh","https://vidiq-marketing-cms.vercel.app","https://vidiq-marketing-cms-git-staging-vidiq.vercel.app","https://vidiq-marketing-cms-git-dev-vidiq.vercel.app","https://vidiq-marketing-cms-git-dev.vidiq.now.sh","https://vidiq-marketing-cms-git-staging.vidiq.now.sh","https://vitals.vercel-analytics.com","https://*.sanity.studio","https://*.sanity.io","http://localhost:3333"] 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.

Sign in to see 31 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

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.

Fix with MCP / CLI

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
72/100Level 3, Bot-AwareCurrent report