Restaurant SEO isn’t about your website. It’s about your GBP and your menu schema.

Restaurant search behaviour splits into five distinct intents, each with its own ranking surface and conversion economics.

1. Cuisine + area intent

“Italian restaurant Shoreditch”, “sushi near me”, “Korean BBQ Manchester”. Map Pack 3 wins this with the right GBP cuisine categorisation, review-keyword density, and recent photos.

2. Occasion intent

“Sunday roast [area]”, “tasting menu London”, “date night restaurant”, “kids menu”, “late night food [area]”. Dedicated landing pages outrank generic cuisine pages because the intent is specific.

3. Dish intent

“Best burger [area]”, “sourdough pizza near me”, “vegan brunch Hackney”. Menu schema feeding dish-specific rich snippets plus dish-mentioning reviews wins this cohort.

4. Brand search intent

“[Restaurant name] booking”, “[Restaurant name] menu”. High intent, high conversion. The opportunity is to control the SERP by ensuring GBP, OpenTable / Resy listing, official site, and key review platforms all show clean current information.

5. Discovery intent

“Where to eat in [area]”, “new restaurants London 2026”. Aggregators (Time Out, Eater, The Infatuation, local press) hold this cohort. The opportunity is to get listed in those aggregators through outreach and digital PR rather than to outrank them.

Restaurant Map Pack ranking is decided by three factors: proximity, relevance, prominence. The Menu schema layered on top feeds rich snippets that compound the relevance signal for dish-specific queries.

What proper restaurant GBP setup looks like

• Primary category set to the most specific cuisine type (“Italian Restaurant”, not “Restaurant”).
• Secondary categories matching real service mix (“Cafe”, “Cocktail Bar”, “Wedding Venue” where applicable).
• Service options populated (“Dine-in”, “Takeaway”, “Delivery”, “Curbside pickup”).
• Dietary options populated (“Vegan options”, “Vegetarian options”, “Gluten-free options”, “Halal”, “Kosher”).
• Reservation link wired through to OpenTable, Resy, SevenRooms, or your own booking system.
• Menu URL pointed at a properly structured menu page.
• Recent photos (food, interior, exterior) refreshed monthly.
• Posts published weekly with seasonal menu changes, events, or news.

What Menu schema does

Menu schema (Restaurant + Menu + MenuItem structured data) feeds Google rich snippets for dish queries. A restaurant with proper Menu schema can appear in answer boxes for “where to get [specific dish] [area]” queries that competitors without schema do not appear in. We implement Menu schema across every dish with prices where stable, allergen flags, and proper category nesting (starters, mains, desserts, drinks).

Most restaurant sites have a single menu page and a homepage. Dish-specific and occasion-specific landing pages are the largest underbuilt asset in restaurant SEO and the highest-leverage investment for an independent restaurant.

The pages we build

• Sunday roast page (for pubs and modern British restaurants).
• Tasting menu page (for fine dining).
• Brunch / weekend brunch page.
• Kids menu / family-friendly page.
• Late-night dining page where applicable.
• Private dining / event space page.
• Christmas / festive menu page (seasonal, refreshed annually).
• Signature dish pages (the 3-5 dishes the restaurant is known for).
• Wine list / cocktail list page for restaurants where drinks are a draw.
• Group dining / sharing menu page.

Why they rank

Each page targets a specific commercial intent with thin competition. “Sunday roast Hampstead” or “tasting menu Marylebone” or “kids menu [area]” have minimal aggregator competition because aggregators serve generic cuisine-by-area queries, not occasion-specific ones. A well-built occasion page typically ranks within 6–12 weeks because the competition is other independent restaurants.

Restaurant Map Pack ranking is heavily review-velocity driven. Beyond raw count, Google reads review text patterns. Reviews mentioning specific dishes (“the duck was incredible”, “best Sunday roast in [area]”) outrank generic “great food” reviews for those specific queries.

How we generate them

• Integration with your reservation system (OpenTable, Resy, SevenRooms) to trigger review requests post-meal.
• Prompt text encouraging mention of specific dishes (“Tell us what you had so other diners can find us”).
• Timing 24 hours after the meal when satisfaction is still fresh.
• Multi-platform distribution: GBP first, then Tripadvisor, then OpenTable / Resy review section.
• Response drafted for every review on retainer accounts, within 24 hours, signed by named manager.

Target velocity

10–25 new reviews per month for a busy independent restaurant. 50%+ mentioning a specific dish, occasion, or visit context. That density consistently outperforms higher-volume but generic review streams.

Independent restaurants can not outrank Tripadvisor, OpenTable, Resy, Time Out, or The Infatuation on most generic blue-link queries. The right strategy is to be the top-ranked listing within those aggregators where it counts, rather than to fight them on the SERP.

What being the top aggregator listing actually does

• Tripadvisor #1 in your category in your area drives meaningful direct booking traffic.
• OpenTable / Resy top-rated in your category drives the platform’s own algorithm to surface you.
• Time Out, Eater, The Infatuation, and SquareMeal inclusion produces high-authority backlinks plus referral traffic.
• Local press inclusion (Evening Standard restaurant section, Manchester Evening News, Cotswold Life) drives local discovery traffic that often outperforms organic Google.

The outreach workstream

Each retainer includes ongoing outreach to relevant aggregators and local press. Press hooks (new menu launches, head chef news, charity events, supplier collaborations) are surfaced as monthly digital PR opportunities. Aggregator profile optimisation is part of the workstream rather than left to the platform’s default settings.