Explain a rebrand accurately across current pages, historical content and official profiles so customers can understand the old and new identities.
A new logo does not explain what happened to the old business.
AI may keep using an old brand name when historical pages, public profiles and current content do not clearly explain the transition. Publish the relationship between the old and new names, update active identity records and preserve useful history with dates. If URLs changed, handle the migration as a separate technical task.
A rebrand creates several questions a customer may ask: Is this the same company? Does the previous service still exist? Is an old contract or support route still relevant? Who now operates the product? A name announcement that ignores those questions leaves room for an incomplete description.
The correction should tell the truth about continuity. A rename, acquisition, merger and product retirement are different events. Do not write “formerly known as” when it inaccurately implies that two distinct organisations were always the same business.
What relationship should the public record explain?
Identify the actual event and effective date before updating copy. The right wording depends on what changed for customers, not only what changed in the brand guidelines.
| Change | Information readers need | Misleading shortcut to avoid |
|---|---|---|
| Rename | Old name, new name, effective date, continuity | Erasing every reference to the former name |
| Acquisition | Buyer, acquired business and actual operating relationship | Treating all products as immediately merged |
| Product rename | Product identity and current support route | Presenting the product as a newly formed company |
| Merger | New organisation and the status of prior offers | Assuming every old service remains available |
| Discontinued brand | What ended and any supported successor | Calling a different offer an identical replacement |
Review the explanation with the person accountable for the business change. A marketing rewrite should not invent legal continuity or customer rights. Publish only the relationships the company can substantiate.
Where should the transition be visible?
Use a dated announcement for the event and a concise current explanation on the About page or relevant product page. Link the announcement to the maintained current information so a visitor arriving from an old source can understand what applies now.
Update active social profiles, partner records, directories and downloadable company descriptions. Prioritise records that customers encounter and those cited in the inaccurate answer. Keep a record of third-party pages you cannot edit directly.
A useful transition statement might be: “Northline Studio changed its trading name to Northline Works on [verified date]. The team continues to provide the services listed on this website. Current enquiries and support use the contact details below.” This is a writing template, not a claim about a real company.
If services or ownership changed, state those differences instead of using that continuity wording. The reader should leave knowing what is the same, what changed and where to act.
What if the domain or URLs changed as well?
Plan redirects and link updates separately from the brand announcement. Google's site migration guidance describes mapping old URLs to their appropriate new destinations and monitoring the move. A renamed company with the same URLs does not need an invented migration.
When pages move, preserve relevant destinations. An old product link should lead to the current equivalent or a clear explanation of its retirement. Sending every URL to the new homepage can leave customers unable to find the specific information they expected.
Review canonical URLs, internal navigation, profile links and major external references you control. Keep the old domain's role and maintenance responsibilities clear within the team. Technical continuity and factual continuity both matter, but a redirect alone does not explain an acquisition or a changed service scope.
What does a rebrand correction look like in practice?
Imagine a fictional scheduling product called Deskday that is renamed Deskflow. The old blog announces features under the former name, the social profile uses the new name and the product homepage never connects the two. An answer describes Deskday as discontinued and Deskflow as unrelated.
The product team can publish a dated rename explanation, add a short identity sentence to the current product page and update the support links. Historical posts can retain their original titles while displaying a clear link to the current product information. The goal is to preserve history without presenting it as the current offer.
| Record | Action | Evidence of completion |
|---|---|---|
| Current product page | Explain the rename and current offer | Accessible page with verified wording |
| Historical announcement | Keep date and add current reference | Reader can navigate to the maintained product |
| Official profile | Update name, description and domain | Public profile shows the approved identity |
| Third-party comparison | Request a factual identity correction | Publisher confirms or visibly updates the record |
The scenario is illustrative. It demonstrates a correction workflow, not a measured change in an assistant's answers.
Should you delete old-name content?
Keep useful historical content when it has a clear purpose and can be understood in context. A past event, product version or company milestone may legitimately use the former name. Label history and guide current customers rather than rewriting every archive as if the old identity never existed.
Remove or revise active sales claims that are no longer true. A current-looking landing page offering an unavailable service is different from an accurately dated archive. Decide page by page based on the reader's task.
Do not overload every heading with both names forever. The transition explanation should be discoverable and consistent, but the current offer still needs clear titles. Review whether the old-name wording remains useful as public confusion declines.
How do you know whether the new identity is understood?
Track current-name questions, old-name questions and continuity questions separately. “What does Deskflow do?” is different from “What happened to Deskday?” and both differ from a category recommendation. Save the complete answers and cited sources.
Look for three outcomes: correct current name, correct relationship to the former name and correct current offer. A response that adopts the new name but imports a retired service is only partly corrected. Follow the service scope guide for that second issue.
Keep an owner for the transition record after the launch campaign ends. The identity guide helps when the rebrand creates namesake confusion, while business fact governance provides the ongoing change process.
Sources and editorial scope
Reviewed September 23, 2026. Platform-specific statements link to the documentation beside the claim. The workflows and examples are Arrow AI editorial guidance. Fictional scenarios illustrate a method; they are not customer results, measured demand or evidence of ranking gains.
Part of What AI Says About Your Business. Explore Arrow GEO or request a free audit to identify the next public-information gap.
