---
title: "Plan a rebrand that keeps your organic search traffic"
description: "Rank the SEO risk of a rebrand, keep the domain when you can, map every redirect, and monitor recovery for 90 days so organic traffic survives."
canonical: "https://scalewithsearch.com/articles/seo-during-rebrand-executives"
date: "2026-03-20"
modified: "2026-09-25"
---
## Site navigation

- [Scale With Search](https://scalewithsearch.com/)
- Real estate
  - Real estate
    - [Real estate](https://scalewithsearch.com/for/real-estate)
- Work
  - Start here
    - [Send your brief](https://scalewithsearch.com/work#send-your-brief)
    - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief)
  - Build
    - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work)
- For your business
  - Trades and home services
    - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops)
    - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair)
    - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors)
    - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors)
    - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning)
    - [Locksmiths](https://scalewithsearch.com/for/locksmiths)
    - [Moving companies](https://scalewithsearch.com/for/moving-companies)
    - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies)
    - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors)
    - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage)
    - [Roofing companies](https://scalewithsearch.com/for/roofing-companies)
    - [Towing companies](https://scalewithsearch.com/for/towing-companies)
    - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping)
    - [Solar installers](https://scalewithsearch.com/for/solar-installation)
    - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction)
    - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving)
  - Practices and professional services
    - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices)
    - [Dental practices](https://scalewithsearch.com/for/dental-practices)
    - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms)
    - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics)
    - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms)
    - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics)
    - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness)
    - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health)
    - [Medical billing companies](https://scalewithsearch.com/for/medical-billing)
    - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies)
    - [Financial advisors](https://scalewithsearch.com/for/financial-advisors)
    - [Property management companies](https://scalewithsearch.com/for/property-management)
    - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing)
    - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers)
    - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain)
  - Agencies, MSPs, and manufacturing
    - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers)
    - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing)
    - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers)
    - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants)
    - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators)
  - Restaurants, shops, studios, and nonprofits
    - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality)
    - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce)
    - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers)
    - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits)
  - [All industries](https://scalewithsearch.com/for/)
- Learn
  - For your office
    - [Office job guides](https://scalewithsearch.com/guides/)
    - [Browser calculators](https://scalewithsearch.com/tools/)
  - Start here
    - [How it works](https://scalewithsearch.com/how-it-works)
    - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip)
    - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip)
  - Guides
    - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide)
    - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business)
    - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide)
  - Articles by cluster
    - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide)
    - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business)
    - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide)
  - For machines
    - [llms.txt](https://scalewithsearch.com/llms.txt)
    - [llms-full.txt](https://scalewithsearch.com/llms-full.txt)
    - [Machine view](https://scalewithsearch.com/?view=machine)
- Company
  - Evidence
    - [Proof](https://scalewithsearch.com/proof)
  - Company
    - [About](https://scalewithsearch.com/about)

# Plan a rebrand that keeps your organic search traffic.

The leadership team approved a new name. The agency delivered a logo. Someone suggests a new domain to match. Nobody has asked what happens to the 12,000 pages that Google indexed under the old domain.

A rebrand can change the domain, the URL structure, and the positioning at once. Each change disrupts how search engines index and rank the site. A poorly executed rebrand can remove a large share of organic traffic for good. Careful planning, conservative technical execution, and close monitoring after launch protect that value.

## Rank the risk of your rebrand

Each type of rebrand carries a different level of SEO risk.

| Rebrand type | What changes | Planning range for traffic effect |
|---|---|---|
| Visual rebrand | Logo, colors, design | 5 to 10 percent temporary fluctuation. The new design must keep mobile usability, page speed, and content access. |
| Name change, same domain | The brand name only | 10 to 20 percent loss, with recovery in 6 to 12 months. Domain authority and backlinks stay intact. |
| Domain migration | `old-brand.com` becomes `new-brand.com` | 15 to 25 percent loss in the first 3 to 6 months even with perfect execution. Common mistakes push losses to 40 to 60 percent or more. |
| Complete repositioning | Audience, product focus, or category | 50 to 80 percent loss. Old content and keywords stop being relevant, and you build a new presence from scratch. |

The ranges are planning allowances for sizing the risk, not measured rates. Replace them with your own forecast once the audit is done.

Change as little as possible at once. The more you change together, the harder it is to diagnose a problem. Separate the stages where you can: update the brand identity in one quarter and migrate the domain two quarters later. Each stage then has its own measurable effect. You can fix one problem before the next one adds to it.

## Decide whether the domain must change

Many rebrands keep the existing domain and avoid migration risk entirely. When Facebook's parent company renamed itself Meta in 2021, the Facebook product kept `facebook.com`. People still searched for "Facebook", and the old name carried enormous equity.

A domain change is justified only in these cases:

- the old brand carries negative associations that damage the business;
- the new domain is much clearer or more memorable, which is rare;
- a legal requirement, such as a trademark dispute, forces the change;
- the new domain is a strategic asset in its own right.

A stakeholder may want a new domain only because it "sounds better". In that case, push back with data on the risk and the cost. An established domain holds organic value that a new one must rebuild.

## Plan three to six months ahead

### Record the baseline

Capture the current state before you change anything:

- all organic keywords and rankings from Google Search Console, Ahrefs, or Semrush;
- every URL that received organic traffic in the last 12 months, from Google Analytics;
- the complete backlink profile, with referring domains and anchor text;
- current domain authority metrics;
- screenshots of key results and features, such as featured snippets and People Also Ask;
- current organic traffic, conversion rates, and attributed revenue.

The baseline lets you measure the rebrand's effect and justify recovery work if traffic falls.

### Audit the technical scope

Count the URLs, because page count drives migration complexity. Record the URL patterns and whether they will change. Map the internal links and the XML sitemap structure. Note the CMS and hosting constraints and every third-party integration, such as analytics and tracking.

Cost scales with page count, the number of templates, and the number of URL patterns that change. A 50,000-page migration costs far more than a 500-page one. Know the scope before you commit.

### Set the timeline

1. Months 1 and 2: planning, documentation, and technical assessment.
2. Months 3 and 4: development and tests in a staging environment.
3. Month 5: technical validation before launch and stakeholder alignment.
4. Month 6: launch.

Launch in your slow season. Ecommerce should avoid November and December. B2B should avoid quarter-ends. Tax software should avoid January to April. A traffic dip in peak season costs the most revenue. Sometimes an acquisition deadline or a legal deadline forces a bad date; plan extra monitoring when it does.

### Split the budget

| Budget area | Share |
|---|---|
| Technical implementation | 40 to 50 percent |
| Testing and QA before launch | 20 to 25 percent |
| Monitoring and fixes after launch | 20 to 25 percent |
| Contingency reserve | 10 to 15 percent |

Most organizations under-budget the work after launch. Reserve real capacity for the first 90 days.

## Execute the domain migration

If the domain must change, careful execution limits the damage. The full procedure is in the [site migration SEO checklist](/articles/site-migration-seo-checklist).

### Build the redirect map

1. Create a spreadsheet that maps each old URL to one new URL.
2. Keep the URL structure where you can, so `old-brand.com/products/item` becomes `new-brand.com/products/item`.
3. Use 301 (permanent) redirects, not 302 (temporary) redirects.
4. Send each old URL straight to its final destination, with no intermediate hop.
5. Test every redirect in staging before launch.

Avoid these mistakes:

- all old URLs redirect to the new homepage, which destroys page-level rankings;
- old category pages redirect to the homepage instead of the equivalent category;
- case errors, where `Old-URL.html` redirects and `old-url.html` does not;
- redirect loops, where A redirects to B and B redirects to A;
- URLs with query parameters, such as `?utm_source=`, that fail to redirect.

[Redirect chains and 301s for developers](/articles/redirect-chains-301-developers) explains how to test the map at scale.

### Test in staging

Clone the current site to staging and add the redirects there. Test each of the top 100 traffic URLs. Sample 20 to 30 percent of the remaining URLs. Confirm that each redirect returns 301 and each destination returns 200, not 404. Check mobile usability and page speed on the new site. Confirm that every internal link points to the new domain.

### Launch

Launch in a low-traffic window, such as a weeknight, not Monday morning or Friday afternoon. Keep the technical team on standby. Prepare a rollback plan. Watch analytics in real time for four to six hours after launch. Record every configuration change you make during launch.

### Verify in the first 48 hours

1. Add and verify the new domain as a Search Console property.
2. Submit the new XML sitemap to that property.
3. Keep the old domain's Search Console property active for monitoring.
4. Request indexing for the most important URLs with the URL Inspection tool. The tool has a daily quota, so start with the top pages.
5. Check the server logs to confirm that Googlebot reaches the new site.
6. Confirm that the redirects return 301.
7. Scan the new domain for 404 errors, which mean redirect failures.
8. Search `site:new-domain.com` to confirm that the new site appears in Google's index.

## Tell the search engines about the move

In Search Console, open the old property, go to Settings, and use the Change of Address tool. It tells Google to treat the two domains as the same site. It speeds up the transfer but does not remove the indexing delay.

Bing Webmaster Tools has a similar site move tool. Check Bing's share of organic traffic in your analytics. The notice takes about 30 minutes, so do it.

Keep the old domain for at least 12 months, and ideally forever. Keep the redirects active, keep the SSL certificate valid, and check that old-domain traffic still reaches the new site. A domain registration and hosting cost almost nothing compared with the traffic they protect. Google's [site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) says to keep redirects as long as possible, and at least one year. Never let the old domain expire. A domain squatter can buy it, confuse your customers, and take the residual traffic.

Ask for backlink updates. Identify high-value editorial links, such as those from domains with Domain Rating 60 or more. Contact the site owners and ask them to link to the new domain. Start with sites you have relationships with, and with links to the homepage and top landing pages. Expect only some owners to update. A 301 redirect passes link value. A direct link still removes the redirect hop and shows that the old domain is retired.

## Manage the shift in brand search

People search for the old brand name for months or years after a rebrand.

Bid on the old brand name in Google Ads, so searchers for the old name reach the new site. Publish a landing page that explains "Old Brand is now New Brand". Show a short notice to visitors who arrive through the redirect. Do not put an interstitial page between the old URL and the new one. The redirect must stay a direct 301.

Track branded search volume for both names. Expect many months before searches for the new name exceed searches for the old one. [Brand search lift](/articles/brand-search-lift-seo) explains how to measure that crossover.

Update every public record of the brand. If the company has a Wikipedia entry, make sure it explains the rebrand through Wikipedia's normal editorial process. Claim the Google knowledge panel through Google's verification process, then suggest the name change from the panel. Change social media handles on the same day. Make sure press releases explain the change clearly.

Watch competitors. They may bid on your old brand name in paid search or publish "Old Brand alternative" content. Monitor and defend searches for the old name. If the old brand was never a registered trademark, consider registering it.

## Decide what happens to the content

| Option | What it means | Risk |
|---|---|---|
| Preserve all content (recommended) | Migrate everything with redirects. Update brand references gradually after launch. | Lowest. Historical rankings stay. |
| Migrate selectively | Migrate the pages that bring the top 80 percent of traffic. Retire the bottom 20 percent, which brings under 1 percent of traffic. | Medium. Removed pages may hold internal links or backlink targets, so audit them first. |
| Rewrite everything | Rewrite all content for the new positioning and launch a new architecture. | Highest. Expect a large loss while the new content builds authority. Justified only when content is outdated, off-brand, or a legal problem. |

Update pages in this order. Change the homepage, primary navigation, and the About page and team bios at launch. Update the top 20 landing pages in the first week. Update product and service pages in the first month. Update the blog and educational content gradually over three to six months. The back catalog can change slowly without major impact.

## Monitor for 90 days and act on red flags

In week 1, check traffic daily, and hourly at first. Watch the Search Console page indexing report for the new site. Track the top 100 keywords. Keep testing redirect samples. Watch for 404 and 500 errors.

In weeks 2 to 4, check traffic every other day and rankings weekly. Watch whether Google recrawls the old domain's backlinks. Track conversion rates, because design changes can affect them. Collect design feedback and run usability tests.

In months 2 and 3, review traffic weekly and rankings every two weeks. Run a competitive analysis each month. Assess the recovery curve and plan changes if it stalls.

Compare the recovery with a planning pattern such as this one. It is an allowance for planning, not a guarantee:

| Period | Planning pattern for traffic |
|---|---|
| Weeks 1 and 2 | A 20 to 40 percent drop while search engines recrawl |
| Weeks 3 to 8 | Gradual recovery as the new domain gains trust |
| Months 3 to 6 | 80 to 90 percent of the pre-rebrand level |
| Months 6 to 12 | 95 to 100 percent, with possible growth |

Act at once on any of these red flags:

- a traffic drop above 50 percent in the first week;
- a new domain that does not appear in results after two weeks;
- major ranking losses on branded queries;
- a spike of 404 errors in Search Console;
- redirect loops and failures.

If traffic does not recover, audit the redirects for every critical page. Check the new site's speed, mobile usability, and crawlability. Increase backlink update outreach. Publish new high-quality content to show the site is active. Bring in an outside consultant if the in-house team is stuck.

## Set expectations with the leadership team

You cannot avoid SEO impact entirely. Good execution keeps the effect small and temporary. For planning, budget for a three to six month recovery and a 10 to 20 percent temporary loss. A claim of "zero SEO impact" usually means that nobody measured the effect. It can also mean that the old brand had little search visibility to lose.

When stakeholders want everything changed at once, push back hard. Suppose the name, domain, content strategy, and design all change together, and traffic falls 40 percent. Nobody can then tell whether redirects, content, design, or brand confusion caused it.

Propose a sequence. First, run the visual rebrand, wait three months, and measure. Second, migrate the domain, wait six months, and measure. Third, reposition the content, wait six months, and measure. The sequence adds delay, but it reduces the risk sharply.

Hire a specialist migration agency or consultant if the team has no migration experience. Domain migrations are rare, high-risk events, and experience matters. A full agency engagement costs several times an advisory arrangement. An in-house team with strong technical skills can execute under a consultant's oversight. A small business may accept more do-it-yourself risk, because its absolute exposure is smaller. If the rebrand follows an acquisition, start with the audit in [SEO due diligence for acquisitions](/articles/seo-due-diligence-acquisitions).

----

```text
                  .|########||.                                       .|########||.                                       .|########||.
               |##||.      .||##|.                                 |##||.      .||##|.                                 |##||.      .||##|.
             |#|.              .|#|.                             |#|.              .|#|.                             |#|.              .|#|.
           |#|                    |#|                          |#|                    |#|                          |#|                    |#|
         .#|                        |#.                      .#|                        |#.                      .#|                        |#.
        .#.                          .#|                    .#.                          .#|                    .#.                          .#|
       |#.                            .#|                  |#.                            .#|                  |#.                            .#|
      |#             ......             #|                |#             ......             #|                |#             ......             #|
     .#           ||#########|           #|              .#           ||#########|           #|              .#           ||#########|           #|
    .#.         |######||######|.        .#.            .#.         |######||######|.        .#.            .#.         |######||######|.        .#.
    #.        .##|###|##|#|######|        .#            #.        .##|###|##|#|######|        .#            #.        .##|###|##|#|######|        .#
   ||        |##|#||||||||||||#||#|        ||          ||        |##|#||||||||||||#||#|        ||          ||        |##|#||||||||||||#||#|        ||
   #        |#||||||||||||||||||||#|        #.         #        |#||||||||||||||||||||#|        #.         #        |#||||||||||||||||||||#|        #.
  ||       |#||||||||||||||||||||||#|       ||        ||       |#||||||||||||||||||||||#|       ||        ||       |#||||||||||||||||||||||#|       ||
  #       .#||||||||||||||||||||||||#|       #        #       .#||||||||||||||||||||||||#|       #        #       .#||||||||||||||||||||||||#|       #
 ||   ....|||#||||||##|#|||#|#||##||||....|. ||      ||   ....|||#||||||##|#|||#|#||##||||....|. ||      ||   ....|||#||||||##|#|||#|#||##||||....|. ||
 #.  .  ....|#  ....#|||   ||| .#|||  ....#. .#      #.  .  ....|#  ....#|||   ||| .#|||  ....#. .#      #.  .  ....|#  ....#|||   ||| .#|||  ....#. .#
 #   .  ||||#| .#####||  . .#| .#|||  ||||#   #.     #   .  ||||#| .#####||  . .#| .#|||  ||||#   #.     #   .  ||||#| .#####||  . .#| .#|||  ||||#   #.
.|   |||||  #. |#|||||. ||  #. |#||. .|||||   ||    .|   |||||  #. |#|||||. ||  #. |#||. .|||||   ||    .|   |||||  #. |#|||||. ||  #. |#||. .|||||   ||
||   |....  #. ....|#.      |. ...|. ....||   ||    ||   |....  #. ....|#.      |. ...|. ....||   ||    ||   |....  #. ....|#.      |. ...|. ....||   ||
#.  .||||||##||||||##||####|||||||#||||||#|   .#    #.  .||||||##||||||##||####|||||||#||||||#|   .#    #.  .||||||##||||||##||####|||||||#||||||#|   .#
#    .||####|###########################|.     #    #    .||####|###########################|.     #    #    .||####|###########################|.     #
#      .#||||||.#.|| # |. ..# #| #|||||#|      #    #      .#||||||.#.|| # |. ..# #| #|||||#|      #    #      .#||||||.#.|| # |. ..# #| #|||||#|      #
#      .#|||||| ..  |# ## |#| ...#|#|||#|      #    #      .#|||||| ..  |# ## |#| ...#|#|||#|      #    #      .#|||||| ..  |# ## |#| ...#|#|||#|      #
#      .#|||#|# .# .#| #| ##|.#..#|||||#|      #    #      .#|||#|# .# .#| #| ##|.#..#|||||#|      #    #      .#|||#|# .# .#| #| ##|.#..#|||||#|      #
#      .#||||||############|######|||||#|      #    #      .#||||||############|######|||||#|      #    #      .#||||||############|######|||||#|      #
#   |...||#||||||#||||#|#||||||#|||||#||| |.|  #    #   |...||#||||||#||||#|#||||||#|||||#||| |.|  #    #   |...||#||||||#||||#|#||||||#|||||#||| |.|  #
#. .. ||||# .|||##|.  |#| .|| || .|||#. #|  # .#    #. .. ||||# .|||##|.  |#| .|| || .|||#. #|  # .#    #. .. ||||# .|||##|.  |#| .|| || .|||#. #|  # .#
|| |  ...||  ...##| |  #| .|. |. #####  .. .| ||    || |  ...||  ...##| |  #| .|. |. #####  .. .| ||    || |  ...||  ...##| |  #| .|. |. #####  .. .| ||
|| ||||| || ||||#|  .  |. |. |#. ||||| |#| || ||    || ||||| || ||||#|  .  |. |. |#. ||||| |#| || ||    || ||||| || ||||#|  .  |. |. |#. ||||| |#| || ||
.# |.....#|....|#.||||.|||##.|#|....||.#||.#. #.    .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #.    .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #.
 #.|||||||#############################| ||| .#      #.|||||||#############################| ||| .#      #.|||||||#############################| ||| .#
 ||       ##||#||#||||||#||#||#||#||##.      ||      ||       ##||#||#||||||#||#||#||#||##.      ||      ||       ##||#||#||||||#||#||#||#||##.      ||
  #       .#|||||||||#||#|||||||||||#|       #        #       .#|||||||||#||#|||||||||||#|       #        #       .#|||||||||#||#|||||||||||#|       #
  ||       |#||||||||||||||||||||||#|       ||        ||       |#||||||||||||||||||||||#|       ||        ||       |#||||||||||||||||||||||#|       ||
  .#        |#||||||||||||||||||||#|        #.        .#        |#||||||||||||||||||||#|        #.        .#        |#||||||||||||||||||||#|        #.
   ||        |#||||||||||||||||||#|        ||          ||        |#||||||||||||||||||#|        ||          ||        |#||||||||||||||||||#|        ||
    #.        .######|#|#########|        .#            #.        .######|#|#########|        .#            #.        .######|#|#########|        .#
    .#.         |#####||||#####|         .#.            .#.         |#####||||#####|         .#.            .#.         |#####||||#####|         .#.
     |#           ||########||           #.              |#           ||########||           #.              |#           ||########||           #.
      |#             ......             #|                |#             ......             #|                |#             ......             #|
       |#.                            .#|                  |#.                            .#|                  |#.                            .#|
        |#.                          .#.                    |#.                          .#.                    |#.                          .#.
         .#|                        |#.                      .#|                        |#.                      .#|                        |#.
           |#|                    |#|                          |#|                    |#|                          |#|                    |#|
            .|#|.              .|#|.                            .|#|.              .|#|.                            .|#|.              .|#|.
               |##||.      .||##|                                  |##||.      .||##|                                  |##||.      .||##|
                 .||########||.                                      .||########||.                                      .||########||.

Scale With Search  2026  [scalewithsearch.com](https://scalewithsearch.com)
```
