Website Redesign SEO Migration Checklist: Keep Rankings During Launch

Inventory the current website before changing it

Crawl the live site and export every indexable URL, title, status code, canonical, heading, internal link, image, and structured-data type. Pull the XML sitemap, analytics landing pages, Search Console pages and queries, backlinks, forms, downloadable files, and any URLs used in advertising or email.

The goal is not to keep every weak page. It is to know which pages have traffic, links, conversions, or business value so each old URL receives an intentional outcome: retain, improve, consolidate with a 301 redirect, or remove with a clear status.

• Record current rankings and organic landing pages.
• Save a list of external links pointing to the domain.
• Document forms, tracking, verification files, and email delivery.
• Back up both files and the database before deployment.

Build a one-to-one redirect and content map

Create a migration sheet that pairs each old URL with its most relevant new destination. Redirects should preserve meaning. Sending every removed page to the homepage creates a confusing experience and weakens the context search engines use to understand the move.

Keep URLs stable when the topic and purpose remain the same. If a page is consolidated, carry forward the useful information and point the old address to the new primary page with a permanent 301 redirect. Avoid redirect chains by mapping directly to the final HTTPS canonical URL.

• Preserve valuable service and portfolio paths where practical.
• Use 301 redirects for permanent moves.
• Update internal links to final URLs instead of relying on redirects.
• Keep canonical tags self-referencing and consistent.

Protect staging without blocking production

A staging site should not compete with the real domain. Protect it with authentication or a noindex directive, and make sure production removes those controls at launch. Check that CSS, JavaScript, images, fonts, and video remain accessible to search crawlers on the public site.

Review page titles, meta descriptions, headings, image alternatives, structured data, social previews, contact details, and legal links on the new templates. Confirm that the canonical domain is the actual launch domain rather than a design preview or old country-code domain.

Test the launch as a search crawler and a customer

After deployment, crawl the production domain. Every important page should return 200, each retired URL should return one clean 301, and true missing pages should return 404. Validate robots.txt, sitemap.xml, canonical tags, HTTPS redirects, mobile layouts, performance, forms, SMTP delivery, analytics, and Search Console verification.

Submit the new sitemap in Google Search Console and inspect the homepage plus priority service pages. Monitor indexing, crawl errors, redirect problems, impressions, clicks, and conversions daily during the first week, then weekly as search systems process the move.

• Check desktop and mobile rendering.
• Test the contact form with realistic information and verify inbox delivery.
• Watch server logs and Search Console for unexpected 404s.
• Keep the migration backup until production is stable.