Part of the Site Migrations series. For the full picture, start with Site migration SEO checklist: crawl before, during and after launch.
Moving to a new CMS is usually decided for reasons that have nothing to do with SEO: a faster editor, a better checkout, a cheaper licence. The SEO risk is that a platform change quietly changes a hundred things search engines care about, and nobody compares them until traffic drops.
This guide covers what changes in a CMS migration and how to compare the old and new site so nothing changes by accident.
What changes when you switch CMS?
| Area | What often changes | Why it matters |
|---|---|---|
| URLs | Path formats, trailing slashes, category prefixes, file extensions | Every changed URL needs a redirect |
| Templates | Title and meta description patterns, H1s, heading structure | Rankings and snippets depend on them |
| Canonicals and indexing | Default canonical behaviour, noindex on archives or tags | Pages can silently drop out of the index |
| Internal links | Navigation, breadcrumbs, related posts, pagination | Crawl paths and link signals change |
| Structured data | Plugins or theme markup that don’t exist on the new platform | Rich results disappear |
| Rendering | Server-rendered HTML replaced by a JavaScript front end | Content may only appear after scripts run |
| Media | Image URLs, alt text, file names | Image search traffic and broken images |
| Performance | Heavier themes, more scripts, a different host | Core Web Vitals and crawl rate |
Google’s guide to site moves with URL changes covers the URL side. If URLs stay exactly the same and only the hosting changes, Google’s guide to moves without URL changes applies instead.
Can you keep the same URLs?
Try hard to. Unchanged URLs need no redirects, keep their links and history, and remove the biggest source of migration risk. Most platforms let you customise URL formats; check before you choose one.
Where URLs must change, build a page-to-page redirect map with server-side 301 or 308 redirects.
How do you compare the old and new site?
The core technique of a safe CMS migration is a side-by-side comparison of the two sites, template by template.
1. Benchmark the old site
Crawl the whole old site and keep the crawl. Connect Search Console and Analytics so you know which pages carry traffic. Export it to Excel: you’ll compare columns against the new site.
2. Crawl the new site on staging
Crawl staging with the same settings. If staging is behind a login, allow your crawler’s IP address; if it’s blocked in robots.txt, turn off Respect robots.txt for this crawl. If the new front end renders in the browser, turn on Render JavaScript.
3. Compare template by template
Take one URL of each template (home, category, product, article, landing page) and compare old and new:
| Element | What to check |
|---|---|
| Status and indexability | 200, indexable, no stray noindex |
| Title, meta description, H1 | Same or deliberately improved; no template defaults like “Home” or blank descriptions |
| Canonical | Self-referencing, on the new URL, not pointing at staging |
| Word count | Similar; a big drop means content or text blocks didn’t migrate |
| Internal links | Navigation, breadcrumbs and related links still present |
| Structured data | Same types, still valid |
| Raw vs rendered HTML | Main content and links present without JavaScript |
| Images | Present, with alt text |
Then run the checks across the whole staging crawl: Missing page title, Duplicate page titles, Missing meta description, Missing H1, Missing canonical tag, Noindex pages, Invalid JSON-LD, Content depends on JavaScript, Images missing alt text and Thin content.
If the URLs don’t change, Crawlens’s Compare works directly between the old-site crawl and a crawl of the new site after launch: it lists URLs that changed status, became non-indexable or changed title, and every issue that’s new.
4. Check JavaScript rendering
If the new platform is a JavaScript framework, read JavaScript SEO: raw vs rendered HTML before launch. Google can render JavaScript, but most AI crawlers don’t, and content or links that only exist after rendering are a common cause of post-migration losses.
5. Check performance
New themes and plugins often add weight. Measure Core Web Vitals on staging templates where possible and right after launch; see Core Web Vitals.
At launch
- Switch on redirects for any changed URLs, in one hop.
- Remove staging
noindexand robots.txt blocks. - Submit the new sitemap.
- If only the host changed, follow Google’s steps for moves without URL changes: lower the DNS TTL beforehand, switch DNS, and “keep an eye on the server logs on both new and old servers.” Google notes “it’s normal to see a temporary drop in Googlebot’s crawl rate immediately after the launch, followed by a steady increase over the next few days.”
After launch
- Crawl the old URL list in URL list mode: every changed URL should redirect once to its new equivalent.
- Crawl the new site from the homepage and compare with the benchmark.
- Check pages with traffic first: Pages with search traffic return errors and Pages with search traffic are not indexable.
- Schedule crawls for the first weeks with alerts; caches, plugins and editors often break things days after launch.
The full before/during/after process is in the site migration SEO checklist.
Checklist
- URL formats on the new platform match the old ones where possible
- Old site crawled and saved as a benchmark, with traffic data
- New site crawled on staging with the same settings (and JavaScript rendering if needed)
- Each template compared: status, indexability, title, description, H1, canonical, word count, links, structured data, images
- Site-wide checks on staging pass
- Content and links present without JavaScript
- Core Web Vitals checked on new templates
- Redirect map for changed URLs; one hop, server-side, permanent
- Staging blocks removed at launch; new sitemap submitted
- Old URL list and new site crawled after launch; pages with traffic checked first
Frequently asked questions
Does changing CMS affect SEO?
It can, because a new platform usually changes URLs, templates, metadata, internal links and sometimes how pages render. If the URLs and the content Google sees stay the same, the impact can be minimal; most losses come from changes nobody checked.
Should I keep the same URLs when changing CMS?
Yes, if the new platform allows it. Unchanged URLs need no redirects and keep all their links. Where URLs must change, redirect each old URL to its new equivalent with a server-side permanent redirect.
What if the new site uses a JavaScript framework?
Check that important content and links are in the HTML or render reliably. Google can process JavaScript, but rendering happens later and can fail, and most AI crawlers don't render it at all. Compare raw and rendered HTML on staging before launch.
What is a site move without URL changes?
Moving to a new host or CDN while every URL stays the same. Google has a separate, simpler process for it: test the new infrastructure, lower DNS TTL, switch DNS and watch both servers' logs. A crawl-rate dip right after launch is normal.
How do I compare the old and new site?
Crawl both with the same settings and compare them: status codes, indexability, titles, meta descriptions, H1s, canonicals, word counts and structured data, template by template. Differences you didn't intend are the things to fix before launch.