Ripple StrategiesRipple
Website redesign guide · SEO migration

Website Redesign SEO Checklist: A Step-by-Step Migration

Eight steps to move to a new site without losing the pages that already work.

A redesign is also a migration: the old site's URLs, content and search history have to move with it. This checklist walks through the eight steps in order, with the evidence to save at each one. Redirects and a sitemap help search engines follow the change, but no process can guarantee rankings won't fluctuate.

Start a project

At a glance

01

Before design

Crawl the current site and export search and inquiry baselines.

02

Before launch

Build the redirect map and crawl the staging site.

03

After launch

Check responses, submit the sitemap and monitor Search Console.

Website redesign SEO migration checklist
StepWhat to doEvidence to save
1. Crawl the old siteList every URL, title, status code and internal linkCrawl export of the live site
2. Save baselinesExport Search Console pages and queries, and analytics inquiriesDated exports
3. Decide each pageKeep, merge, improve or retire, with a reasonContent inventory
4. Build the redirect mapOne old URL to one relevant new URLRedirect map with exceptions recorded
5. Crawl stagingTitles, canonicals, headings, noindex rules, internal linksStaging crawl report
6. Launch checksTest redirects, status codes, robots.txt and real form submissionsHTTP checks and test submissions
7. Tell Search ConsoleSubmit the new sitemap and inspect key URLsSitemap status and inspection results
8. MonitorCompare indexing, queries and inquiries with the baselineWeekly comparisons

What should a website redesign SEO checklist include?

The migration checklist Ripple Strategies in Chilliwack, BC works through on a redesign has eight steps: crawl the old site, save Search Console baselines, decide each page's fate, build a one-to-one redirect map, crawl staging, run launch-day checks, submit the new sitemap and monitor against the baseline. Each step leaves evidence you can check later.

Step 1: Crawl the old site

Run a crawler over the live site and export every URL with its status code, title, meta description, canonical and internal links. Add pages that are missing from the navigation but still exist, such as old service pages, blog posts and PDFs.

Pull the URL list from your XML sitemap and from Search Console too. Pages that only show up there often have links or traffic you would otherwise miss.

Step 2: Save your baselines

In Search Console, export the pages and queries reports for the last few months. In analytics, export landing pages and completed inquiries such as form submissions and tracked calls. Date every export.

These files are the before picture. Without them, a change after launch can't be measured against anything.

Step 3: Decide what happens to each page

Mark each URL as keep, merge, improve or retire, and write down why. A page that brings in search traffic or inquiries should keep its content, even if its layout changes.

Keep the same URL when you can. A URL that doesn't change needs no redirect.

Step 4: Build the redirect map

For every URL that moves, map the old address to the closest relevant new page with a permanent (301) redirect. Don't send retired pages to the homepage by default; a visitor looking for a specific service should land on that service.

Check the map for chains (A to B to C), loops and destinations that return errors. Google's guidance on site moves with URL changes covers redirects in detail.

Step 5: Crawl the staging site

Crawl the new site before launch. Check that each page has a unique title and description, one clear heading, a canonical pointing to the production URL, and internal links that resolve.

Staging should be blocked from indexing, but confirm that rule is not carried over to production. Check the rendered page as well as the delivered HTML so important service text isn't hidden behind JavaScript.

Step 6: Run launch-day checks

Once the new site is live, run the old URL list through a status checker. Every old URL should return a 200 or a single 301 to its mapped destination. Check robots.txt and confirm no public page carries a noindex tag.

Submit each contact and quote form and confirm the inquiry actually arrives. A form that renders is not proof it delivers a lead.

Step 7: Tell Search Console

Submit the new XML sitemap with only final, indexable URLs. Use URL Inspection on your most important pages to request indexing and confirm Google sees the canonical you intended.

If the domain itself changed, use Search Console's Change of Address tool as well.

Step 8: Monitor against the baseline

For the first several weeks, check Search Console's page indexing and performance reports weekly, and compare queries, clicks and inquiries with the Step 2 exports. Fix any 404s that appear for URLs the map missed.

Keep the redirect map and test evidence. If something drops, you can investigate the actual changes instead of guessing. For the service itself, see our website redesign page.

Frequently asked questions

Should every old page redirect to the homepage?

No. Keep useful pages or map a moved page to a relevant replacement. A homepage redirect doesn't answer the visitor's original request. Record intentional removals and check the resulting responses.

Does a redesign guarantee better rankings?

No. Better content and technical delivery can improve the site, but rankings depend on the wider search system and competition. Save a baseline and monitor indexing, queries and qualified inquiries after launch.

Talk through your project.

Book a call