Name the relationship
Use plain language that identifies the former name and current name.
Branding guide · Rename continuity
A new name must carry old memory before the old cue disappears.
A rename changes more than a word. It changes what people type, say, remember, link to, recognize, and trust. The transition works when old and new names point to one entity, one destination, and a deliberate recognition bridge.
One entity State clearly that the old and new names refer to the same company, product, or service.
One destination Redirect old domains and routes directly to the current canonical answer.
One bridge Keep enough visual, verbal, and operating continuity for buyers to recognize the change.
Name-change Search-memory Risk
name · entity · route · bridge
01
What a rename puts at risk.
Typed memory People continue searching the old spelling, abbreviation, or product name.
Spoken memory Referrals use the name people learned before the change.
Linked memory Articles, citations, bookmarks, and partner references keep the old address.
Visual memory The old name may be attached to color, shape, package, place, or service cues.
Entity clarity Search systems can treat old and new names as different entities when the relationship is vague.
02
Build the recognition bridge.
Run the transition long enough for people and machines to connect both names to one current entity.
Carry every important route
Send old domains and paths to the closest current destination in one hop.
Keep a useful cue
Carry forward a color, shape, product, service, place, or verbal element buyers already know.
Teach the connection
Use the bridge across homepage, product, support, media, and partner surfaces.
Align public records
Change canonical tags, profiles, structured data, feeds, and ownership references.
Watch old-name demand
Track old queries, referral language, missed routes, and confusion before removing the bridge.
03
Rename risk by symptom.
undefined
Symptom
Likely break
Repair
Evidence
Old name dominates search
The connection is under-taught
State former and current names together
Query and referral patterns
New name is mistaken for another entity
Category and ownership are unclear
Add explicit entity and offer language
Search results and support questions
Direct traffic falls
Old domains or routes were lost
Restore ownership and one-hop redirects
Access and redirect logs
Customers ask whether the company closed
The continuity message is missing
Show the operating bridge
Support and sales language
The name is remembered but not the offer
The category cue disappeared
Reconnect name, product, and buying situation
Buyer recall interviews
04
Rename release checklist.
- The old and new names resolve to one entity.
- Old domains and routes have controlled destinations.
- A useful recognition cue crosses the transition.
- Products, services, and category remain explicit.
- The team can monitor old-name demand.
- The new name needs explanation to reveal the category.
- The old domain can expire or be captured.
- Support and sales use different transition language.
- All familiar cues disappear at once.
- There is no route plan for old links and citations.
05
Use this for your brand.
Pressure-test the decision before buyers do.
If a name, color, mark, message, voice, or page is starting to affect sales or trust, get the public-facing decision checked before rollout makes it harder to change.
06
Useful sources and next pages.
Decision guide Should You Rename Your Company? Decide whether the change earns its cost.
Guide Brand Naming Evaluate the replacement name.
Guide Brand Recognition Protect useful recognition cues.
Brand page FedEx Naming continuity tied to an operating promise.
Brand page Gap Recognition disruption and reversal.
Brand page Meta Corporate naming and product-entity separation.
Brand page Alphabet Parent-company naming and product continuity.
Brand page Mastercard Name and visual continuity across simplification.