{"@context":"https://schema.org","@type":"BlogPosting","headline":"AI Search for Bistros in Paris (2026): The Guidebook City Where Restaurant Websites Disappear","description":"A cross-vertical field test of the AI-search methodology, completing the staked-out Restaurants/Paris slot. 26 prompt templates × 5 AI engines (ChatGPT, Perplexity, Gemini, Copilot, Google AI Mode) × EN/FR, matched to a 579-venue Paris bistro registry (500-row Apify seed + 79 Google Places recoveries; 438 classified bistros/brasseries, 387 with websites). ChatGPT cites a bistro's own website in 0.9% of its 331 citations — the series floor, without the thin-owned-web excuse. The guide layer takes the citations: 38% local editorial (parisjetaime.com is the first tourism board to be every engine's consensus source), 10% restaurant guides, 14% global press. The predicted TheFork takeover never happens (49 cites ≈ 1.4%; Michelin out-cites it 65–49). Bistrot des Tournelles is the five-engine consensus recommendation (108 captures). First measurable neighbourhood test in the series: 94% arrondissement accuracy, with Perplexity the outlier at 47%.","datePublished":"2026-07-08","dateModified":"2026-07-08","url":"https://nicolassitter.com/research/bistros-paris-ai-search-2026","category":"research","keywords":["AI search bistros Paris","ChatGPT restaurant recommendations","TheFork AI citations","best bistros Paris AI","AI local search study","GEO restaurants","Michelin Guide AI","arrondissement accuracy"],"articleSection":"Research","wordCount":3100,"readTime":"13 min","articleBody":"|\n\n|\n\nJuly 2026AI Search Studies\n\n# AI Search for Bistros in Paris (2026):The guidebook city where restaurant websites disappear\n\n**TL;DR:** We asked five AI engines 26 bistro questions in two languages and checked where every one of their 3,406 citations pointed. ChatGPT linked to a bistro’s own website **0.9% of the time** — the lowest share in the six cases of this series, in the city with the best-equipped restaurants we’ve tested (387 of 579 venues have a site). What replaced them wasn’t TheFork either: the reservation layer stayed near **2%**. It was the guide layer — **parisjetaime.com**, the city’s official tourism site, tops the cross-engine consensus (55 citations, all five engines), with Time Out and the Michelin Guide close behind. On the answer side, **Bistrot des Tournelles** is the consensus recommendation (named by all 5 engines, 108 captures), and Paris gave us the first real neighbourhood test of the series: **94%** of located recommendations sit in the right arrondissement — except on Perplexity, which drops to 47%.\n\nPublished July 8, 2026\n\n5\n\nAI engines\n\n26\n\nPrompt templates\n\n438\n\nBistros & brasseries\n\nEN + FR\n\nBoth languages\n\n[Read the Report](#executive-summary)\n\n[Summary](#executive-summary)[1\\. Source Mix](#source-mix)[2\\. The 0.9% Floor](#website-floor)[3\\. The Guide Layer](#guide-layer)[4\\. The TheFork Test](#thefork)[5\\. Reddit & Instagram](#reddit)[6\\. Gemini’s List Sites](#gemini-diet)[7\\. Leaderboard](#leaderboard)[8\\. Arrondissements](#arrondissements)[9\\. EN vs FR](#language)[10\\. Vs. 5 Cities](#six-cases)[11\\. AI Behaviour](#ai-behaviour)[For Bistro Owners](#takeaways)[Conclusion](#conclusion)[Methodology](#methodology)[FAQ](#faq)\n\n## Executive Summary\n\nThis study completes the Restaurants/Paris slot we staked out when the series began — scoped to bistros so the reference set stays a real universe. The question we brought to it: do reservation platforms capture AI restaurant search the way booking marketplaces captured Berlin yoga?\n\nThe answer is no — and what wins instead is more interesting. ChatGPT’s citations for Paris bistros put the restaurant’s own website at **0.9%** (3 URLs out of 331). Tokyo bookstores (8%) and Marseille coffee (10%) had already broken the ~32% own-website share we measured across Paris yoga, Berlin yoga and Amsterdam bikes, but both had an excuse: thin owned webs, scenes documented on social. Paris bistros remove the excuse. Two thirds of the venue registry has a website — the highest of any study in this series — and ChatGPT still routes essentially none of its grounding through them.\n\nWhere does it ground instead? In the guide layer Paris has been accumulating for a century, now in web form: **38% local editorial** (parisjetaime.com — the official tourism board — Time Out, Sortir à Paris), **14% global food & travel press**, **10% restaurant guides**, almost all of it the Michelin Guide. TheFork — the platform we expected to dominate a French restaurant vertical — shows up on every engine but never rises above a few percent. Booking a table is what you do _after_ the answer; the engines cite whoever wrote the recommendation down first.\n\n**One distinction throughout:** _citations_ are the URLs an engine used as support; _mentions_ are the bistros actually named in the visible answer. Source-mix numbers count citations; the leaderboard counts mentions. Keeping them separate is what lets us see that a bistro can dominate answers while its website is never cited.\n\nSection 1\n\n## Source mix by platform\n\nEvery cited URL, bucketed into an 11-category taxonomy built for this vertical (reservation platforms and restaurant guides get their own buckets — they’re the hypothesis). Percentages are of each engine’s own citation pool.\n\nsource-mix-by-platform-paris-bistros\n\nColumns sum to 100% (largest-remainder rounding). “Other” holds the unbucketed long tail — mostly one-off blogs and venue sites outside the registry.\n\nCopilot\n\n### Website-first, at 74%\n\nStill the engine that grounds recommendations in the business’s own site — but the share keeps sliding down the series: 95–97% in yoga and bikes, 89% in Tokyo, 83% in Marseille, **74%** here. Even for Copilot, Paris’s editorial gravity pulls a quarter of the citations away from the restaurants themselves.\n\nPerplexity\n\n### The second entity engine — 35%\n\nA role reversal: in Berlin, Perplexity was the booking-marketplace engine (31% of its URLs). For Paris bistros it cites more restaurant websites than any engine except Copilot — its top domains are literally levieuxbistrot-paris.fr (32 cites) and bistrot-cafe-de-paris.com (28). One caveat lands in Section 8: the venues are right, the neighbourhoods often aren’t.\n\nAI Mode\n\n### 70% Google self-citations\n\nGoogle AI Mode keeps citing Google: **70%** of its URLs are google.com, in line with Marseille (80%) and Tokyo (61%). The rest scatters thinly across the same guide layer the other engines use.\n\nReading across the series, each city so far has had one dominant “discovery infrastructure” that the engines mirror: a booking marketplace in Berlin, Instagram and micro-guides in Marseille, the local-guide web in Tokyo. Paris’s infrastructure turns out to be its guidebooks — official, editorial and Michelin — and every engine except Copilot defers to them.\n\nSection 2\n\n## The 0.9% floor\n\nSix replications in, the own-website share has a floor, and Paris bistros just set it. What makes this one different from Tokyo’s 8% or Marseille’s 10% is that the usual explanation is unavailable.\n\n0.9%\n\nChatGPT citations pointing at a Paris bistro’s own website — 3 URLs out of 331.\n\nIn a registry where 387 of 579 venues (67%) have a website — the best-equipped vertical we’ve measured.\n\nchatgpt-own-website-share-six-cases\n\nIn Marseille we could explain the low share with the scene itself: only 41% of coffee venues had any website, so the engines had little to cite. Here the bistros did their homework — sites, menus, reservation widgets — and it made no measurable difference to ChatGPT. The competition isn’t absence; it’s abundance. Paris is plausibly the most guidebook-documented restaurant city on earth, and a retrieval system choosing between lebistrotduperigord.fr and a Time Out roundup of “the 23 best bistros in Paris” picks the roundup, which answers the whole question in one document.\n\nThe practical readout: for a Paris restaurant, the own-website share of AI citations is so small that watching it is pointless. The visibility question is whether you’re _named in the answers_ (Section 7) and _present in the documents the engines actually cite_ (Section 3). Your website still matters for entity resolution — it’s how our pipeline, and plausibly the engines, tie your name to a place — but as a citation destination it has effectively vanished.\n\nSection 3\n\n## The guide layer that took the citations\n\nThe domains cited across the most engines, with volume. This is the infrastructure an AI answer about Paris bistros is actually built on.\n\nTop cross-platform cited domains for Paris bistros, ranked by number of engines then citations.\n\nPlatforms\n\nCites\n\nBucket\n\nDomain\n\n5 / 5\n\n55\n\neditorial — local\n\nparisjetaime.com (official tourism board)\n\n5 / 5\n\n41\n\neditorial — local\n\nsortiraparis.com\n\n5 / 5\n\n26\n\nbooking\n\nthefork.fr\n\n4 / 5\n\n59\n\neditorial — local\n\ntimeout.fr\n\n4 / 5\n\n58\n\nrestaurant guide\n\nguide.michelin.com\n\n4 / 5\n\n36\n\npress — global\n\npariseater.com\n\n**The city’s own tourism board is the #1 consensus source.** Only three domains reach all five engines — parisjetaime.com (55 cites), sortiraparis.com (41) and thefork.fr (26) — and the tourism board leads them. That’s a first in this series, where the cross-engine consensus slot has always been held by Reddit or a private guide. If you want one placement that reaches every AI engine answering bistro questions about Paris, the official city guide is that placement — ahead of any booking platform, and far ahead of your homepage.\n\nSection 4\n\n## The TheFork test: a hypothesis that failed\n\nWe came into this study with a specific prediction, made when the Restaurants/Paris slot was staked out: engines would route restaurant answers through reservation platforms — TheFork above all, in its home market — the way Berlin’s yoga answers ran through booking marketplaces. Worth stating clearly, because the data said otherwise.\n\n49\n\nTheFork citations, all engines combined\n\n1.4% of the 3,406 URLs in the study. The full booking bucket — TheFork, OpenTable, SevenRooms — reaches 66 citations, about 2%.\n\n### Present everywhere, dominant nowhere\n\nTheFork does something no restaurant website manages: it appears in the citations of all five engines (Perplexity 22, ChatGPT 16, AI Mode 6, Copilot 3, Gemini 2). But the volume never follows. Compare Berlin yoga, where Urban Sports Club, Eversports and ClassPass together took 31% of Perplexity’s citations — here the equivalent reservation layer peaks at 3% of Perplexity. The Michelin Guide alone out-cites TheFork 65 to 49.\n\nOur best reading of the difference: in Berlin, the marketplaces _are_ the discovery layer — class schedules, studio pages and comparison content live there. In Paris restaurants, discovery editorial already existed for decades before online booking arrived, so TheFork functions as checkout, and checkout pages answer no one’s “where should I eat” question.\n\nIf you run visibility for a restaurant group and your AI strategy is “keep the TheFork profile perfect,” the citation data says you’re optimising the 2%, not the 60%+ that flows through editorial guides, the tourism board and the Michelin Guide.\n\nSection 5\n\n## Reddit narrows to one engine; Instagram stays home\n\nTwo social findings, both departures from the earlier cities.\n\n61 of 74\n\n### Reddit citations that belong to ChatGPT\n\nReddit is still ChatGPT’s single favourite domain here (61 cites, 18% of its pool, more than any other single source). But the habit stops there: AI Mode adds 9, Gemini 4, and Copilot and Perplexity cite Reddit exactly zero times for Paris bistros. In earlier cities Reddit was the cross-engine consensus source; in Paris that role passed to the tourism board, and Reddit became a ChatGPT quirk.\n\n32 vs 237\n\n### Instagram citations, Paris bistros vs Marseille coffee\n\nMarseille’s standout signal — Instagram as a primary AI citation source, 237 cites — does not travel to Paris. 32 citations across the whole study, despite plenty of bistros here also living on Instagram. Instagram-as-citation looks like a property of scenes whose _only_ documentation is Instagram — it evidently isn’t a French thing or a food thing.\n\nSection 6\n\n## Gemini skips Michelin’s city and cites list sites\n\nGemini’s pattern in this series is to anchor on one editorial vein per city. Its Paris pick is the strangest yet.\n\n45\n\ncitations to `restaurantsforkings.com` on Gemini\n\n15% of Gemini’s entire Paris citation pool — its single largest source, ahead of the Michelin Guide (18).\n\n### In the world’s most guide-covered restaurant city, Gemini’s top sources are low-recognition English list sites\n\nIts top domains: restaurantsforkings.com (45 — a Florida-based, occasion-themed restaurant-ranking platform), everydayparisian.com (31 — an American expat lifestyle blog), then the Michelin Guide (18), Paris by Mouth (15) and topratedplaces.ai (10 — a generic “top places” rankings site on a .ai domain). The list-site bucket takes **22%** of Gemini’s citations — no other engine gives it more than 2%.\n\nIn Marseille, Gemini’s concentration at least landed on trade press (Barista Magazine). Here the same behaviour — find one authoritative-looking editorial vein and drink deeply — selects sites whose main qualification appears to be ranking-shaped content in English. For a city where Le Fooding, Le Monde and fifty years of guide culture are a query away, that’s a retrieval-quality finding in itself.\n\nThe GEO-industry implication cuts both ways. Uncomfortable: a ranking-formatted site nobody in Paris has heard of can become Gemini’s primary source for Paris. Actionable: list-shaped content demonstrably gets retrieved — the format works, on this engine, even without brand authority.\n\nSection 7\n\n## The Paris Bistro AI Leaderboard\n\nRanked by how many captures actually _name_ the bistro in the visible answer (chains and sibling venues merged into brands). The citation-counted score sits alongside for contrast — the two metrics tell usefully different stories here.\n\nai-favourite-paris-bistros-2026\n\nTop 12 Paris bistros by text-mention total (captures whose visible answer names the brand), with the citation-counted score alongside. Engines = how many of the five engines named the brand at least once. Brand-aggregated: sibling venues sharing one website domain count as one brand.\n\nRank\n\nBistro\n\nText mentions\n\nCite score\n\nEngines\n\n#1\n\nBistrot Des Tournelles\n\n108\n\n58\n\n5 / 5\n\n#2\n\nBistrot Paul Bert\n\n75\n\n14\n\n5 / 5\n\n#3\n\nLe Vieux Bistrot\n\n71\n\n75\n\n4 / 5\n\n#4\n\nBistro des Livres\n\n64\n\n119\n\n4 / 5\n\n#5\n\nBrasserie Martin\n\n56\n\n31\n\n5 / 5\n\n#6\n\nBistrotters\n\n50\n\n26\n\n5 / 5\n\n### Why the cite-score ranking disagrees\n\nBy citations, #1 would be **Bistro des Livres** (score 119): its family of three sibling bistros — des Livres, des Lettres, des Poèmes — shares one domain, bistrodeslettres.com, which engines cite heavily (66 cites across 3 engines). By what the answers actually say, it’s #4. Same lesson as Marseille’s cite-#1 artifact, milder form: citation counts reward domain arrangements; text mentions reward being recommended.\n\n### Two rows to read carefully\n\n**#5 “Brasserie Martin”** is really the Nouvelle Garde group — its restaurants (Martin, des Prés, Dubillot, Bellanger) share lanouvellegarde.com, so brand aggregation merges them; read that row as the group’s combined AI presence. **#9 Bouillon Pigalle** likewise merges Bouillon République via bouillonlesite.com. Both are honest merges of sibling venues, flagged so nobody reads them as single dining rooms.\n\n### The same leaderboard, split by engine\n\nCell = share of that engine’s captures whose visible answer names the brand (raw count in parentheses). Capture counts differ per engine — ChatGPT, Gemini and Copilot ran both proxies (104 each), AI Mode and Perplexity US-only (52) — so rates, not raw counts, are the comparable unit.\n\nBistrot des Tournelles is the only brand every engine agrees on at volume — 33% of AI Mode’s captures, 36% of Copilot’s, about a fifth of everything else. Gemini’s zeros on Le Vieux Bistrot, Bistro des Livres and Bistrot Richelieu are real: its answers simply favour a different set (Paul Bert 31%, Le Bon Georges 20%) — consistent with it reading different sources (Section 6).\n\n#\n\nBistro\n\nAI Mode52 prompts\n\nChatGPT104 prompts\n\nPerplexity52 prompts\n\nGemini104 prompts\n\nCopilot104 prompts\n\n1\n\nBistrot Des Tournelles\n\n32.7%(17)\n\n20.2%(21)\n\n19.2%(10)\n\n22.1%(23)\n\n35.6%(37)\n\n2\n\nBistrot Paul Bert\n\n11.5%(6)\n\n18.3%(19)\n\n15.4%(8)\n\n30.8%(32)\n\n9.6%(10)\n\n3\n\nLe Vieux Bistrot\n\n19.2%(10)\n\n10.6%(11)\n\n50%(26)\n\n0(0)\n\n23.1%(24)\n\n4\n\nBistro des Livres\n\n19.2%(10)\n\n11.5%(12)\n\n21.2%(11)\n\n0(0)\n\n29.8%(31)\n\n5\n\nBrasserie Martin\n\n30.8%(16)\n\n9.6%(10)\n\n1.9%(1)\n\n10.6%(11)\n\n17.3%(18)\n\n6\n\nBistrotters\n\n15.4%(8)\n\n26.9%(28)\n\n1.9%(1)\n\n1.9%(2)\n\n10.6%(11)\n\n7\n\nLe P'tit Bistrot\n\n21.2%(11)\n\n7.7%(8)\n\n1.9%(1)\n\n0(0)\n\n23.1%(24)\n\n8\n\nBistrot Richelieu\n\n19.2%(10)\n\n6.7%(7)\n\n17.3%(9)\n\n0(0)\n\n16.3%(17)\n\n9\n\nBouillon Pigalle\n\n23.1%(12)\n\n4.8%(5)\n\n3.8%(2)\n\n18.3%(19)\n\n3.8%(4)\n\n10\n\nLe Bon Georges\n\n7.7%(4)\n\n10.6%(11)\n\n5.8%(3)\n\n20.2%(21)\n\n0(0)\n\n11\n\nBistrot de l’Oulette\n\n11.5%(6)\n\n15.4%(16)\n\n3.8%(2)\n\n0(0)\n\n13.5%(14)\n\n12\n\nBistrot Rougemont\n\n1.9%(1)\n\n20.2%(21)\n\n1.9%(1)\n\n0(0)\n\n9.6%(10)\n\nRows ordered by total text mentions; colour scales to the table maximum (Le Vieux Bistrot on Perplexity, 50%), zero cells greyed out. Hovering shows the raw counts behind each rate.\n\n**How this leaderboard is built — and corrected.** Every answer runs through a deterministic (temperature 0) extraction pass that pulls out the venues it actually recommends; a brand counts once per answer. Names are then resolved against the Google Maps seed — and here Paris needed a bigger correction than any previous city. The engines’ favourite bistros are the century-old canon (Chez Georges, Bouillon Chartier, Allard…), and a 500-place Maps scrape of “bistro” misses much of it. 79 frequently-recommended venues were recovered and verified via Google Places before counting (each confirmed a real Paris restaurant); names below the recovery threshold stay conservatively uncounted. The cite-score column uses citation-domain matching and is shown for contrast only.\n\n### Where the winners are\n\nThe 12 leaderboard brands on the map — multi-venue brands show every location. Click a marker for the per-engine mention breakdown.\n\n#### Top 12 most-recommended brands — popups show per-engine text mentions\n\n1Bistrot Des Tournelles2Bistrot Paul Bert3Le Vieux Bistrot4Bistro des Livres5Brasserie Martin6Bistrotters7Le P'tit Bistrot8Bistrot Richelieu9Bouillon Pigalle10Le Bon Georges11Bistrot de l’Oulette12Bistrot Rougemont\n\nSection 8\n\n## The first real neighbourhood test — and Perplexity fails it\n\nEvery previous city rendered the neighbourhood-accuracy question unanswerable: the seeds stored “Amsterdam” or “Marseille” with no district field. Paris postal codes encode the arrondissement, so 494 of our 579 venues carry one — and for the five neighbourhood prompts (11th arrondissement, Le Marais, Saint-Germain-des-Prés, Montmartre, Canal Saint-Martin) we can finally score every located recommendation.\n\n94%\n\nof resolved neighbourhood-prompt recommendations sit in the target arrondissement (168 of 179, all engines).\n\nLe Marais scored against the 3rd + 4th, Canal Saint-Martin against the 10th, Saint-Germain the 6th, Montmartre the 18th.\n\nArrondissement accuracy per engine on the five neighbourhood prompt templates. Denominator = NER-resolved recommendations whose venue carries an arrondissement.\n\nEngine\n\nIn target arrondissement\n\nAccuracy\n\nChatGPT\n\n52 / 52\n\n100%\n\nCopilot\n\n47 / 47\n\n100%\n\nAI Mode\n\n24 / 24\n\n100%\n\nGemini\n\n36 / 37\n\n97%\n\nPerplexity\n\n9 / 19\n\n47%\n\nThree engines are literally perfect, Gemini misses once — and then there’s Perplexity at **47%** (9 of 19; a small sample, flagged as such, but every other engine’s sample of similar size scored 97–100%). The failure shape is specific: ask Perplexity for bistros in the Marais and it answers with excellent bistros… in the 5th, the 9th, the 11th. Its website-heavy retrieval seems to reward venues whose sites rank for “bistro Paris” regardless of where they stand. A user following its Marais answer would eat well, two métro lines away.\n\n### The supply side, mapped\n\nEvery geocoded venue in the registry. Hover a dot for the name. The engines’ favourites cluster where the seed clusters — the 11th, the Marais, Saint-Germain — which is part of why the accuracy test is passable at all.\n\n#### All 579 geocoded seed venues (438 classified as bistros/brasseries)\n\nSection 9\n\n## EN vs FR: back to the 25% baseline\n\nSame question, both languages, ChatGPT on the FR proxy: how much of the top 5 survives translation? After Marseille’s 11%, Paris bistros land exactly where Berlin yoga and Paris yoga did.\n\nEN vs FR top-5 overlap (Jaccard) per template group, ChatGPT, FR proxy. Templates with identical overlap grouped.\n\nTemplate\n\nEN vs FR top-5 overlap\n\ndist\\_marais / dist\\_canal / dist\\_saint\\_germain\n\n67%\n\nbleed\\_brasserie / booking / persona\\_tourist / dist\\_montmartre\n\n43%\n\ncontrol (best bistros in Paris)\n\n25%\n\npersona\\_date / style\\_traditional / style\\_wine / vibe\\_historic / vibe\\_aesthetic\n\n25%\n\nmichelin / price\\_cheap / price\\_premium / time\\_lunch / time\\_late / dist\\_11e\n\n11%\n\npersona\\_local / persona\\_family / style\\_neo / style\\_seasonal / time\\_sunday / vibe\\_terrace / bleed\\_winebar\n\n0%\n\nThe control prompt overlaps **25%** — matching Berlin yoga (25%) and Paris yoga (25%), double Marseille’s 11%. That fits the guide-layer story: Paris is thoroughly documented in _both_ languages, so neither language starves. But the split by template is the sharper finding. Neighbourhood prompts converge (67% — geography anchors both languages to the same famous spots), while identity prompts diverge to zero: _“bistros where locals actually eat,”_ neo-bistros, Sunday opening, family dining — the FR answers and EN answers share nothing at all in their top fives.\n\nThe audit advice follows from the split itself: if your customers ask geographic questions, one language roughly covers you; if they ask taste questions — local, seasonal, natural wine — the EN and FR answer sets are disjoint, and you need eyes on both.\n\nSection 10\n\n## Six cases in: what the series now says\n\nOne row per replication, on the axis that has become the series’ spine — how much of ChatGPT’s grounding the businesses themselves get, and what takes the rest.\n\nSix cross-vertical replications of the AI-search methodology, on the own-website axis.\n\nCity + vertical\n\nChatGPT own-site %\n\nWhat takes the citations instead\n\nParis yoga\n\n32%\n\nReddit\n\nBerlin yoga\n\n32%\n\nBooking marketplaces (Urban Sports Club)\n\nAmsterdam bikes\n\n42%\n\nReddit\n\nTokyo bookstores\n\n8%\n\nLocal-guide web (whenin.tokyo, Tokyo Weekender)\n\nMarseille coffee\n\n10%\n\nInstagram + Reddit + French micro-guides\n\nParis bistros\n\n0.9%\n\nThe guide layer: tourism board, Time Out, Michelin\n\n### What replicated\n\n-   **Engine personalities.** Copilot most website-first (74%), AI Mode 70% Google self-cites, Gemini concentrated on one editorial vein, ChatGPT blending social with editorial.\n-   **The 25% language overlap** on the control prompt, matching Berlin and Paris yoga — which recasts Marseille’s 11% as the series outlier.\n-   **Citation-vs-mention divergence.** The cite-counted #1 (a shared-domain family) again differs from the consensus the answers actually name.\n\n### What Paris bistros adds\n\n-   **The own-website floor is not about missing websites.** 67% of the registry has one; ChatGPT cites them 0.9%. Editorial abundance suppresses them as effectively as owned-web scarcity did.\n-   **Reservation platforms are not a discovery layer.** The Berlin marketplace takeover has a boundary, and it’s here.\n-   **Neighbourhood accuracy is measurable and engine-specific.** 94% overall, with a 100%-vs-47% split between ChatGPT-class engines and Perplexity.\n\n[Read: AI Search for Specialty Coffee in Marseille](/research/specialty-coffee-marseille-ai-search-2026) [Read: AI Search for Yoga Studios in Berlin](/research/yoga-studios-berlin-ai-search-2026) [All AI Search Studies](/research?topic=ai-search)\n\nSection 11\n\n## Dataset shape and operational notes\n\nWhat landed, what didn’t, and one infrastructure incident worth recording.\n\n416\n\nCaptures across 8 of 10 platform×proxy batches: ChatGPT, Gemini and Copilot on both proxies (104 each), Perplexity and AI Mode on US only (52 each).\n\n3,406\n\nCited URLs, bucketed into the 11-bucket taxonomy. After the Paris taxonomy pass, the residual “other” bucket holds 20% — mostly one-off blogs and sites of venues outside the registry.\n\n3,034\n\nExtracted mention rows from the NER pass; 70% resolved to the registry after Places recovery. Unresolved names are mostly wine bars from the entity-bleed prompts — correctly outside a bistro registry.\n\n**Two batches are absent, for different reasons.** Perplexity × FR proxy failed at the Bright Data _download_ stage (fetch\\_error) across two runs and five attempts — a new failure mode, distinct from the trigger-level FR rejection that has followed AI Mode through Paris yoga and Marseille coffee. AI Mode × FR we did not fire at all, given that trigger-rejection history and the study’s cost cap. Both engines’ numbers on this page are US-proxy only (both prompt languages present); nothing is imputed. Separately, an infrastructure retry duplicated the ChatGPT × US batch — 52 duplicate captures were detected and removed before any analysis.\n\n**The TLD split is unmeasurable this time, for a new reason.** In Marseille the .fr sample was too thin because venues lacked websites. Here the bistros have websites — ChatGPT just doesn’t cite them (3 URLs total), so a .com-vs-.fr comparison over entity domains has no sample to stand on. Recorded as a measurement limit, not a finding.\n\nFor bistro owners\n\n## What this means if you run a Paris restaurant\n\nThe citation economy for Paris food runs through the guide layer, so that’s where the work is:\n\n-   **Chase the guide layer before the platform layer.** parisjetaime.com, Sortir à Paris and Time Out are what all engines cite; a Bib Gourmand listing feeds the 10% guide bucket. Your TheFork profile converts diners — it just doesn’t create AI visibility.\n-   **Keep the website — its job has changed.** It anchors your name to a place and menu for every resolution system — ours included — even while earning almost no citations directly.\n-   **Reddit reaches exactly one engine.** Threads about you feed ChatGPT (18% of its grounding) and nothing else. Price the effort accordingly.\n-   **Check what Gemini reads.** Its top Paris sources are English list sites most restaurateurs have never heard of — being absent from restaurantsforkings.com costs Gemini visibility specifically.\n-   **Audit both languages when it’s a taste question.** Locals, natural wine and Sunday-open prompts have zero EN/FR overlap; neighbourhood prompts mostly converge.\n\nConclusion\n\n## A century of guidebooks, machine-readable at last\n\nWe expected TheFork to own this vertical and it doesn’t. We assumed a scene where two thirds of businesses maintain websites would lift the own-site share and it set a record low instead. Both surprises have the same cause: Paris restaurants are the most editorially documented local businesses we’ve tested, and retrieval systems prefer a document that answers the whole question to five documents that each answer a fifth of it.\n\nThat preference has history on its side here. Paris invented the modern restaurant guide; what the engines are doing is reading a hundred years of that tradition — tourism-board lists, Michelin entries, Time Out roundups — and treating the restaurants’ own voices as raw material rather than sources. The bistros wrote the menus. The guides got the citations.\n\nFor the series, Paris closes a question Tokyo and Marseille opened. Low own-website shares aren’t a symptom of scenes too scrappy to build websites; they happen wherever some other layer documents the scene better than the businesses do. What varies by city is only which layer that is. Six cases in, predicting an AI engine’s sources for a city means asking one question first: who already wrote the best guide?\n\nMethodology\n\n## Study design\n\n### Data collection\n\n-   26 prompt templates × 2 languages (EN/FR) × 2 proxy countries (US/FR) × 5 AI engines = 520 theoretical; 416 captured (Perplexity × FR download failure, −52; AI Mode × FR not fired, −52)\n-   Engines: ChatGPT, Perplexity, Gemini, Copilot, Google AI Mode\n-   Captured 2026-07-08 via Bright Data; a duplicated ChatGPT × US batch (infrastructure retry) was removed before analysis\n-   416 captures · 3,406 cited URLs · 3,034 extracted mention rows (70% resolved)\n-   Seed: 500-row Apify Google Maps pull for “bistro” in Paris (359 classified real bistros/brasseries) + 79 Google Places recoveries → 579 venues, 438 real, 387 with websites\n\n### What we measured\n\n-   Bistros named per answer (brand-aggregated leaderboard, text mentions primary)\n-   Cited URLs bucketed into an 11-bucket source taxonomy (booking and restaurant guides broken out)\n-   Reservation-platform share per engine (the staked-out hypothesis)\n-   EN vs FR top-5 overlap per prompt template\n-   Arrondissement accuracy of neighbourhood-targeted recommendations, per engine\n-   Cross-city comparison vs Paris yoga, Berlin yoga, Amsterdam bikes, Tokyo bookstores, Marseille coffee\n\n### How we turned answers into bistros: the NER pipeline\n\nAI answers are free text — “Paul Bert remains the benchmark, though Les Arlots up by the Gare du Nord…” — not a clean list of businesses. To count anything, we first extract the venue mentions. Each answer runs through a deterministic named-entity-recognition pass in four steps:\n\n1.  **Extraction.** A Gemini pass at temperature 0, constrained to a strict JSON schema, pulls every venue the answer actually recommends — named places only, no inferred ones — with its position in the answer.\n2.  **Normalisation.** Candidates are lower-cased and stripped of boilerplate (“Paris,” arrondissement suffixes, punctuation) so “Bistrot Paul Bert Paris” and “Paul Bert” collapse toward the same key.\n3.  **Entity resolution.** Normalised mentions match the venue registry exactly or by fuzzy similarity (cutoff 0.86). Names that don’t resolve are flagged, and frequently-recommended ones are looked up in Google Places: results verified as real Paris restaurants join the registry and their mentions re-resolve (79 venues entered this way — the classic canon a “bistro” Maps scrape misses); everything else stays uncounted.\n4.  **Brand aggregation.** Venues sharing a website domain merge into one brand (Nouvelle Garde’s restaurants, the Livres/Lettres/Poèmes family, both Bouillons), with per-location coordinates kept for the map. Social and booking domains are excluded from brand identity so an Instagram-only venue can’t absorb instagram.com citations.\n\nA taxonomy pass then tightened the source bucketing: before it, the residual “other” bucket held 39% of citations (the Paris editorial tail plus recovered venues’ websites the seed didn’t know); after adding the recovered venues’ websites and the Paris-specific editorial needles, “other” sits at 20%.\n\n### Caveats\n\n-   **Perplexity × FR proxy is missing** (Bright Data download-stage fetch\\_error after two runs and five attempts). Perplexity numbers are US-proxy only; both prompt languages are present in that batch.\n-   **AI Mode × FR was not fired.** The trigger-level FR-proxy rejection hit Paris yoga and Marseille coffee before this study; combined with the cost cap, we spent the calls elsewhere. AI Mode numbers are US-proxy only.\n-   **The TLD test has no sample.** ChatGPT cited 3 entity-website URLs in total; no .com-vs-.fr split can be read from that. Measurement limit, not a finding.\n-   **Perplexity’s arrondissement sample is small** (19 resolved mentions vs 24–52 for the others). Its 47% is flagged with its n; the perfect scores around it make the gap meaningful, not conclusive.\n-   **Venues named in fewer than 5 captures were not Places-recovered**; their mentions stay unresolved, so leaderboard counts are conservative lower bounds. One known miss: Benoit (Alain Ducasse’s bistro, ~12 mentions) was rejected by the recovery type-gate and is absent from the leaderboard.\n-   **Seed scope is “bistro”-anchored.** The registry is built from a Maps search for bistros plus engine-recommended recoveries; it is a bistro universe, not a census of all Paris restaurants.\n-   Google AI Mode’s google.com self-citations (70%) inflate its citation volume relative to engines that cite the open web.\n-   **Disclosure:** no personal affiliation with any Paris restaurant.\n\nFAQ\n\n## Frequently Asked Questions\n\n### Summarize with AI\n\n## Continue Reading\n\nThe rest of the cross-vertical series, and the hotel research it grew out of.\n\n[AI Search for Specialty Coffee in Marseille (2026)](/research/specialty-coffee-marseille-ai-search-2026)[Anatomy of ChatGPT Hotel Search (2026)](/research/anatomy-chatgpt-hotel-search-2026)\n\n[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/bistros-paris-ai-search-2026","mainEntityOfPage":{"@type":"WebPage","@id":"https://nicolassitter.com/research/bistros-paris-ai-search-2026"},"tags":["AI Search","Local Search","Restaurants","Paris","Citations","GEO"],"sameAs":["https://hotelrank.ai/research/bistros-paris-ai-search-2026"],"alternateFormat":{"html":"https://nicolassitter.com/research/bistros-paris-ai-search-2026","json":"https://nicolassitter.com/api/post/bistros-paris-ai-search-2026","rss":"https://nicolassitter.com/rss.xml"},"datasets":[{"name":"summary","contentUrl":"https://nicolassitter.com/data/bistros-paris-ai-search-2026/summary.csv","encodingFormat":"text/csv"}]}