Threads that gather, pass through a circle and fan out again, three of them orange.

Switching platforms without losing traffic

After twenty years and a couple of hundred platform migrations, it’s rarely the technology that worries me. It’s everything else: what a website has built up over the years that neither shows in the design nor appears in the requirements. It’s the easiest thing to lose in a move and the hardest to get back.

The week after launch, the new website is often better at everything you can demonstrate in a meeting: it’s faster, easier to update and in line with the new visual identity. Yet visits from Google may have fallen. The reason is usually the same: no one found out what the old website was actually doing well.

The migrations I’ve handled have ranged from large, complex sites with hundreds of thousands of records to small websites. Size has determined how much work the move required, but keeping visitors coming has been a concern in every one. On a large site, that means thousands of URLs; on a small one, perhaps a dozen pages. And if those are the pages generating enquiries, just as much is at stake.

What happens to traffic when you switch platforms?

When a website switches platforms, its pages move, and that move puts traffic at risk. Google indexes and assesses each page by its address (URL), and everything that contributes to its ranking, from links on other websites to the keywords it answers and how visitors have used it, is tied to that particular URL. If the page gets a new URL without a permanent redirect (a 301, which automatically sends visitors and search engines from the old URL to the new one), that connection breaks and Google treats the page as new. It then has to build its ranking from scratch.

That’s what makes it different from a regular update, where pages get a new look but keep their URLs. In a platform migration, every URL, link and signal has to end up in the right place. Otherwise, the pages that brought in the most traffic start again from zero.

Google’s own guidance on site moves says the same thing: redirect old URLs to new ones using permanent redirects and keep them in place for as long as possible, generally at least a year.

Why do so many sites lose traffic?

We see the same four causes time and again.

  1. The first is that no one has taken stock of the old site. The requirements describe the new website in detail but say nothing about the old one, so no one knows which pages bring in traffic, which have links from other sites or which forms generate enquiries, until traffic has already fallen.
  2. URLs often change without anyone deciding they should. A new platform has its own rules for building URLs, so categories are renamed, folders disappear and suffixes are added. Each change is small on its own. Together, they can mean hundreds of pages getting new URLs.
  3. Redirects, which should preserve what can be preserved, are often left until last. They’re added the week before launch by someone who doesn’t know which pages matter, so many end up pointing to the homepage, something Google may treat as a broken page (a so-called soft 404). Others form chains, where an old URL goes through several redirects before reaching its destination. This slows the site down and is something Google explicitly advises against.
  4. Finally, settings from the test environment get carried over. A site built at a test URL is usually blocked from search engines, and that block needs to be removed at launch. If it’s forgotten, the site won’t appear in search results at all, however good it is.

What does it cost?

A migration error often shows up in traffic within the first few days, but how long the impact lasts depends on how serious the error is and how quickly someone spots it. Sometimes the site recovers in a few weeks. Sometimes it takes months, and sometimes rankings never return because a competitor has taken those positions in the meantime.

The cost rarely shows up in a technical report. It shows up in fewer enquiries, often only when the sales team starts wondering where they’ve gone.

How to plan a successful switch

1. Measure before you build

You can’t compare results after the switch if you haven’t measured them beforehand, so start by recording where things stand today:

  • Pages receiving visits from Google, with click totals for the past twelve months (from Search Console).
  • Keywords and rankings for the pages that matter most.
  • Pages with links from other websites.
  • Form submissions, phone number clicks and other events that generate business, and the pages where they happen.
  • A complete crawl of all URLs, so no page is overlooked.

The result is a list of what must not be lost, and that list is the foundation for every step that follows.

2. Decide on URLs before design begins

URL structure belongs in the planning stage, not the build. Decide early which pages will keep their URLs and which will get new ones. The more you keep, the fewer redirects you need and the less can go wrong. Don’t change URLs just because that’s the new platform’s default: most systems can be configured to keep them as they were.

3. Create a complete redirect list

Every old URL that ranks or has links from other sites should point to the new page that answers the same question. The list must meet four requirements:

  • Page to page. Not everything to the homepage.
  • One hop. Old URL straight to new, with no steps in between.
  • Permanent (301). Not temporary.
  • Tested before launch on a copy of the site, checking the entire list.

Pages that are removed entirely should redirect to the closest match on the same topic. If there isn’t one, a clear 404 response (page not found) is better than a redirect to the wrong place.

4. Move what ranks, and improve it later

It’s tempting to rewrite all the copy while you’re switching platforms, but leave the pages that bring in traffic alone. Move them first with the same headings and content, then improve them once the migration has settled. That way, you’ll know what caused any change in traffic. You can’t know that if the platform and the copy change on the same day.

5. Bring the unseen details with you

What gets lost in a migration is usually what visitors don’t see but search engines read:

  • Page titles and meta descriptions.
  • Headings and internal links.
  • Image alt text.
  • Canonical tags (which identify the preferred URL when the same content appears at several addresses).
  • Language versions and hreflang (which identifies each language version), if the site is multilingual.
  • Structured data.
  • A sitemap with the new URLs, and a robots.txt file that allows search engines access.
  • Tracking: Analytics, Tag Manager and conversions.

6. Check on launch day

Run these checks the day the site goes live, not the following week, because every day with an error costs you traffic:

  1. Search engine blocks have been removed, both in robots.txt and in the platform settings.
  2. The most important old URLs lead to the right page in one hop.
  3. The new sitemap has been submitted in Search Console.
  4. The pages listed in step 1 return a 200 response (page exists) and have the right title.
  5. Forms and tracking work, tested as a regular visitor rather than while logged in.

7. Monitor for ten weeks

The first few weeks will show whether anything has gone wrong. Track clicks and impressions in Search Console day by day, compare them with the equivalent period before the switch and pay particular attention to the pages listed in step 1.

Monitoring needs a clear owner who also has the authority to get changes made. An error spotted on day four is small, but by day forty the same error has become expensive.

What should you expect from your agency?

You can ask these questions during public procurement, before you’ve chosen a supplier:

  1. How do you identify which pages bring in traffic today?
  2. Who decides the URL structure, and when?
  3. Will we receive the redirect list before launch so we can review it?
  4. How do you test that it works?
  5. What happens to page titles, headings and internal links?
  6. Who monitors traffic after launch, and for how long?
  7. What do you do if traffic falls?

An agency that gives concrete answers to these seven questions has done this before. If it says instead that search engine optimisation will be addressed at a later stage that’s a warning sign, and it’s also mistake 10 in ten mistakes we see in website procurement.

Does this apply even if we have good reasons to switch platforms?

Yes, perhaps especially then. Leaving a platform that’s outdated, insecure or expensive to maintain is often the right decision, but even the right decision can be carried out badly. We cover how to choose a new platform in the CMS guide. This article is about making the move without losing what you’ve already built up.

Frequently asked questions

Planning a web project?

Our guide Website procurement walks you through the whole process, from the brief and target audience to the requirements. Download the guide


Sources