CanAgentUse

https://www.idc.com/
Rescan Report
Share Report
Copy Report Link
New Scan
https://www.idc.com/
Rescan Report
Share Report
Copy Report Link
Export Report
56/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability62%Agent Easeof Use50%Security& Trust61%GEO, AIO, AEO61%SEO100%Performance70%Accessibility0%
  • AI Discoverability 62 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 61 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 100 out of 100
  • Performance 70 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

IDC | Trusted Tech Intelligence favicon

IDC | Trusted Tech Intelligence

Navigate the changing tech landscape with IDC’s trusted intelligence and insights from 11 billion data points.

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.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
62
Needs work3410View details
Discoverability
67
Needs work800
Content Readiness
77
Mostly ready2500
Bot Access Control
45
Priority fix110View details
GEO, AIO and AEO
61
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
61
Needs work1620View details
Security & Trust
61
Needs work1620View details
Performance
70
Needs work1400
Performance
70
Needs work1400
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

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

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

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.

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 fetch baseline".

40 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src is present but not meaningfully restrictive.

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

60/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

  1. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

  2. Evaluate script execution

    script-src allows dangerous script schemes: blob:.

Evidence log2 steps · 8 lines
Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["'self'","https:"] explicitFetchDirectives=["child-src","connect-src","font-src","frame-src","img-src","media-src","object-src","script-src","style-src","worker-src"]FAILCompare fetch baseline actual=["'self'","https:"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","blob:","*.idc.com","*.wp.com","assets.vidyard.com","*.bing.com","cdn.icomoon.io","cdn.parsely.com","parser.ly","*.trustarc.com","googleads.g.doubleclick.net","js.driftt.com","js.zi-scripts.com","kit.fontawesome.com","pagead2.googlesyndication.com","*.hotjar.com","*.zoominfo.com","*.bugherd.com","snap.licdn.com","*.linkedin.com","www.google.com","www.googletagmanager.com","www.gstatic.com","yoast.com","www.google-analytics.com","stats.g.doubleclick.net","connect.facebook.net","munchkin.marketo.net","cdn.6sense.com","js.intercomcdn.com","maze.co","*.pendo.io","cdn.jsdelivr.net","cvent.com","insight.adsrvr.org","youtube.com","youtube-nocookie.com","*.maze.co","*.clarity.ms","j.6sc.co","*.maze.design"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":true,"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:.

AccessibilityAccessibilityBrowser audit

Certain ARIA roles must contain particular children

100 Fail

Check name

Certain ARIA roles must contain particular children

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Certain ARIA roles must contain particular children

Evidence
{
  "ruleId": "aria-required-children",
  "impact": "critical",
  "description": "Ensure elements with an ARIA role that require child roles contain them",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 2,
  "nodes": [
    {
      "target": [
        ".header-nav-list"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 72
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: [role=menubar], button[aria-controls]"
    },
    {
      "target": [
        ".dropdown-menu-wrapper"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 129
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: button[aria-controls]"
    }
  ]
}

Sign in to see 43 other issues and the full report

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

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

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

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
56/100Level 3, Bot-AwareCurrent report