Website redesign SEO migration checklist

Reviewed by Identity Pixel's web and search team

A new website can improve clarity, conversion and technical quality. It can also remove URLs, links and content that search engines already understand. The risk comes from treating launch as a file replacement instead of a controlled migration.

1. Build an evidence-based URL inventory

Export current URLs from the sitemap, analytics, Search Console, backlink data and a full crawl. Add pages that receive clicks, impressions, enquiries, external links or important internal links. This becomes the migration register.

For every old URL, choose one outcome: keep it unchanged, permanently redirect it to a closely equivalent page, consolidate it into a genuinely relevant destination, or return a real 404 or 410 when no replacement exists. Google advises against sending many unrelated old URLs to the homepage because that can confuse users and be treated as a soft 404.

2. Preserve what currently earns value

Design teams can accidentally remove the paragraphs, headings, case evidence and internal links that explain why a page is relevant. Compare the old and new page at the query level. Preserve useful subject coverage while improving readability and eliminating weak repetition.

• Keep one clear H1 and a logical heading sequence.
• Retain accurate titles and descriptions until there is evidence for a better version.
• Move first-hand examples, specifications and FAQs into the new structure.
• Carry over descriptive image alternatives and meaningful internal links.
• Make sure important content is present in rendered HTML and accessible on mobile.

3. Prepare redirects and canonical signals before launch

Create a one-to-one redirect map and test it in the staging environment. Permanent moves should use server-side permanent redirects. Avoid chains, loops and JavaScript-only detours. New pages should use self-referencing canonical URLs that match the live HTTPS, preferred-host version.

Google recommends keeping redirects for at least a year during a site move, and notes that permanent redirects do not cause a loss in PageRank. Internal links should still be updated to point directly to their final destinations, reducing unnecessary requests for users and crawlers.

4. Test measurement and conversion paths

A technically successful launch can still be commercially blind. Test analytics consent, page views, form submissions, telephone and email clicks, advertising parameters, thank-you behaviour and duplicate-event prevention. Submit each real form on desktop and mobile and confirm where the record arrives.

Record baseline data before launch: organic clicks, impressions, priority query positions, landing-page sessions, leads and lead quality. That baseline helps distinguish normal migration fluctuation from a broken page or tracking event.

5. Use a controlled launch checklist

6. Monitor after launch

Google says ranking fluctuation can occur while a moved site is recrawled and reindexed. Monitor server errors, redirect failures, excluded URLs, sitemap processing, priority queries and conversions daily at first, then weekly as the site stabilises. Inspect important URLs individually when behaviour differs from expectation.

A hosting-only move with unchanged public URLs requires a different plan: prepare and test the new infrastructure, change DNS, monitor both hosts and retire the old host only after traffic has moved. That is why confirming the actual FTP destination matters before deployment.

Identity Pixel combines web design with technical SEO so migration controls are part of delivery, not an afterthought.