A rebrand creates a continuity problem
A buyer searches the new business name and finds an old homepage in the results. Google Maps shows the former name. A partner page points to a retired domain. An AI answer describes services the company no longer sells. Each source may be individually understandable, but together they make the business look uncertain.
That's why a rebrand is an identity migration rather than a copy update. The job is to connect the old public evidence to an approved new identity across the website, search systems, profiles, reviews, directories, partner pages, and buyer journeys.
Consistency helps recognition, but it doesn't guarantee rankings, review retention, a Knowledge Panel, an AI citation, or a recommendation. The practical goal is narrower. Give people and systems accurate evidence of what changed, what stayed continuous, and where the current source of truth lives.
If the business hasn't planned a change and you are trying to diagnose inaccurate representation, start with how search and AI systems understand the business. This guide begins when a change is approved or close enough to approval that the migration can be governed.
Define what is actually changing
Start by naming the change precisely. A public brand can change while the registered company remains the same. A company can change its legal name while continuing to trade under an established brand. A new domain can accompany either change. An acquisition, ownership transfer, new service model, or genuinely new business raises different continuity questions again.
Write down the approved old and new values for the public brand, company name, registered business name, domain, locations, contact details, service categories, ownership, and effective date. Name the person who can approve each value. If the team can't agree on these facts, publishing them across more channels will multiply the confusion.
Australian businesses need to keep registry terms distinct. ASIC's company name change process applies to a registered company. ASIC's current business name guidance explains that changing details attached to a registered business name is a separate task. Moving to a different trading name may require registering another business name rather than editing the existing name into a new one.
Registration is only one part of the job. Trademark, tax, contract, privacy, advertising, and ownership questions may need qualified advice. Resolve those questions before search and website teams treat a marketing decision as an authorised identity.
Decide whether the old identity can continue
The highest-risk local decision comes before anyone edits Google Business Profile. Google's current Business Profile rebranding criteria say a profile may be eligible for a minor name change when the proper nouns and described services remain unchanged and the business category remains unchanged. Google also provides an allowance for multi-location businesses whose name changes. A name change outside those criteria is treated as a new business, with the existing profile marked closed and a new profile created.
Apply that rule to the actual rebrand. Don't assume that common ownership, the same address, or a desire to preserve reviews settles eligibility. Material changes to the name, category, services, or business identity need case-specific review. Use platform support when the boundary isn't clear.
Google requires the profile name to match the name used consistently in real-world branding. Its profile editing guidance also warns that edits can require the business to verify again. Before launch, confirm profile ownership and account access, then prepare current website evidence, signage, stationery, or other genuine branding evidence that supports the new name.
Review continuity depends on the eligible route and Google's handling of the change. It isn't something a migration plan can promise. Once the decision is made, use the Google Business Profile guide for ongoing categories, reviews, website alignment, and maintenance.
Build the migration record before launch
Create one working record that every owner uses. It should hold the approved values, systems affected, access status, dependencies, update windows, verification evidence, and escalation route. This prevents the website team from publishing one version while the profile owner submits another.
The record should also separate controlled systems from outside sources. You can update the website, schema, social profiles, and many directory records directly. A newspaper mention, partner page, or review platform may require a request and its own review time. Use the third-party business signal inventory and correction workflow to prioritise those external sources without turning the rebrand plan into an unweighted list of every mention online.
A missed dependency can delay every later change. Give the team a compact control record before distributing the work.
Prepare the website and domain path
A name-only change on the same domain is still a site-wide publishing job. Update the header, footer, about page, contact details, service copy, title tags, descriptions, image assets, alt text, legal references, email templates, forms, downloadable documents, and proof pages that name the business. Search old and new values across templates and content before launch. The structured content guide shows how visible facts, metadata, proof, links, and templates should reinforce the same identity.
A new domain adds a technical site move. Google's current site move guidance calls for testing the new site, mapping old URLs to their new equivalents, using permanent server-side redirects, updating internal links and canonicals, submitting a new sitemap, verifying the relevant Search Console properties, and using Change of Address for a domain move where applicable.
Map each valuable old URL to the closest relevant new URL. Sending every page to the new homepage discards useful page-level context and can produce soft 404s. Keep the old domain under business control and leave redirects in place long enough for users and search systems to encounter the move. Google's guidance recommends keeping redirects for at least a year, while user-facing links may continue to reach the old URLs for longer.
Avoid combining avoidable technical changes. Google recommends changing one thing at a time when a domain move, content management system change, and new layout are all planned. If the commercial launch requires a combined change, raise the testing, monitoring, capacity, and rollback controls accordingly.
Expect Google to recrawl and reindex the site. Search visibility can fluctuate during that work, and no responsible plan can promise a recovery date. Preserve analytics, paid campaign destinations, email links, forms, consent controls, and conversion tracking so the team can distinguish a search issue from a broken buyer path.
Update the canonical organisation record
The visible website should establish the new identity before structured data repeats it. Align the name, truthful alternate name, URL, logo, telephone, address, and public profile links with the approved record.
Google's Organization structured data documentation describes these fields as signals that can help Google understand and disambiguate an organisation. Schema is a declaration layer, not proof that the rebrand qualifies for a search feature.
Preserve a stable @id only when the organisation genuinely continues. Use alternateName when it truthfully describes a recognised alternate identity. Don't use either field to manufacture continuity between businesses that should remain distinct. The Organisation schema implementation guide covers the JSON-LD, stable identifier, validation, and maintenance work in detail.
Sequence profiles and outside sources
Publish the controlled website source of truth, then coordinate the profiles that depend on it. Confirm access before the update window. Prepare new logos, descriptions, URLs, contact details, location evidence, and approved service language in advance. Capture the live state before and after each change.
Start with high-impact sources that buyers use and that other publishers may repeat. Depending on the business, that can include Google Business Profile, LinkedIn, major review platforms, industry directories, social profiles, partner pages, memberships, marketplaces, and press profiles. A source that cannot be changed immediately belongs in a correction queue with an owner and evidence trail.
Multi-location businesses need a location-level plan. Google expects consistent naming across locations within a country, subject to its documented exceptions. Assign ownership for every profile and check whether a central brand change affects local categories, URLs, phone numbers, or verification evidence.
When a founder, author, or expert identity changes with the brand, keep the person's biography, authorship links, employer relationship, and public profiles accurate. The Person and ProfilePage implementation guide is useful for that specific case. A business rebrand alone doesn't require every person record to be rebuilt.
Control the launch day
The exact hour will depend on platform access and review times, but the controlled work needs a clear order.
- Publish the approved website facts and confirm priority pages, forms, and assets are live.
- Activate and test one-to-one redirects if URLs or the domain changed.
- Validate canonicals, internal links, sitemaps, Search Console access, analytics, and conversion tracking.
- Update controlled profiles in the approved sequence, applying Google's rebrand decision before changing Business Profile.
- Check branded buyer journeys from old and new names across search, maps, email, paid campaigns, social profiles, and referral links.
- Record evidence, failures, owners, and escalation actions in the migration record.
Don't mark the migration complete because the homepage looks right. A failed redirect, inaccessible profile, unverified location, broken form, or old campaign link can affect buyers while the visual rebrand appears finished.
Validate the new identity after launch
Start with checks that establish direct facts. Crawl the old URLs and confirm their destination and status. Inspect priority pages in Search Console. Validate the rendered Organization markup against visible content. Confirm the live Business Profile state and check major external sources from a signed-out browser where possible.
Then review representation. Search the old name, new name, domain, phone number, services, and locations. Test representative branded prompts in the AI tools your buyers may use. Record whether an answer shows the former name, mixes identities, or cites stale sources. An AI answer is a useful observation, but it doesn't prove why a system chose that description or when it will change.
Connect those observations to commercial measures. Watch organic landing pages, referral routes, calls, forms, qualified enquiries, and customer questions. A fall in one dashboard isn't enough to diagnose the cause. Redirect integrity, indexation, profile status, tracking, and buyer-facing pages need to be reviewed together.
Off Piste's operational preference is to schedule 30, 60, and 90-day reviews, then adjust the cadence to the scale and risk of the migration. Those dates are management checkpoints, not promises about Google or AI systems. Keep unresolved corrections open until the live source is verified.
Choose the work the migration actually needs
The final decision follows the source of risk. A rebrand with a new domain, architecture, templates, or buyer experience needs strategic website and migration work. The site, redirect plan, content, tracking, and launch controls have to be designed as one system.
A stable website with conflicting profiles, declining search visibility, uncertain indexation, or a large external correction queue needs SEO and AI visibility migration support. The work centres on diagnosis, technical validation, representation, and prioritised cleanup.
Some rebrands need both disciplines under one owner. Begin by approving the identity record and deciding whether Google treats the Business Profile change as an eligible rebrand. Those two controls determine much of the work that follows.