Travel & Hospitality · Rank #89 of 100

Expedia

https://www.expedia.com

Agent Readiness

13/100

Agent-Invisible

WAF blocks AI agents

Example agent task tested

Can an AI agent bundle flight + hotel and identify the best deal?

Dimension Breakdown

Six-dimension scorecard

AI Discoverability29

Answer Engine Readiness13

Agent Usability0

Trust & Verification1

Content Worthiness20

Machine Readiness13

Key Strengths

What's working

robots.txt present
GET https://www.expedia.com/robots.txt → HTTP 200, 78 directive lines
AI-bot directives
Named: ['ChatGPT-User', 'OAI-SearchBot', 'PerplexityBot']; disallowed: []

Key Gaps

Biggest opportunities

AI agents blocked at the WAF
Homepage GET returned HTTP 429 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.
XML sitemap discovered
No sitemap.xml or Sitemap: directive in robots.txt
→ Publish an XML sitemap at /sitemap.xml and declare it in robots.txt via 'Sitemap: https://yourdomain/sitemap.xml'.
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

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.
XML sitemap discovered — Publish an XML sitemap at /sitemap.xml and declare it in robots.txt via 'Sitemap: https://yourdomain/sitemap.xml'.
Primary content structure — Render important content server-side or provide a static HTML representation.
Business clarity on homepage — Ensure the homepage renders core messaging server-side.
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 Expedia and the rest of the Index.

Scan your website View the full Index

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