A new website should create more enquiries, not make your existing visibility disappear. Yet businesses regularly lose rankings after a redesign or platform move because key pages vanish, redirects are missed, or search engines are given mixed signals. This website migration SEO guide explains how to move a site without gambling with the traffic you have already earned.
A migration is not just changing a website’s appearance. It can mean moving to a new domain, changing a URL structure, switching from WordPress to Shopify, combining websites, adding HTTPS, or rebuilding the site on a different platform. Each change affects how Google finds, understands and values your pages.
Start with a clear migration plan
The biggest mistake is treating SEO as a task for the final few days before launch. By then, developers may have built pages with different addresses, removed useful content, or overlooked technical settings that take time to fix.
Start by defining exactly what is changing and what must stay protected. For most small and mid-sized businesses, that means your service pages, location pages, blog articles that bring in traffic, contact details, tracking, and the pages that generate enquiries.
Before any work begins, take a full backup of the current website. Keep copies of the files, database, content, images and settings. A backup will not prevent an SEO problem, but it gives you a reliable route back if something goes wrong.
You should also record a baseline. Note current organic traffic, keyword visibility, conversions, top landing pages and backlinks. Search Console and analytics data are particularly useful here. Without a baseline, it is difficult to tell whether a dip after launch is normal short-term fluctuation or a genuine problem that needs attention.
Build a URL inventory
Every important existing URL needs a decision. It should either remain live on the same address, move permanently to the closest relevant new page, or be deliberately retired because it has no value or equivalent.
Do not rely on memory or a basic page list from the new website. Crawl the existing site and combine that data with your analytics and Search Console reports. A page with modest traffic may still rank for a valuable local search or attract a link from an industry website.
Create a simple spreadsheet with the old URL, the intended new URL, page purpose, traffic level and redirect status. This becomes the working document for the migration. It also makes conversations between the business owner, developer and SEO team much clearer.
Keep the content and intent that rank
A redesign is often a good opportunity to improve weak copy, clarify your offer and make the site easier to use. It is not a reason to delete every page that looks old.
If a service page ranks because it answers a specific customer question, preserve that topic and search intent in the replacement page. You can improve the wording, add clearer calls to action and update the design, but do not turn three focused pages into one vague page simply to make the menu tidier.
The same applies to local SEO. If you serve multiple areas and have useful, distinct location pages, removing them can reduce visibility across those areas. On the other hand, creating dozens of near-identical town pages is unlikely to help. The right approach depends on whether each page provides a genuine reason for a customer in that location to use it.
Retain the practical on-page elements too: page titles, headings, internal links, image alt text and structured information where relevant. These are not magic ranking buttons, but they help search engines understand each page and help customers decide whether you are right for them.
Use 301 redirects properly
Redirects are the safety net of a migration. A 301 redirect tells search engines and visitors that an old page has permanently moved to a new address. Done properly, it passes visitors to the right place and gives Google a clear instruction about the change.
Each old URL should redirect directly to its closest match. A discontinued service page might redirect to a broader service page. An old blog post may redirect to an updated version covering the same subject. Redirecting everything to the homepage is a common shortcut, but it creates a poor user experience and can waste the relevance those pages built up.
Avoid redirect chains, where one old URL sends visitors to another old URL before eventually reaching the final page. They slow the journey and make crawling less efficient. The goal is one direct redirect from old to new.
Check common variations as well. That includes http and https, www and non-www versions, trailing slash versions where applicable, and old campaign URLs. A migration can look fine during a quick test while these less obvious paths still return errors.
Test the new site before anyone sees it
A staging site gives you space to test without exposing unfinished work. It should be blocked from search engines while it is being built, usually through password protection or a noindex setting. The critical point is remembering to remove the noindex instruction when the live website launches.
Before launch, crawl the staging site and check for broken internal links, missing images, duplicate titles, pages with no indexability, slow-loading templates and incorrect canonical tags. Canonical tags should usually point to the final live version of each page, not the staging address.
Test the journeys that matter commercially. Submit the contact form, call the phone number on a mobile, request a quote, make a purchase if you sell online, and check thank-you pages and confirmation emails. SEO traffic only has value if the website can turn it into an enquiry or sale.
Make sure analytics, conversion tracking and Search Console verification are ready as well. Losing measurement during a migration leaves you trying to diagnose problems with incomplete information.
Launch carefully and monitor the result
Once the site is live, remove any temporary blocks that stop search engines from crawling it. Check that the live robots.txt file is not blocking important sections and that the XML sitemap contains the correct, indexable URLs. Submit the new sitemap through Search Console.
Then test redirects at scale, not just on a handful of pages. Crawl the old URL list and confirm that each address returns a 301 redirect to the intended final destination. Crawl the new site too, looking for broken links, 404 errors, accidental redirect loops and pages pointing to the old domain.
For a domain change, use Google’s Change of Address process in Search Console once the redirects are live and verified. Keep the old domain active and redirecting for the long term. Turning it off after a few months can break old links, bookmarks and search engine signals that still matter.
A small period of movement in rankings is normal, especially when page design, content and URLs all change at once. A sharp, sustained drop is different. Watch organic traffic, indexed pages, crawl errors, top landing pages and conversion volume daily in the first week, then regularly over the following month.
Do not make three major changes at once unless necessary
There is a trade-off between ambition and control. If you change domain, platform, copy, branding, navigation and URL structure all at the same time, diagnosing a problem becomes harder. Sometimes a complete change is unavoidable, but where possible, preserve URLs and successful content during the first move. Improve them in planned phases afterwards.
This is also why a cheap rebuild can become expensive. A site may look polished on launch day while losing the pages and technical foundations that brought in enquiries. Good migration work is often invisible when it is done well, because customers and search engines simply continue finding what they need.
A practical website migration SEO guide checklist
Before launch, confirm that you have a backup, a complete old-to-new URL map, direct 301 redirects, protected staging settings, preserved high-value content, working tracking and a tested sitemap.
At launch, remove noindex blocks, publish the redirects, check forms and key conversion paths, submit the sitemap, and verify that the preferred live domain is loading correctly.
After launch, monitor Search Console and analytics, fix broken links quickly, review rankings for your priority services and locations, and keep the old domain redirecting. Do not panic over one day of data, but do not ignore a clear downward trend either.
A website migration is a business change as much as a technical one. When the plan protects the pages, searches and customer journeys that already work, a new website becomes a platform for growth rather than an avoidable setback. If you are unsure about a proposed move, ask for the redirect map and testing plan before approving launch. Clear answers now are far cheaper than recovering lost visibility later.