Back to the Index
Travel & Hospitality · Rank #91 of 100

American Airlines

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

Can an AI agent locate frequent-flyer benefits and check status thresholds?

Dimension Breakdown

Six-dimension scorecard

AI Discoverability22
Answer Engine Readiness13
Agent Usability0
Trust & Verification1
Content Worthiness20
Machine Readiness13
Key Strengths

What's working

  • robots.txt present
    GET https://www.aa.com/robots.txt → HTTP 200, 20 directive lines
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.
  • 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.
  • Answer-first formatting
    No pages available to analyze.
    → Make the homepage reachable to crawlers.
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. Primary content structure — Render important content server-side or provide a static HTML representation.
  3. Business clarity on homepage — Ensure the homepage renders core messaging server-side.
  4. 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.
  5. Answer-first formatting — Make the homepage reachable to crawlers.

Get a fresh Agent Readiness audit for your own site

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

Last scanned 6/5/2026, 4:50:35 PM · Scan duration 1.9s · Detected site type: campaign_microsite

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