# Preparación para AI de booking.com

> Medido en la página de inicio. Calificación general: Aceptable.

Puntuación 55/100, nota Aceptable. Medido 2026-09-04T22:10:40.601+00:00, motor ax-audit@4.1.0.

## Comprobaciones

### Contenido — 36/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 202) for "Accept: text/markdown"
  Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
  https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No <link rel="alternate" type="text/markdown"> fallback found on the homepage
  If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
  https://axrush.com/guides/content-negotiation#no-alternate

#### Operabilidad para agentes — 100/100

- **PASS** Method note: this reads markup, not a rendered accessibility tree
  Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.

#### Structured Data — 0/100

- **FAIL** No JSON-LD structured data found
  Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
  https://axrush.com/guides/structured-data#not-found

#### HTML Rendering — 25/100

- **FAIL** No visible text content in static HTML
  Your homepage appears to be a JavaScript-only shell. Add server-side rendering (Next.js SSR/SSG, Astro, Remix, or a static prerender) so AI agents that do not execute JS can read your content.
  https://axrush.com/guides/html-rendering#js-shell
- **WARN** Low text-to-markup ratio (0.0%)
  Recommended minimum: 5%
  A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
  https://axrush.com/guides/html-rendering#low-ratio
- **WARN** No semantic HTML landmarks found
  Replace generic <div> structures with semantic tags: <main>, <article>, <header>, <nav>, <footer>. Agents use these to identify the primary content region.
  https://axrush.com/guides/html-rendering#no-landmarks
- **PASS** Single <h1> heading: "JavaScript is disabled"

#### SEO Basics — 45/100

- **FAIL** <title> is missing or empty
  Add a <title> in <head> describing the page in 20-70 characters. Agents quote it as the document name.
  https://axrush.com/guides/seo-basics#no-title
- **FAIL** <meta name="description"> is missing
  Add <meta name="description" content="..."> in <head> with a 70-160 character summary. Agents use this as the canonical short description.
  https://axrush.com/guides/seo-basics#no-description
- **WARN** No <link rel="canonical"> found
  Add <link rel="canonical" href="https://your-site.com/page"> so agents have an unambiguous URL to cite even when crawled via a redirect or query-string variant.
  https://axrush.com/guides/seo-basics#no-canonical
- **PASS** <html lang="en">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1"

### Acceso — 86/100

#### TLS / HTTPS — 100/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=63072000
- **PASS** HSTS includes subdomains
- **PASS** HSTS preload-eligible

#### Agent Access — 75/100

- **WARN** GPTBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** ClaudeBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** Meta-ExternalAgent receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** Amazonbot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** Bytespider receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** CCBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** OAI-SearchBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** Claude-SearchBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** PerplexityBot receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** ChatGPT-User receives a AWS WAF challenge instead of the page
  x-amzn-waf-action: challenge; status 202
  Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#challenge-page
- **WARN** 10 crawler probe(s) could not be settled from outside
  GPTBot, ClaudeBot, Meta-ExternalAgent, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#inconclusive-probe

#### Directivas de IA — 100/100

- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page

#### Higiene HTTP — 100/100

- **WARN** Could not test 404 handling — the probe was challenged
  x-amzn-waf-action: challenge; status 202
  Bot management answered a plain GET with an interstitial, so status-code honesty could not be verified from outside.
  https://axrush.com/guides/http-hygiene#probe-challenged
- **PASS** Homepage answers without a redirect
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 40/100

- **WARN** Response is not compressed
  No Content-Encoding header
  Enable Brotli or gzip for text responses. Compression cuts bytes transferred by ~70–80% and reduces crawl cost for every agent and bot that fetches your pages.
  https://axrush.com/guides/crawl-efficiency#no-compression
- **WARN** No ETag or Last-Modified header — conditional requests unsupported
  Send an ETag or Last-Modified header so crawlers can revalidate with If-None-Match / If-Modified-Since and receive a cheap 304 Not Modified instead of the full body.
  https://axrush.com/guides/crawl-efficiency#no-validators
- **PASS** Homepage size is reasonable (2.0 KB decompressed)
- **WARN** Roughly 0 tokens of content in 502 tokens of response (100% markup)
  Estimated at four characters per token.
  An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
  https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 9ms

### Descubrimiento — 55/100

#### LLMs.txt — 60/100

- **PASS** /llms.txt exists
- **WARN** /llms.txt Content-Type is "text/html"
  Expected one of: text/plain, text/markdown
  Configure your server to serve /llms.txt as text/plain so AI agents parse it correctly.
  https://axrush.com/guides/llms-txt#wrong-content-type
- **WARN** Missing H1 heading (first line should start with "# ")
  Add an H1 heading as the first line of your llms.txt file, e.g.: # Your Site Name
  https://axrush.com/guides/llms-txt#missing-h1
- **WARN** No blockquote description found ("> ...")
  Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
  https://axrush.com/guides/llms-txt#missing-blockquote
- **WARN** No section headings found (## ...)
  Organize your llms.txt content with ## section headings (e.g., ## About, ## API, ## Documentation).
  https://axrush.com/guides/llms-txt#missing-sections
- **WARN** No Markdown links found
  Add Markdown links to relevant pages: [Page Title](https://example.com/page). This helps AI agents navigate your site.
  https://axrush.com/guides/llms-txt#no-links
- **PASS** /llms-full.txt also available (bonus)
- **WARN** No rel="describedby" link to llms.txt
  llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
  https://axrush.com/guides/llms-txt#no-describedby
- **WARN** No per-page Markdown mirror found
  Tried /index.md and /index.html.md.
  llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
  https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
  Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.

#### Robots.txt — 55/100

- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
  Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
  https://axrush.com/guides/robots-txt#no-core-crawlers
- **WARN** No Sitemap directive found
  Add a Sitemap directive to your robots.txt: Sitemap: https://your-site.com/sitemap.xml
  https://axrush.com/guides/robots-txt#missing-sitemap
- **WARN** No Content-Signal directive found (optional)
  Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
  https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 0/57 known AI crawlers have explicit rules
  Add explicit User-agent entries for more AI crawlers to maximize discoverability.
  https://axrush.com/guides/robots-txt#low-coverage

#### Meta Tags — 36/100

- **WARN** No AI meta tags (ai:*) found
  Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
  https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** No rel="alternate" link to llms.txt in HTML
  Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
  https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** No rel="alternate" link to the Agent Card in HTML
  Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
  https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** No rel="me" identity links found
  Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
  https://axrush.com/guides/meta-tags#no-rel-me
- **WARN** No OpenGraph meta tags found
  Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.
  https://axrush.com/guides/meta-tags#no-opengraph
- **WARN** No Twitter Card meta tags found
  Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.
  https://axrush.com/guides/meta-tags#no-twitter

#### Sitemap — 20/100

- **PASS** Sitemap located: https://booking.com/sitemap.xml
- **FAIL** Sitemap response does not look like XML
  <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta nam
  Serve the sitemap with valid XML and Content-Type: application/xml. Confirm the file starts with <?xml ...?> and contains <urlset> or <sitemapindex>.
  https://axrush.com/guides/sitemap#not-xml

#### HTTP Headers — 70/100

- **FAIL** Missing critical header: X-Content-Type-Options
  Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.
  https://axrush.com/guides/http-headers#missing-critical-header
- **WARN** Only 1/7 security headers present
  Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.
  https://axrush.com/guides/http-headers#low-security-headers
- **WARN** No Link header for AI discovery (llms.txt, Agent Card)
  Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
  https://axrush.com/guides/http-headers#no-link-header
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
  describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
  Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
  https://axrush.com/guides/http-headers#discovery-relations

### Protocolos — 0/100

#### Agent Card (A2A) — N/D

- **PASS** No agent-facing surface — an Agent Card does not apply to this site
  No API, MCP server or existing card was found. An Agent Card advertises capabilities another agent can invoke; a site that offers none has nothing to put in it. Run with --profile agent to audit as though it did.

#### OpenAPI Spec — N/D

- **PASS** No API surface — API discovery does not apply to this site
  No description, catalog, service-desc relation or developer area was found. Run with --profile api to audit as though the site offered one.

#### MCP (Model Context Protocol) — N/D

- **PASS** No MCP server — MCP discovery does not apply to this site
  A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.

#### Catálogo de IA — 0/100 (informa, no puntúa)

- **WARN** No agent resource catalog found
  Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
  A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
  https://axrush.com/guides/ai-catalog#not-found

#### Habilidades de agente — N/D

- **PASS** No developer-facing surface — skills do not apply to this site
  No documentation links, llms.txt, or API description found. Skills describe procedures an agent follows; a site with no procedures to teach has nothing to publish.

#### WebMCP — N/D

- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool

#### Descubrimiento de comercio — N/D

- **PASS** No commerce surface — agentic-commerce discovery does not apply to this site
  No Product or Offer structured data, cart links, or product price tags found.

#### Descubrimiento de autenticación — N/D

- **PASS** Nothing on this site requires authorization — auth discovery does not apply
  No API description, API catalog, MCP server card or commerce profile found.

### Política — 44/100

#### Security.txt — 80/100

- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **PASS** Required field "Expires" present
- **FAIL** Expires date is in the past — security.txt is expired
  Update the Expires field to a future date. RFC 9116 requires security.txt to have a valid, non-expired date.
  https://axrush.com/guides/security-txt#expired
- **PASS** 1/5 optional fields present

#### RSL License — 0/100

- **FAIL** No RSL license discovery found
  Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
  Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
  https://axrush.com/guides/rsl#not-found

#### Política de uso — 40/100

- **WARN** No machine-readable usage policy declared
  Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
  State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
  https://axrush.com/guides/usage-policy#no-policy

---

Representación en Markdown de https://axrush.com/report/booking.com
