Skip to content
Back to articles
September 23, 2026·7 min read

Redesigning a website without losing Google rankings: an SEO migration step by step

A website redesign is one of the few moments when a single decision can wipe out years of work on your Google rankings. The new site looks better, runs faster — and search traffic drops by half, because the addresses Google knew disappeared along the way. It is avoidable. Here is an SEO migration step by step: what to do before the design starts, on launch day, and in the first weeks after.

Author: Bartosz Gonta

Photo: Anete Lusina / Pexels

1. Why does Google traffic drop after a redesign?

Google does not rank a website as a whole; it ranks individual addresses. Every page that brings visits today has a history: links from other sites, the queries it answers, and a position built up over months. When the address disappears, the history goes with it.

Drops after a redesign almost always have the same causes:

  • Changed URLs with no redirects: /services/bathroom-renovation becomes /work/bathrooms, and the old address returns a 404. To Google that is a new, unknown page and a deleted old one.
  • Deleted pages that had traffic: old blog posts or “minor” service pages get dropped in the clean-up, even though they were bringing in some of the customers.
  • New titles and thinner content: shorter copy and rewritten headings and page titles mean the page stops answering the queries people used to find it by.
  • A block left over from staging: a noindex tag or a robots.txt rule meant to hide the draft ends up in production. The site drops out of results within days.
  • A domain, www or https switch without a plan: to Google, each of those variants is a separate address that has to be redirected explicitly.

A new look on its own does not hurt rankings. What hurts is what disappears along the way: URLs, content and internal links.

2. Before the project starts: list what works today

An SEO migration starts before the first sketch of the new site, not on launch day. You need a complete list of URLs and to know which of them actually do the work.

  1. Export the Performance report from Google Search Console for the last 16 months — broken down by page and by query. That is the list of URLs bringing clicks and the queries they answer.
  2. Download the current sitemap.xml and crawl the site with a tool such as Screaming Frog (free up to 500 URLs). It finds pages missing from the sitemap.
  3. Record the title, H1 and meta description of every important page. After launch you will have something to compare against.
  4. Check which pages have links from other sites (the Links report in Search Console). Those URLs need particularly careful redirects.

That list drives the most important design decision: which content moves across unchanged, which gets merged, and which can genuinely go. A page with traffic that “doesn't fit the new structure” usually deserves a place in it.

3. The 301 redirect map — the heart of the migration

A 301 redirect tells a search engine: this address has moved permanently, over there. Google then passes the signals the old URL collected — links and history — on to the new one. Without a redirect you start from zero.

A redirect map is a plain table: the old URL in the first column, the new one in the second. A few rules decide whether it works:

  • The closest equivalent, not the homepage: an old service URL points to the new page for the same service. Google treats redirecting everything to the homepage as a 404 (a so-called soft 404), and the signals are lost.
  • One hop, no chains: the old URL goes straight to its destination. A chain A → B → C is slower and weakens the redirect.
  • Every domain variant: http and https, with www and without — each must reach one final version in a single hop.
  • 301, not 302: a temporary redirect (302) tells Google the old address will come back. In a redesign, that is not true.

If the URLs do not change because the new site keeps the existing structure, half of the migration risk disappears. It is worth fighting for at the design stage.

4. Content, titles and internal links on the new site

A new design is a good opportunity to improve the copy — but pages that bring traffic today should be changed carefully. The phrases customers find them by should stay in the title, the H1 and the body.

Your pre-launch checklist should include:

  • page titles and meta descriptions carried over or deliberately improved, not regenerated from scratch,
  • blog posts and guides kept — they often bring the long-tail traffic,
  • internal links pointing straight to the new URLs, not through redirects,
  • structured data (schema.org) for the business, articles and breadcrumbs, if the old site had it,
  • image alt text and headings in the right order.

A redesign is also usually the moment site speed improves noticeably. It is one of the few cases where a new site can start doing better in Google than the old one straight away — provided it loses nothing on the way.

5. Launch day: a checklist

Most migration disasters happen in the first hour after launch. Tick these off straight away:

  1. Remove the staging blocks: noindex in the code and disallow rules in robots.txt.
  2. Test the redirects on a sample of URLs from your list — above all the ones with the most traffic and external links.
  3. Submit the new sitemap in Google Search Console.
  4. If the domain changes, use the Change of Address tool in Search Console.
  5. Check that analytics records data on the new site and the contact form actually sends messages.
  6. Crawl the new site and fix any links leading to 404 errors.

6. After launch: what to expect in the first weeks

Even after a flawless migration, rankings fluctuate for a few weeks. Google has to revisit the old URLs, see the redirects and move the signals across — for a small site that usually takes two to six weeks.

During that time, watch two reports in Search Console: Performance (clicks and impressions compared with the same period before launch) and Pages (what is indexed, what is not, and why).

Old URLs listed as “Page with redirect” in the Pages report are not an error — they confirm the redirects work. There is nothing to “fix” and no fix to validate.

What should worry you is a lasting drop on specific pages after six weeks. Then check that their redirect leads where it should and that the new content still answers the same questions.

7. Common questions about redesigns and SEO

Does changing the look of a website affect SEO?

The look itself does not. Rankings depend on URLs, content, link structure and speed. If those stay the same or improve, a new design does no harm.

Does switching technology (e.g. away from WordPress) hurt SEO?

Not as long as you keep the URLs or redirect them. Google sees the final HTML, not the system that produced it. Switching often helps, because lighter code loads faster.

How long should redirects stay in place?

Google recommends at least a year. In practice it is best to keep them for good — they cost one line of configuration, and old links on the web live on for years.

8. How to plan your own redesign

The cheapest moment to plan an SEO migration is the start of the project: the URL structure is still a decision then, not a problem to fix. Every redesign I run starts with a list of pages that get traffic and a redirect map.

Send me your current site's address and a line on what you want to change, and you'll get a free quote within 48 hours — along with a note on which pages need moving with particular care.

Have a project in mind? Describe it briefly — I reply personally, usually within 24 hours.

By sending this form you agree to be contacted about your project. No spam, no newsletter.

Read next