Updating stale brand data in SI models after a rebrand
Why does SI keep describing your old brand after a name or identity change? Learn how to plan the transition and clean up outdated information step by step.
Outdated brand information in SI models after a rebrand is updated by explicitly linking the new name to the old one, consistently updating the brand’s own sources and external sources, and regularly monitoring this change in SI answers. A brand that changes its name, logo or positioning can launch its website, social media accounts and ads with the new identity from launch day. For SI models, however, the change does not happen at the same speed. When ChatGPT or Gemini is asked about the new brand name, the answer may be “I could not find a company by that name”, while asking about the old name may produce a description of services the brand no longer offers. This is because part of a model’s knowledge comes from training data and part from real-time web search, and the two sources update at different speeds. Brands that plan a rebrand only as a design and communications project can remain stuck between two identities in SI answers for months. In this guide, we look at why the model keeps remembering the old name, what needs to be prepared before the transition and which sources should be updated in what order.
Why does the model keep remembering the old brand name?
The model keeps remembering the old brand name because its training data contains thousands of texts that described the brand by its old name for years, and the new name does not appear in them at all. A language model’s training data is frozen at a certain date; changes after that date do not enter the model’s own knowledge until a new model version is trained. If the rebrand took place after that date, the model does not recognise the new name and passes on information about the old name as if it were current.
In answers that run real-time web searches, the situation changes faster, but a different problem arises here too. The number of pages on the web containing the old name is far greater than those containing the new name. News, business directories, job postings, forum comments and partners’ websites continue to use the old name. When the model searches, the weight of these sources can overshadow the few sources containing the new name. Moreover, if the new name is a common word or the same as another company’s, the model may not associate the new name with the brand at all. Together, these two mechanisms create a long transition period after a rebrand in which the old and new identities appear mixed in SI answers.
What should be prepared before a rebrand?
Before a rebrand, the brand’s current SI visibility should be recorded, the sources that mention the old name should be inventoried and the communication copy that links the old and new names should be prepared. Work after launch is unavoidable, but doing the preparation in advance shortens the transition significantly. In particular, testing how the new name will be perceived in SI answers during the naming stage prevents problems that are hard to solve later.
The preparations to complete before a rebrand are:
- Recording the current state: Recording which questions the brand appears in within SI answers, with which information and based on which sources; this record is the basis for comparison after the transition.
- Pre-testing the new name: Asking about candidate names on different SI platforms to check whether they are confused with another company, product or concept.
- Source inventory: Listing the business directories, news sites, partner pages, comparison platforms and social profiles that mention the old name.
- Preparing a bridge sentence: Writing a standard definition sentence that mentions the old and new names together, in the form “X, formerly known as Y, …”.
- URL and redirect plan: If the domain is changing, identifying the equivalent of every page on the old domain at the new address.
- Press and partner communication: Planning which publications and partners will be informed of the change, and with what copy.
Who will build the link between the old and new names?
The brand itself should build the link between the old and new names; expecting the model to build it on its own prolongs the transition unnecessarily. The most effective method is to explicitly mention the old name in every important context where the new name appears. The about page, the homepage introduction, the corporate boilerplate in press releases and social media profile descriptions should be updated with a consistent definition containing the phrase “formerly known as”.
This link should also be built in structured data. The old name can appear in the alternateName property of the Organization markup, linking searches for the old name and sources written with the old name to the same entity. It is also helpful to prepare a separate page or announcement that describes the rebrand itself. This page should clearly explain the date of the change, the reason for it, and what has changed and what has stayed the same. When users and models ask “what happened to company Y?”, this page becomes a direct and reliable source of answers. Even if the old name falls out of use over time, it is recommended that this bridge be maintained for at least several years.
Are 301 redirects enough for SI too?
301 redirects are necessary because they move bots and users visiting old addresses to new ones, but they do not resolve identity confusion in SI answers on their own. Redirects ensure that value from pages linking to the old domain is passed to the new domain and that bots discover the new pages. However, as long as texts in external sources continue to be written with the old name, the model may struggle to associate the name used in those texts with the new brand. Redirects should therefore be applied together with the bridge sentence and external source updates. Page-by-page redirects produce far healthier results than redirecting all old addresses to the homepage.
Which external sources should be updated first?
The external sources to update first are those most frequently cited in SI answers and those that carry the brand’s core identity information. Because it is usually not possible to update every source at once, prioritisation is needed. The record made before the rebrand is the most reliable basis for this prioritisation, since it shows which sources are actually used in SI answers.
| Source | Why It Matters | Priority |
|---|---|---|
| Google Business Profile and map listings | Used directly in local queries and Google’s SI answers. | Launch day |
| LinkedIn company page and official social profiles | Frequently consulted for company identity questions. | Launch day |
| Wikipedia and Wikidata records | Treated by models as strong references in defining entities. | First week, in line with community rules |
| Industry directories and comparison platforms | Used as sources in product and service comparisons. | First two weeks |
| Partner and reseller websites | Contain copy introducing the brand’s products or services. | First month |
| News sites and old press releases | The most persistent content written with the old name; supported with new coverage rather than correction. | Alongside the launch announcement |
Changing old articles on news sites is usually neither possible nor necessary; these articles carry correct information for the period in which they were written. What needs to be done here is to ensure that new coverage announcing the rebrand mentions the old and new names together. That way, when the model reads an article written with the old name, it has a link through which it can reach the new identity.
How should the narrative be built if products or services also change?
If the rebrand is not only a name change but also includes a change in the product or service range, what has been dropped and what has been added should be explained clearly. Otherwise, the model continues to describe services the brand no longer offers, based on old sources. For example, a company moving from hardware sales to software services may be presented as a hardware seller in SI answers for a long time and recommended to the wrong users.
In this case, the rebrand announcement should set out the brand’s new focus with a clear definition and clearly state what happens to discontinued services. If pages for old services are to be removed, they should be redirected to the relevant new service pages or to the page explaining the change. Questions frequently asked by existing customers, such as how support for old products will continue, should be answered in a separate Q&A section. This approach ensures both that existing customers are directed correctly in SI answers and that the new target audience is reached with the right identity.
What should be monitored in the first months after a rebrand?
In the first months after a rebrand, teams should monitor whether the brand is recognised in questions asked with the new name, whether questions asked with the old name are redirected to the new identity and which sources are used in answers. On platforms that run real-time searches, improvement usually starts within weeks, while old information may remain longer in answers based on training data. This difference is normal and should be built into the transition plan’s timeline.
As part of its GEO consulting, Webtures joins rebrand projects before launch, tests what candidate names evoke in SI answers, inventories the sources where the old name lives on and builds the transition plan according to the priority of those sources. When questions about the old name, the new name and the brand’s service area are tracked through the same prompt set with a GEO tool such as Brantial after launch, it becomes visible over time on which platforms the new identity has settled and where old information still dominates. This monitoring also shows concretely which sources and content the rebrand budget should be directed to after launch.
