( Redesign )
Website Redesign SEO Checklist: Rebuilding Without Losing Your Rankings
The before, launch-day and after checklist for a website redesign that keeps its Google rankings — URL inventory, redirect map, preserved copy, sitemap resubmission and thirty days of monitoring.
( The Short Answer )
Redesigns typically drop organic traffic 10–25% in the first month, and the ones that never recover skipped the same four steps: a full URL inventory before anything changes, a 301 redirect for every URL that moves, preserved copy and headings on the pages that already rank, and a sitemap resubmission on launch day with thirty days of monitoring. Everything below is that list in order, for any tier in the redesign guide.
A redesign is the most common way a business loses rankings it spent years earning, and it almost never happens because the new design is worse. It happens because URLs changed without redirects, a template dropped the heading that was ranking, internal links broke, or Google couldn't render the new site. Every one of those is preventable, and they are all on this list.
Expect a 10–25% dip in the first thirty days even when everything is done right — Google re-evaluates a changed site. Recovery takes two to eight months depending on how much changed. The drops that never recover are the ones below.
Before anything changes
- Benchmark. Export Search Console's Performance report — queries and pages, last twelve months. Without a baseline you cannot tell normal volatility from a broken migration.
- Inventory every indexed URL. Crawl the current site (Screaming Frog or similar) and export from Search Console's Pages report. Include URLs not in your sitemap; there are always some.
- List the pages that earn. Top 20 by organic traffic, everything with a backlink, everything that converts. These survive with their copy, title and headings intact — improved if you like, but about the same thing.
- Build the redirect map. Every old URL → its new URL, or "unchanged". Deleted pages redirect to the closest surviving page, never to the homepage.
- Keep titles and H1s on ranking pages unless you have a specific reason. A rewritten heading is a new page to Google.
- Keep the staging site out of the index. `noindex` or password-protect it. A staging site that gets indexed competes with the live one.
- Check the new templates render text as text. Headings inside images, copy loaded only by JavaScript after interaction, and content behind tabs that never reaches the HTML are the quiet killers.
Launch day
- Test every redirect from the map. Old URL in, new URL out, 301 status — not 302, not a JavaScript hop.
- Remove the staging noindex. The most common launch-day mistake is shipping the block to production.
- Check robots.txt isn't the staging version.
- Re-submit the sitemap in Search Console. Confirm it lists the new URLs, not the old ones.
- Request indexing for your top pages via URL Inspection.
- Verify canonicals point at the live domain, not staging.
- Spot-check structured data with the Rich Results Test on the homepage and one inner page.
The first thirty days
- Weekly: Search Console → Pages. Watch for "Not found (404)" rising — that is a missing redirect — and for "Crawled, currently not indexed" on pages that used to rank.
- Weekly: compare to the benchmark. A 10–25% dip is expected. A single page falling out of the index is not.
- Fix 404s as they appear. Every one is a redirect you missed.
- Watch Core Web Vitals. A slower new site is a ranking cost that compounds.
- Leave it alone otherwise. Re-redesigning in week two because traffic dipped is how a recoverable dip becomes a permanent one.
The mistakes that cause permanent drops
| Mistake | What it looks like | Fix |
|---|---|---|
| No redirect map | 404s in Search Console within a week | Build it before launch; 301 everything that moved |
| Rewritten ranking pages | A page keeps its URL but loses its query | Restore the original heading and core copy |
| Staging noindex shipped | Whole site drops out of the index | Remove the tag; request indexing |
| Content moved into JavaScript | Pages indexed but text missing from Google's cache | Server-render it |
| Internal links to old URLs | Crawl errors, diluted equity | Update nav, footer, and in-body links |
| Slower new site | Vitals go red; rankings slide over weeks | Performance pass before launch, not after |
Where this fits
This checklist is stage three and stage five of the complete redesign guide. If you are still deciding whether to redesign at all, start with the signs that actually justify one. Our own redesigns ship with the redirect map as a deliverable, because it is the part of the job that protects what you already have.
Frequently asked questions
- Will redesigning my website hurt my SEO?
- Temporarily, usually — a 10–25% dip in the first thirty days is normal as Google re-evaluates the site, with recovery in two to eight months. Permanent drops are almost always caused by missing 301 redirects, rewritten pages that lost what they ranked for, or a staging noindex shipped to production. All three are preventable.
- How do I keep my rankings after a website redesign?
- Inventory every indexed URL before you start, map each old URL to a new one, 301-redirect everything that moves, keep the copy and headings on pages that already rank, remove any staging noindex on launch, resubmit the sitemap, and monitor Search Console weekly for a month.
- How long does it take to recover SEO after a redesign?
- Two to eight months, depending on how much changed. A redesign that keeps URLs and copy recovers in weeks; a replatform with new URLs takes longer. If a page has not recovered in three months, check for a missed redirect or a rewritten heading.
- Do I need 301 redirects when redesigning a website?
- Yes, for every URL that changes. A 301 tells Google the page moved permanently and passes its ranking signals to the new address. Without it, the old URL 404s and its rankings are lost. Redirect deleted pages to the closest equivalent, not the homepage.
- Should I change my URLs during a redesign?
- Only if you have to. Every changed URL is a redirect to maintain and a small amount of ranking signal at risk. Keep URLs where the content is the same; change them only for pages that genuinely moved or merged.
