TL;DR
A restaurant is more likely to appear in ChatGPT when the system can find a clear first-party record, match it to consistent listings and reviews, and corroborate it through trusted local sources. Start with crawl access and accurate menu facts, then test the real questions diners ask.
There is no button that adds a restaurant to ChatGPT. You cannot buy a guaranteed recommendation through schema, a listing package or a burst of reviews. You can make the evidence much easier to find, understand and trust.
That matters because diners have already changed how they choose. DoorDash's 2026 Restaurant Industry Trends Report found that 22% of surveyed US consumers had used ChatGPT or Gemini to help choose a restaurant. BrightLocal's 2026 survey found that 45% of US adults had used AI for a local business recommendation, up from 6% in 2025. Of those AI users, 97% sometimes checked the answer against real reviews.
If the venue is already absent from AI answers, first diagnose why your restaurant is invisible on ChatGPT, then use the steps below to fix the gaps.
Can you submit a restaurant to ChatGPT?
No. OpenAI does not offer a restaurant submission form or a guaranteed inclusion programme for organic ChatGPT answers.
When ChatGPT searches the web, OpenAI's official crawler documentation says OAI-SearchBot is the crawler used to surface websites in ChatGPT search results. A site that blocks OAI-SearchBot may be excluded from search answers, although it can still appear as a navigational link. GPTBot is a separate control for model training, so blocking GPTBot does not require you to block ChatGPT search.
This gives you a clear technical gate. Crawl access only makes the page eligible to be considered. OpenAI does not publish a formula that guarantees whether a restaurant gets named.
What does ChatGPT need before it can recommend a restaurant?
In practice, a restaurant recommendation is easier to support when the available sources answer five questions clearly.
| Test | What the system needs to resolve | What your restaurant should provide |
|---|---|---|
| Discoverable | Can it reach the page? | Crawl access, indexable HTML and a working canonical URL |
| Identifiable | Is this one real venue? | One name, address, phone number and canonical venue page |
| Specific | Does it fit the diner's request? | Cuisine, neighbourhood, price, opening hours, menu and dining attributes |
| Corroborated | Do other sources agree? | Current listings, genuine reviews and independent local coverage |
| Current | Are the facts still true? | Fresh hours, menu, booking details and visible update routines |
Google's guidance for AI features supports the technical parts of this checklist. A page must be indexed and eligible to show a snippet, important content should be available as text, structured data should match the visible page, and the Google Business Profile should stay current. Google also says there is no special AI file or schema type required to appear in its AI features.
How do you get a restaurant recommended by ChatGPT in 9 steps?
Allow four to six weeks to complete the work you control for one venue with existing access. Reviews and independent coverage may take several months, so treat them as ongoing work rather than part of a fixed completion date.
What you need before Step 1: access to your website, robots.txt, Google Business Profile, booking profiles, main review profiles and the current menu. Create a simple sheet with one row per fact and one column per source so every mismatch is visible.
1. Allow OAI-SearchBot and keep the restaurant page crawlable
Check robots.txt, page-level robots rules and any security layer that can block automated visits. OAI-SearchBot should be allowed to reach the public restaurant, menu and location pages you want ChatGPT search to use. OpenAI notes that a robots change can take about 24 hours to affect its systems.
Then fetch the restaurant page as raw HTML. The venue name, address, hours, menu details and core description should be present in that response. Do not hide the only useful facts inside an image, PDF, booking widget or client-side script.
Expected outcome: your canonical restaurant page returns a successful response, allows OAI-SearchBot and exposes the main facts as text.
2. Build one canonical page for the venue
Use one page as the restaurant's first-party record. Put the exact trading name, full address, local phone number, opening hours, booking route, menu link, cuisine and neighbourhood on it. If there is only one restaurant, avoid splitting those facts across several thin location pages.
Write the description around real decisions. "Seasonal food in a relaxed room" says little. "A 40-seat Basque restaurant in Soho serving pintxos and charcoal-grilled fish, with counter seats, vegetarian options and an average dinner spend of £45 to £60 before drinks" gives an engine facts it can match to a prompt.
Expected outcome: one URL answers who the restaurant is, where it is, what it serves, what it costs and how a diner can visit.
3. Publish the menu as useful HTML
A PDF menu can remain available for printing, but it should not be the only version. Put dish names, short descriptions and current prices in the page HTML. Mark vegetarian, vegan, halal, gluten-aware and allergen information only when the restaurant can support those claims in practice.
Include the details that change a recommendation: set-menu price, kitchen closing time, children's menu, group size, counter seating, outdoor space, wheelchair access and whether bookings are required. DoorDash's 2026 survey found that 59% of consumers seek or value dietary and allergen information when choosing where to eat.
Expected outcome: ChatGPT can retrieve the menu facts needed to answer price, dietary, occasion and group questions without reading a PDF image.
4. Align Google Business Profile and booking listings
Use the same real-world name, address, phone number, primary category and opening hours everywhere. Google's Business Profile guidelines call for an accurate real-world name, the fewest categories needed to describe the business, a precise address and one profile per business.
Apply that record to booking platforms, map listings, social profiles and the restaurant's contact page. Remove old phone numbers and duplicate profiles. Update holiday hours in the sources people check.
Expected outcome: the main external records match the venue page on identity, contact details and availability.
5. Add Restaurant structured data that matches the page
Add Restaurant structured data to the canonical venue page. Include the restaurant name, URL, image, telephone, price range, cuisine, address, coordinates, opening hours and menu URL when those details are visible and current.
Schema clarifies the record. It does not guarantee a recommendation, and it should never claim details the guest cannot see on the page. Google says structured data for AI features must match the visible text and that no special schema is needed for AI eligibility.
Expected outcome: the page exposes one valid Restaurant entity whose details match the copy a diner can read.
6. Build a steady base of real, current reviews
Ask guests for honest reviews at natural points after a visit. Send each request to the correct venue profile and never offer a reward for a positive score. The useful signal is a current body of detailed experiences, not a sudden spike of empty five-star ratings.
Reviews also act as a fact-check. BrightLocal found that 97% of AI users sometimes double-check local recommendations against real reviews. Track recurring complaints about hours, access, service style or menu availability and correct the underlying fact on your site and listings.
Expected outcome: the venue has a growing stream of genuine reviews tied to the correct location, with recurring factual errors fed back into the source record.
7. Earn coverage in the local sources ChatGPT already reads
Do not start with a generic directory list. First learn which sources appear in answers for your city, cuisine and price point, then seek relevant inclusion based on a real editorial reason.
Our London dining citation study tracked about 85 real dining questions daily across major AI engines for two weeks in July 2026. On ChatGPT, the source pattern was concentrated:
| London source | Retrieved in ChatGPT dining answers |
|---|---|
| Time Out | 64% |
| thatsup | 56% |
| The Infatuation | 42% |
| 33% | |
| SquareMeal | 32% |
| Visit London | 30% |
| OpenTable | 29% |
| Condé Nast Traveller | 28% |
| Michelin | 26% |
These figures describe one city and one two-week measurement window, not a universal ranking. Our Berlin study and New York study produced different source hierarchies. The practical rule is local: map the sources that shape your market, then give editors and community members something true and specific to discuss.
Expected outcome: the venue appears in several independent sources that are frequently retrieved in restaurant answers for its city.
8. Answer the detailed questions diners actually ask
Brand pages help ChatGPT verify a restaurant. Discovery pages help it choose one. Publish short, clear sections that answer the questions where the venue has a genuine fit: a work lunch near a station, a quiet anniversary dinner, a table for eight, a good-value pre-theatre menu or a late kitchen on Sunday.
Do not create a page for an attribute the restaurant cannot deliver. State the fit, proof and limits. For example: "The private room seats 10 to 16 guests, costs £900 minimum spend on Friday evenings and is reached by one flight of stairs."
Link those sections to the canonical restaurant page and menu. For multi-site businesses, use the separate restaurant-group AI search playbook, because each venue needs its own entity and test set.
Expected outcome: the site contains direct, extractable answers for the venue's strongest occasions, attributes and local discovery prompts.
9. Test a fixed prompt set every month
Run the same questions through ChatGPT at the same cadence. Do not treat one answer from one account as a trend. Record whether the venue is named, how it is described, which facts are right, which source is cited and which alternatives appear.
Use at least five prompt classes:
| Prompt class | Example test |
|---|---|
| Brand fact | What kind of restaurant is [name], and when is it open? |
| Local discovery | Where should I eat near [landmark] for under £50 a head? |
| Occasion | Which restaurant near [area] is good for a quiet anniversary dinner? |
| Attribute | Which [area] restaurant has a strong vegetarian menu and wheelchair access? |
| Comparison | [Restaurant A] or [Restaurant B] for a group of eight? |
Run the same set in Google AI Mode, Gemini and Perplexity if those engines matter to your guests. They may choose different sources. Track the answer and the cited evidence separately so you know whether a wrong statement comes from your page, a listing or an outside article.
Expected outcome: you have a repeatable monthly record of mentions, factual accuracy and source use rather than a screenshot of one favourable answer.
Which fixes should a restaurant make first in 2026?
Fix access and factual conflicts before commissioning new content or PR. A simple priority order keeps the work tied to the cause.
| Problem | First fix | Why it comes first |
|---|---|---|
| ChatGPT cannot retrieve the site | Crawl access and raw HTML | No page or campaign can compensate for blocked evidence |
| ChatGPT confuses the restaurant or address | Canonical venue page and listing alignment | The system needs one resolvable entity |
| Hours, menu or price are wrong | First-party page, GBP and booking profiles | These are operational facts under your control |
| The venue appears for branded prompts only | Occasion and local discovery pages | The site lacks evidence for open discovery questions |
| The venue is absent from category shortlists | Independent local coverage and reviews | The answer lacks outside consensus |
| Results vary by engine | Source mapping by engine | Different systems consult different evidence mixes |
Do not start with schema if the address is wrong, or with press coverage if the menu is unreadable. Each layer depends on the one before it.
What should you do when ChatGPT gets restaurant details wrong?
Trace the wrong fact to its strongest visible source. Correct the canonical venue page first, then Google Business Profile, booking platforms and other high-use listings. Ask an external publisher for a correction when its page carries the error. Keep screenshots and dates so you can see whether the answer changes after recrawling.
Do not try to correct a wrong answer by publishing the same fact on dozens of weak directories. A small set of accurate, current sources is more useful than a large set of copied profiles that nobody maintains.
If the false claim creates a safety issue, such as incorrect allergen or accessibility information, correct every source under your control at once and contact the publisher that states it. ChatGPT output itself may change between sessions, but the source record is the part a restaurant can own.
How long does it take for a restaurant to show up in ChatGPT?
There is no fixed timeline. OpenAI says robots changes can take about 24 hours to affect its systems, but that only concerns crawl instructions. Search inclusion, source selection and recommendation frequency follow separate processes and carry no guarantee.
Technical fixes can make a page available quickly. Correcting listings may take days or weeks as platforms review changes. Earning reviews and independent editorial coverage often takes several months. Judge progress by the fixed prompt set, factual accuracy and source pattern, not by a promised date.
What does success look like?
Success is not a single ChatGPT mention. A restaurant has a stronger AI discovery position when it is named for several relevant non-branded prompts, described with the right facts, supported by current sources and visible across more than one engine.
The practical sequence is simple: make the venue crawlable, create one clean record, add the details that drive a dining decision, align outside listings, earn local proof and test the answer. If you want the starting point measured for you, Schmitdy's free AI search audit checks the questions and sources that matter for your restaurant.
Sources
- OpenAI, "Overview of OpenAI Crawlers": official roles for OAI-SearchBot, GPTBot and ChatGPT-User, plus crawler-control guidance.
- Google Search Central, "AI Features and Your Website": eligibility, text availability, Business Profile and structured-data guidance for AI Overviews and AI Mode.
- Google Business Profile, "Guidelines for Representing Your Business on Google": official name, address, category and profile-quality rules.
- Schema.org, "Restaurant": the vocabulary for restaurant structured data.
- DoorDash, "2026 Restaurant Industry Trends Report": Dynata survey of 3,001 US consumers and 509 restaurant operators, conducted in March 2026.
- BrightLocal, "Local Consumer Review Survey 2026": representative panel of 1,002 US adults, published in March 2026.
- Schmitdy, "Which Sources ChatGPT Cites for London Dining": daily tracking of about 85 London dining questions across major AI engines for two weeks in July 2026.
