Website migration without losing rankings: the complete checklist

Published on 7 minute read Team Tecnico Studio Mate
Website migration without losing rankings: the complete checklist

Changing hosting, moving to a new domain or completely rebuilding a website are operations that, if handled without a precise plan, can cause the organic traffic built up over years to collapse, even when the new site is technically better than the previous one. Ranking on Google depends not only on content, but also on URLs, redirects and technical signals that must be carefully preserved during every phase of the migration.

In brief

A website migration without losing rankings requires three distinct phases: careful preparation before the change (URL mapping, backup, analysis of the current site), precise technical execution during the migration (301 redirects, keeping the semantic structure, updating the sitemap), and careful monitoring in the following weeks (checking indexing, catching errors, comparing traffic). Skipping even one of these phases — especially the 301 redirects from the old URLs to the new ones — is the most common cause of traffic collapse after a migration.

What can cause a loss of rankings during a migration?

Google treats every URL as a distinct entity with its own authority accumulated over time. When a migration changes URL, structure or domain without correctly signalling the link between the old and the new site, that authority risks being lost, even if the content remained identical.

The most frequent technical causes

Missing or badly configured 301 redirects, a change in the URL structure without mapping, content removed or rewritten at the same time as the technical switch, and degraded loading times on the new site are the most recurrent causes of a drop in organic traffic after a migration.

Pre-migration checklist: what to do before the change

The preparation phase is what determines most of the final result: a plan done well before touching any technical element drastically reduces the risks in the following phases.

  1. Take a complete backup of the current site (files and database), to be kept as a reference regardless of the outcome of the migration.
  2. Export the full list of indexed URLs, from Google Search Console or from a crawl of the site, to have an exact picture of what needs to be preserved.
  3. Create a 1:1 mapping between old and new URLs. Every existing URL must have a precise match on the new site, even when the structure changes.
  4. Note the pages with the most traffic and backlinks, so that you can check them with absolute priority after the switch, before any other page.
  5. Check the current performance status (speed, Core Web Vitals) of the site, to have an objective benchmark after the migration.
  6. Plan the migration at a low-traffic time, to reduce the impact of any temporary downtime during the operation.

Checklist during the migration: what to do at the moment of the change

During the technical execution, every step must be verified before considering the migration complete, without assuming that “if the site displays”, then everything went well.

  1. Set up the 301 redirects from every old URL to its corresponding new URL, according to the mapping prepared in advance: it is the most critical step of the whole migration.
  2. Update the XML sitemap with the new URLs and submit it again through Google Search Console, to explicitly signal the new structure of the site.
  3. Check the robots.txt file, making sure it does not accidentally block search engines from crawling the new site.
  4. Check the canonical tags on every page, to confirm they correctly point to the new URLs and not to obsolete versions.
  5. Keep titles, main content and the H1/H2 tag structure unchanged on the pages with the most traffic, avoiding rewriting them at the same time as the technical switch.
  6. Verify that forms, checkout and internal links work on the new site, to rule out errors that would harm the user experience as well as rankings.

What to monitor after the migration?

The weeks immediately following the migration are when any errors become visible, both in the Google Search Console data and in the site’s real traffic. Active monitoring at this stage makes it possible to fix problems quickly, before they have a lasting impact on rankings.

In the first few days

Check in Search Console for any crawl errors, pages with missing redirects (404 errors) and the indexing coverage of the new URLs, intervening immediately on any anomaly found.

In the following weeks

Compare the organic traffic trend with the period before the migration, checking page by page, not just at an aggregate level: a drop concentrated on a few specific pages almost always indicates a localised, fixable technical problem, while a generalised drop may require deeper analysis.

How long does it take for rankings to stabilise after a migration?

Google generally takes a few weeks to fully reprocess the signals of a migrated site, with a normal traffic fluctuation in the first few days even when the migration was carried out correctly. Full recovery, if all the technical steps were respected, typically happens within a few weeks; longer times or traffic that does not recover at all are generally a sign of a technical problem still present, which must be checked as a priority.

Studio Mate handles migrations of WordPress, WooCommerce and Laravel application sites with a structured approach that includes URL mapping, redirect management and post-launch technical monitoring, to minimise the risk of losing rankings during the switch.

Hosting migration, domain migration or redesign: does the strategy change?

Not all migrations carry the same level of risk for rankings, and it is useful to distinguish them before planning the intervention.

Hosting change only, same domain and same URLs

It is the lowest-risk migration: if the domain and the URL structure remain unchanged, rankings depend above all on the continuity of the site during the switch (minimal downtime) and on maintaining the same technical performance on the new hosting.

Redesign with a new URL structure, same domain

The risk rises, because even staying on the same domain, every URL that changes requires a dedicated 301 redirect: it is the situation in which the URL mapping described in this guide becomes truly essential so as not to lose ranked pages.

Domain change

It is by far the highest-risk scenario, because it moves the entire SEO authority accumulated onto a different domain name: it requires, in addition to the redirects, the correct configuration of the property verification tools in Search Console for the new domain and extended monitoring over time.

Frequently asked questions

Are 301 redirects always enough to preserve rankings?

They are the most important step, but not the only one: the consistency of the content, the speed of the new site and the absence of crawl errors also matter. Correct redirects without the rest of the checklist still reduce the risk, but do not eliminate it entirely.

Can I change content and design at the same time as the technical migration?

It is not advisable to do both simultaneously: changing URLs, content and design at the same time makes it much harder to understand which element caused a possible drop in traffic. Better to separate the two phases whenever possible.

What happens if I forget some redirects on certain pages?

Pages without redirects return a 404 error, losing the authority accumulated and creating a poor experience for those arriving from a link or a previous search. They must be identified and fixed as soon as possible through Search Console.

Do migrating to HTTPS or changing domain involve additional risks?

Yes, a domain change is the highest-risk migration of all, because it involves the entire authority of the site tied to that domain name: it requires an even more rigorous mapping and longer monitoring than a simple hosting migration.

Do I need an experienced technician or can I handle the migration myself?

For simple sites with few pages it is manageable even on your own by following a rigorous checklist; for sites with many indexed pages, ecommerce or high organic traffic, technical experience significantly reduces the risk of errors that are hard to spot and fix in time.

T
Team Tecnico Studio Mate

Team tecnico Studio Mate — sviluppo software su misura.

The service we talk about in this article

Problem solving

Discover the service