Migrating a Website to a New CMS Without Losing Google Rankings: A Practical Checklist

There are many reasons why a business may decide to move its website to a new CMS. The existing system may be outdated, slow, difficult to manage, restrictive from an SEO perspective, or simply no longer suitable for the company’s needs.

However, changing a CMS is not just a design and development project. From an SEO perspective, it is a full website migration, and one of the main goals should be to preserve the search visibility the site has already built up.

A poorly managed migration can lead to a number of problems:

• important pages disappearing from Google;
• 404 errors;
• incorrect redirects;
• a drop in organic traffic;
• duplicate content;
• incorrect canonical URLs;
• broken internal links;
• lost SEO titles and meta descriptions.

Google’s site migration guidance recommends creating an accurate mapping between old and new URLs in advance and implementing proper redirects whenever addresses change.

The main principle behind a successful CMS migration is therefore simple:

Change the technology, but do not unnecessarily change what Google already knows, indexes and understands.

1. Create a complete list of your existing URLs before the migration

Before development begins on the new CMS, create and save a complete list of all indexable URLs on the existing website.

This should include:

• the homepage;
• service pages;
• product pages;
• category pages;
• blog posts;
• project or portfolio pages;
• contact pages;
• language versions;
• PDFs and other important files;
• any other pages receiving organic traffic.

Ideally, compare data from several different sources:

• the current website’s XML sitemap;
• Google Search Console;
• Google Analytics;
• server data or crawling tools;
• the existing CMS database.

This list will become one of the key working documents for the migration.

Pay particular attention to pages that already receive organic clicks, rank well for valuable queries or have external links pointing to them.

2. Keep existing URLs whenever possible

The safest CMS migration is one where the technology changes but the page URLs stay the same.

If a service page currently lives at:

example.com/services/web-development

then, unless there is a strong reason to change it, the new CMS should ideally keep exactly the same URL.

This reduces the amount of reprocessing Google needs to do and generally makes the migration much easier to manage.

URLs should not be changed simply because the new CMS uses a different default structure.

For example, there is usually no reason to change:

/blog/seo-audit

to:

/articles/digital-marketing/seo-audit-2026

if the existing URL is clear, functional and already indexed.

If a URL works well, there is often more to gain from keeping it than from changing it for purely technical or cosmetic reasons.

3. Map old URLs to new URLs

If some URLs do need to change, prepare a clear URL mapping document before the migration.

Every old URL should have a specific and logical destination.

Whenever possible, redirect an old page to the most relevant equivalent page on the new website rather than sending every outdated URL to the homepage.

Google recommends completing the URL mapping process before the redirects are implemented.

4. Use permanent 301 redirects

When an old page is permanently replaced by a new URL, a server-side permanent 301 redirect is usually the correct solution.

This tells search engines that the old address has been replaced and that the new URL should become the primary destination.

Avoid unnecessary redirect chains such as:

Old URL → intermediate URL → another URL → final URL

A much cleaner setup is:

Old URL → final URL

The simpler the redirect structure, the easier it is to maintain and the lower the risk of unnecessary technical issues during the migration.

5. Preserve SEO titles and meta descriptions

A common migration mistake is to move the visible page content but forget about the underlying SEO data.

Before the migration, preserve at least:

• SEO titles;
• meta descriptions;
• H1 headings;
• H2/H3 structure;
• image alt text;
• canonical URLs;
• robots directives;
• structured data.

Be especially careful if the new CMS generates SEO titles automatically using a different template. A small configuration change can result in dozens or even hundreds of page titles changing at once.

A CMS migration is generally not the best time to change large numbers of SEO elements unnecessarily.

Major SEO improvements are often safer as a separate phase once the migration has settled.

6. Keep valuable content

A CMS migration should not automatically become a content-cleanup exercise where older pages are deleted simply because they are no longer visible in the main navigation.

An older blog post may still:

• receive traffic from Google;
• rank for specific long-tail queries;
• attract external links;
• support other pages through internal linking;
• be referenced by other websites.

Before deleting any page, check whether it still has SEO value.

If the content is outdated, updating it may be a better option.

If two pages cover almost the same subject, they may be combined into one stronger page, with the old URL redirected to the consolidated version.

7. Check canonical URLs

Many CMS platforms generate canonical tags automatically, so these need to be reviewed before launch.

For important pages, the canonical should normally point to the correct preferred URL.

Potentially serious problems include:

• new pages still pointing canonicals to the old domain;
• every page pointing its canonical to the homepage;
• staging URLs remaining in canonical tags;
• HTTP and HTTPS versions being mixed;
• incorrect canonical relationships between language versions.

Google uses several signals when determining canonical URLs, including redirects, rel="canonical" and sitemap information.

These signals should therefore support one another rather than conflict.

8. Update internal links

A 301 redirect will help if an old link still exists somewhere, but internal links on the new website should ideally point directly to the final destination.

There is little value in linking internally to an outdated URL and relying on a redirect every time a user or Googlebot follows it.

Check:

• the main navigation;
• the footer;
• blog posts;
• service pages;
• related-content sections;
• image links;
• buttons;
• breadcrumbs;
• mobile menus.

The fewer outdated URLs remain in the new website’s internal structure, the cleaner the migration will be.

9. Check robots.txt and noindex settings

One of the most damaging migration mistakes can happen when a staging site is intentionally blocked from indexing and those restrictions accidentally remain in place after launch.

Before publishing the new website, check:

• robots.txt;
• meta robots directives;
• HTTP X-Robots-Tag;
• CMS indexing settings.

Googlebot needs to be able to access the pages and resources you want indexed.

In particular, make sure important pages have not accidentally retained:

noindex

A single configuration mistake of this kind can have a significant effect on search visibility.

10. Create a clean XML sitemap

The new CMS should generate a valid and up-to-date XML sitemap.

Ideally, it should contain only the URLs you actually want search engines to index.

Avoid including:

• 404 pages;
• redirected URLs;
• noindex pages;
• staging pages;
• unnecessary filter combinations;
• duplicate URLs.

A sitemap helps search engines discover important pages and may also contribute as one of the signals used to identify canonical URLs.

After the migration, submit the new sitemap in Google Search Console.

11. Check HTTP status codes

After the new CMS goes live, run a full crawl and make sure URLs return the correct HTTP status codes.

The most important ones are:

200

The page is working and accessible.

301

The old address permanently redirects to the new one.

404

The page cannot be found.

A 404 is not automatically an SEO problem if the page genuinely no longer exists and there is no suitable replacement.

It becomes a problem when important URLs suddenly start returning 404s, including:

• key service pages;
• popular blog posts;
• pages with external backlinks;
• URLs that previously ranked well.

This is why comparing your pre-migration URL list with the live site’s status codes is so important.

12. Preserve structured data

Structured data based on schema.org should also be reviewed during the migration.

Depending on the website, this may include:

• Organization;
• Person;
• Article;
• BlogPosting;
• BreadcrumbList;
• Product;
• other structured data types relevant to the content.

If structured data worked correctly on the old website, make sure it has not disappeared, been duplicated or become invalid in the new CMS.

13. Pay special attention to language versions

CMS migrations are usually more complex for multilingual websites because the relationships between different versions of the same content also need to be preserved.

Check:

• whether all language-specific URLs have been retained;
• whether the language switcher works correctly;
• whether each language version points to the appropriate translation;
• whether hreflang is implemented correctly;
• whether canonicals have not been mixed between languages;
• whether the sitemap includes all required language versions.

Be particularly careful if the new CMS automatically changes the structure of language-specific URLs.

14. Test the new website thoroughly before launch

The new website should be tested before DNS changes or the production environment is switched over.

At minimum, check:

• page layouts;
• mobile behaviour;
• contact and enquiry forms;
• internal and external links;
• redirects;
• canonical tags;
• robots settings;
• the sitemap;
• SEO titles;
• meta descriptions;
• structured data;
• images;
• the 404 page;
• analytics;
• cookie and consent functionality.

At the same time, make sure the staging environment does not accidentally become publicly indexable.

15. Do not change everything on migration day

Whenever possible, avoid combining a CMS migration with all of the following at the same time:

• a complete domain change;
• a completely new URL structure;
• a rewrite of all website content;
• a full rebrand;
• major information architecture changes;
• replacement of all SEO titles.

The more variables you change at once, the harder it becomes to identify the cause if rankings or traffic fall after launch.

Major changes to content and URL structure also mean that Google has more information to rediscover, process and reassess.

A safer approach is to split the project into stages.

First, migrate the technology while preserving as many existing SEO signals as possible. Once the website has stabilised, larger content, design and structural improvements can be introduced separately.

16. Monitor Google Search Console after the migration

The project does not end when the new website goes live.

After the migration, monitor Google Search Console regularly.

Pay attention to:

• indexed pages;
• non-indexed pages;
• 404 errors;
• redirects;
• canonical issues;
• sitemap status;
• clicks;
• impressions;
• average positions.

Important individual pages can be checked using the URL Inspection tool.

For a larger number of URLs, the sitemap remains one of the main ways to help Google discover the new addresses.

Should you use Google Change of Address for a CMS migration?

Usually no, as long as the domain or subdomain does not change.

Google’s Change of Address tool is intended for situations where an entire website moves to another domain, for example:

example.com → newexample.com

It is not intended for a simple CMS replacement or individual URL changes within the same website.

In those cases, correct redirects, updated internal links and a clean sitemap are the important elements.

Monitor performance after the migration

A migration is not finished the moment the new website becomes accessible.

During the first few weeks, compare:

• organic traffic;
• clicks to key pages;
• impressions;
• the number of indexed URLs;
• the number of 404 errors;
• rankings for important keywords;
• conversions and enquiries.

Google needs time to revisit old and new URLs and process migration signals. Larger websites may take longer to settle.

For that reason, small short-term fluctuations are not automatically a sign that the migration has failed.

The priority is to confirm that the technical migration has been implemented correctly and that no systematic errors remain.

CMS Migration SEO Checklist

Before migration

• A complete list of old URLs has been saved.
• Pages receiving organic traffic have been identified.
• SEO titles and meta descriptions have been preserved.
• H1/H2 structure has been preserved.
• Valuable content has been retained.
• Old-to-new URL mapping has been completed.
• 301 redirects have been prepared.
• Canonical URLs have been checked.
• Image alt text has been transferred.
• Structured data has been preserved.

Before launch

• The mobile version has been tested.
• Forms have been tested.
• Internal links have been checked.
• robots.txt has been reviewed.
• Unnecessary noindex directives have been removed.
• An XML sitemap has been created.
• Language versions have been checked.
• Analytics has been tested.
• The 404 page has been checked.
• 301 redirects have been tested.

After launch

• The sitemap has been submitted to Google Search Console.
• Key URLs have been checked.
• 404 errors have been reviewed.
• Indexing is being monitored.
• Organic traffic has been compared with pre-migration levels.
• Google rankings for important pages have been checked.
• Conversions have been reviewed.
• Necessary redirects from old URLs remain active.

Conclusion

Moving a website to a new CMS does not automatically mean losing Google rankings.

A safe migration depends less on the CMS platform itself and more on how carefully the transition is planned and executed.

The most important steps are:

1. keep existing URLs wherever possible;
2. create accurate old-to-new URL mapping;
3. use proper 301 redirects;
4. preserve SEO data and valuable content;
5. check canonicals, robots directives and the sitemap;
6. update internal links;
7. preserve structured data and language versions;
8. test everything thoroughly before launch;
9. monitor Google Search Console and organic traffic after migration.

One of the biggest mistakes during a CMS migration is focusing entirely on new design and functionality while overlooking the SEO value the existing website may have accumulated over many years.

When a CMS migration is treated as both a technical and SEO project from the beginning, the transition can be handled much more safely — preserving existing visibility while creating a stronger technical foundation for future growth.