Moving to a New CMS Without Shedding Search Visibility: A UK SME Migration Playbook

A migration is an SEO event, not just a web build

Most website migrations sold to UK SMEs are framed as platform upgrades: a new CMS, a faster storefront, a better booking flow. Search visibility is treated as a technical detail to be handled at the end. That sequencing is backwards. The moment URLs, templates and internal links change, search engines must relearn the site. Rankings can fall before the launch checklist is signed off.

The good news is that most migration damage is preventable. The bad news is that prevention requires boring work: inventories, redirect maps, staging crawls and post-launch monitoring. If an agency cannot show you those artefacts, the migration is not ready.

Risk one: URL mapping left to guesswork

Every URL that matters should be mapped from the old site to the new one. That includes pages with organic traffic, pages with backlinks, category pages, product pages, blog posts and any local landing pages. Export the list from Google Search Console, analytics, XML sitemaps and a full crawl. Then map each old URL to the closest new equivalent.

Redirecting everything to the homepage is not a migration strategy. It tells search engines that the old page has been replaced by a generic entry point, and it usually frustrates customers. Use permanent 301 redirects at server level. Avoid redirect chains, loops and JavaScript-based redirects. Where a page genuinely no longer exists, return a clear 404 rather than sending users to an irrelevant page.

Risk two: redirects that work in testing but fail in practice

A redirect map can look complete in a spreadsheet and still fail after launch. Test the old URLs, including those with trailing slashes, uppercase characters and query strings. Check that HTTPS and the preferred www or non-www host resolve consistently. Confirm that redirects do not point to staging URLs, password-protected pages or another redirect.

Keep redirects in place for at least a year, and longer for established pages with backlinks. A redirect is not a temporary courtesy. It is part of the site's historical record.

Risk three: template changes quietly remove signals

A new theme can improve design and damage search signals at the same time. Check page titles, meta descriptions, heading structure, canonical tags, robots directives and structured data. Ensure that staging noindex tags are removed at launch. Confirm that pagination, filters and category pages behave as intended.

For UK service firms, local business structured data and location-page templates deserve particular attention. For ecommerce businesses, product and category templates need unique copy, sensible internal links and stable canonical rules. A faster template is welcome, but speed does not compensate for missing or duplicated page signals.

Risk four: internal links still point to the old site

Internal links should point to final URLs, not rely on redirects. New CMS content often contains hardcoded links to the old domain or old paths. Navigation menus, footer links, calls to action and blog body copy all need review. Update the XML sitemap and robots.txt at the same time.

This is also the moment to fix orphan pages and weak category structures. A migration is a rare chance to improve internal linking, but only if someone owns the task.

Risk five: launch without a monitoring plan

Before launch, record a baseline: organic sessions, rankings for priority terms, indexed page count, conversions and revenue where relevant. After launch, monitor Google Search Console for coverage errors, page indexing changes and manual actions. Crawl the new site, check for 404s and redirect chains, and compare performance against the baseline.

Lower DNS time-to-live before launch so that a rollback is possible. Avoid a Friday afternoon switchover. Have a named person responsible for checking the site on day one, day seven and day thirty.

A UK SME migration checklist

Before build: secure ownership of the domain, DNS, analytics and Search Console; create a full URL inventory; agree the redirect map; crawl the old site; freeze content changes; back up the site.

At launch: deploy redirects; remove staging blocks; publish the new sitemap; check robots.txt; test forms and key journeys; verify canonicals and structured data.

After launch: submit the sitemap; monitor indexing; fix broken links; update internal links to final URLs; review Core Web Vitals; keep redirects live; report against the baseline.

Agency handover mistakes worth challenging

Be direct with any agency or developer managing the move. Ask for the URL inventory and redirect map. Ask who owns Search Console and DNS. Ask what post-launch monitoring is included and for how long. Ask whether internal links will be updated or left to redirect.

If the answer is that only the main pages will be redirected, or that monitoring starts when rankings fall, challenge it. A migration is not complete on launch day. It is complete when the new site is crawlable, indexed, measured and stable.

The straight-talking conclusion

A platform move can improve speed, administration and customer experience. It can also erase years of search equity in a weekend. The difference is not luck. It is a mapped URL set, tested redirects, reviewed templates, corrected internal links and disciplined post-launch monitoring. UK SMEs should demand those basics before the switch is flicked.