Moving or Rebranding a Local Business: A Coordinated Online Changeover
Treat a move or rebrand as one coordinated change to your identity, your access and your instructions to customers. Confirm what is continuing, set the effective date, list every public record and keep the old contact routes working while the new details take effect.
A new logo and an announcement are only part of the job. Customers may still land on an old profile, follow an old website link or call the number printed on last year's quotation.
This guide gives the owner a changeover plan to share with staff, a web supplier and whoever manages your profiles.
Establish what is actually changing
| Change | What remains to be established |
|---|---|
| Same business moves premises | Continuity, effective arrival date, access and profile verification implications |
| Same business changes public name | Real-world branding, customer recognition and platform rebrand rules |
| Another branch opens | Genuine branch operation and separate local facts |
| A branch closes while the business continues | Correct closed-location treatment and the route customers should use |
| A different business takes over a site | Separate identity and authority; old reviews/history do not automatically belong to the new operator |
| Website domain changes | Ownership, redirects, email dependencies and measurement continuity |
Settle identity before you edit any record. A platform may treat a major rebrand differently from an ordinary name correction. Do not reuse an old profile as a container for a different business without checking eligibility and continuity.
Name one change owner who can approve the facts and coordinate the effective date. Suppliers can finish their own tasks, but someone inside the business has to check the whole result fits together.
Build the change register
List every important public and operational route. Include the website, map profiles, relevant directories, social profiles, association records, email signatures, printed materials and customer-facing documents.
| Record | Current state | Target state | Dependency | Owner | Public recheck |
|---|---|---|---|---|---|
| Main website | Current domain/name/address | Approved replacement facts | Content, access and any URL plan | Named supplier | Date/result |
| Google profile | Existing managed record | Correct continuing identity/location | Authority and applicable verification | Authorised manager | Date/result |
| Directory profile | Public URL and current facts | Approved details | Access and platform review | Named person | Date/result |
| Phone | Existing routing | Intended continuity or new number | Telecom arrangements and testing | Operations owner | Call result |
| Current domain/accounts | Working addresses and forwarding as agreed | Domain/DNS/provider access | Account owner | Send/receive result | |
| Arrival instructions | Old entrance/location | Correct new destination | Premises ready and date agreed | Location owner | Customer-view check |
Track submitted, approved and publicly checked as three separate states. The transition is not finished because each supplier says its form was saved.
Confirm account access before the deadline
Check domain registration, website administration, Google/profile authority, email and important phone services. Establish recovery responsibility and remove dependence on former employees' personal accounts where possible through the appropriate recovery process.
Do this while the old operation still works. The week of the move is a bad time to find out that nobody can edit a profile, or that your email runs on a domain you are about to cancel.
Use individual supplier permissions where they are supported. A change plan should never depend on a spreadsheet of shared passwords.
If a public profile is already controlled by someone else, resolve access as its own dependency. The Google setup guide explains the ownership paths.
Prepare the website transition
If only facts are changing, identify all places they appear: contact pages, footers, service pages, structured information, maps, downloadable documents and images containing the old branding.
If URLs or the domain change, make a mapping from each important old URL to the most appropriate new destination. Preserve equivalent content where it remains useful. Redirecting every old page to a generic homepage can discard the context of the original visit.
Google's site-move guidance recommends planning URL mappings, implementing the appropriate redirects and monitoring the move. Its guidance includes retaining redirects for at least a year; longer continuity can be useful for customers and old references. Ask the developer to follow the current technical instructions for the actual move. Google's URL-change guidance
Test important old links, including tagged campaign links, on a phone. Check that the destination still answers the service question and that necessary parameters and enquiry routes behave as intended.
Coordinate email and phone continuity
A domain change can affect email as well as the public website. Establish which addresses need to keep receiving messages, how customers are notified and which accounts use those addresses for recovery.
For a phone change, decide how the old route should behave during the transition. Test any forwarding, recorded message or branch routing that has actually been agreed with the provider. Do not assume a forwarding arrangement exists because it appears in the plan.
Protect private messages and account access throughout the change. An old domain or telephone number should not be released casually while it still controls important recovery routes or receives customer information.
Record the real technical outcome with the responsible provider. An announcement is not a substitute for testing that routes still work.
Update the correct Google profile
For a continuing business that relocates, Google's duplicate guidance says to update the existing profile's address rather than creating a new profile at the new location. Relocation and duplicate handling
Google's editing guidance also states that an address change after verification requires verification again, and a business-name change may require it. Plan for the actual review/verification route rather than guaranteeing immediate public visibility. Profile editing guidance
Keep the old and new facts, effective date and confirmation references together. If a duplicate or mistaken separate identity exists, handle it through the appropriate case rather than editing several uncertain records simultaneously.
Do not mark the business permanently closed merely because it is moving and continuing, unless that is the correct treatment for the specific record and platform situation. Check the move instructions for the actual case.
Choose a public effective date
Write the operational promise in customer language: when visits stop at the old premises, when service starts at the new location and what happens during any interruption.
Make announcements consistent with the readiness of the premises, staff and contact routes. An early update can send visitors to an unopened location; a late update can send them to the closed one.
Where platforms review changes asynchronously, record that dependency and provide accurate current website/contact instructions. Do not imply you can control the exact moment every external system reflects the update.
For multiple countries or branches, use the relevant local date/timezone rather than a vague midnight cutover.
A practical sequence
Before the change
Approve the identity facts and effective dates. Confirm access, prepare website content and URL mappings, arrange contact continuity and identify platforms requiring evidence or review. Notify affected staff of the actual customer instructions.
At the agreed transition
Publish the approved website information, apply the prepared technical changes and submit/update the relevant external records through authorised routes. Test the new contact and arrival experience.
Immediately afterwards
Check both old and new customer paths. Record which external changes are public, pending or action-required. Correct the highest-consequence errors first.
During the follow-on period
Review search, enquiries and old-route activity. Maintain redirects/forwarding according to the real arrangements and platform guidance. Retire obsolete material deliberately rather than losing track of it.
The duration of each phase depends on the operation and the services involved. Use the sequence as a dependency plan. It is not a promise that the online move takes a day.
Worked example: a bakery changes premises and its website
The example is fictional. A neighbourhood bakery moves to a larger shop and adopts a shorter trading name. Its website domain also changes.
The owner confirms that the business continues, identifies the accepted new branding and sets the last collection at the old shop and first collection at the new one. The website supplier maps important menu/contact pages to their new equivalents and checks email dependencies before changing the domain.
The profile manager updates the existing eligible profile through the appropriate route and tracks verification/review. The directory owner updates the same branch identity rather than inventing a second bakery solely because the address changed.
After the cutover, the team tests an old printed QR code, an old menu link, the phone route and public directions. An outdated photograph showing the old entrance is identified as a remaining task. The owner keeps that task open until the customer-facing material is corrected.
The process keeps useful continuity and still makes the new facts clear.
Verify outcomes rather than submission counts
A post-change check should include:
- Current name and location on important public pages.
- Correct old-to-new website destinations.
- Working phone and email routes.
- Appropriate address visibility and map/entrance information.
- Accurate hours during the transition.
- Owner access and supplier permissions.
- Measurement notes identifying the date and technical changes.
A change in reported traffic can reflect the site move or measurement configuration. Keep those changes documented before drawing a marketing conclusion.
Use the identity register as the continuing record and the duplicate-listing guide for remaining identity cases. Close the changeover when the important customer paths work and the outstanding exceptions have explicit owners.