A website redesign changes more than colours and layouts. It can alter URLs, content, navigation, metadata, and the paths search engines and customers use to reach important information. Without a migration plan, an attractive new website may launch with missing pages or broken enquiry journeys.
This SEO migration checklist helps business owners organise a redesign before development begins, through launch, and into the monitoring period. Use it whether you stay on the same platform or move to a different one.
Define the redesign’s purpose and baseline
Write down what needs to improve: unclear services, difficult editing, weak mobile usability, poor performance, or an outdated customer journey. Agree what success will mean and which existing strengths should be preserved.
Record current organic landing pages, relevant search activity, enquiries, and important external links where that information is available. Note seasonal or campaign factors that could affect comparisons after launch.
Keep an inventory of existing pages and their purpose. Include articles, projects, downloads, category pages, and other routes that may not appear in the main navigation. A redesign brief based only on the visible menu can miss valuable content.
Give content decisions their own deadlines and approval owners. Waiting until deployment to discover that a service description is missing can delay launch or encourage rushed substitutions. Track unresolved content questions alongside development work so the final website is complete, not merely technically deployable.
Decide what to retain, improve, combine, or retire
Review each page against a real customer need. Retain useful content, improve incomplete answers, and combine overlapping pages only when the new destination genuinely serves the same intent.
Do not assume that deleting old articles automatically improves SEO. A dated article may still answer an important question or attract relevant visitors. Review its substance, accuracy, and role before deciding its future.
If content is retired without a suitable replacement, allow the URL to return an appropriate missing-page response. Do not send every removed page to the homepage simply because it is a convenient destination.
Create a URL mapping before launch
For every changed URL, identify the most relevant destination. Keep important URLs stable where there is no reason to change them. When a change is necessary, document the old route, new route, purpose, and expected redirect.
Google’s site migration guidance explains the importance of mapping URLs, implementing redirects, and monitoring the move. It also notes that processing changes takes time and that search visibility can fluctuate.
Aim for direct permanent redirects to suitable replacements. Test them rather than relying on a spreadsheet alone. Check for loops, long chains, and destinations that themselves return an error.
Preserve the meaning of important pages
Carry over relevant title information, useful headings, descriptive content, and internal links. A redesigned service page should still make its offering clear even if its visual presentation changes substantially.
Check canonical URLs and metadata on the rendered pages. Ensure structured data describes what customers can actually see. Use accurate image alternatives and avoid replacing important text with text embedded in graphics.
Review our AI search preparation guide for a content approach that prioritises complete answers and technical discoverability without depending on fashionable markup.
Protect staging without blocking production
Keep development copies out of public search through an appropriate staging setup. Record the protections applied so they can be checked at launch. A setting that protects a staging site can become a serious problem if it remains on production unintentionally.
Before launch, inspect production crawl access, robots instructions, page-level indexing directives, canonical domains, and sitemap locations. Check both the page markup and the actual server response where relevant.
Do not assume that a homepage loading successfully proves every template is ready. Test articles, projects, forms, policy pages, and representative service pages individually.
Verify the complete customer journey
Test navigation and internal links against the final production URLs. Confirm that contact forms, booking links, downloads, and ecommerce operations work. Include error handling and confirmation states.
Check the redesign on phones and tablets as well as desktop. Content wrapping, sticky headers, overlays, and image cropping can change the usability of a journey even when all URLs are technically correct.
Use our Core Web Vitals guide to review loading and interaction quality. A redesign should not introduce unnecessary visual weight or a dependency that makes routine tasks slower.
Launch with a controlled checklist
Choose an appropriate launch window and identify who can make changes or restore service. Back up the existing implementation and document how rollback would work. Avoid making unrelated infrastructure changes at the same moment unless they are necessary.
Verify HTTPS, preferred domain handling, redirects, sitemap output, and representative page responses immediately after deployment. Keep a launch log so any issue can be connected to a known change.
If URLs changed, update internal references to the new routes rather than making visitors and crawlers rely on redirects for normal navigation. Submit the relevant sitemap through an authorised Search Console account.
Monitor and improve after launch
Review crawl and indexing reports, missing URLs, organic landing pages, and enquiries. Investigate meaningful changes against the baseline and migration map. A short-term fluctuation needs context rather than an immediate conclusion that the whole redesign failed.
Keep a list of post-launch fixes with priorities and owners. Correct broken destinations quickly, then continue refining content and customer journeys. Maintain suitable redirects while old links and search references may still be in use.
For a redesign that combines visual quality with a careful migration, explore website design and development and SEO and content strategy, then share your current website with Ali Dev Solutions.