A website redesign fails at SEO in one predictable way: the new site launches, the old URLs return 404 errors, and every ranking those pages held disappears within days. This is avoidable with a checklist followed in order, not fixed after the fact.
The steps below cover both the visual and technical sides of a redesign, with extra weight on the SEO preservation steps teams forget most often: URL mapping, redirects, metadata, internal links and the post-launch check in Search Console. Work through this before you touch the live site.
Before you start: audit what you already have
- Export a full list of your existing URLs from your CMS, sitemap and Google Search Console
- Identify which pages drive organic traffic, rankings or backlinks using your analytics and Search Console data
- Record current title tags, meta descriptions and H1s for every page worth preserving
- Note every external site linking to you, and to which specific pages, using a backlink tool or Search Console's links report
- Take a snapshot of current rankings for your target keywords so you have a baseline to compare after launch
The redesign checklist
| Step | What to do |
|---|---|
| 1. URL mapping | Map every old URL to its new equivalent, one to one, before development starts |
| 2. 301 redirects | Implement a 301 redirect for every mapped URL, pointing to the most relevant new page, not the homepage |
| 3. Avoid redirect chains | Point each old URL directly to its final destination rather than through several hops |
| 4. Preserve titles and meta descriptions | Carry over metadata that already performs well instead of rewriting everything by default |
| 5. Preserve internal links | Rebuild internal linking so key pages keep the same link paths and anchor text they had before |
| 6. Keep heading structure | Match H1 and core heading text where the page content has not fundamentally changed |
| 7. Update the XML sitemap | Generate a new sitemap reflecting the final URLs and submit it in Search Console |
| 8. Check robots.txt | Confirm the new site is not accidentally blocking search engines from crawling it |
| 9. Verify structured data | Reapply schema markup for products, articles or local business data that the old site used |
| 10. Test on staging | Run redirects, forms and page speed checks on a staging URL before pointing the domain at it |
URL mapping and redirects, done properly
Start the map early, not the week before launch. Go page by page through your existing sitemap and assign each URL a destination on the new site. Where a page has no direct replacement, redirect it to the closest topical match, such as a category page, rather than defaulting every orphan to the homepage. A pile of URLs all redirecting to the homepage looks like a soft 404 to search engines and wastes the equity those pages built.
Implement redirects at the server or platform level as 301s, which signal a permanent move and pass ranking value to the new URL. A 302 signals a temporary move and search engines treat it differently, so it is the wrong tool for a permanent redesign.
Metadata and content: change deliberately, not by accident
A full redesign often comes with a full rewrite, and that is where pages lose rankings even with perfect redirects in place. If a page's title tag and meta description already rank well and match search intent, keep them, or change them with intent rather than as a side effect of a new template. The same applies to core body content on pages that already perform. A visual refresh does not require a content rewrite, and separating the two decisions protects rankings the redesign was never meant to touch.
Internal links people forget to rebuild
Internal links pass authority between pages and help search engines understand site structure. A new navigation, footer or related-posts widget can quietly drop links that used to point at your best-performing pages. Before launch, check that your highest-value pages still receive internal links from elsewhere on the site, not just from the main navigation.
After launch: what to check in Search Console
- Submit the new XML sitemap and request indexing for key pages
- Watch the Coverage or Pages report for a spike in 404 errors, which signals a missed redirect
- Check the URL Inspection tool on your most important pages to confirm Google sees the new version correctly
- Monitor the Performance report over the following weeks and compare it against your pre-launch baseline
- Recrawl your own site with a crawler tool to confirm every redirect resolves in one hop with no loops
Expect some short-term fluctuation even with a clean migration. What you are watching for is a fast recovery back toward baseline, not a permanent drop, which would signal a missed redirect or a metadata change that hurt a page that used to perform.
Common mistakes that quietly cost rankings
A few patterns show up again and again in redesigns that lose traffic, and each one is preventable with the right checklist step in place before launch.
- Redirecting everything to the homepage. This treats every old page the same and discards the specific relevance search engines had matched to each one. Map to the closest equivalent page instead.
- Changing URL structure without a plan. Moving from a flat structure to nested categories, or the other way around, is fine on its own, but only if every old path gets a corresponding redirect in the new structure.
- Launching before the redirect map is finished. A partial redirect list means some old URLs go live as 404s, and those are the pages losing rankings while the rest of the migration looks fine.
- Rewriting every page's copy at once. A visual refresh does not require new body content on pages that already rank. Separate the design change from the content change so you can tell which one caused any movement.
- Forgetting canonical tags and hreflang. If the old site used canonical URLs or language targeting, carry that configuration into the new templates rather than leaving it to default behavior.
- Not telling anyone before launch. If paid campaigns, email links or partner sites point at old URLs, a redirect protects the click, but someone still needs to know the URLs are changing so they can update what they control.
A note on timing
Launch a redesign when you can watch it closely for the first one to two weeks, not right before a holiday, a major campaign, or a period when nobody on your team is available to react. Most redirect and indexing issues are simple to fix quickly. The damage comes from a mistake sitting unnoticed for weeks while traffic quietly drops.
What to do next
A redesign is also a natural point to fix technical SEO issues that built up over years, not just to avoid losing what you already have. If you want the redesign audited before launch, or handled end to end with the redirect and metadata work built in from the start, our SEO team can review the plan alongside a WordPress or custom rebuild. Get in touch before you launch, not after the rankings have already dropped.
