Short answer: Most traffic drops after a redesign are avoidable. This checklist covers what to record, redirect, test and monitor.

A redesign changes how your site looks. If you are not careful it also changes the URLs, headings and internal links that search engines use to understand it. Traffic drops after a relaunch usually come from a short list of avoidable mistakes. This checklist walks through them in the order you will meet them.

Before you design anything: record what you have

  • Crawl the current site and export every URL, title, meta description, H1 and status code.
  • Pull Search Console data for the last 12 months: which pages earn clicks, which queries they rank for.
  • Flag your top pages by organic traffic, conversions and backlinks. These are the pages you must not break.
  • Save a copy of the old site's sitemap. You will compare it with the new one later.

Plan the new structure

Decide which pages stay, merge or go. Keep URLs the same wherever the page still makes sense. A new design does not need new addresses. Where a URL must change, record the old and new address in a redirect map. Keep paths short, readable and consistent, and pick one trailing-slash policy and enforce it.

Build the redirect map

Every old URL that will no longer exist needs a permanent (301 or 308) redirect to the most relevant new page. Redirect to a page that answers the same question, not blindly to the homepage. Avoid chains, where A redirects to B and B redirects to C, because each hop wastes crawl time.

Carry over what ranks

  • Keep the title tags, headings and body copy of high-performing pages unless you have a reason to improve them.
  • Preserve internal links between related pages, and use descriptive anchor text.
  • Keep structured data (organisation, breadcrumbs, articles) and make sure it still validates.
  • Retain image alt text and compress images into modern formats without changing their purpose.

Test on a staging site

Block staging from search engines with authentication, not only a robots rule. Then crawl it the same way you crawled the live site. Compare titles, headings, canonicals, status codes and internal links. Check that every key template has a self-referencing canonical and that nothing important is set to noindex. Test forms, tracking and page speed. Core Web Vitals targets are an LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.

Launch day

  1. Remove any noindex or password protection that was only meant for staging.
  2. Switch DNS and confirm HTTPS works on the exact domain you want indexed.
  3. Test the redirect map against the old URL list and fix every miss.
  4. Submit the new XML sitemap in Search Console and confirm robots.txt allows crawling.
  5. Confirm analytics and conversion tracking fire on the new pages.

After launch: watch closely for 90 days

Check Search Console daily in the first week and weekly after that. Look at coverage and indexing reports, 404 errors and the queries and pages that gained or lost impressions. Small dips in the first weeks are normal while Google reprocesses the site. A sharp drop on a specific section usually points to a redirect or template problem you can fix quickly.

If you want a team to handle this end to end, our web design service includes URL mapping, redirects and post-launch monitoring, and our SEO service can audit a site that has already been relaunched.