How to redesign a website without losing your Google rankings

You can redesign a website without losing your Google rankings, as long as you treat the project as a migration and not only as a new design. That means keeping every URL that ranks, redirecting every URL that changes, and carrying over the content and signals that earned your positions in the first place. This guide walks through a practical checklist for before, during and after launch, with a table you can work through with your web team.

Why do websites lose rankings after a redesign?

Websites lose rankings after a redesign because the signals Google relied on disappear or move without a clear trail. A new design on its own rarely causes a drop; what causes it is what changes behind the design.

The most common causes are:

• URLs change and the old ones return 404 errors instead of redirecting, so links, bookmarks and Google’s index all point to pages that no longer exist.
• Content that ranked is cut, merged carelessly or rewritten into thinner copy.
• Title tags and meta descriptions are replaced with generic ones from a template.
• Internal links to important pages are lost when the navigation is reorganised.
• A noindex tag or robots.txt block from the staging site is copied to the live site.
• Structured data that existed on the old site is not rebuilt in the new templates.
• The new site is slower or harder to use on mobile.

Every one of these is preventable with a plan that starts before any design work.

What should you do before the redesign starts?

Before any design work begins, crawl your existing website and build a full inventory of every URL it has.

Use a crawling tool to list every page, then add the URLs from your XML sitemap and from the Pages report in Google Search Console, so you also catch pages that are no longer linked internally. For each URL, record the title tag, meta description, main heading, canonical tag, status code and whether it is indexable. This spreadsheet becomes the reference you check everything against later.

Identify the pages that carry value

Next, mark the pages that matter most. Export the pages with clicks and impressions from Google Search Console over the past year, check your analytics for pages that bring traffic, enquiries or sales, and use a backlink tool to find pages that other websites link to. These pages form your priority list, and they deserve the most care at every stage.

Keep URLs wherever you can

The safest URL is one that does not change. Navigation and URLs are separate decisions, so you can reorganise menus and page layouts while keeping the same addresses underneath. Change a URL only when there is a clear benefit, for example removing dates, ID numbers or a structure forced on you by an old platform.

How do you build a 301 redirect map?

A 301 redirect map is a spreadsheet that pairs every old URL that will change with the single best matching new URL, and it is the most important document in any redesign.

A 301 redirect tells browsers and search engines that a page has moved permanently, so visitors land in the right place and search engines transfer the old page’s signals to the new one. Follow these rules when you build the map:

• Map one old URL to one new URL wherever possible.
• Redirect to the closest relevant page, not to the homepage. Mass redirects to the homepage are often treated as errors.
• Avoid redirect chains (old to interim to new) and loops.
• Include URL variations: http and https, www and non-www, trailing slashes, and old PDFs or images that have backlinks.
• Let a page return a 404 or 410 only when it has no replacement and no traffic or links worth keeping.

Which content and SEO elements should you carry over?

Carry over everything that helps a page rank: the content itself, the title tag, the meta description, headings, internal links and structured data.

A redesign is a good moment to improve content, but rewrite ranking pages carefully. Keep the topics they cover, the questions they answer and the phrases people search for. If you merge two pages, move the useful content into the surviving page and redirect the other one to it.

On each priority page, check that the new version keeps:

• The title tag and meta description, or an improved version of them.
• A clear main heading and a sensible heading structure.
• The body copy, FAQs and supporting detail that answered the searcher’s question.
• Image alt text.
• Internal links pointing to it from other relevant pages.
• Correct canonical tags, and hreflang tags if the site is multilingual.

Keep or improve your structured data

If your current site has schema.org markup, such as Organization, LocalBusiness, Product, Article or FAQ data, make sure the new templates output it too, and validate it with Google’s Rich Results Test. A redesign is also a good time to add structured data you never had. It helps search engines and AI assistants understand who you are and what you offer, which we explain further in AEO vs SEO vs GEO.

How should you set up the staging site?

Build the new website on a staging environment that search engines cannot index, and keep it hidden until launch day.

Password protection is the safest option, because a noindex tag alone can still let staging pages be discovered and a robots.txt block alone does not stop URLs appearing in search. The bigger risk comes at launch, when those blocks are accidentally copied to the live site. Put “remove all staging blocks” on your launch checklist and make one person responsible for it.

What should you check before launch?

Before launch, crawl the staging site as if it were live and compare the results against your original inventory.

• Every priority page exists on the new site or has a redirect to its replacement.
• Each old URL in the redirect map returns a single 301 to the correct page.
• Titles, meta descriptions and headings have been carried over or improved.
• There are no broken internal links.
• Canonical tags point to the live domain, not the staging address.
• Structured data validates without errors.
• The new XML sitemap lists only live, indexable pages.
• Analytics tracking and Search Console verification are in place.
• Key templates load quickly and work properly on mobile.

What needs to happen on launch day?

On launch day, the priority is to make the redirects live at the same moment as the new site, and then tell search engines about the change.

1. Deploy the new site and switch on the redirect map immediately.
2. Remove every staging block: check that robots.txt allows crawling and that no page carries a noindex tag by mistake.
3. Test a sample of old URLs, starting with your priority list, and confirm each one lands on the right page.
4. Submit the new XML sitemap in Google Search Console and in Bing Webmaster Tools.
5. If the domain itself has changed, use the Change of Address tool in Google Search Console.
6. Confirm that analytics and conversion tracking are recording visits.
7. Request indexing for your most important pages in Search Console.

Choose a launch date when your team is available for the following days, and avoid your busiest trading period.

How do you monitor rankings and traffic after launch?

After launch, watch 404 errors, indexing, rankings and traffic closely for the following weeks, and fix problems as soon as they appear.

• Check the Pages and crawl reports in Google Search Console for new 404 errors and pages that are not being indexed.
• Add redirects for any old URL that still returns a 404 and has traffic or links.
• Track rankings for the search terms behind your priority pages.
• Compare organic traffic, enquiries and sales with the same period before launch.
• Keep an eye on page speed and Core Web Vitals on the live site.

Some movement in the first weeks is normal while Google recrawls the site. A short dip that recovers is common; a steady decline on specific pages usually points to a specific cause, such as a missing redirect or lost content, which your inventory helps you trace.

What does the full migration checklist look like?

The full checklist splits into three stages, and each one has its own non-negotiable tasks.

How does M7Alpha handle website redesigns?

We followed this exact process when we rebuilt our own website, m7alpha.com: we inventoried the old WordPress site, kept the original blog URLs unchanged, and built a redirect map from every old WordPress URL that changed to its new equivalent. Our web design and development team handles the migration in-house alongside the design and build, so the redirects, content and structured data are planned from the start rather than fixed after launch.