Back to the Index
B2B, Industrial & Enterprise Services · Rank #85 of 100

Oracle

https://www.oracle.com
Agent Readiness
19/100
Agent-Invisible
WAF blocks AI agents
Example agent task tested

Can an AI agent locate database product editions and pricing?

Dimension Breakdown

Six-dimension scorecard

AI Discoverability43
Answer Engine Readiness35
Agent Usability0
Trust & Verification9
Content Worthiness20
Machine Readiness6
Key Strengths

What's working

  • robots.txt present
    GET https://www.oracle.com/robots.txt → HTTP 200, 42 directive lines
  • XML sitemap discovered
    https://www.oracle.com/sitemap.xml → 500 URL(s) listed via 13 nested sitemaps
  • AI-bot directives
    Named: ['Applebot-Extended', 'ChatGPT-User', 'Claude-Web', 'ClaudeBot', 'GPTBot', 'Google-Extended', 'OAI-SearchBot', 'PerplexityBot', 'anthropic-ai']; disallowed: []
  • Lists & tables for structured chunks
    Per-page weighted score 19.8 (target ≥4) across 3 page(s): /cx/insights/ (ul=10, ol=0, table=0) · /applications/jd-edwards-enterpriseone/solution-logistics/ (ul=16, ol=1, table=0) · /ai-data-platform/price-optimization/ (ul=23, ol=6, table=0).
Key Gaps

Biggest opportunities

  • AI agents blocked at the WAF
    Homepage GET returned HTTP 403 from every fetch path we tried — plain HTTP request, browser-style user agent, AND a real headless Chromium browser. The block is at the WAF / TLS layer, not user-agent-based filtering.
    → Allowlist known AI-agent user agents (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bytespider) and their published IP ranges in your WAF (Akamai/Cloudflare). Ease bot-protection rules for /.well-known/* and /robots.txt at minimum. Publish /llms.txt and /.well-known/agent-skills/index.json so agents can find a machine-readable map of your site.
  • Structured data / Schema.org coverage
    Homepage (1 sampled): missing Product pages (1 sampled): missing Blog index / posts (1 sampled): missing Service pages (1 sampled): missing
    → Quick wins (highest impact ÷ effort): • Add Organization or Website on / (Homepage) — impact +10, ease 1/5. • Add Service or Professionalservice on /cx/* (Service pages) — impact +8, ease 2/5. • Add Blog or Article or Blogposting or Itemlist on /cx/* (Blog index / posts) — impact +6, ease 2/5. Highest raw impact: • Add Organization or Website on / (Homepage) — impact +10, ease 1/5. • Add Product on /applications/* (Product pages) — impact +10, ease 4/5. • Add Service or Professionalservice on /cx/* (Service pages) — impact +8, ease 2/5.
  • Primary content structure
    Homepage not fetchable
    → Render important content server-side or provide a static HTML representation.
  • Business clarity on homepage
    Could not fetch homepage
    → Ensure the homepage renders core messaging server-side.
  • Structured data — Homepage
    Sampled 1 homepage; expected Organization OR Website, found: no JSON-LD.
    → Add Organization JSON-LD to your homepage with `legalName`, `url`, `logo`, and `sameAs` (Twitter / LinkedIn / GitHub). Target path pattern: /. Also consider: Add WebSite JSON-LD with a `potentialAction` of `SearchAction` so AI systems and search know where to query your site.
Suggested Improvements

Where to focus next

  1. AI agents blocked at the WAF — Allowlist known AI-agent user agents (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bytespider) and their published IP ranges in your WAF (Akamai/Cloudflare). Ease bot-protection rules for /.well-known/* and /robots.txt at minimum. Publish /llms.txt and /.well-known/agent-skills/index.json so agents can find a machine-readable map of your site.
  2. Structured data / Schema.org coverage — Quick wins (highest impact ÷ effort): • Add Organization or Website on / (Homepage) — impact +10, ease 1/5. • Add Service or Professionalservice on /cx/* (Service pages) — impact +8, ease 2/5. • Add Blog or Article or Blogposting or Itemlist on /cx/* (Blog index / posts) — impact +6, ease 2/5. Highest raw impact: • Add Organization or Website on / (Homepage) — impact +10, ease 1/5. • Add Product on /applications/* (Product pages) — impact +10, ease 4/5. • Add Service or Professionalservice on /cx/* (Service pages) — impact +8, ease 2/5.
  3. Primary content structure — Render important content server-side or provide a static HTML representation.
  4. Business clarity on homepage — Ensure the homepage renders core messaging server-side.
  5. Structured data — Homepage — Add Organization JSON-LD to your homepage with `legalName`, `url`, `logo`, and `sameAs` (Twitter / LinkedIn / GitHub). Target path pattern: /. Also consider: Add WebSite JSON-LD with a `potentialAction` of `SearchAction` so AI systems and search know where to query your site.

Get a fresh Agent Readiness audit for your own site

Run a free scan now and see how your website compares to Oracle and the rest of the Index.

Last scanned 6/5/2026, 5:11:24 PM · Scan duration 3.4s · Detected site type: hybrid

Are We Agent Ready?

The Agent Readiness Score for AI-first business. Free website audit covering technical crawlability, AEO, GEO, and agent task readiness — weighted for your actual business type.

Product
  • Free website scan
  • Progress tracking
  • AEO / GEO analysis
  • Future audits (coming soon)
Methodology
  • Three-pillar framework
  • Website-type classification
  • Conditional scoring
  • Representative sampling
© 2026 Are We Agent Ready?v1.0