A website redesign can improve trust, enquiries and sales. It can also remove the pages, signals and technical settings that currently bring customers to your business. An SEO migration checklist for a website redesign provides the control needed to retain existing organic visibility while the new site is built and launched.
The key principle is simple: do not treat design, development and SEO as separate workstreams. Search engines and customers need to find the same useful content at the same addresses, or receive a clear instruction when an address has changed. A good migration records those decisions before launch, tests them before they become public, and checks the outcome afterwards.
Start the SEO migration checklist before design approval
The migration should begin before wireframes are signed off, not when the new website is ready to publish. At this stage, establish what the current website earns from search. Rankings alone are not enough. Identify the pages producing organic visits, telephone calls, contact form submissions, quote requests and sales.
Create a full crawl of the existing website. The export should include every indexable URL, page title, meta description, heading, canonical tag, status code, internal link count and word count. Keep a separate record of image files, PDFs and other documents that receive search traffic or have external links pointing to them.
Use analytics and search performance data to classify pages by value. A page with modest traffic may still matter if it generates high-value enquiries. Equally, a page that receives visits but has no commercial purpose may be a candidate for consolidation. The decision should be based on evidence, not whether a page looks outdated.
Before content is rewritten, record the following baseline measures:
- Organic sessions and conversions by landing page
- Search impressions, clicks and average positions for priority queries
- Indexed page counts and crawl errors
- Backlinks pointing to important URLs
- Page speed and Core Web Vitals where data is available
- Revenue or qualified enquiries attributed to organic search
These figures give the business a realistic comparison point after launch. Without them, it is difficult to separate a migration issue from normal seasonal movement, market changes or tracking faults.
Set URL rules before the new site is built
URL changes are one of the largest sources of avoidable traffic loss. A redesign does not automatically require new page addresses. If an existing URL is clear, relevant and performing, retain it. Changing it solely to create a neater structure adds risk without necessarily adding value.
Where a URL must change, map every old address to the closest equivalent new page. This is a one-to-one decision wherever possible. Redirecting many old service pages to the homepage is not a substitute for proper mapping. It gives users little useful information and can weaken relevance signals.
A redirect map should include the old URL, the destination URL, the reason for the change and the person responsible for approval. Include variations such as HTTP and HTTPS, www and non-www, trailing slash versions and old campaign URLs if they are still receiving visits.
Use permanent 301 redirects for pages that have moved permanently. Do not use redirect chains. An old URL should send users and search engines directly to the final destination in one step. If a page has no relevant replacement, a genuine 404 or 410 response can be appropriate, but this should be an informed choice rather than an accidental result of missing content.
Protect page relevance, not just page addresses
A redirect preserves part of a page’s value, but it does not replace useful content. The new page still needs to meet the searcher’s likely intent. If a current service page ranks because it explains a specific service in Kent, replacing it with a short generic paragraph may reduce its ability to compete even if the redirect is correct.
Review priority pages individually. Carry forward their core topic, supporting information, headings, internal links and calls to action where they remain accurate. Improve weak content, but avoid removing sections simply because the new design requires more white space. A leaner page can be better for users, yet it must still answer the questions that made it useful.
Pay close attention to title tags, H1 headings and meta descriptions. These should be unique and aligned with the page purpose. Do not duplicate titles across service or location pages. It creates ambiguity for search engines and makes search results less useful for potential customers.
Images also need review. Maintain descriptive file names and alt text where images carry meaning. Compress files appropriately, but do not replace valuable visual content with empty decorative assets if it helps customers understand the service, process or result.
Check technical controls on the staging site
A staging website should not appear in search results. It is normal to restrict it using password protection, IP restrictions or noindex directives while it is in development. The risk comes at launch, when those restrictions are left in place.
Before publication, verify that the live environment is prepared to be crawled and indexed. Check the following controls as part of the website redesign migration checklist:
- The live site does not retain a sitewide noindex tag
- robots.txt does not block essential pages, CSS, JavaScript or image resources
- Canonical tags point to the preferred live URLs
- XML sitemaps contain only live, indexable canonical pages
- HTTPS is enforced consistently across the website
- Structured data, where used, matches the visible content
- Contact forms, telephone links and conversion tracking work correctly
Canonical tags deserve careful attention. They tell search engines which version of similar pages should be treated as the primary version. A staging canonical, an old domain reference or a blanket canonical to the homepage can prevent new pages from being indexed as intended.
Mobile testing is equally necessary. Check page templates on common screen sizes, including navigation, forms, accordions, service tables and buttons. If key content is hidden, slow to load or difficult to use on a phone, the redesign can affect both enquiries and organic performance.
Test redirects and internal links before launch
Do not wait until the site is public to discover that redirects are missing. Upload the redirect rules to a test environment where possible, then crawl the old URL list. Each important old address should return a 301 response and land on the intended final page.
Next, crawl the new site. Look for broken internal links, orphan pages, duplicate titles, missing headings, redirect loops and pages returning 4xx or 5xx errors. Internal links should point directly to current URLs, not pass through redirects. This improves crawl efficiency and avoids unnecessary friction for visitors.
Test conversion paths as a customer would. Submit forms, check confirmation messages, call telephone numbers, download documents and test any payment or booking process. SEO traffic has little value if a redesign breaks the route from visit to enquiry.
Launch in a controlled order
Choose a launch period when the team can monitor the website and correct faults quickly. Avoid publishing immediately before a bank holiday, major campaign or period when access to the developer is limited.
Once the site is live, complete the required actions promptly. Remove staging blocks. Confirm the preferred domain redirects correctly. Submit the updated XML sitemap through the relevant search console property, and request indexing only for the most important changed pages where appropriate.
Keep the old website available as a backup until the new site has been checked. A rollback plan is sensible for complex websites, especially where ecommerce, large content libraries or integrations are involved. The aim is not to avoid every risk. It is to ensure that a fault can be corrected without prolonged loss of business.
Monitor the first weeks after publication
Some movement in rankings and traffic is normal after a substantial redesign. Search engines need time to crawl redirects, process new content and reassess page relevance. A temporary fluctuation is different from a persistent technical problem.
Review crawl reports, indexing data and analytics daily during the first week, then regularly over the following month. Investigate sudden rises in 404 errors, major drops in indexed pages, lost conversion tracking or declines concentrated on a group of previously successful landing pages.
Do not make broad changes in response to one day of data. First check whether redirects, canonicals, robots directives and analytics tags are functioning correctly. Then compare affected pages against the pre-launch record. If a key page has lost relevance through reduced content or a changed heading structure, restore the missing value rather than making cosmetic alterations.
For businesses relying on search enquiries across Maidstone, Kent or wider UK markets, a redesign is an opportunity to improve performance, but only when the existing search equity is handled with care. Treat every valuable URL as a business asset, verify each technical instruction, and give the new website time to prove that it can earn its place in search results.