What changed besides the name?
Write a change statement that distinguishes the brand, legal entity, product names and positioning. A visual refresh may leave the company name unchanged. An acquisition may change ownership while the operating brand remains. Ask the accountable corporate and product owners to confirm which relationships should appear publicly.
Prepare a mapping of old names and URLs to their current equivalents. Include languages and markets where the transition differs. Record the effective date and the expected treatment of historical material. Without this map, editors can accidentally rename a discontinued product or imply that a former legal entity still exists.
Where should the current identity appear?
Prioritize the homepage, about page, product pages, contact details, public documentation and active commercial material. Use a plain transition statement where readers need it. An illustrative statement is: “Example Ledger became Example Finance on 1 September 2026. The service continues to provide invoice reconciliation under the new brand.” Only retain that continuity claim if it is factually correct.
Keep dated history useful. A sentence describing an event under the old name can remain accurate. An AI answer that says “formerly Example Ledger” may demonstrate successful understanding of the change. Count current-name errors separately from appropriate historical mentions.
What should happen to URLs and structured data?
Give the site owner an approved redirect map for replaced pages and verify each destination. Preserve valuable historical pages when their purpose remains. Google's canonical guidance describes redirects and canonical annotations as signals for preferred URLs; consistent implementation matters.
Review organization names, alternate names, URLs and logos in structured data so they match visible information. Google's Organization documentation describes applicable identity properties. Markup can express the identity consistently, but it cannot guarantee recognition by every AI system.
How should external records be handled?
List business profiles, partner directories, public registries and frequently cited third-party pages that need a legitimate update. Follow each record owner's process. Give editors the public announcement and explain exactly which current statement is inaccurate.
If a Wikipedia article is affected, disclose your connection and use the transparent process described in its conflict-of-interest guidance. Avoid treating an encyclopedia as a company-controlled brand page. Its editors determine whether sources support a change and how history should be represented.
How do you measure the transition?
Save a question panel covering current identity, former name, product purpose and ownership. Label each later answer as current and accurate, historically accurate, incorrectly current under the old name, confused entity, or unresolved. Record the relevant quotation and source support.
Report the denominator as the answers inspected under those conditions. If some answers retain the old name, that does not measure the fraction of a model's knowledge that is stale. Use the error log to repair specific evidence and retain a maintenance owner until major records are consistent.
Steps to follow
Define the identity change
Approve names, dates, entity relationships and continuity claims.
Map current and historical surfaces
Assign each page or record a current update, redirect or history treatment.
Update records transparently
Verify owned changes and log third-party requests with public evidence.
Classify transition answers
Separate genuine current-name errors from accurate historical references.
A rebrand evidence transition map
A blank CSV worksheet for your own evidence and decisions.
Download worksheet (CSV)Sources
Put the guide to work
A rebrand evidence transition map
Explore the public playbooks ↗