Website Redesign Without Losing SEO: 12-Step Checklist

To redesign a website without losing SEO, keep or 301-redirect every old URL, keep titles and content that rank, and crawl the new site before and after launch.

A redesign should bring in more customers, but I regularly get calls from business owners whose traffic dropped by half the week after their shiny new site went live. The design wasn't the problem. Old URLs started returning 404, page titles were replaced with "Home", the text that ranked was cut for a cleaner look, or the staging site's noindex tag shipped to production. All of it is avoidable. This is the checklist I follow when I rebuild a client's site, in the order I do it.

Key takeaways

• Every old URL needs a new home. Keep the same URL where you can, and 301-redirect the rest to the closest matching new page, never all to the homepage.
• Benchmark before you touch anything: export your top pages and queries from Google Search Console and crawl the old site.
• Keep what ranks. The titles, headings and body text of your best pages are why Google sends you traffic.
• Block staging, unblock production. A leftover noindex or Disallow: / is the single most damaging launch mistake.
• Keep redirects for at least a year. Google's own advice; in practice, keep them for good.

Before the redesign: take a snapshot

1. Export what Google already likes

In Google Search Console, open Performance → Search results, set the date range to the last 12 months, and export the Pages and Queries tabs. These are the pages that bring visitors and the searches that find them. Sort pages by clicks. The top 20 are your "do not break" list.

2. Crawl the old site

Run a crawler (Screaming Frog's free version handles 500 URLs; Ahrefs and Semrush have site audit tools) and save the full URL list with each page's title, meta description, H1 and status code. Also grab the URLs from your current sitemap. Pages that are linked from other websites matter too: Search Console's Links report lists your most-linked pages.

3. Record your baseline

Note your weekly clicks, impressions and the positions of your main keywords. Also measure speed for your key templates (home, a service page, a blog post) in PageSpeed Insights. After launch you'll compare against these numbers, not against memory.

During the build: protect what ranks

4. Keep URLs the same wherever possible

The safest redirect is the one you don't need. If /services/plumbing works, keep it, even if the new CMS prefers another structure. Changing URLs "to be cleaner" costs rankings for weeks with no SEO gain.

5. Build the redirect map

For every URL that does change, write one row: old URL → new URL. Rules I follow:

• One-to-one where possible. The old "Kitchen renovation" page goes to the new "Kitchen renovation" page.
• Closest match otherwise. A removed sub-service goes to its parent service page.
• Never redirect everything to the homepage. Google treats mass homepage redirects like 404s (soft 404s), so the old page's value is lost anyway.
• No chains. If an old URL already redirected once, point the original straight to the final URL.
• Use 301 (or 308), not 302. Permanent redirects tell Google to move the ranking signals to the new URL.

6. Keep the content that ranks

Designers like less text. Google and AI search like answers. For your top pages, keep the main body copy, the headings that match search queries, and the FAQ sections, then design around them. Rewriting is fine for weak pages; for strong pages, improve rather than replace.

7. Carry over titles, descriptions and structured data

Copy each important page's title tag and meta description into the new site, and keep any schema (LocalBusiness, Product, FAQ, reviews). Make sure every page has one H1, a canonical URL that points to itself, and alt text on images.

8. Hide staging from Google

Put the staging site behind a password (HTTP basic auth is easiest) rather than relying only on noindex. A password also keeps staging out of AI crawlers and stops clients' half-finished pages from leaking.

Launch day: switch it on carefully

9. Remove every staging block

Check the live site's robots.txt doesn't contain Disallow: /, view the page source of a few pages for <meta name="robots" content="noindex">, and check the HTTP headers for X-Robots-Tag: noindex:

curl -sI https://www.example.com/ | grep -i x-robots
curl -s https://www.example.com/robots.txt

10. Test every redirect

Don't trust the redirect plugin's settings page; test the real responses. Save the old URLs one per line in old-urls.txt and run:

while read -r url; do
  curl -s -o /dev/null -w "%{http_code} %{redirect_url}  <- $url\n" "$url"
done < old-urls.txt

Every line should show 301 (or 200 for kept URLs) and a sensible target. Look for 404s, 302s and redirects to the homepage.

11. Submit the new sitemap and crawl again

Submit the new XML sitemap in Search Console, then crawl the live site. Fix broken internal links (they should point at final URLs, not through redirects), missing titles, duplicate H1s and pages with no canonical.

After launch: watch for four weeks

12. Monitor and fix fast

• Search Console → Pages: watch "Not found (404)" and "Page with redirect" counts. A jump in 404s means the redirect map missed URLs.
• Performance report: compare clicks week over week against your baseline. A small dip for a week or two while Google recrawls is normal; a steady slide is not.
• Server logs: grep for 404s that real visitors and bots hit, and add redirects for them.
• Speed: re-run PageSpeed Insights on your key templates. Redesigns often add heavy hero images and fonts. My LCP guide covers the usual fixes.

If new pages sit in "Crawled, currently not indexed", read how I fix that status. And if you want the new site to show up in ChatGPT and Google's AI answers, my AI search guide lists the structure that helps.

Changing your domain name too?

Everything above still applies, with two additions: redirect every URL on the old domain to its match on the new domain (not just the homepage), and use the Change of Address tool in the old domain's Search Console property once the redirects are live. Keep the old domain registered and the redirects running; Google says at least a year, and I recommend never letting it lapse, because someone else can buy it.

Frequently asked questions

Will a website redesign hurt my SEO?

It doesn't have to. Traffic drops after a redesign come from broken or missing redirects, removed content, changed titles, slower pages, or a leftover noindex. Handle those and a redesign usually improves rankings over time.

How long should I keep 301 redirects?

Google recommends at least one year so its crawlers see each redirect several times. Redirects cost almost nothing to keep, so I leave them in place permanently, especially for pages that have backlinks.

Should I redirect deleted pages to the homepage?

No. Redirect them to the most relevant remaining page. If nothing is relevant, let the page return 404 or 410. Mass redirects to the homepage are treated as soft 404s and pass no value.

How long does it take to recover rankings after a redesign?

With correct redirects, most sites settle within a few weeks as Google recrawls the important pages first. If traffic is still falling after a month, look for redirect gaps, lost content and indexing problems instead of waiting.

Do I need to tell Google about my new website?

Submit the new sitemap in Search Console and request indexing for your key pages. The Change of Address tool is only for moving to a new domain, not for a redesign on the same domain.

Planning a redesign?

I design and build fast business websites with the redirect map, content migration and launch checks included, so your rankings come with you. See my business website design service, the technical SEO audit if your traffic already dropped, all website design services, or contact me with your current site's address.