Google ranks URLs and entities, not your new palette
Equity sits on documents and the entity those documents describe. Paint is not a ranking factor. If the rebrand only changes CSS and images, treat it as a design launch. If it changes slugs, titles, and legal name, treat it as a migration.
Refresh versus rename: different ranking risks
Refresh: swap assets, keep H1s unless they were lies. Rename: people will search the old name for years — keep a legacy mention, 301s, and a clear “formerly” on About for a while. Ego wants to erase history; Search wants a bridge.
Redirect map before the launch party
Spreadsheet: old path, new path, status, owner, tested. No leftover chains. No homepage dumps for every blog URL. Launch without this map is how you discover the problem in week six.
- Crawl the old site before DNS or theme cutover
- Preserve high-traffic URLs when the content is still true
- Fix internal links; do not rely only on 301s
- Watch Search Console and GBP for 14–28 days after
Domain, legal name, and GMB as one story
Pick one canonical story. A new domain with the old trading name and a third GST print name is three brands. Trademark and ROC changes: should you trademark and your CA, not the designer alone.
Content you must rewrite, not just restyle
Service pages that named the old offer. Author bios. Schema LegalName. OG images that still show the retired mark. If you chase AI Overviews and citations, stale entity names in Binderr-length guides will keep teaching the old world.
GEO and Binderr-length pages after a rename
Generative systems cite clear, current pages. Update the answers, FAQs, and llms-style indexes if you keep them. Do not ship forty thin “new brand” locations instead of repairing the URLs that already had proof.
How Brevia sequences identity and SEO from Chennai
Kit freeze → URL inventory → build or restyle → redirect QA → GBP/NAP day → content pass. UI/UX from ₹50,000 if templates change. Website if the stack moves. Identity from ₹25,000 is the look; migration is scoped beside it. Contact.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.