How to Migrate Your CMS Without Losing SEO Rankings

A website migration is the moment a lot of business owners lose sleep. You have spent years building up rankings on Google, that hard-won visibility brings in real enquiries, and now someone wants to move the whole site to a new platform. The fear is simple: do this wrong and the traffic vanishes.

It is a fair worry, but it is a manageable one. The aim of this guide is to show you, in plain terms, how to migrate your CMS without losing SEO. The headline is reassuring: ranking drops almost always come from avoidable mistakes, not from the migration itself. Get the planning right and your rankings should carry across.

Why badly-run migrations tank rankings

It helps to know what actually causes the damage, because once you see it, the fixes are obvious.

Google has spent years building a map of your site. It knows your URLs, what each page is about, and how much authority each one has earned. A migration that ignores that map is what causes the carnage. The usual culprits are:

• Changed URLs with no redirects. Pages move to new addresses and the old ones simply die. Google keeps sending people to dead pages, and the authority those pages built up evaporates.
• Dropped page signals. Titles, meta descriptions, headings and structured data get lost in the move, so pages that ranked clearly suddenly look vague to a search engine.
• Stale or missing sitemaps. Google is left guessing at the new structure instead of being handed a clear map.
• Accidental blocking. A leftover setting from the staging site quietly tells Google not to index the new site at all. This one is brutal and surprisingly common.

Notice that none of these are caused by the destination platform. Whether you are moving to Laravel, Statamic or anything else, the rankings risk lives in the handover, not the technology. That is good news, because the handover is entirely within your control.

Start with a pre-migration SEO audit

You cannot preserve what you have not measured. Before anything is built or moved, the first job is a full inventory of your current search presence. Think of it as taking a careful survey of a building before you renovate it.

Two sources matter most:

1. Google Search Console. This shows you which of your pages Google actually indexes, which ones bring in traffic, and which search terms they rank for. Export the indexed pages and the top-performing queries. This is your ground truth for what must not break.
2. A full site crawl. A crawler walks your entire site the way Google does and produces a complete list of URLs, along with their current titles, meta descriptions, headings, status codes and internal links. This catches pages that Search Console might not surface, including old ones you had forgotten about.

Cross-reference the two. The result is a master list of every URL worth preserving, ranked by how much traffic and authority it carries. Your highest-traffic and highest-authority pages get the most careful attention. Nothing important should be a surprise on launch day.

While you are auditing, also note which pages earn backlinks from other websites. Those inbound links are valuable, and you want the destination pages to keep working so that authority is not lost.

URL preservation and the 301 redirect map

This is the single most important part of the whole exercise, so it gets the most care.

The simplest, safest path is to keep your URLs identical wherever you can. If an address does not change, there is nothing to redirect and nothing to break. A well-planned Laravel build can usually preserve your existing URL structure deliberately, which removes the biggest source of risk before it ever appears.

Where URLs genuinely have to change, every old address needs a 301 redirect to its new home. A 301 is a permanent signpost. It tells browsers and Google "this has moved here for good", and it passes the old page's ranking authority across to the new one.

The deliverable is a redirect map: a one-to-one list pairing every old URL with its new destination.

A few rules keep this clean:

• Map to the closest equivalent. Send each page to the new page that matches it, not to a catch-all like the homepage. Bulk-redirecting everything to the homepage is treated by Google as good as deleting it.
• Avoid redirect chains. A redirect should point straight at the final URL, not hop through two or three others on the way.
• Do not leave orphans. Every indexed URL on your audit list needs a destination. The redirect map is not finished until each one is accounted for.

Preserving your on-page signals

With URLs handled, the next job is making sure each page still says the same thing to a search engine after the move. These signals are how Google understands and ranks a page, so they need to travel across intact:

• Page titles and meta descriptions. Carry them over exactly. These are often what shows in the search results, and changing them en masse can shift both rankings and click-through.
• Headings and body content. The actual words on the page are doing the ranking work. Keep them, and resist the temptation to "tidy" everything at the same time as migrating, as it makes any problem far harder to diagnose.
• Canonical tags. These tell Google which version of a page is the definitive one. Make sure they point at the correct new URLs and not at old or staging addresses.
• Structured data. Any schema markup, for products, articles, reviews, FAQs, breadcrumbs, needs recreating on the new site so your rich results in Google keep working.
• XML sitemap. Generate a fresh sitemap reflecting the new URLs, and make sure each entry carries an accurate lastmod date so Google knows what has genuinely changed. A Laravel site can generate this automatically and keep it current.
• Image alt text and file references. Preserve alt text, and make sure images still resolve at their new locations so image search and page context are not lost.

The rule of thumb: migrate first, improve later. Move everything across faithfully, confirm rankings are stable, and only then start optimising. Changing the platform and the content in one go means you can never be sure which change caused which result.

Redirect testing and the launch-day checklist

Redirects are worthless if they do not actually work, so they get tested before launch, not after. On a staging version of the new site, run your redirect map through automatically and confirm that every old URL lands on the right new one with a genuine 301, not a 404 and not a chain. Pay particular attention to your highest-traffic pages from the audit.

When launch day arrives, work through a clear checklist:

• The redirect map is live, and a sample of old URLs has been confirmed to resolve correctly.
• The new site is open to indexing. Double-check there is no leftover block from staging quietly hiding the site from Google.
• The XML sitemap is updated, published and submitted in Google Search Console.
• Titles, meta descriptions, canonical tags and structured data have carried over on your key pages, spot-checked directly.
• Analytics and Search Console tracking are in place and recording on the new site.
• Your most important and highest-traffic pages have been opened and checked by hand. Automated tools are essential, but human eyes catch things they miss.

Launching at a quieter time of day or week gives you a calmer window to watch for problems and react before much traffic is affected.

Post-launch monitoring and how to react

Going live is the start of the watching period, not the end of the job. For the first few weeks, Google Search Console is where you live.

Keep an eye on:

• Coverage and crawl errors. A small bump in "not found" errors as Google recrawls is normal at first. A growing pile of them means a redirect has been missed. Find the offending URL, add the 301, and it resolves.
• Indexed pages. The count should track close to your old site. A sharp drop is a warning sign worth investigating straight away.
• Impressions and clicks. A slight, brief dip as Google reprocesses the site is common and usually recovers within a few weeks. A steep, sustained fall is your signal to dig in rather than wait.
• Top queries and pages. Compare them against your pre-migration audit. If a page that used to rank well has slipped, check its redirect, its title and its content first, as the cause is usually one of those.

If something does move the wrong way, the audit you took at the start becomes your safety net. Because you measured everything beforehand, you can pinpoint exactly which page changed and put it right, rather than guessing in the dark. A clean migration usually settles quickly, and a faster, more stable site often does better than the old one once the dust clears.

Migrate with confidence

A migration does not have to be a gamble with your rankings. With a proper audit, a complete redirect map, faithfully preserved page signals and close monitoring afterwards, your hard-won visibility comes across with you. For the bigger picture of why a move makes sense in the first place, see our guide on moving from a legacy CMS to Laravel, and if you are coming from WordPress specifically, WordPress to Laravel migration covers the platform details.

If the thought of managing all this yourself is daunting, that is exactly what we handle. At AugmentBLU, an Edinburgh studio working with businesses across Scotland and the UK, SEO preservation is built into every migration as standard. Book a free consultation and we will talk through your current rankings and how we would protect them, with no obligation and a reply within 24 hours. You can also read more about our phased, low-risk approach on the CMS migration page.