How to redesign a website without losing SEO

How to redesign a website without losing SEO

A website redesign keeps its SEO when every existing URL is accounted for, redirected correctly if it changes, and its content and metadata are carried over rather than rewritten from scratch on launch day. Most SEO losses from a redesign come from URLs that quietly stop working or content that gets thinner in the rebuild, not from anything Google actively penalises.

This applies whether you are redesigning a corporate website, rebuilding on a new CMS, or moving a store to Shopify. The steps are the same: know what you have, plan where it goes, and check it actually happened after launch.

A redesign is also a good moment to fix things that have quietly gone wrong over the years, thin content, missing alt text, or pages that no longer serve a purpose, as long as those fixes are made deliberately and tracked, rather than introduced as an accidental side effect of a new template.

Crawl your site and build a full URL inventory

Before any redesign work starts, crawl your current site and export every indexed URL, because you cannot redirect or preserve pages you have forgotten exist. A crawler tool combined with your Google Search Console index coverage report and your existing sitemap will usually surface pages that are no longer in the main navigation but still rank and receive traffic.

For each URL, note its current title, meta description, main heading, and approximate traffic or ranking if you have that data. This inventory becomes the checklist you work through for the rest of the project, and it's the single most skipped step in redesigns that lose search visibility.

It helps to put this list in a single spreadsheet that everyone on the project can see, developers, designers, and whoever owns the content, so nobody is working from a different or outdated version of the site's structure partway through the build.

Build a 301 redirect map

A 301 redirect map is a spreadsheet listing every old URL and the new URL it should point to, and it needs to be finished and tested before launch, not written afterward once someone notices traffic dropped. A 301 redirect passes on most of the ranking value the old URL had built up, while a page that simply disappears or redirects to an unrelated page loses that value.

Map old URLs to their closest genuine equivalent on the new site, not automatically to the homepage. Redirecting every old URL to the homepage is a common shortcut that keeps links from breaking outright but loses far more ranking value than a proper one to one mapping.

Where two old pages genuinely merge into one new page, redirect both to that new page rather than picking one and leaving the other to redirect nowhere useful. Chained redirects, where an old URL points to another redirect instead of the final page, should be flattened to a single hop wherever possible.

Keep your content and metadata

Pages that already rank should keep their core content, title tag, and meta description through a redesign unless there is a clear reason to change them, since a visual refresh does not require rewriting text that is already working. It's tempting to rewrite everything during a rebuild, but doing so on every page at once makes it hard to tell whether a later ranking change came from the redesign or from the new content.

If a page's content genuinely needs updating, that's a reasonable time to do it, just track which pages changed so you can watch their performance separately from pages that were left as is.

This also applies to the internal links within your content. If an old page linked to five other pages on your site, those links need to point to the correct new URLs once the redesign goes live, rather than to whatever the redirect chain happens to resolve to.

Keep staging sites noindexed

A staging or development version of the new site should have a noindex tag or password protection for its entire duration, because a search engine that finds and indexes your staging site can create duplicate content issues or, in rare cases, get the wrong version indexed at launch. This is a simple setting that gets missed surprisingly often, especially when a staging site is left live for months during a longer project.

Double check this setting again right before launch, since some platforms reset it and some teams remove it too early to show a client a preview, then forget to reapply it.

Launch day checks

On launch day, check that redirects work, the correct robots.txt is live, the sitemap reflects the new URLs, and analytics and Search Console are still tracking correctly, ideally before you announce the new site publicly. It's common for a staging robots.txt that blocks all crawlers to accidentally go live with the new site, which can stop Google from crawling it entirely until someone notices.

Test a sample of your most important URLs from the redirect map directly after launch, not just a handful at random, and check both the www and non www versions plus http and https resolve the way they should.

It's also worth checking that structured data, such as schema for your services, business address, or products, carried over correctly, since a template change can sometimes drop or duplicate this markup without it being visible anywhere on the page itself.

Post launch monitoring in Search Console

Google Search Console is where you'll see redesign problems first, through the index coverage report, the performance report, and any new crawl errors, so check it daily for the first couple of weeks after launch. A spike in "not found" or "redirect error" pages in Search Console usually points to a gap in your redirect map that needs fixing quickly.

Keep comparing overall clicks and impressions in Search Console for at least a month after launch against the weeks before, since some fluctuation is normal while Google reprocesses the new site, but a sustained drop is a signal something in the migration needs attention.

Getting help with a redesign

A redesign is one of the few moments where existing SEO can be lost quickly through avoidable mistakes, which is why we treat the checklist above as a standard part of every rebuild we run. Our website redesign service includes the URL inventory, redirect map, and post launch monitoring described here.

If you are moving a store specifically, our Shopify migration service follows the same process for platform moves from WooCommerce or Magento. Get a free audit of your current site before you start planning, or get in touch to talk through the project.