Research · June 2026

Ask ChatGPT to book a room, not pick one, and it switches to the OTAs

We ran 719 ChatGPT hotel searches across Paris, London and New York, varying one thing: how transactional the question was. A date barely moves where it looks. A booking verb moves everything.

1.7% → 87%
OTA citations: browse vs book
73%
panel prices from an unnamed feed
719
live captures

ChatGPT will quote you a hotel’s nightly rate. The interesting question is where it goes to get one — and whether that changes when you tell it your dates or your budget. We held the cities fixed (Paris, London, New York) and varied the shape of the question: plain “best hotels” asks, the same asks with check-in dates a month and three months out, “a hotel tonight”, a budget cap, an explicit “what’s the best rate”, and “which hotels have rooms available”. Eight conditions, two phrasings each, fifteen repeats — 719 live searches with web search on.

The trigger isn’t the date — it’s the booking intent. Asking for “the best hotels in Paris” grounds the answer on editorial sources (Reddit, Time Out, Oyster), and adding a date barely changes that — OTA citations stay around 2–5%. But ask which hotels have rooms available, or for the best rate, or for a room tonight, and ChatGPT swings to the booking sites: Expedia, Booking, Kayak. OTA citation share jumps from 1.7% to as high as 87%.

A date is a detail; “available” is a switch

Share of all citations that come from an OTA or metasearch site (Expedia, Booking, Kayak, Hotels.com, Skyscanner, HotelTonight…), by how the question was phrased. The top four are discovery questions; the bottom four carry booking intent.

“Best hotels in …”
1.7%
…for September 18–20
2.3%
…for July 10–12
5%
…under €250 a night
10.2%
“…a hotel tonight”
44%
“…the best rate for…”
47.5%
budget + dates
48.4%
“…rooms available on…”
86.9%

The jump is roughly fiftyfold from the calmest discovery prompt to the most transactional one. And the OTA that benefits most is specific: across the four booking-intent conditions, the Expedia family (expedia.com plus its country domains) takes ~23% of all citations, more than four times Booking’s ~5%. The one exception is “a hotel tonight”, where the single most-cited domain is hoteltonight.com — ChatGPT reaching for the brand whose name matches the query.

For a hotel, the lesson is about which query you’re trying to win. Discovery questions are decided on Reddit threads and Time Out lists — earned, editorial ground. The moment the traveller signals they’re ready to book, the answer is sourced from the OTAs, where your rate and availability are whatever your channel manager is pushing.

The price it shows you has no name on it

Alongside the written answer, ChatGPT often renders a map panel of hotels with a nightly price on each card — Ritz Paris, “$5,193”. We logged the source field on every priced card across all 719 searches. Nearly three quarters carry an internal feed code, b1, with no link and no named provider. Only 3.2% of priced cards exposed a provider URL at all.

b1 (unlabelled feed)
73%
Yelp
19.3%
Tripadvisor
5.5%
other / none
2.2%

Provider field on priced map-panel cards, n = 5,099 cards. Tripadvisor — the one feed many assume sits behind these prices — labels just 5.5% of them.

So the headline panel rate is the least transparent number on the screen: shown confidently, attributed to nothing the user can click. The cited, checkable prices live in the written answer, and those trace back to the OTAs from the section above. The panel and the prose are two different pricing systems sitting in one reply.

It does carry your dates into the search

Behind each answer, ChatGPT fires off its own background web searches (the “fan-out”). When the prompt has booking intent, those searches almost always carry the actual dates — it isn’t decorating the reply with a date it ignored. Share of fan-out queries that contained the check-in dates or “tonight”:

“…rooms available on…”
100%
“…a hotel tonight”
100%
“…the best rate for…”
99%
budget + dates
79%
…for September 18–20
53%
…for July 10–12
43%
“Best hotels” (no date)
0%

A plain “best hotels” prompt never injects a date (there isn’t one). Note the gradient: an explicit “available on these dates” lands the date 100% of the time, while a date merely attached to a discovery question makes it into the search under half the time.

That gap matters for accuracy. When the date reliably reaches the search (the transactional asks), the rate you see has a real chance of being live and date-correct. When it doesn’t (a date tacked onto “best hotels”), the price is closer to a generic nightly figure dressed up with your dates.

The budget word reshuffles the whole shortlist

Telling ChatGPT a budget doesn’t just filter — it changes which hotels it even considers. The median panel price collapses from the luxury default to genuine value stock the moment “under €250” appears, in every city:

Paris
open
$2,251
under €250
$194
New York
open
$1,342
under €250
$158
London
open
$723
under €250
$147

Median nightly price across all map-panel cards, per city, open vs budget-capped prompts.

One thing it does not do is move a given hotel’s price around. For the 83 hotels that appeared in both open and dated prompts, the median price ratio was exactly 1.0 — the same property gets the same number whether or not you named a date. And across repeat runs of an identical prompt, a hotel’s price held within ~8% most of the time (though ~1 in 5 swung more than 25%). The number is fairly stable; the shortlist it sits in is what your wording controls.

The ARI read. ChatGPT’s sense of “your rate” is whatever the OTAs publish, and it surfaces only when the traveller asks a booking question. A hotel has no direct lever on the panel price (unnamed feed) and only an indirect one on the prose price (its OTA rates). The visible, winnable surface is still the discovery layer — the editorial sources that decide the pre-booking shortlist.

Method & limits

719 live ChatGPT searches (web search on), captured via Bright Data, June 2026, across Paris, London and New York. Eight prompt conditions — open, near date (~1 month), far date (~3 months), “tonight”, budget cap, budget + date, explicit price, and availability — each written two ways and repeated 15 times per city. We English-only the prompts deliberately: a prior study showed query language doesn’t move ChatGPT’s sources. Every capture logs the citations, the fan-out search queries, and the structured map/hotel panel including each card’s price and provider field.

Limits. “OTA citation” counts the domain of cited sources, so it captures which sites ChatGPT consulted; ChatGPT itself books nothing. Theb1 provider code is opaque by design — we can show it’s unattributed but cannot identify the feed behind it. Three cities, one model snapshot, one currency view per market; ChatGPT is non-deterministic, which is why every condition is repeated 30× (2 phrasings × 15) per city. Results describe ChatGPT’s web-search behaviour, not other engines.

FAQ

Barely, on its own. A date attached to a “best hotels” question keeps OTA citations around 2–5% — the answer still leans on editorial sources like Reddit and Time Out. What flips the sources is booking intent: asking which hotels have rooms available, or for the best rate, or for a room tonight, pushes OTA citation share up to 44–87%.

Summarize with AI

ChatGPTPerplexityClaudeGeminiGrok

Same question, every language

We also asked whether the language you use changes ChatGPT’s hotel picks. The hotels shuffle; the sources stay English.

Read: Does language change ChatGPT’s picks?