A restaurant's search visibility is decided on two very different screens: the business card in the map results and the pages on your own domain. Guests usually glance at both, then decide within seconds. Restaurant SEO is the work of making those two screens tell the same story and answer the guest's question at first sight.
This guide walks through the decisions to make, in order, before you rebuild your site or sign with an SEO provider. Each section gives you a criterion, a checklist or a question to put to an agency.
01Sorting guest searches into four intent groups
Restaurant searches do not fit one keyword list; they split into four intent groups, and each needs a different page. Without this split, content ends up crammed into the home page or spread across generic posts that match no query.
- Dish searches: "birria tacos", "wood fired pizza", "gluten free pasta"; the guest is looking for a plate, not a venue, and sees both the map and organic pages.
- Place searches: "brunch in Shoreditch", "seafood on the waterfront" or simply "ramen near me"; distance carries the most weight here and the map card leads.
- Need searches: "kid friendly cafe with play area", "private room for twenty", "late night diner"; the guest wants a place that meets a condition.
- Brand searches: your name, your name plus "menu", your name plus "reservations"; the group you should win and the one most often lost.
To find your groups, look at the real queries in Search Console and the search terms in your Business Profile performance view. Also ask your hosts to note the questions they hear on the phone for a week; if "do you have vegan options" comes up daily, that is a search group waiting for an answer.
02A page plan that gives each query one answer
Once the groups are clear, write down which surface answers each one; when three pages try to answer the same question, none of them stands out. The plan also tells whoever writes content what not to write.
- Group the queries: sort Search Console data and the noted questions into the four groups, merging near duplicates into a single line.
- Pick the surface: place and open now queries go to the profile, dish queries to the menu and signature dish pages, need queries to experience pages.
- Mark the gaps: list groups with no answer yet; a gap is not always a new page, sometimes it is a paragraph added to an existing one.
- Remove overlaps: if two pages target the same query, make one the main page and link the other to it, or merge them.
- Review twice a year: update the table when the menu changes, the season turns or a new location opens.
The table fits on a single page, and in restaurant SEO it often saves more time than any other deliverable, because every new page idea gets tested against it first. It is also the first thing we hand over in our SEO consulting process.
03What you can actually influence in map results
Google says local results are based mainly on three factors: how relevant a profile is to the search, how far the business is from the searcher and how prominent the business is. You cannot change distance, so the whole job sits in the other two, and both are largely in your hands.
Relevance is how closely the profile matches what someone types. The primary category is the strongest signal here: a breakfast spot listed only as "Cafe" can trail behind on "breakfast" searches. Secondary categories, attributes and the profile menu widen the match. Prominence comes from review count and rating, links to your site and local sources that mention you; Google itself states that more reviews and positive ratings can help local ranking.
- Primary category: choose it by the word guests most often use to find you, not by the phrase that flatters your cooking.
- Attributes: fill in outdoor seating, high chairs, wheelchair access and vegan options honestly and keep them current.
- Special hours: enter Thanksgiving, Christmas and other holiday hours ahead of time; wrong hours are the fastest route to an angry review.
- Local mentions: neighborhood guides, city event listings and food writers' roundups are worth more, and carry less risk, than bought links.
Adding a neighborhood or dish to the business name may look like a relevance boost, but it breaks the guidelines and can get the profile suspended.
04Menu text and signature dish pages for dish searches
Showing up for dish searches starts with every menu item being written under the name guests actually use; a few dishes then deserve a page of their own beyond the menu line. Choosing those dishes pays off more than random blog posts.
Use two names together on the menu line: your house name and the common name people search. A menu that says "Slow Braised Short Rib" already matches "short rib"; one that says "The Chef's Cut" does not. Abbreviations, kitchen shorthand and names printed onto an image are invisible to search engines.
- Demand test: does the dish name show up in Search Console or profile queries, so there is real search interest behind it.
- Story test: is there something to say that will not fit on a menu line, such as the cooking method, the sourcing or the reason it is on the menu.
- Staying power test: will the dish stay for several seasons; a page for something that leaves in two months is wasted effort.
- Photo test: do you have several real, current, well lit photos of the plate.
A dish that passes three of these is a strong candidate. The page should carry first hand detail from the chef or owner, portion and sharing advice, allergen notes and a button that leads to a table or an order. In the UK, if you take orders online or by phone, allergen information has to be available before the purchase is completed and again on delivery, so keep those notes easy to find.
05Building experience, occasion and seasonal pages
Need searches are answered by an experience page full of concrete facts that prove the condition is met. "We welcome families" proves nothing on its own; the size of the play corner, a kids' menu and a changing table do.
Each experience page should answer the questions a guest asks before showing up. A group dining page states the table layout, the largest party you can seat, set menu options and how much notice you need. A patio page covers shade, heaters and what happens when it rains. These details speed up the guest's decision and also give AI assistants short, quotable sentences to work with.
- Occasion page: birthdays, rehearsal dinners or business lunches, with the space you can close off, sound setup and your policy on outside cakes.
- Access page: number of steps, ramp, parking and the nearest transit stop.
- Seasonal page: Mother's Day brunch, New Year's Eve dinner or the summer terrace, refreshed at the same address every year.
Update seasonal pages before searches climb, not when the season opens. People look for Mother's Day or holiday party bookings weeks ahead; a page still showing last year's dates sends them to a competitor. Give each seasonal page a fixed review date on a yearly calendar.
06Locations, delivery zones and guests from abroad
A separate location page belongs only to an address where you actually seat guests; cloning near identical pages for every delivery zone is the doorway approach Google's spam policies describe.
A real location page is set apart by details that apply only to that address: its own hours, menu differences, photos of that dining room and patio, parking and transit notes, a direct phone number and a link to that location's profile. If half of those facts are identical across locations, the pages read like copies of one template. Groups should manage each location's profile separately while keeping name format and categories consistent from head office.
In tourist areas, guests do not know the city and often search in their own language. Menu and experience pages then need separate addresses per language, with each version pointing to the others and to itself through hreflang. Machine translated dish names can mislead; keep names such as "pastel de nata" or "pho" intact and add a short, accurate description next to them. We cover similar language and map decisions for accommodation on our hotel SEO page.
- Does each location's profile link to its own location page or just the home page?
- How many sentences on each location page apply only to that address?
- Is the menu in other languages updated on the same day as the main menu?
07Collecting reviews, replying and keeping claims honest
Reviews are both a prominence signal and the text guests decide on, so how you collect them matters as much as how many you get. Google's policies forbid offering discounts or free items for reviews, asking only happy guests and discouraging negative reviews.
The safe setup is one request made to every guest in the same way: a QR code on the receipt, a card in takeout bags or a message after a reservation. A server handing a tablet only to tables that look pleased is selective solicitation. In the UK, the Digital Markets, Competition and Consumers Act 2024 also bans fake reviews and reviews that conceal an incentive.
Replies are read on the results page too. Leave out personal details and order specifics; a short answer that acknowledges what happened, says what changed and invites contact is enough. Do not script reviews either; an open question such as "what did you enjoy" brings dish names in naturally.
The same standard applies to claims on your site. Use words like "organic", "made in house" or "award winning" only when you can document them, because guests will test them in their reviews. Marking up reviews you display about yourself with star ratings does nothing, since Google does not show review stars for that kind of self serving review.
08Winning back searches for your own name
For brand searches, the goal is that a guest typing your name clicks a page you control first; you cannot remove delivery apps from the results, but you can usually get ahead of them. This is your warmest traffic, because the guest has already chosen you.
Start by recording what a search for your name shows today, including where the business card's website and menu links go. Then work through these steps.
- Home page title: put the full restaurant name and neighborhood in the page title; a slogan title is weak for this query.
- Profile links: point the website, menu and reservation links to your site; if the order link goes to a delivery app, make that a deliberate choice.
- Social accounts: make the bio link on Instagram and other accounts lead to your site, and link back to those accounts from the site.
- Platform listings: keep your name, address and hours on delivery and review platforms identical to the site.
- Words people add to your name: give "menu", "prices", "reservations" and "takeout" a clear answer on the site.
Track the effect in Search Console through the click through rate on brand queries. If impressions rise while clicks fall, another result is being chosen over yours on that page.
09A fast, crawlable site on the phone
The most common technical problem in restaurant SEO audits is a menu that search engines cannot read; the second is food photography that makes pages heavy on a phone. Both are cheap to fix when planned and expensive when discovered later.
If the menu loads in an iframe from another service, exists only as images or sits on the site only as a PDF, its dish names do not count for your domain. If you keep the QR menu service, make sure the main, current copy lives on your site as HTML text.
Serve images in modern formats at the right size. Core Web Vitals count as good when the largest content element loads (LCP) within 2.5 seconds, the page responds to input (INP) within 200 milliseconds and layout shift (CLS) stays at 0.1 or less.
- Menu test: can you select and copy a dish name on the menu page; if not, it is not text.
- One address rule: keep the menu at one permanent URL instead of a new file name with every update.
- Image names: let file names and alt text describe the plate; "IMG_4021" says nothing.
- Cookie banner: a large overlay that hides the menu on a phone costs you guests as surely as slow loading does.
Booking and ordering widgets add weight too, so load each one only on the pages that use it. If your current platform cannot carry this setup, the structure we recommend is described on our restaurant website page.
10Choosing structured data for a restaurant
On a restaurant site, structured data exists to state your address, hours, cuisine and menu link without ambiguity; the goal is consistent information, not decoration on the results page. The schema.org Restaurant type is a better starting point for that than the generic LocalBusiness type.
Use one Restaurant markup per address, on the home page or on each location page; packing every location into one block blurs which hours belong where.
- Core properties: name, address, telephone, geo, url and openingHoursSpecification, with special date ranges for holidays.
- Restaurant properties: servesCuisine for the cuisine, hasMenu for the menu page address and acceptsReservations for booking details.
- Menu markup: if you wish, mark up sections with the Menu, MenuSection and MenuItem types and use suitableForDiet on a MenuItem for vegan or gluten free dishes.
- Linked accounts: list your official social accounts under sameAs, but leave delivery platform listings out.
Google has no dedicated rich result for menus, so menu markup is a tidy data layer rather than a requirement. Before publishing, check the markup for errors with our structured data tool and confirm the hours in the markup match the hours shown on the page.
11Becoming the venue AI assistants suggest
Guests now put long questions such as "quiet place for dinner nearby that works with a toddler" to AI assistants, and those answers draw on web pages, map data and reviews. Nobody can promise that an assistant will name you, but producing information that is easy to quote is within your control.
Assistants pick up verifiable sentences, not vague praise. "A warm atmosphere" answers no question; "twelve tables in the garden, heaters in winter, dogs welcome outside" answers three. Writing experience pages in short, concrete sentences that make sense on their own helps classic search and AI answers at the same time.
- List the questions: write ten questions a guest might ask an assistant, mixing neighborhood, dish, need and price level.
- Ask regularly: put them to a few assistants once a month and record whether your restaurant appears and which source gets cited.
- Strengthen the source: if the cited source is an outdated guide article, add the current version of that information to your own page and profile.
We describe this tracking method, and which page structures are easier to cite, in our AI visibility service.
12Measurement, reporting and realistic timing
Restaurant SEO success is measured in interactions that become tables and orders, namely direction requests, calls, bookings and order clicks, not in visitor counts. If these four are not tracked separately, you will never see which query brings guests in which season.
Tracking has three layers. The Business Profile performance view shows map side searches, direction requests and website clicks. Search Console provides organic queries and the click through rate on brand searches. In GA4, click to call, booking, WhatsApp and order buttons are set up as separate events; tagging the profile's website link with our UTM builder separates map visits from organic traffic. Setting up analytics in line with cookie consent and placing a privacy notice next to the booking form belong to this layer as well.
Timing depends on the type of work. Category, hours and menu fixes often show in map visibility within the first weeks; dish and experience pages usually take months to settle in organic results. No provider can promise a specific position; the right expectation is a written timeline and milestones you can check every month.
Instead of a ranking list, ask the monthly report how many direction requests and calls came in and which pages started a booking.
13Common restaurant SEO mistakes
Most restaurant mistakes come from haste rather than bad intent; a shortcut of a few hours can put months of visibility at risk.
- Stuffing the business name: names like "Tony's Pizza Pasta Wings Downtown" risk suspension; use the real name and fill in categories and the menu properly instead.
- A copy page for every zone: cloned delivery area pages lower trust; one delivery area page plus separate pages for real locations works better.
- A menu published only as images: a photo menu is invisible to dish searches; use images to support a text menu instead.
- Rewarding reviews: reviews can be removed and the profile restricted, and in the UK concealing such an incentive is a banned practice; ask everyone the same way with nothing in return.
- A new seasonal page every year: a new address resets last year's gains; update the same URL with new dates and dishes.
- Reports built on rankings alone: rankings can rise while calls and bookings fall; track interactions by query and by page.
14Choosing who to work with and your next step
When choosing a restaurant SEO provider, look at the method they describe and at whose name the accounts stay in; screenshots of past rankings tell you nothing about competition in your neighborhood. A few questions in the first call reveal the approach quickly.
- What data will you use to choose the profile's primary category?
- Where will the main copy of the menu live, and who updates it?
- What review request setup do you recommend, and what will you never do?
- Which interactions will the monthly report show?
- Whose name will Search Console, GA4 and the Business Profile stay in?
We do not yet have a restaurant or cafe SEO project we can show as a reference; our local work in other industries is on the references page. If you also want to support takeout and bookings with paid search, the paid side, planned on the same timeline as organic work, is covered on our restaurant advertising page.
Before starting restaurant SEO, have your site address, Business Profile link and current menu ready. You can review fixed scope packages in the SEO pricing section, and for a priority list and written quote for your venue, reach us through the contact form.