Rebrand or repositioning
A rebrand is a Consistency problem at scale. The old meaning lives in customers' heads, in third-party profiles, in cached pages and in what models learned. The work is to define the new meaning precisely, prove it is real, replace the old evidence everywhere it is placed, and give machines an unbroken path from old entity to new.
The name, category, audience or promise is changing, and every existing association, human and machine, is now partly wrong.
Meaning, then Signals. The new identity has to be explicit before anything else, and the technical continuity (redirects, identifiers, sameAs) decides whether machines carry the old authority forward or start from zero.
Define. Prove. Distribute. Enable.
- New canonical identity, with explicit statement of what changed and what did not.
- Alias map: every old name, product name and URL that should resolve to the new entity.
- Revised ICPs and message architecture; retire vocabulary that belongs to the old position.
- Prompt universe re-run: which old associations should persist, which must go.
- Evidence that the new position is true now: outcomes, customers, experts under the new name.
- Case studies and references updated or re-attributed with customer consent.
- Expert and founder entities carried across with continuity statements.
- Correction requests to every third-party profile, directory, review site and publisher that still describes the old entity.
- Announcement coverage that states the relationship between old and new in plain words.
- Paid and owned channels switched on the same date with the same architecture.
- Community and customer advocates briefed first, so the first explanations in the market are accurate.
- Redirect map, canonical consolidation and updated identifiers; sameAs linking old and new where they are genuinely the same entity.
- Schema and EntityMap updated with the alias relationships, then recrawl requested.
- Fact register as the single source for every surface during the transition; dated changelog of what changed.
- Feeds, marketplaces, agents and voice surfaces updated, not left to pick up the change later.
Use a baseline, not a vibe.
Share of model descriptions using the new name and position; third-party profiles corrected; old-name search and prompt traffic resolving to the new entity; message recall for the new position in the ICP.
Changing the name and the position in the same week with no alias map is how a brand loses its Authority in retrieval. Never let the old entity simply disappear.
Run the audit first.
The playbook assumes you know the constraint. The 24-statement audit takes ten minutes and tells you which pillar and which reader to start with.