Discussion starter: an entity SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Entity SEO
Merging two brands after an acquisition: how did you migrate the entity, knowledge panel and sameAs profiles without losing brand SERP features?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
Treat the entity migration as a separate workstream from the website migration, because redirects move pages but do not move a brand’s identity across the web. The pieces are the brand architecture decision, a page on the new site that explains the change and targets searches for the old name, Organization markup that describes the relationship honestly, renamed rather than recreated social profiles, updates to the knowledge sources Google draws on, and consolidation of review and business profiles. Brand results for the old name will persist for months or years, so the aim is not to erase them but to make every result point people to the new brand.
Decide the brand architecture first
Approach What happens to the acquired brand Entity implications Absorb Retired; everything moves to the acquirer’s brand Old entity should point to the new one; redirects and explanatory page are essential Endorse “X, part of Y” for a transition period Both entities remain, connected by parent and subsidiary relationships Keep Continues as a separate brand Mainly adding the parent relationship; little migration Most entity problems after acquisitions come from not deciding, or from deciding late, so that the website moves before anyone has planned what happens to profiles, listings and knowledge sources.
The migration workstream
- Website. One-to-one redirects from the old site to the equivalent new pages, kept indefinitely. A dedicated page such as “X is now Y” that uses the old brand name clearly, explains the change and links onwards. It will receive old-brand searches for a long time.
- Structured data. For an absorbed brand, the new brand’s Organization markup can mention the former name where it is genuinely used, such as in the explanatory page’s content. For endorsed or kept brands, use parent and subsidiary relationships to connect the organisations.
- Social profiles. Rename and rebrand existing profiles where platforms allow, rather than creating new ones, so followers and history carry over. Update
sameAslinks accordingly. - Knowledge sources. Update Wikidata through its normal processes, for example recording that the organisation was acquired or replaced, with references. Wikipedia articles are updated or merged by editors under their own policies; provide sources, do not edit promotionally.
- Business Profiles. Rename or merge location profiles; expect reverification for name changes; avoid duplicate profiles for the same location.
- Review platforms and directories. Many platforms have processes for company name changes or profile merges. Consolidate reviews where possible rather than starting from zero.
- Knowledge panels. Claim the panels for both brands and suggest edits with public sources once the change is announced.
Protecting brand results during the transition
- Keep the old domain registered and redirecting; letting it lapse invites someone else to use it.
- Monitor searches for the old brand name: which results appear, and whether they lead people to the new brand.
- Update high-value third-party references, such as major directories, partner pages and marketplace listings, to the new name and URL.
- Keep the old brand name on the explanatory page and in relevant content for as long as people search for it.
- Watch sitelinks: they depend on the new site’s structure and may take time to reappear for the new brand.
Hypothetical example:
A software company acquires a smaller competitor and absorbs its brand. It redirects the old site page by page, publishes “Acme is now part of Northwind” with a guide for existing customers, renames the acquired brand’s LinkedIn and YouTube channels, updates Wikidata with the acquisition and references, and asks the review platform to merge the product’s reviews into its own listing. Searches for the old name show the explanatory page near the top within weeks. A year later the old brand still receives searches, but every result leads to the new brand, and the knowledge panel for the old name mentions the acquisition.
Watch for this:
Creating new social accounts and abandoning the old ones leaves the old brand’s profiles orphaned, still appearing for brand searches and sometimes sending customers to unmanaged accounts. Rename where possible, and where not, post a final message pointing to the new accounts and keep the old ones secured.
Expect a long tail
Customers, journalists and systems will refer to the old brand for years. Assistants trained on older data may describe the old company as independent. Knowledge panels may keep old facts until sources are updated. That is why the explanatory page, the redirects and the updated knowledge sources matter more than any single quick fix: they make sure that whatever someone finds under the old name leads to the right place and the right facts.
Decide the brand architecture before the migration, run the entity work alongside the site move, rename profiles rather than recreating them, update the sources Google and assistants rely on, and keep a page that answers the old brand name for as long as people search for it.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.