How to rebrand a restaurant without losing search visibility

A restaurant rebrand can lose search visibility without a single technical failure. The new sign goes up, but the Business Profile keeps the old name. The website changes domain, but old menu links return errors. Booking platforms use a third version. Guests search the old brand and cannot tell whether the restaurant moved, closed or became something else.

This decision governs everything that follows. Google says a business should be represented as it is consistently recognised in the real world and should have only one profile. Its review guidance says minor name changes can retain reviews, while a name change outside its criteria may be considered a new business. A dramatic change in name, category, ownership model and customer experience should not be disguised as a minor edit simply to keep review history.

Source: Google Business Profile Help — Guidelines for representing your business — Google's rules on real-world representation, accurate categories and one profile per business.

Source: Google Business Profile Help — Move reviews across profiles — Google's current distinctions for ownership, relocation, minor name changes and materially new businesses.

Add an owner, target date, completed date and verification method beside each item. The purpose is not bureaucracy. It prevents the common half-rebrand where the website, map pin and booking confirmation each tell a different story.

1. 01Secure owner access and record the existing profile ID, links, categories, photos and performance baseline.
2. 02Finish the real-world evidence: permanent signage, website identity and official customer-facing materials.
3. 03Update the existing profile only when the new identity is genuinely in use.
4. 04Use the fewest accurate categories; do not stuff the new name with cuisine or location keywords.
5. 05Update menu, reservation, order and social links in the same session.
6. 06Watch for reverification requests, rejected edits, duplicates and guest-suggested changes.
7. 07Search both old and new names while signed out and from several locations during the transition.

Google may review profile edits, and some changes can trigger verification. Build time for that uncertainty into the launch rather than promising the team that every surface will switch at midnight.

Source: Google Business Profile Help — Edit your Business Profile — Google's process for editing verified profile information and reviewing changes.

A domain migration is not one redirect from the old homepage to the new homepage. Build an old-to-new URL map. The old private-dining page should go to the new private-dining page; the old menu should go to the new menu; every location should go to its matching location. Keep redirects live for as long as practical, update internal links and canonical tags, and submit the new sitemap.

Google recommends permanent server-side redirects such as 301 or 308 for permanent moves, changing one thing at a time where possible, testing the redirect map, and keeping redirects for at least a year. Temporary ranking fluctuation can happen while Google processes a move; that is different from losing the old pages entirely through errors.

Source: Google Search Central — Site moves with URL changes — Google's migration sequence, redirect guidance, monitoring and one-year minimum recommendation.

Source: Google Search Central — Redirects and Google Search — Google's guidance on permanent redirects and choosing the most relevant new destination.

Redirects preserve the route for guests and search engines, but they are not the last step. Update important press, tourism, supplier and partner links when the publisher is willing; prioritise pages that already send referral traffic or point to a commercially valuable old URL. Update the visible name, address, phone, menu and booking route together with LocalBusiness structured data. The markup should confirm the page — never carry an old identity the visitor cannot see.

Review continuity is valuable only when the reviews still describe the business a guest will visit. For a minor rename or ownership change with the same name, Google says reviews generally remain. If the restaurant is materially different, old reviews can be irrelevant; Google may not move them. The honest approach is to explain the transition publicly, answer recent reviews where useful, and begin earning current feedback under the new experience.

Do not treat review retention as a launch guarantee. Document the existing profile, avoid duplicates and follow Google's support route if eligible reviews disappear after an accurate change. Google names categories — including hotels — where reviews do not automatically move with a relocation. A restaurant inside a hotel or another multi-use venue should therefore confirm the profile's category-specific treatment instead of assuming continuity.

A name, domain, site structure, booking provider, menu format and analytics setup can all change during a rebrand, but changing every layer together destroys the ability to diagnose a loss. Freeze avoidable changes. Preserve URL paths where they still make sense, keep measurement identifiers and conversion definitions stable, and record each unavoidable change with an owner and timestamp.

Keep the old analytics and Search Console history. Mark the date of the name, domain, menu and profile changes. Compare like with like: branded searches will split between old and new names for a while, so read them together. Keep call, direction, booking and revenue outcomes beside rankings. A clean new dashboard that discards the baseline makes the rebrand impossible to judge.

Written by

Alex Opsenica

Founder, Moolah Media

Founder of Moolah Media, a founder-led restaurant marketing specialist based in Ireland, working with restaurants worldwide on websites, SEO and Google Maps, and Google Ads. Around 20 years in hospitality, including hands-on restaurant management.

More about how Moolah works.