Travel & Hospitality · Rank #86 of 100

Marriott

Agent Readiness

17/100

Agent-Invisible

WAF blocks AI agents

Example agent task tested

Can an AI agent find a family hotel for 4, compare amenities, understand cancellation policy, and initiate booking?

Dimension Breakdown

Six-dimension scorecard

AI Discoverability36

Answer Engine Readiness35

Agent Usability0

Trust & Verification3

Content Worthiness20

Machine Readiness10

Key Strengths

robots.txt present
GET https://www.marriott.com/robots.txt → HTTP 200, 60 directive lines
XML sitemap discovered
https://www.marriott.com/sitemap-index.xml → 138 URL(s) listed via 50 nested sitemaps
Lists & tables for structured chunks
Per-page weighted score 13.0 (target ≥4) across 1 page(s): /luxury/about-us (ul=13, ol=0, table=0).

Key Gaps

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.
Trust and proof signals
No trust-building signals detected
→ Add an About page, visible testimonials or customer logos, and standard policy pages (Privacy, Terms).

Suggested Improvements

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.
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.
Trust and proof signals — Add an About page, visible testimonials or customer logos, and standard policy pages (Privacy, Terms).

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

Last scanned 6/5/2026, 4:46:27 PM · Scan duration 3.5s · Detected site type: content_publisher