Your Google Business Profile is the most visited page most local restaurants have, and most restaurants treat it as a form to fill out once and forget. The operators who have figured out what a working GBP actually does treat it as an active surface, one that drives map pack rankings, review velocity, and discovery traffic in ways the restaurant website alone cannot.
This is the GBP playbook I run for restaurants. It covers the setup that most operators skip, the ongoing management that separates the map pack first column from the third, and the specific features that are worth the time to implement, including one that Google shut off in late 2025 that a lot of older advice still recommends.
Why does the Google Business Profile matter more than the restaurant website for local search?
For a local search query like "brunch near me" or "Italian restaurant Philadelphia," the Google map pack (the three listings that appear with a map above the organic results) captures a large share of the clicks on that page. Backlinko's analysis of search behavior puts it at 42 percent of people who run a local search clicking a map pack result (Backlinko, Google user behavior study). Organic results below the pack split the remaining attention across ten positions instead of three. A restaurant in the top three of the map pack is reaching a share of attention that would otherwise take a page-one organic ranking to earn, and the map pack is generally the faster of the two to move.
The map pack ranking is determined by the GBP, not the website. Domain authority, backlinks, and most of the traditional SEO signals matter far less to map pack placement than the GBP's own optimization signals do. Between two otherwise similar restaurants, the one with the better-optimized GBP has the real edge in the map pack, regardless of which one has the nicer website.
What GBP setup do most restaurants get wrong?
The setup errors I find in almost every restaurant GBP audit, in order of frequency:
1. The primary category is too broad
"Restaurant" as the primary category is the default and the wrong choice for almost every restaurant. Primary category is not just an important field, it is the single highest-impact ranking factor GBP has: it topped Whitespark's Local Search Ranking Factors report, the closest thing local SEO has to an industry consensus survey, ahead of reviews, links, and every other lever. Choosing a broad category means competing against every restaurant in the city rather than filtering to your specific cuisine type.
The correct primary category is the most specific accurate descriptor of the restaurant: "Italian Restaurant," "Sushi Restaurant," "Brunch Restaurant," "Gastropub." Secondary categories handle the edge cases: "Bar" as a secondary category for a restaurant that also runs a cocktail program, "Catering" for a restaurant that takes private events. If you do nothing else in this article, check this one field.
2. Business hours are not updated for holidays or seasonal changes
Stale hours are a conversion killer even before they are anything else. A customer who calls during hours marked open and reaches voicemail or a closed restaurant does not usually try again, they go to whoever answered, and some of them leave a review about it on their way out. That review then does the ranking damage indirectly, through the review signal, rather than through some direct penalty for the hours themselves.
The fix is a quarterly calendar reminder to review and update GBP hours, plus using the special hours feature in GBP for holidays. It lets you set exceptions without changing the regular schedule, so you can set Thanksgiving hours, Christmas Eve hours, and New Year's hours all at once in fifteen minutes.
3. No menu is linked or it links to a PDF
GBP supports native menu integration via the Menu tab. Restaurants that link to a PDF menu are missing a real opportunity here, but I want to be precise about what the opportunity actually is. Google does not have a supported dish-level or menu rich result, so linking an HTML menu will not get a specific dish surfaced in a special result the way a recipe or a product can be. What it does get you is a menu Google can actually read and index as text, on a page that loads properly on a phone and that you can update in five minutes instead of re-exporting a PDF. That is a real, if less flashy, win: an indexable menu supports your general relevance for dish and cuisine searches, even without a dedicated rich result to point to.
The menu link in GBP should point to an HTML menu page on the restaurant's own domain, not to a PDF, not to a third-party menu aggregator. Third-party links (SinglePlatform, OpenMenu, MenuPages) keep the content off your own domain, so none of the indexing benefit accrues to your site.
4. Treating Q&A as a thing you still need to manage
Older versions of this advice tell you to police your GBP Q&A section: answer unanswered questions, upvote correct answers, pre-populate your five most common questions. Skip all of it. Google discontinued the Q&A feature and its API on November 3, 2025. It no longer exists to manage.
What replaces it, practically, is putting the same information somewhere Google can still read it: an FAQ section on your own website, written in plain question-and-answer language, covering the things people used to ask in that box (do you take reservations, is there parking, do you have a kids' menu, are you dog-friendly on the patio). It will not surface on the profile the way GBP Q&A used to, but it feeds your site's relevance for those exact queries and it is a page you control completely, which the old Q&A box never was.
What ongoing management actually moves map pack rankings?
The GBP signals that correlate most strongly with map pack ranking, in rough order of impact:
Review velocity and response rate
Reviews sit under what Google's own guidance calls prominence, one of the three pillars of local ranking alongside relevance and distance, and Google states plainly that "more reviews and positive ratings can help your business's local ranking" (Google, How Business Profile ranking works). Recency inside that pillar matters more than most operators assume. Whitespark, which runs the annual ranking factors survey, has flagged review recency as one of the more underweighted factors in practice, noting a direct pattern in case data: new reviews track with better rankings, and a dry spell tracks with worse ones (Whitespark, on review recency). The practical read: a steady trickle of new reviews earns more than a large pile of old ones sitting untouched.
On responses specifically, Google's language is more modest than the ranking claim some sites make for it. Google does not classify review responses as a relevance signal. What Google actually says is that replying "shows that you value their feedback" and that "positive reviews and helpful replies can help your business stand out" to a searcher deciding between options. Treat it as a conversion and trust signal for the human reading it, not a lever you are pulling on the algorithm. A brief, non-templated response to every review, positive and negative, is enough to do that job.
Photo recency and volume
GBP surfaces photos by recency as well as quality. A profile with no photos in the past six months reads as stale in Google's measurement. The cadence I recommend: one to two new photos per week, added directly to GBP. The photos should include food (the highest engagement category by a wide margin), interior, and the team. Exterior shots and menu photos are secondary.
Post frequency
GBP Posts (the update cards that appear below the main profile in desktop results and in the panel on mobile) are underused, and worth separating cleanly from ranking. I am not aware of a controlled, published test that shows posting frequency moving map pack position, and I would treat anyone selling posting as a ranking tactic with real skepticism. Post anyway, for a different reason: the profile is where a hungry person actually decides, and a current special in front of them at that moment converts, independent of ranking. The post does not need to be long. A photo, two sentences on a special or event, and a call-to-action button (book a table, order online) is the complete format.
This is the one item in this section that is a conversion lever rather than a ranking one, and it earns its place on those grounds alone.
Booking integration
If the restaurant uses a reservation platform, it should be integrated into GBP via the Reservations feature. GBP supports native integration with OpenTable, Resy, Yelp Reservations, and several regional platforms. An integrated booking button on the GBP ("Reserve a table") is a direct conversion from profile impression to reservation, with no website visit required. For restaurants where reservation intent is a significant part of the discovery funnel, this is the single highest-impact integration in the GBP.
What GBP features are not worth the time?
A few GBP features that are commonly recommended but produce minimal impact for most restaurants:
- Products. The Products tab is designed for retail businesses with inventory. For restaurants, the Menu tab is the correct feature. Adding products that duplicate menu items adds noise without ranking benefit.
- Services. The Services tab is relevant for service-category businesses. For restaurants, menu and booking are the relevant data, the Services feature adds minimal value.
- Identity attributes (women-owned, LGBTQ+ friendly, etc.). These are relevant for filtering in some search contexts, but they are not significant ranking signals and should only be added if they are accurate.
How often should I check the GBP for problems?
The GBP is a live document that can be edited by anyone via Google Maps contributions. Hours, addresses, and even business names can be suggested by users and approved by Google without owner input if the profile is not actively monitored. I recommend a weekly five-minute check: confirm hours are accurate, check for suggested edits that need to be approved or rejected, and respond to any new reviews from the past seven days. A monthly deeper review covers photos and post performance, and now that Q&A is gone, checking your own site's FAQ page for anything new worth adding.
A GBP that is actively managed on this cadence separates itself from one that is set up once and never touched again, mostly because the neglected version accumulates exactly the problems this article covers: a stale category nobody revisits, hours that drift from reality, a review count that stalls, and a menu still sitting in a PDF. None of that is a single dramatic failure. It is a slow accumulation, and it shows up in the map pack over time.
