A website relaunch can look like progress while quietly removing the pages, signals and technical foundations that brought in your best enquiries. A proper seo migration checklist turns a redesign, platform change or domain move into a controlled process, rather than a gamble with Google visibility.
For a local business, lost rankings are not just a reporting issue. They can mean fewer calls, fewer quote requests and a slower pipeline for weeks or months after launch. The objective is simple: keep what already performs, improve what does not, and give search engines clear instructions about what has changed.
When an SEO migration is needed
An SEO migration is required whenever a change could affect how search engines crawl, understand or rank your website. This includes a website redesign, a move to WordPress or another platform, changing domain name, switching from HTTP to HTTPS, restructuring services or location pages, and combining multiple sites.
The level of risk depends on the change. Refreshing page colours and imagery on an existing site is usually low risk. Replacing every URL, rewriting all content and moving to a new domain at the same time is high risk. Where possible, phase major changes rather than combining them into one launch.
The work should start before design and development are signed off. SEO is not a final-stage task to add after the new website is built. It affects page structure, copy, navigation, URLs, internal links and the information needed to turn visitors into customers.
SEO migration checklist before development
Begin by creating a clear record of the current website. You need to know what is valuable before deciding what can be removed, merged or improved.
Benchmark the site you have
Export a list of all crawlable URLs, including service pages, blog posts, contact pages, PDFs and location pages. Record each page title, meta description, heading, canonical tag, status code and indexability. This becomes the baseline for the new site.
Then identify the pages that matter commercially. Look at organic visits, rankings, backlinks, conversions and assisted enquiries. A page with modest traffic may still be valuable if it ranks for a high-intent local service search or generates regular contact form submissions.
Keep copies of current analytics, Search Console data and ranking reports. These figures allow you to distinguish a normal short-term fluctuation from a genuine migration problem once the new site goes live.
Map every old URL to a destination
Create a redirect map before development begins. Every important old URL should have one clear equivalent on the new website. If a service page remains relevant, redirect it to the improved version of that same service page, not to the homepage.
This is one of the most important decisions in the process. Redirecting dozens of old pages to a generic page gives users a poor experience and can weaken the relevance signals that helped those pages rank. If content is being retired because it is outdated or duplicated, choose the closest useful alternative. If there is no suitable replacement, a 410 status may be more honest than an irrelevant redirect, but use this sparingly.
Avoid redirect chains. An old URL should redirect directly to its final live destination in a single step.
Protect search intent and page content
A redesign is a good opportunity to improve weak content, but it is not a reason to remove useful detail simply to make a page look cleaner. If a page ranks because it clearly explains a service, location, process or specialist capability, retain that relevance in the new version.
Review the search terms each key page attracts. A Bristol accountant, building contractor or consultant may need different landing pages for services that appear similar internally but are searched differently by potential customers. Combining pages can be sensible when they genuinely serve the same intent. It can also remove visibility if it forces distinct searches onto one vague page.
Keep primary headings, supporting copy and calls to action purposeful. The new page should answer the query, establish trust and make the next step obvious.
Build technical SEO into the new site
Before launch, check the development site is blocked from indexing. This can be done through password protection or appropriate technical controls. Do not rely on a temporary instruction being remembered later.
The live build needs clean, consistent URLs, one preferred version of each page, a logical internal linking structure and fast-loading templates. Check that structured data, image alt text, XML sitemaps, analytics and conversion tracking are included where appropriate.
Mobile usability deserves particular attention. Most local service searches happen on a phone, often when the user is ready to contact someone. A site that looks impressive on a desktop but makes forms, phone numbers or service information difficult to use will lose enquiries regardless of its rankings.
Checks to complete before launch
A staging-site crawl should be treated like a final inspection. Do not assume that templates behave consistently across every page type.
Check the following before the website is made public:
- The redirect map is complete, tested and ready to publish at launch.
- Important pages return a 200 status code and do not contain accidental noindex tags.
- Canonical tags point to the correct preferred URLs.
- Navigation, breadcrumbs and contextual links point to live final URLs.
- Page titles and meta descriptions are present, unique and relevant to the page.
- Forms, click-to-call buttons, email links and tracking events work correctly.
- The XML sitemap contains only indexable, canonical pages.
- Core service, contact and location pages work properly on mobile devices.
Also review robots.txt carefully. A common and costly error is leaving a development block in place after launch, which prevents search engines from accessing the new website. Equally, do not allow staging pages, test files or duplicate environments to become indexable.
Launch day: make the switch carefully
Publish redirects at the same time as the new website, not days later. Use permanent 301 redirects for moved pages, and test a representative sample immediately. Test important URLs from the old site, pages with strong backlinks and pages that historically generated leads.
Once the new site is live, submit the updated XML sitemap through Search Console and request indexing for priority pages where needed. Check that the preferred domain version is consistent, whether that is www or non-www, and that HTTPS works across every page.
Do not make broad changes to content, navigation and URLs in the first few days unless there is a genuine error. Search engines need a stable version of the site to crawl and process. Constantly changing the structure makes it harder to diagnose what is affecting performance.
Monitor the migration after launch
The first month after launch is when attention matters most. Crawl the live website again to find broken links, missing redirects, accidental duplicate pages and unexpected noindex directives. Review server errors and look for 404 pages that receive visits or external links.
Monitor organic clicks, impressions, average positions and conversions rather than reacting to a single ranking movement. Some volatility is normal as Google recrawls URLs and reassesses the new pages. The concern is a sustained fall in visibility, especially on important commercial terms, or a sharp rise in excluded pages and crawl errors.
Pay close attention to enquiries as well as traffic. A migration can preserve rankings but still reduce leads if contact forms are broken, page speed has slipped or calls to action are less prominent. Search performance and conversion performance need to be reviewed together.
Common migration mistakes
The most damaging mistakes are usually avoidable: launching without redirects, redirecting everything to the homepage, deleting well-performing pages without checking their value, blocking the live site from indexing, and changing content so heavily that the original search intent disappears.
Another frequent problem is judging the project solely on launch day. A successful migration needs post-launch monitoring and a willingness to correct issues quickly. This is particularly relevant for established businesses with years of accumulated pages, links and local visibility.
A well-planned migration gives you the confidence to improve your website without sacrificing the visibility that supports growth. Treat your existing rankings and enquiry pages as business assets, test the change thoroughly, and keep a close eye on real customer actions once the new site is live.