Rebranding without losing SEO: the migration plan we follow

When we worked through our own rebranding process at Choco Media, the question that kept us up at night wasn’t the logo or the new name — it was the rebranding SEO risk. We’d spent months building organic visibility, earning backlinks, and signaling topical authority to search engines. The idea of watching that evaporate because we moved URLs or changed our brand signals felt genuinely painful. This post is the migration plan we wish someone had handed us before we started — the redirect logic, the internal link strategy, the content decisions, and the timeline that lets a rebrand happen without a traffic crater.

This isn’t theory. It’s the process we now run with clients going through name changes, domain migrations, and full identity overhauls. If you’re a brand, founder, or marketing lead staring down a rebrand, this is for you. You’ll leave with a step-by-step migration plan you can adapt regardless of the scale of your change.

One caveat before we begin: not every rebrand carries equal SEO risk. Changing your visual identity while keeping your domain and URL structure is low-risk. Moving to a new domain with hundreds of indexed pages is high-risk. The principles below apply across the spectrum — calibrate the depth of execution to your situation.

Why Rebranding SEO Is Riskier Than Most Teams Expect

The common mistake is treating a rebrand as a marketing problem. The logo, the messaging, the new name — that’s the visible work. But underneath it, search engines have built a model of your site: what it’s about, which pages answer which queries, which domains trust you enough to link to you. A rebrand touches nearly all of that.

When you change your domain, you lose the direct link equity that lives on your old URLs unless you redirect it correctly. When you change your brand name, anchor text from existing backlinks no longer matches your brand. When you restructure your site as part of the rebrand, you can create orphan pages, broken internal links, and crawlability gaps that take Google months to re-process.

• Domain changes typically cause a 10–30% traffic drop in the first 1–3 months even when redirects are done correctly — Google confirms this is expected but temporary
• Without proper 301s, a domain migration can look like a site shutdown to crawlers
• Brand name changes affect how backlinks read: a link with anchor text “OldName” pointing to your new domain is still valuable for equity, but it no longer reinforces your brand signal
• Internal link rot — pages that link to old URLs internally — compounds crawl waste and dilutes PageRank flow

Understanding this isn’t meant to discourage rebranding. It’s meant to put the right team in the room before the launch date gets locked in.

Start Here: The Pre-Rebrand SEO Audit

Before you move a single URL, you need a complete inventory of what you’re working with. Think of this as the baseline you’ll measure recovery against.

What to document

• All indexed URLs: Use Google Search Console to export every indexed page. This is your migration checklist.
• Top-traffic pages: Identify the 20% of pages driving 80% of your organic sessions. These are your highest-risk assets.
• Backlink profile: Export your full backlink profile from Ahrefs, Semrush, or a similar tool. Note which pages have the most linking root domains — these need bulletproof redirects.
• Keyword rankings: Capture current positions for your target keywords. You’ll use this to measure recovery post-launch.
• Internal link structure: Crawl your site with Screaming Frog or a similar tool to map all internal links. This becomes the update list when URLs change.

This audit typically takes one to two days for a site with under 500 pages. Don’t skip it. The teams that skip it are the ones calling us four months later wondering why rankings never recovered.

The 301 Redirect Strategy: Getting It Right

The 301 redirect is the load-bearing wall of any domain migration. Done correctly, it transfers roughly 90–99% of link equity from old URLs to new ones. Done poorly, it’s the most expensive mistake you can make in rebranding SEO.

Core principles for your redirect map

• Page-to-page, not page-to-homepage: Every old URL should redirect to its equivalent new URL. Redirecting everything to your homepage wastes link equity and frustrates users who bookmarked specific pages.
• No redirect chains: A 301 pointing to a 301 pointing to a final URL bleeds equity at each hop. Clean up any existing redirect chains before adding a new layer.
• Redirect everything, including XML sitemaps: Your old sitemap URL should redirect to the new one. Your old RSS feed should redirect. Even your robots.txt should be updated if the domain changes.
• Keep redirects live for at least 12 months: Google recommends this as the minimum. We keep them live indefinitely where hosting costs allow.

“The redirect map is the most mechanical part of a migration and the most commonly botched. We build it as a spreadsheet: old URL, new URL, HTTP status to verify post-launch. It takes time to build correctly. It saves weeks of recovery if you do.”

For large sites, consider building your redirect map in stages: high-traffic pages first, then medium, then the long tail. This lets you prioritise verification effort where it matters most. Your SEO strategy needs to treat redirects as infrastructure, not an afterthought.

How to Update Internal Links Without Missing Any

Internal links are how PageRank flows through your site. When you move to a new domain or restructure URLs, every internal link pointing to an old URL becomes a redirect hop — or worse, a broken link if the redirects aren’t in place yet.

The process we follow:

• Run a full crawl with Screaming Frog before launch to export all internal links as a CSV
• Use find-and-replace in your CMS or database to update all internal links in bulk where possible
• For WordPress sites, plugins like “Better Search Replace” can update URLs in the database without manual edits to every page
• After the domain migration, run a second crawl to verify no internal links still point to the old domain
• Check navigation menus, footer links, and sidebar widgets separately — these are frequently missed in bulk updates

The goal is for every internal link to point directly to the correct new URL, not through a redirect. This is cleaner for crawlers and faster for users.

Handling Backlinks: What You Can Control and What You Can’t

Your backlink profile is the one piece of your SEO you can’t fully control. Other sites chose to link to you — they don’t have to update those links when you change your domain. What you can do is make sure the redirects are in place so equity still flows, and reach out proactively to update the most valuable ones.

The outreach priority list

• Tier 1 — update these first: High-authority backlinks from publications, industry directories, and major partners. Reach out and ask them to update the link. Most will.
• Tier 2 — useful to update: Mid-authority links where you have a relationship with the site owner. Worth an email.
• Tier 3 — let redirects handle it: The long tail of links from small blogs, forums, and aggregators. The 301 redirect does the job here.

Also check your Google Business Profile, social media bios, and any paid directory listings — these are easy wins that don’t require anyone else’s co-operation. Our branding work always includes an asset inventory of exactly these touchpoints so nothing gets missed in a transition.

The Content and Keyword Migration Decision

Rebranding often comes with a temptation to “refresh” the content while you’re at it. This is where teams get into trouble. Changing URLs, changing domain, and changing content all at once makes it nearly impossible to diagnose what caused a traffic drop if one occurs.

Our rule: separate the structural migration from the content refresh

• Phase 1 — structural migration: Move URLs, update redirects, update internal links. Keep content identical.
• Phase 2 — content refresh: After rankings have stabilised on the new domain (usually 8–12 weeks post-launch), begin updating or improving pages.

This isn’t always possible — sometimes the rebrand comes with a messaging overhaul that genuinely requires new content. In those cases, keep page structure (headings, schema, format) as consistent as possible while updating copy, and document what changed so you can diagnose issues if traffic drops.

For pages targeting competitive keywords, the most defensible approach is to maintain the keyword targeting through the transition. Your target audience is searching for the same terms before and after you rebrand. Dropping a well-ranking page’s keyword focus during migration adds risk with no SEO benefit.

Schema Markup and Structured Data After a Rebrand

If you’ve implemented schema markup — and you should have — a domain change requires updating several structured data types that reference your brand or domain explicitly.

• Organization schema: Update the url, name, logo, and sameAs fields to reflect your new brand identity and domain
• BreadcrumbList schema: Any breadcrumb markup using absolute URLs needs to reference the new domain
• Article and BlogPosting schema: The publisher field references your organisation — update this globally
• LocalBusiness schema: If you’re a local business (as we are in Rovaniemi), update your name and URL fields here
• Sitelinks Searchbox: If you had this implemented, it needs to be updated with your new domain target

Use Google’s Rich Results Test after launch to verify structured data is valid on your key pages. Errors in schema won’t cause a ranking penalty, but invalid markup means missed opportunities for rich results.

The Migration Timeline: What Happens When

The most common mistake in rebrand migrations is trying to do everything at once over a single weekend. In our experience, the migrations that go smoothest are the ones that use a staged rollout with monitoring checkpoints between each phase.

A realistic timeline for a mid-size site (50–500 pages)

• Weeks 1–2: Full SEO audit, redirect map build, internal link inventory, keyword baseline capture
• Week 3: Set up new domain on staging, implement all redirects, update all internal links, update schema
• Week 4: QA crawl on staging — verify redirects, check for broken links, validate schema
• Launch week: Go live on new domain, submit updated XML sitemap to Google Search Console, update GSC property, verify redirects in production
• Weeks 1–4 post-launch: Daily monitoring of GSC for crawl errors, index coverage drops, and ranking movements. Don’t panic at normal fluctuations.
• Weeks 8–12 post-launch: Rankings typically stabilise. Begin Tier 1 backlink outreach for link updates. Assess traffic recovery vs. baseline.

If you’re working with a domain that has significant link equity — say, a domain with 500+ referring domains and years of history — build in an extra two weeks of QA before launch. The more equity at stake, the higher the cost of a mistake.

For a deeper look at how our conversion and website services integrate with rebrands, see our websites and funnels work — getting the new domain set up for performance from day one is part of the same conversation.

Monitoring and Recovery: What to Watch After Launch

Launching the new domain isn’t the end of the migration — it’s the beginning of a monitoring period. Here’s what we track and for how long.

• Google Search Console — Coverage report: Watch for “Excluded” pages that shouldn’t be excluded, crawl errors, and redirect errors. Check daily for the first two weeks.
• Organic traffic in GA4: Segment organic traffic by landing page to see which pages have recovered vs. which are still depressed. Week-over-week comparisons are more useful than day-over-day here.
• Keyword ranking movements: Run weekly rank tracking for your top 50 target keywords. Expect volatility in weeks 1–4. If rankings haven’t begun recovering by week 12, dig into the technical audit — something in the migration went wrong.
• Crawl rate: Google should start crawling the new domain aggressively after migration. A low crawl rate suggests the redirects aren’t being followed correctly.
• Index count: The number of indexed pages on the new domain should climb toward your pre-migration indexed count over 4–8 weeks.

In client work, we typically set up a shared reporting dashboard during migration so the team and client can see all of these signals in one place without needing to pull reports manually. Transparency during a migration period reduces panic — most traffic dips are temporary and expected, but they look alarming without context.

The Most Common Rebranding SEO Mistakes We See

After running a number of these migrations, patterns emerge in what goes wrong. These are the mistakes worth specifically protecting against.

• Launching without verifying redirects in production: Redirects that worked on staging sometimes don’t work in production. Always verify with a crawl tool immediately after launch.
• Blocking the new domain with robots.txt during development: If you built the new site while blocking crawlers and forgot to unblock before launch, you’ve just launched an invisible website. Check robots.txt on day one.
• Forgetting to update Google Search Console: Add the new domain as a property, submit the new sitemap, and use the Change of Address tool if you’re migrating domains. Google’s documentation on this process is unusually clear and worth following exactly.
• Changing too much at once: URL structure + domain + content + design simultaneously. Each of these is a separate risk factor. Stack them and you lose the ability to diagnose problems.
• Announcing the rebrand before the SEO migration is complete: PR momentum is real, but a flood of links pointing to a domain that isn’t live yet — or that redirects poorly — wastes earned attention.

If you’re planning a rebrand and want a second set of eyes on the migration plan before you launch, reach out and we’ll walk through it with you. A 30-minute conversation before launch is worth considerably more than six months of recovery work after.