Skip to content

Technical SEO · guide 6 of 7

Moving or redesigning a site without losing your Google traffic

A step-by-step plan for changing domain, platform or URLs, based on Google’s own site-move guidance: list every URL, redirect one to one, keep what ranks, test, then watch.

28 min readUpdated 9 Nov 2026

  • 13 questions to test yourself
  • 1 calculator
  • 8-item checklist
On this page11 sections

The line that is missing from most redesign quotes

You have probably heard the story: a business launches a beautiful new website, and a month later the phone goes quiet. The design was fine. The new site was faster. And yet the visits from Google fell off a cliff.

By the end of this guide you will have a plan you can hand to any developer: which URLs to save, where each one should point, what must not change on the page, and what to watch in the eight weeks after launch.

Two payoffs along the way. Halfway down, you will hunt for one setting, nothing to do with redirects, that can hide a finished site from Google while it looks perfect to every human. And at the end there is one question you can ask your developer this week that tells you in a minute whether your traffic is in safe hands. First, what do you think went wrong in that story?

Quick quiz

An illustrative example: a made-up bakery launches a new site on a new platform. Six weeks later, visits from Google are well down. What is the most likely cause?

Pick one. Your first answer is the one that counts.

That cause is the line missing from most redesign quotes: nobody was paid to send the old addresses anywhere. Google had years of history attached to “/services/boiler-repair”. On launch day that address started returning “page not found”, and the history had nowhere to go.

Why migrations lose traffic

Google ranks pages, not just whole websites. Each page you have built up over the years has its own history: the searches it shows for, the links other sites point at it, the clicks it has earned. That history is attached to its exact address.

A “migration” is any change that moves pages to new addresses: a new domain (from bakery-sofia.com to sofiabakery.bg), a new platform (WordPress to Shopify, which builds its own URL patterns), a new structure (“/about-us.html” becoming “/about”), or a switch from http to https. A redesign that keeps every URL exactly the same is much lower risk; a redesign that changes them is a migration, whether anyone calls it one or not.

Traffic is lost in a handful of predictable ways, and every one of them is avoidable:

  • Old URLs return a 404 (“not found”) error instead of redirecting.
  • Old URLs redirect, but all to the homepage, which Google may treat like a missing page.
  • Pages that ranked were cut, merged or rewritten until they no longer answer the search.
  • The new site still carries the “do not index” setting from its test version.
  • Internal links, the sitemap and canonical tags still point at the old addresses.

Myth or fact?

Migration or not? Four changes you might be planning

For each one: myth or fact?0 of 4 answered
  1. 1.Switching from http:// to https:// is only a security upgrade: no page changes its address.

  2. 2.Moving a shop from WordPress to Shopify on the same domain changes most page addresses.

  3. 3.Renaming “/about-us.html” to “/about” is too small a change to need a redirect.

  4. 4.New colours, fonts and layout, with every page keeping its exact URL, needs no redirects.

Keep those five leaks in mind: each one has its own fix in the sections below, and the go or no-go score near the end checks you against all five.

Inventory: every URL that gets visits or links

You cannot redirect a page you forgot existed. The first job is a list of every old URL worth keeping, and it is longer than the menu suggests: old blog posts, PDF price lists, landing pages from an ad campaign three years ago, product pages for items you still sell under a new name.

Build the list from several places, because each one sees something the others miss. Put everything into one spreadsheet column, remove duplicates, and add a second column for visits and a third for links.

Three of the five sources are in Google Search Console. If you have never opened it, or are not sure your site is verified, the 20-minute Search Console tour in the measuring series gets you set up first; it is also where you will watch the move afterwards.

  • Google Search Console, Performance report, Pages tab: the pages that actually get clicks from Google. Set the date range to the last 12 or 16 months so seasonal pages appear. The export in the interface is capped at 1,000 rows, which is enough for most small sites.
  • Search Console, Links report, Top linked pages: the pages other sites link to. These matter even if they get few visits, because the links carry trust.
  • Your analytics landing-page report (in GA4: Reports, Engagement, Landing page): pages where visits start, from any source.
  • Your current sitemap (often at /sitemap.xml) and an export from your CMS: the pages that exist, even unloved ones.
  • A crawl of the live site with a crawler tool, which finds pages linked from your own pages that the other sources missed.

One of our illustrative case studies, Doppio Commercialisti (an invented accounting firm in Turin), shows what a forgotten corner of a site costs. When two firms merged their websites into one, the redirects for some 900 old guide pages were dropped, and the move left redirect chains and soft 404s behind. The repair in that study is the work of the next two sections: each old page matched to its closest new page with a single 301, and every chain pointed straight at its final address.

Try the numbers

How many visits depend on your redirect map?

Use your own numbers from Search Console or analytics. Count only old URLs that get visits or links, set the share of your Google visits that land on them, and how many of them already have a row in your redirect map. You will see how many visits depend on redirects, and how many would hit an error if launch happened today.

1,500 visits
120 URLs
70%
40%

Monthly visits that depend on redirects

1,050 visits

Of those, visits hitting an unmapped URL today

630 visits

Rows still to fill in your redirect map

72 URLs

An estimate from your own figures, not a forecast. It shows where the risk sits, not what Google will do, and it assumes mapped and unmapped URLs get similar visits; if you mapped the busiest pages first, the real risk is lower. The last number is your to-do list for the next section: start with the rows that carry the most visits.

The redirect map: one old URL to one best new URL

The redirect map is a two-column sheet: old URL on the left, new URL on the right. It is the single most valuable document in a migration, and it is worth doing by hand for every URL that gets visits or links.

The rule is simple: send each old page to the one new page that answers the same question. Not the homepage, not the nearest category, not “something close enough”. If the old page sold a green waterproof jacket, the new address should be that jacket, or its direct replacement.

Use a permanent, server-side redirect: a 301 (or 308) status code. Google’s documentation on redirects describes permanent redirects as a strong signal that the new URL should be the one shown in search. A 302 or 307 says “temporary”, which is the wrong message for a move. Your developer or platform sets these up; Shopify and the common WordPress redirect plugins have a URL-redirect screen that takes the same two columns.

What would you do?

Redirect matcher: one old page, four possible homes

An illustrative example. A made-up plumbing company is moving to a new site. The old page “/services/boiler-repair-sofia.html” gets steady visits and has links from two local directories.

The new site has: the homepage, a “/services” overview, “/services/boiler-repair” (same service, rewritten), and “/blog/when-to-replace-a-boiler”.

Where should the old boiler repair page redirect?

Make a guess

After a move, how long does Google’s site move documentation say you should keep the redirects in place, at a minimum?

3 months
1 month3 years

Anything within ±1 months counts as right.

Content and titles that must survive

A perfect redirect to a weaker page still loses. If the old boiler repair page had 600 words answering prices, call-out times and which brands you service, and the new one has a slogan and a button, the redirect is fine but the page no longer earns its place.

Before launch, compare your top 20 pages old and new, side by side. Keep the title tag (the blue headline in results) and the main heading close to what worked, unless you have a clear reason to change them. Keep the answers, the prices, the FAQs, the photos with descriptive file names and alt text. You can redesign how it looks; be careful with what it says.

Planning to cut or merge pages on purpose? Decide that before the redirect map is final, page by page, with each page’s visits and links in front of you. The guide on planning a website redesign walks you through a keep, merge, rewrite or drop decision for every page.

Then the plumbing behind the pages, three jobs that are easy to forget because no visitor ever sees them:

  • Internal links: point menus, buttons and in-text links straight at the new URLs, rather than relying on redirects.
  • Canonical tags (the line that says “this is the main version of this page”): each page’s should point at its own new address.
  • Sitemap: publish one that lists only the new URLs.

Before and after

An illustrative example: the same page after two different redesigns

Redesign that trimmed

Boiler repair

Title tag: “Home | Example Plumbing”.

Heading: “We’re here for you.”

Text: two sentences and a “Contact us” button. The price guide, the list of brands and the FAQ were cut “to look cleaner”.

Redesign that kept what ranked

Boiler repair in Sofia

Title tag: “Boiler repair in Sofia, same-day call-outs | Example Plumbing”.

Heading: “Boiler repair in Sofia”.

Text: the same price guide, brands and FAQ, rewritten more clearly and laid out in the new design, with a booking button at the top.

  • Both pages have a correct redirect. Only the second still answers the search that brought people in.
  • A new design is a chance to make the answers easier to read, not a reason to delete them.

Staging, noindex and the classic launch-day mistake

The new site is usually built on a test copy, often called staging, at an address like staging.example.com. You do not want Google to index the test copy, so developers block it. The safest way is a password (server-side login), because Google cannot see behind it at all.

Many teams instead add a “noindex” tag (an instruction telling search engines not to list the page) or a robots.txt rule like “Disallow: /”. Both are fine on staging. The classic mistake is copying the staging site to the live address with those settings still switched on. The new site launches looking perfect to every human, and is invisible or fading in Google.

This is the setting promised at the start: a noindex or robots.txt block left over from staging. Here is a staging handover note. Three of the six lines would hurt you if they went live unchanged. Decide for each one, then flip it.

Test yourself

Spot the launch bug: three of these six are errors

Think of your answer, then flip the card.0 of 6 flipped

Before you pick a launch date: the go or no-go score

A launch date set before the redirect map is finished is the root of most horror stories. Score yourself honestly, and come back to rescore as the work gets done. Anything below the top band is a reason to move the date, not to hope.

Put it in order

First, the whole move at a glance: put the five stages in order

Use the arrows to move each item, then check.

  1. Launch and remove the staging blocks
  2. Set up 301s and test them on staging
  3. Map each old URL to one new URL
  4. Watch Search Console for eight weeks
  5. List every old URL with visits or links

Score yourself

Are you ready to launch?

  1. I have one list of old URLs from Search Console, analytics, the sitemap and a crawl

  2. Every URL with visits or links has one best new URL in the redirect map

  3. The redirects are permanent (301 or 308) and tested on staging

  4. My top 20 pages keep their key text, titles and headings

  5. Internal links, canonical tags and the sitemap use the new URLs

  6. I know who removes noindex and robots.txt blocks on launch day

  7. I have saved a copy of the old site and its Search Console data

  8. Launch is not in my busiest season

0 / 16

0 of 8 answered. Answer them all to see your result.

Launch day: the checklist

Launch early in the week and early in the day, when your developer is around to fix things, not on a Friday evening. Then work through the list in order. Your ticks are saved on this device.

This list covers the move itself. Launch day has other quiet failures that have nothing to do with redirects, such as contact forms that send to nowhere and email that stops arriving; the website launch checklist guide covers those, from three weeks before to the first eight weeks after.

Checklist

On launch day

0 of 8 done

Saved on this device only

The first eight weeks: what to watch in Search Console

Google’s site move documentation is honest about this: rankings can fluctuate while Google recrawls and processes the move, and how long it takes depends mainly on how many URLs you have and how fast your server responds. It says a medium-sized site can take a few weeks for most pages to move in Google’s index, and larger sites longer.

So a wobble is normal. What you are watching for is the difference between a wobble and a leak. Here is a typical shape, as an illustration rather than a promise.

Timeline

What usually happens after a well-run move

  1. Day 1–3

    Check the redirects again, with real traffic

    In Search Console, use URL Inspection on a few old and new URLs. Old ones should show the redirect; new ones should be crawlable and indexable. Fix any wrong redirects the same day.

    Then run the free broken link checker on this site over the new site. It follows your links across up to 50 pages and lists any that lead nowhere or still go through a redirect: that is the internal-links leak from earlier, found in a minute.

  2. Week 1–2

    Google recrawls and the numbers move

    Clicks may dip and shift between old and new addresses in the Performance report. Google may still show some old URLs in results for a while; with redirects working, visitors still land on the right page.

  3. Week 2–4

    The Page indexing report fills in

    Old URLs move to “Page with redirect”, which is what you want. Look hard at “Not found (404)”: any URL there that had visits or links is missing from your map.

  4. Week 4–8

    Compare like with like

    Compare clicks to the same weeks before launch (or last year, for seasonal businesses), page by page. There is no fixed date for recovery, but on a well-run move most pages tend to settle near where they were. A page that stays well below is a page to investigate: its redirect, its content or its title.

  5. After month 2

    Keep the redirects, keep watching

    Leave the redirects in place, re-check the 404 list monthly for a while, and ask the sites that link to you most to update their links to the new address.

Three Search Console reports do most of the work:

  • Performance: clicks and impressions, with the Compare option for before and after, and the Pages tab to see which pages moved.
  • Page indexing: which URLs are indexed, which are redirects, which are 404 or excluded by noindex. A sudden rise in “Excluded by ‘noindex’ tag” on the new site is the staging mistake. What every other status in that report means, and which ones are real problems, is translated in the guide on why a page is not on Google.
  • Settings, Crawl stats: how often Google is fetching your site and which response codes it gets. A burst of crawling after launch is normal and a good sign.

What would you do?

Week 3: a wobble or a leak?

An illustrative example. Three weeks after a made-up florist moved to a new platform, total clicks from Google are somewhat below the same weeks before launch. In the Pages tab, most pages are close to their old numbers, but “/wedding-flowers” has fallen to almost nothing.

In Page indexing, “Not found (404)” lists “/weddings/bouquets”, the old address of that page, which had links from two wedding blogs.

What do you do first?

Not every dip after a launch is the move. If clicks in Search Console look normal but your analytics shows fewer visits from Google, suspect the tracking first: a missing analytics tag on the new templates, or visits now labelled “Direct” instead of “Organic Search”. The calm diagnosis checklist in “My Google traffic dropped” walks through those checks, and the other causes, in the right order.

When to roll back, and how

Something looks wrong a week after launch, and someone says: “just put the old site back”. Before you read what to do, test your instincts on four beliefs, one of them about exactly that moment.

Myth or fact?

Myth or fact: four beliefs about moves and rollbacks

For each one: myth or fact?0 of 4 answered
  1. 1.A temporary 302 redirect is just as good for a permanent move, because Google treats every redirect the same way.

  2. 2.If traffic drops in the first weeks after launch, rolling back to the old site is the safest fix.

  3. 3.If you redirect everything correctly, you are guaranteed not to lose any traffic.

  4. 4.Changing the domain and the design at separate times makes problems easier to diagnose than changing both at once.

So fixing forward is the default. Wrong redirects, a forgotten noindex, missing content: these are fixed in hours or days on the new site, without making Google process the whole move twice.

Roll back only when the new site is broken in a way you cannot fix quickly, for example the checkout fails for many customers, or the platform cannot produce the URLs and redirects you need. If you do, restore the old site at its original URLs exactly as they were (this is why you kept a copy), redirect any new URLs that Google has already picked up back to their old equivalents, and treat the second attempt as a fresh migration with this guide.

What to do this week

If your launch is months away, this week is the cheapest moment to protect it. Export your top pages from Search Console, ask your developer or agency to show you the redirect map (and who owns it), and put “redirects tested” in the contract or brief as a launch condition.

Here is the one-minute question promised at the start. Pick your best page from that export, the one with the most clicks, and ask: “Where will this exact URL go on the new site?” A good answer is a specific new address, read from a redirect map that already exists. “We’ll sort redirects at the end” or “it will go to the homepage” means you have found the most important conversation of the project, and you found it while it is still cheap to have.

Questions people ask

My URLs are not changing, only the design. Do I need any of this?

Less of it. Skip the redirect map, but still protect the content and titles of your top pages, check for noindex and robots.txt on launch day, and watch Search Console for a few weeks.

How many redirects is too many?

There is no practical limit for a small business site. Thousands of one-to-one redirects are normal for shops. What matters is that each one points straight at the right page.

What about pages I am deleting for good?

If there is a genuinely close replacement, redirect to it. If there is none, let the old URL return a 404 or 410 (“gone”) with a helpful page that links to your main sections. That is more honest than sending everyone to the homepage.

Should I change domain at all?

Only for a real reason: a rebrand, a legal issue, a much clearer name. A domain change done well can keep most of your visibility, but it adds risk and work, so it should earn its place.

Once the redirects are holding, one question is left that this guide has not answered: is the new site actually better for the people using it? A new design can be slower than the old one, especially on phones, and that does not show up in a redirect check. Core Web Vitals explained without the jargon, next in this series, shows how to read Google’s speed reports for your real visitors, and why a perfect lab score can still fail.

You reached the end

Your summary

This guide has 13 quick questions

Try them to see how much you already know. Your first answer is the one that counts.

Start with the first question
Your checklist0 of 8 done
Revisit the section “Launch day: the checklist”

New guides by email when they are published.

Unsubscribe in one click.

What to do next

  1. Export the Pages tab of the Search Console Performance report for the last 16 months and save it as the start of your URL list.
  2. Ask your developer the one-minute question, “Where will this exact URL go?”, for your top page, then ask for the redirect map as a two-column sheet and check your top 10 pages.
  3. Write down who will remove noindex and robots.txt blocks on launch day, and put a check of it on the launch checklist.

Find the broken links on your site

Scan up to 50 pages for links that lead nowhere, with the page each one is on.

Scan for broken links

Technical SEO

Core Web Vitals explained without the jargon

A page can score 100 in a speed test and still fail Core Web Vitals for real visitors. Here is why.

25 min readStart reading

See it applied in an illustrative case study

Invented businesses and modelled figures, not client results: how the work in this guide fits into a whole engagement.

See all 83 studies