CMS Migration Without Breaking SEO: A Practical Checklist

Migrating a website to a new CMS is not just about moving pages and content.

A migration can affect your search visibility when URLs, redirects, metadata, and other SEO elements are not handled carefully.

The good news is that most migration problems are preventable when you plan the move before changing anything.

Here’s a practical checklist to help you protect your SEO during a CMS migration.

𝗕𝗲𝗳𝗼𝗿𝗲 𝗬𝗼𝘂 𝗦𝘁𝗮𝗿𝘁

𝗜𝗻𝘃𝗲𝗻𝘁𝗼𝗿𝘆 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴

Start by making a complete list of what exists on the current website.

Include:

• Pages
• Blog posts
• Images and other media
• Forms
• Important URLs
• Other content that matters to the business

Do not rely on just one source for your URL list.

Your sitemap, Google Search Console, analytics, and the current CMS can each show different parts of the website.

A page that looks unimportant can still be bringing in search traffic or backlinks.

𝗥𝗲𝗰𝗼𝗿𝗱 𝗬𝗼𝘂𝗿 𝗖𝘂𝗿𝗿𝗲𝗻𝘁 𝗦𝗘𝗢 𝗕𝗮𝘀𝗲𝗹𝗶𝗻𝗲

Before making changes, record what normal looks like.

This can include:

• Current rankings for important search terms
• Organic traffic
• Pages bringing in organic traffic
• Other important performance data

Take two to four weeks of baseline data before the migration when possible.

Also take a full backup of the existing website before work begins.

𝗗𝗲𝗰𝗶𝗱𝗲 𝗪𝗵𝗮𝘁 𝗦𝘁𝗮𝘆𝘀 𝗮𝗻𝗱 𝗪𝗵𝗮𝘁 𝗚𝗼𝗲𝘀

A migration is a good opportunity to review your existing content.

For every page, decide whether it should be:

𝗞𝗲𝗽𝘁

𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗱

𝗥𝗲𝘁𝗶𝗿𝗲𝗱

You do not have to carry every old page into the new CMS.

For anything you remove, decide what should happen to the old URL. A genuinely retired page should be handled deliberately rather than sending visitors somewhere irrelevant.

𝗗𝘂𝗿𝗶𝗻𝗴 𝘁𝗵𝗲 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻

𝗞𝗲𝗲𝗽 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗨𝗥𝗟𝘀 𝗪𝗵𝗲𝗿𝗲 𝗣𝗼𝘀𝘀𝗶𝗯𝗹𝗲

Your URLs are what search engines recognize, not just the page itself.

When possible, keep important URLs exactly the same after the migration.

For example:

/about-us

should remain:

/about-us

when there is no good reason to change it.

Keeping the same URLs helps maintain search continuity during the move.

𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗥𝗲𝗱𝗶𝗿𝗲𝗰𝘁 𝗠𝗮𝗽

When a URL has to change, create a simple old-to-new URL map.

For example:

Old URL → New URL

/old-page → /new-page

/services/web-design → /services/website-design

Set up the redirects before the site goes live.

A 301 redirect tells search engines that the old URL has permanently moved to a new address.

Also avoid redirecting removed content to the homepage just to make the old URL work. The destination should be genuinely relevant.

𝗥𝗲𝗺𝗲𝗺𝗯𝗲𝗿 𝗧𝗵𝗮𝘁 𝗖𝗼𝗻𝘁𝗲𝗻𝘁 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗜𝘀 𝗡𝗼𝘁 𝗦𝗘𝗢 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻

Moving your content from one CMS to another does not automatically preserve your search visibility.

Content transfer and redirect mapping are separate jobs.

Your pages and posts may move successfully while the SEO value associated with their old URLs is still at risk.

That is why migration tooling should be evaluated based on what it actually transfers, not just whether it can import content.

𝗥𝗲𝗯𝘂𝗶𝗹𝗱 𝘁𝗵𝗲 𝗗𝗲𝘀𝗶𝗴𝗻 𝗖𝗮𝗿𝗲𝗳𝘂𝗹𝗹𝘆

Moving platforms does not necessarily mean manually retyping all your content.

Pages and posts can often be exported and imported with field mapping.

What usually needs to be rebuilt is the design, because themes do not simply transfer between different platforms.

Build the new site on a private staging environment and keep it hidden from search engines while work is in progress.

𝗕𝗲𝗳𝗼𝗿𝗲 𝗬𝗼𝘂 𝗚𝗼 𝗟𝗶𝘃𝗲

𝗖𝗵𝗲𝗰𝗸 𝗘𝘃𝗲𝗿𝘆 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗣𝗮𝗴𝗲

Before changing DNS or pointing the domain to the new website, verify that:

• Pages are present
• Posts are present
• Content is correct
• Images are working
• Navigation works
• Forms work
• Metadata is set

A migration should not use launch day as the testing phase.

𝗧𝗲𝘀𝘁 𝗬𝗼𝘂𝗿 𝗥𝗲𝗱𝗶𝗿𝗲𝗰𝘁𝘀

Take a sample of old URLs and test them against the redirect map.

Make sure they reach the correct new destination.

This is especially important for high-value pages and common URL patterns.

The goal is to catch redirect problems before search engines encounter broken URLs on the live site.

𝗖𝗵𝗲𝗰𝗸 𝗬𝗼𝘂𝗿 𝗦𝗘𝗢 𝗠𝗲𝘁𝗮𝗱𝗮𝘁𝗮

Make sure important pages still have their SEO information in place.

Check things such as:

• Page titles
• Meta descriptions
• Canonical information
• Relevant schema
• Noindex rules where applicable

SEO metadata should be reviewed during the migration rather than treated as cleanup afterward.

𝗔𝗳𝘁𝗲𝗿 𝗟𝗮𝘂𝗻𝗰𝗵

𝗦𝘂𝗯𝗺𝗶𝘁 𝘁𝗵𝗲 𝗡𝗲𝘄 𝗦𝗶𝘁𝗲𝗺𝗮𝗽

Once the new website is live, submit the new sitemap in Google Search Console.

If the domain is also changing, additional migration steps may be required.

Keep the old site and its backup available until the new site is fully indexed.

𝗘𝘅𝗽𝗲𝗰𝘁 𝗦𝗼𝗺𝗲 𝗠𝗼𝘃𝗲𝗺𝗲𝗻𝘁 𝗶𝗻 𝗥𝗮𝗻𝗸𝗶𝗻𝗴𝘀

A temporary dip after a migration can happen.

Search engines need time to crawl the new URLs, process redirects, and update their index.

That does not automatically mean the migration failed.

What matters is whether the site recovers and whether there are specific issues causing a continued decline.

𝗞𝗲𝗲𝗽 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗔𝗳𝘁𝗲𝗿 𝗟𝗮𝘂𝗻𝗰𝗵

Do not stop checking the site immediately after launch.

Review the migration at:

𝗧𝗵𝗶𝗿𝘁𝘆 𝗱𝗮𝘆𝘀

𝗦𝗶𝘅𝘁𝘆 𝗱𝗮𝘆𝘀

𝗡𝗶𝗻𝗲𝘁𝘆 𝗱𝗮𝘆𝘀

Monitor important URLs, traffic, indexing, redirects, and overall site performance.

A short-term dip can be expected. A problem that remains after the initial transition deserves investigation.

𝗙𝗶𝗻𝗮𝗹 𝗖𝗠𝗦 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗖𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁

☐ Inventoried important pages, posts, media, and forms

☐ Recorded your pre-migration SEO and traffic baseline

☐ Taken a full backup

☐ Decided what content to keep, improve, or retire

☐ Preserved important URLs where possible

☐ Created an old-URL to new-URL redirect map

☐ Set up redirects before launch

☐ Verified SEO metadata

☐ Tested the staging site

☐ Checked pages, content, images, navigation, and forms

☐ Tested important redirects

☐ Submitted the new sitemap

☐ Monitored the site after launch

𝗙𝗶𝗻𝗮𝗹 𝗧𝗵𝗼𝘂𝗴𝗵𝘁

A CMS migration should not start with:

𝗟𝗲𝘁’𝘀 𝗺𝗼𝘃𝗲 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴.

Start with:

𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗺𝗼𝘃𝗲, 𝘄𝗵𝗮𝘁 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗯𝗲 𝗿𝗲𝗯𝘂𝗶𝗹𝘁, 𝗮𝗻𝗱 𝘄𝗵𝗮𝘁 𝗰𝗼𝘂𝗹𝗱 𝗯𝗿𝗲𝗮𝗸?

The more clearly you scope the migration before launch, the fewer surprises you have to deal with afterward.

Based directly on the existing SGEN migration guide and its seven-step migration process.