{"@context":"https://schema.org","@type":"BlogPosting","headline":"Anatomy of ChatGPT Hotel Search 2026: How AI Finds Hotels Under the Hood","description":"Technical teardown of ChatGPT hotel recommendations: 12 systems, 5 data providers, entity linking, RRF fusion.","datePublished":"2026-02-08","dateModified":"2026-04-13","url":"https://nicolassitter.com/research/anatomy-chatgpt-hotel-search-2026","category":"research","keywords":["ChatGPT hotel search","ChatGPT architecture","hotel AI systems","OpenAI hotel data"],"articleSection":"Research","wordCount":4300,"readTime":"17 min","articleBody":"February 2026Technical Teardown\n\n# Inside ChatGPT's Hotel Search Engine\n\nA technical teardown of what happens when someone asks ChatGPT for a hotel recommendation — from query classification to entity fusion.\n\n**TL;DR:** ChatGPT's hotel search runs through 12 interconnected systems. **Google powers ~94% of the data** via SerpAPI and Places API. Hotels get linked to Google Place IDs through entity recognition (89% success rate). Results are ranked using RRF fusion, rewarding hotels that appear across multiple sources. **The Google vs SerpAPI lawsuit could break it all.**\n\nNS\n\nNicolas Sitter\n\nAI Search Researcher · Published February 8, 2026\n\n[Read Methodology](#methodology)[What This Means for Hotels](#implications)\n\n## Executive Summary\n\n### Google Powers Everything\n\n~94% of ChatGPT hotel data flows through Google — via SerpAPI for web results and Google Places for entity data.\n\n### Entity Recognition is Key\n\n89% of hotel mentions get linked to Google Place IDs. The 11% that don't may appear as duplicates or lose visibility entirely.\n\n### Multi-Source Wins\n\nRRF fusion rewards hotels that rank well across multiple sources. Being present on TripAdvisor, Booking, AND editorial lists compounds your score.\n\n1\n\n## Search Decision: The Sonic Classifier\n\nBefore ChatGPT's main language model even sees your hotel query, a fast classifier called \"Sonic\" decides whether to trigger web search. It assigns a probability score — if above ~65%, web search activates. We first explored this mechanism in our [November 2025 analysis](/blog/anatomy-of-a-hotel-chatgpt-web-search).\n\nsearch-trigger-rates\n\n#### Search Trigger Rate by Hotel Query Type\n\nSearch Trigger Rate by Hotel Query Type\n\nQuery Type\n\nExample\n\nTrigger Rate\n\nLocation-specific\n\n\"Best hotels in Paris\"\n\n98%\n\nPrice queries\n\n\"Cheap hotels near me\"\n\n91%\n\nAmenity queries\n\n\"Hotels with pool in Miami\"\n\n87%\n\nComparison\n\n\"Hilton vs Marriott Paris\"\n\n72%\n\nDefinitional\n\n\"What is a boutique hotel\"\n\n8%\n\nHotel queries almost always trigger web search because they're location-specific and time-sensitive. Questions asking for recommendations (\"best hotels in...\") trigger 98% of the time. Price queries are high too (91%) — likely because they require real-time ARI (Availability Rate Inventory) data that the model can't answer from training data alone. Pure definitions (\"what is a hotel\") rely on training data alone.\n\n2\n\n## Query Classification: Prompt Taxonomy\n\nOnce web search is triggered, ChatGPT classifies the query with boolean flags: Local (location-based), Image (needs visuals), Recency (time-sensitive). It also assigns a \"thinking mode\" — System 1 for quick answers, System 2 for research-heavy queries.\n\nQuery Classification Examples\n\nQuery\n\nLocal\n\nImage\n\nRecency\n\nMode\n\nBest hotels in Paris for couples\n\nSystem 2\n\nCheap hotels near Times Square\n\nSystem 2\n\nFour Seasons Paris reviews\n\nSystem 2\n\nWhat is a boutique hotel?\n\nSystem 1\n\nHotel check-in time\n\nSystem 1\n\nMost hotel queries activate all three flags simultaneously: they're local (city-specific), image-heavy (travelers want to see rooms), and time-sensitive (prices and availability change). This triggers the most comprehensive search mode.\n\n3\n\n## Fan-Out Engine: Parallel Query Expansion\n\nChatGPT doesn't run one search — it fans out your query into 3-5 parallel sub-queries. Each sub-query averages 8-10 words and is a rephrasing of the original prompt designed to trigger web search. In practice, this means massively scraping Google Search results via SerpAPI — each fan-out fires a separate Google query and pulls back a full SERP page.\n\n\"Best boutique hotel in Paris\"\n\nSerpAPI (Web)\n\n\"best boutique hotels Paris 2026\"\n\nEditorial lists\n\nSerpAPI (Web)\n\n\"boutique hotel Paris reviews\"\n\nUser reviews\n\nGoogle Places\n\n\"boutique hotel Paris\"\n\nEntity data\n\nBing Images\n\n\"Paris boutique hotel interior\"\n\nVisuals\n\nSerpAPI (Web)\n\n\"top rated small hotels Paris\"\n\nAlternative phrasing\n\nHotel queries average 3-5 parallel searches, each rephrased in 8-10 words to capture editorial lists, user reviews, entity data, and alternative phrasings — then merges everything.\n\n#### Update — March 6, 2026\n\nSince the release of GPT-5.4 (API) and GPT-5.3 (UI), fan-outs seem to have disappeared from the UI — sometimes replaced by a single search, sometimes nothing visible at all. It's moving. This could be temporary and fan-outs may return. Fan-outs are still observed in the API. See [Section 10](#march-2026-update) for full details.\n\n**The bigger signal:** OpenAI is actively building its own search index. Their [web search API docs](https://developers.openai.com/api/docs/guides/tools-web-search) now expose an `external_web_access` parameter — set it to `false` and the model searches only cached/indexed results. This confirms OpenAI maintains its own index alongside live Google scraping. The disappearance of fan-outs in the UI may signal a shift from scraping Google in real-time to querying their own index first.\n\n4\n\n## Data Providers: Who Supplies What\n\nChatGPT pulls hotel data from 5 providers. Google dominates: SerpAPI provides web search results, Google Places provides entity data. Yelp was integrated in January 2026 for US cities and Berlin — see our [Yelp in ChatGPT study](/research/yelp-chatgpt-hotels-study-2026) for the full analysis.\n\nprovider-usage\n\n#### Data Provider Usage Rate for Hotel Queries\n\nData Provider Details\n\nProvider\n\nPurpose\n\nUnderlying Source\n\nUsage %\n\nSerpAPI (Google Web)\n\nWeb search results, snippets\n\nGoogle Search\n\n94%\n\nGoogle Places API\n\nEntity data, ratings, reviews\n\nGoogle Maps\n\n89%\n\nBing Image Search\n\nSecondary image source\n\nBing\n\n67%\n\nYelp\n\nReviews, ratings, business data (US cities + Berlin)\n\nYelp Fusion API\n\n33%\n\nOpenStreetMap\n\nMap tiles, location data\n\nOSM\n\n100%\n\nGoogle powers ~94% of ChatGPT's hotel data through intermediaries. If Google restricts access to SerpAPI or Places API, ChatGPT's hotel recommendations would fundamentally degrade.\n\n**Yelp is US-mostly and restaurant-heavy.** Since January 2026, Yelp data appears in ~33% of hotel queries — but almost exclusively for US cities (Las Vegas, LA, San Francisco) plus Berlin. Hotels with on-site restaurants benefit the most, as Yelp's restaurant data enriches the hotel's overall entity profile. See our [full Yelp study](/research/yelp-chatgpt-hotels-study-2026).\n\n5\n\n## Hotel Images: Dual Pipeline\n\nChatGPT uses two image pipelines: \"Entity images\" come from Google Business Profile (higher quality, pre-verified), while \"Web images\" come from Bing search (lower quality, more variety).\n\nimage-quality\n\n#### Image Quality Score by Source\n\nImage Sources by Type and Quality\n\nSource\n\nType\n\nQuality Score\n\nUsage %\n\nGoogle Business Profile\n\nEntity\n\n8.7/10\n\n71%\n\nBing Image Search\n\nWeb\n\n6.4/10\n\n67%\n\nHotel Website\n\nWeb\n\n7.1/10\n\n34%\n\n**Watch out for wrong images.** It's not uncommon for ChatGPT to display images that aren't actually your hotel — a competitor's lobby, a stock photo, or a completely unrelated building. This happens because the Bing Image Search pipeline matches on query keywords, not on verified entity data. If your hotel has a generic name, the risk is even higher. Your best defense: a well-optimized Google Business Profile with plenty of photos, so the entity pipeline wins over the web pipeline.\n\n6\n\n## Entity Recognition: Linking Hotels to Place IDs\n\nWhen ChatGPT encounters \"The Ritz Paris\" in search results, entity recognition confirms it's the same hotel across all sources by linking to Google Place ID. Hotels without Place IDs become \"orphaned\" — they may appear as duplicates or lose visibility entirely.\n\n**Since GPT-5.2 — and even more so with GPT-5.4 — we've observed that hotels with inconsistent entity data across the web — different names on GBP, their website, their schema markup, and OTAs — get penalized.** If your GBP says \"Hôtel Le Printemps\", your website says \"Hotel Printemps Paris\", and Booking.com lists \"Printemps Hotel\", the entity linker struggles — and your hotel loses visibility.\n\nEntity Recognition Examples\n\nHotel Name\n\nPlace ID\n\nSignals Used\n\nThe Ritz Paris\n\nChIJAVkDPz...\n\nName, Address, Reviews\n\nHotel Negresco Nice\n\nChIJ8SjBnC...\n\nName, Photos, Category\n\nLe Marais Boutique\n\n(not linked)\n\nName only\n\nHotel & Spa Resort\n\n(not linked)\n\nGeneric name\n\n89% of hotels get successfully linked to Google Place IDs. The 11% that fail often have generic names (\"Hotel & Spa\") or inconsistent NAP data across sources. A verified Google Business Profile dramatically increases your link rate. **Your hotel name, address, phone, and category must be identical everywhere:** Google Business Profile, Booking.com, Expedia, TripAdvisor, your website, your Schema.org markup, social media profiles — every digital touchpoint. One inconsistency and the entity linker may split you into two hotels or fail to link entirely.\n\n**The generic name problem is real.** Hotels named \"The Hotel\", \"Hotel Printemps\", or \"Grand Hotel\" face constant entity confusion — AI models can't tell which one you are. We've seen some of these properties actively consider rebranding because of this. It makes sense: in a world where AI needs to match a name to a unique entity, a distinctive name is no longer just marketing — it's infrastructure.\n\n**Entity recognition paves the way to ads.** Once AI models can reliably link a hotel mention to a structured entity (name, ID, location, attributes) rather than just plain text, the door opens to paid placements. This is the shift from \"Hotel A\" as a string in a paragraph to `{name: \"Hotel A\", id: \"ChIJ...\", stars: 5}` as a structured object that can be sponsored, tracked, and measured. Expect hotel ads inside AI recommendations soon.\n\n7\n\n## Result Fusion: Reciprocal Rank Fusion (RRF)\n\nAfter fan-out queries return results from multiple providers, ChatGPT merges them using **Reciprocal Rank Fusion (RRF)**. RRF doesn't care about absolute relevance scores — it only uses rank positions. This makes it ideal for combining results from completely different sources (SerpAPI, Google Places, Yelp) that have no common scoring scale.\n\n#### The RRF Formula\n\nS(d) = Σ wi / (k + ri(d))\n\n**k = 60** — dampening constant. Reduces the impact of rank gaps: being #1 vs #5 matters much more than #50 vs #55.\n\n**ri(d)** — 1-based rank of the page in sub-query i. If absent from a source, rank = ∞ (score contribution = 0).\n\n**wi** — weight per sub-query (≈1, equal weighting assumed). Bing has `rrf_alpha: 1` suggesting forced weighting.\n\n### Retrieval Pool: 38-65 Sources\n\nPer query, ChatGPT retrieves **38 to 65 total sources** depending on query complexity. These form the \"retrieval pool\" — only pages in this pool can ever be cited. **If your hotel isn't fetched, it scores zero.** Rank #60 in a source that isn't queried is effectively invisible.\n\n#### Citation Threshold: τ ≥ 0.020\n\nPages with a fused RRF score of **0.020 or above** almost always land in the final top-60 citation pool. Below that, you're retrieved but not cited.\n\n2 appearances\n\n≤ rank 40 each\n\n3 appearances\n\n≤ rank 90 each\n\n4 appearances\n\n≤ rank 140 each\n\n### Three Citation Tiers\n\nNot all retrieved sources are shown equally. ChatGPT uses three tiers of citation visibility:\n\nTier 1 — Cited\n\nInline citation at sentence end + Sources panel. Maximum visibility. This is what you want.\n\nTier 2 — Other Sources\n\n\"More\" section below citations. Medium visibility. Users rarely click these.\n\nTier 3 — Hidden\n\nInternal grounding links (Wikipedia, Arxiv). Never shown to users. Used for fact-checking only.\n\nRRF Worked Example: 'Best boutique hotel Paris'\n\nHotel\n\nSerpAPI Rank\n\nPlaces Rank\n\nTripAdvisor Rank\n\nRRF Score\n\nFinal Rank\n\nHotel Le Pavillon\n\n#2\n\n#1\n\n#3\n\n0.0492\n\n1\n\nThe Hoxton Paris\n\n#1\n\n#4\n\n#2\n\n0.0476\n\n2\n\nHotel Providence\n\n#3\n\n#2\n\n#5\n\n0.0473\n\n3\n\nMaison Souquet\n\n#5\n\n#3\n\n#1\n\n0.0469\n\n4\n\n**It's better to rank #10 for three specific queries than #60 for everything.** The math is clear: a hotel appearing in 3 fan-out sub-queries at rank 10 each scores 3 × 1/(60+10) = 0.0429 — well above the 0.020 citation threshold. A hotel at rank 60 in a single query scores just 1/(60+60) = 0.0083 — invisible.\n\n**For hotels, multi-source presence is the strategy.** Being listed on TripAdvisor, Booking.com, your own website, AND editorial lists (Condé Nast, Time Out) means you appear across multiple fan-out sub-queries. Each appearance compounds your RRF score. A hotel with a strong GBP, active OTA listings, and editorial coverage is mathematically hard to beat.\n\n8\n\n## Local & Maps: The Hybrid Stack\n\nChatGPT's maps use OpenStreetMap for tiles but Google Places for business data. The Place ID is the crucial link — hotels without one can't appear on ChatGPT's maps.\n\nLocal/Maps Component Stack\n\nComponent\n\nSource\n\nData Included\n\nUpdate Frequency\n\nMap Tiles\n\nOpenStreetMap\n\nStreet layout, POIs\n\nDaily\n\nPlace Markers\n\nGoogle Places\n\nHotel locations, pins\n\nReal-time\n\nRouting\n\nOpenStreetMap\n\nDirections, distances\n\nWeekly\n\nBusiness Info\n\nGoogle Places\n\nHours, contact, photos\n\nDaily\n\n**Yelp adds a local layer — but only in the US.** For hotels in Las Vegas, Los Angeles, San Francisco, and Berlin, Yelp data now feeds into ChatGPT's local results alongside Google Places. Hotels with on-site restaurants benefit the most: Yelp's restaurant reviews and ratings enrich the hotel's local entity profile, giving it more data points in the map/local stack. If your hotel has a restaurant, make sure it has its own Yelp listing linked to the hotel. See our [Yelp in ChatGPT study](/research/yelp-chatgpt-hotels-study-2026).\n\n9\n\n## A/B Testing: Constant Experimentation\n\nChatGPT uses Statsig for A/B testing. At any given moment, a massive number of experiments run in parallel — testing different ranking algorithms, UI layouts, source weightings, and search behaviors. Feature gates, dynamic configs, and layer configs are constantly being toggled. The system is never static.\n\nThis means two users asking the exact same hotel query at the exact same time can get different results. Different ranking logic, different provider weights, different citation thresholds — all potentially different depending on which experiment bucket you're in.\n\n**Don't over-optimize from a single test.** If you search \"best hotels in Paris\" and your hotel doesn't appear, that doesn't mean you're invisible — you might just be in a different A/B test group. Always test from multiple accounts, browsers, and devices before drawing conclusions. What matters is consistent presence across sources (see Section 7), not a single query result.\n\n10\n\n## March 2026 Update: GPT-5.4 & Fan-Out Changes\n\n### Architecture Shift — March 2026\n\nOpenAI released **GPT-5.4 in the API** and **GPT-5.3 in the ChatGPT UI**. The most visible change for hotel search: fan-out queries seem to have disappeared from the UI — sometimes replaced by a single search, sometimes none at all. It's moving. We're watching.\n\n### What Changed\n\n#### UIChatGPT UI (GPT-5.3)\n\n-   **Fan-outs seem to have disappeared** — sometimes we see a single search, sometimes no visible search at all. The 3-5 parallel rephrasings described in Section 3 are no longer consistently observed.\n-   This could be temporary — an A/B test, a cost optimization, or a transition phase. Fan-outs may return.\n-   Results appear faster, but with potentially less source diversity per query.\n\n#### APIAPI (GPT-5.4)\n\n-   Latest model available via API, with improved reasoning and tool use.\n-   API users can still implement their own fan-out patterns via function calling.\n-   The search infrastructure is model-version dependent — API and UI now diverge in behavior.\n\n### Impact on Hotel Search\n\nBefore vs After: Fan-Out Changes\n\nAspect\n\nBefore (GPT-5.1/5.2)\n\nAfter (GPT-5.3/5.4 UI)\n\nSub-queries per request\n\n3-5 parallel fan-outs\n\nUnclear — sometimes 1, sometimes 0\n\nSource diversity\n\nHigh — hits multiple providers simultaneously\n\nUnclear — behavior is inconsistent\n\nSpeed\n\nSlower (waits for all fan-outs)\n\nFaster (fewer round-trips)\n\nRRF fusion input\n\nMultiple ranked lists merged\n\nFewer lists, heavier model weighting\n\nMulti-source advantage\n\nStrong — more sources = higher RRF\n\nUnclear — may still work differently server-side\n\nConsistency\n\nLower (fan-out variance)\n\nAppears higher (fewer moving parts)\n\n**This is an observation, not a conclusion.** We're seeing single-query behavior in the UI right now, but this could be an A/B test, a temporary optimization, or a shift that gets reversed. OpenAI changes search behavior constantly (see Section 9). What we can say: **if fan-outs are truly reduced, Google Business Profile and the hotel's own website become even more critical** — because with fewer queries, the model will prioritize high-authority, entity-rich sources over broad web scraping. But multi-source presence remains the safest long-term strategy regardless.\n\n### Update — April 13, 2026: Sponsored Ads Are Live\n\nSince March 31, 2026, **sponsored ads now appear in 20–35% of hotel queries** for US free-tier users. The ad arrives as a separate `type: \"ads\"` event after the message stream completes — it's not generated by the model, it's appended by the serving infrastructure.\n\n**Booking.com dominates with 43.5% of all ad slots**, followed by Airbnb (21.2%) and Expedia (17.6%). OTAs collectively own 87.7% of ad inventory. Only 3 hotel brands advertise (Preferred Hotels & Resorts, Barcelo, Marriott). The ad creative uses a `target.type: \"url\"` format — currently always an external URL, but the schema supports other types, suggesting `type: \"app\"` (deep-linking to ChatGPT GPTs) may be coming.\n\nRead the full analysis: [ChatGPT Hotel Ads Are Live — Who Pays for Your Recommendations?](/research/chatgpt-hotel-ads-live-2026)\n\n11\n\n## Legal Context: Google vs SerpAPI\n\nIn December 2024, Google filed a lawsuit against SerpAPI alleging DMCA §1201 violations for scraping Google Search results. SerpAPI is ChatGPT's primary data provider. If Google wins, ChatGPT's hotel search fundamentally breaks.\n\n### Google LLC v. SerpAPI Inc. (2024)\n\nFiled December 2024 in California. Google alleges SerpAPI violates DMCA §1201 by circumventing access controls. Also alleges violations of Computer Fraud and Abuse Act (CFAA) and tortious interference.\n\nChatGPT Functions at Risk\n\nFunction\n\nGoogle Source\n\nBackup Option\n\nRisk Level\n\nWeb Search Results\n\nSerpAPI (Google)\n\nBing\n\nCritical\n\nEntity Data\n\nGoogle Places API\n\nNone\n\nCritical\n\nHotel Photos\n\nGBP Images\n\nBing Images\n\nMedium\n\nReviews/Ratings\n\nGoogle Reviews\n\nTripAdvisor API\n\nHigh\n\nMaps Display\n\nOSM (not Google)\n\nN/A\n\nLow\n\nIf SerpAPI is blocked, OpenAI would need to find alternative data sources. Bing could partially substitute for web search, but there's no replacement for Google Places entity data. Hotels visible through Google Places would retain advantage even in a restructured system.\n\n12\n\n## What This Means for Hotels\n\nBased on how ChatGPT's hotel search actually works, here are the 7 actions that matter most:\n\n1\n\n### Claim & Optimize Your GBP\n\nYour Google Business Profile is the source of truth for entity data. Complete all fields, add 50+ photos, keep hours updated. And **check your star rating** — we've seen hotels listed as 3-star on GBP when they're actually 4-star. If Google has it wrong, ChatGPT will too.\n\n2\n\n### Be Present Across Multiple Sources\n\nRRF rewards multi-source presence. Ensure you're on TripAdvisor, Booking.com, AND editorial lists like Condé Nast Traveler.\n\n3\n\n### Reply to Reviews\n\nReview replies are free content. Every response is an opportunity to naturally mention what you want to rank for — \"our rooftop pool\", \"our Michelin-starred restaurant\", \"walking distance from the Eiffel Tower\". AI models read replies. Use them strategically.\n\n4\n\n### Upload High-Quality Images to GBP\n\nGBP photos get priority in ChatGPT's entity pipeline. They're shown in entity panels and maps. Prioritize professional shots — exterior, lobby, room types, amenities.\n\n5\n\n### Encourage Recent Reviews\n\nChatGPT's recency filter prioritizes fresh content. A hotel with 10 reviews from last month outranks one with 100 reviews from last year.\n\n6\n\n### Perfect Your Schema Markup\n\nUse the `Hotel` type (not LocalBusiness) with starRating, amenityFeature, aggregateRating, and geo. This is how ChatGPT classifies your category, price tier, and amenities. [Read our complete Schema.org guide](/learn/schema-markup-hotels).\n\n7\n\n### Monitor the Google vs SerpAPI Case\n\nIf Google wins, ChatGPT's data sources will shift. Hotels with strong direct presence (website SEO, brand recognition) will be more resilient.\n\n## Methodology\n\n### Methods\n\n-   • Browser DevTools network inspection\n-   • JavaScript bundle analysis\n-   • API request/response logging\n-   • Statsig configuration extraction\n\n### Sources\n\n-   • ChatGPT web interface\n-   • OpenAI API documentation\n-   • Court filings (Google v. SerpAPI)\n-   • Nicolas Sitter technical research\n\n### Limitations\n\n-   • Investigative research, not official docs\n-   • Systems change frequently\n-   • A/B tests affect observed behavior\n-   • Hotel-focused interpretation\n\nThis analysis is based on technical investigation of ChatGPT's web search infrastructure. It is not official OpenAI documentation. ChatGPT's systems are constantly evolving; specific details may change. Based on ongoing technical research into ChatGPT web search applied to the hotel vertical.\n\n## Frequently Asked Questions\n\n### Where does ChatGPT get hotel information from?\n\nChatGPT gets hotel information primarily from Google through SerpAPI, which provides web search results, and Google Places API for entity data like ratings, reviews, and photos. Secondary sources include Bing for images and OpenStreetMap for mapping. Approximately 94% of ChatGPT's hotel data flows through Google-owned or Google-sourced systems.\n\n### How does ChatGPT decide when to search the web for hotels?\n\nChatGPT uses a fast classifier called \"Sonic\" that runs before the main language model. This classifier assigns a probability score to each query, and if the score exceeds roughly 65%, web search is triggered. For hotel queries, the trigger rate is very high: location-specific hotel questions trigger search 98% of the time, price queries 91%, while purely definitional questions (\"What is a boutique hotel?\") trigger only 8%.\n\n### What is the fan-out engine in ChatGPT hotel search?\n\nThe fan-out engine takes a single user query like \"Best boutique hotel in Paris\" and expands it into 5-7 parallel sub-queries sent to different data providers. For example: \"best boutique hotels Paris\" to SerpAPI, \"boutique hotel Paris reviews\" to web search, and \"Paris boutique hotel\" to Google Places. This parallel approach gathers diverse information quickly. Hotel queries average 5.3 parallel searches per request.\n\n### How does ChatGPT rank hotels from multiple sources?\n\nChatGPT uses Reciprocal Rank Fusion (RRF) to combine results from multiple sources. Each hotel gets a score based on its rank in each source using the formula 1/(k+rank), where k=60. Hotels appearing in multiple sources get their scores added together. This means a hotel ranked #1 in two sources scores much higher than one ranked #1 in just one source. Multi-source presence is the key to visibility.\n\n### What is entity recognition in ChatGPT hotel search?\n\nEntity recognition links hotel names mentioned in search results to their canonical Google Place ID. When ChatGPT encounters \"The Ritz Paris\" in multiple sources, entity recognition confirms they all refer to the same hotel (Place ID: ChIJ...) and merges their information. About 89% of hotels get successfully linked to Place IDs. The 11% that fail may appear as duplicates or lose visibility entirely.\n\n### Could the Google vs SerpAPI lawsuit break ChatGPT hotel search?\n\nYes, it could fundamentally break it. In December 2024, Google filed a lawsuit against SerpAPI alleging DMCA violations for scraping search results. SerpAPI provides ~94% of ChatGPT's hotel search data. If Google wins, OpenAI would need to find alternative data sources, potentially degrading hotel recommendation quality significantly. The case is ongoing and represents an existential risk to current ChatGPT hotel search capabilities.\n\n## Continue Reading\n\nExplore more Nicolas Sitter research on AI hotel search.\n\n[AI Hotel Landscape 2026](/research/ai-hotel-landscape-2026)\n\n[Google AI Mode Study](/research/google-ai-mode-hotel-study-2026)[Yelp in ChatGPT](/research/yelp-chatgpt-hotels-study-2026)[Ranking Consistency Study](/research/ai-hotel-rankings-consistency-study-2026)[All Research](/research)","author":{"@type":"Person","name":"Nicolas Sitter","url":"https://nicolassitter.com/about","sameAs":["https://www.linkedin.com/in/nicolassitternolleau/","https://github.com/Nicositter88","https://hotelrank.ai"]},"publisher":{"@type":"Person","name":"Nicolas Sitter","url":"https://nicolassitter.com"},"image":"https://nicolassitter.com/api/og/anatomy-chatgpt-hotel-search-2026","mainEntityOfPage":{"@type":"WebPage","@id":"https://nicolassitter.com/research/anatomy-chatgpt-hotel-search-2026"},"tags":["ChatGPT","Technical Teardown","Hotel Search","OpenAI"],"sameAs":["https://hotelrank.ai/research/anatomy-chatgpt-hotel-search-2026"],"alternateFormat":{"html":"https://nicolassitter.com/research/anatomy-chatgpt-hotel-search-2026","json":"https://nicolassitter.com/api/post/anatomy-chatgpt-hotel-search-2026","rss":"https://nicolassitter.com/rss.xml"},"datasets":[{"name":"summary","contentUrl":"https://nicolassitter.com/data/anatomy-chatgpt-hotel-search-2026/summary.csv","encodingFormat":"text/csv"}]}