SeahawkVIP

Migrating to WordPress without losing search traffic

A CMS migration is an SEO project whether you plan it as one or not. This is the checklist we use to keep rankings intact through cutover.

By Seahawk Engineering Team 2 min read

Teams put off leaving Drupal, Sitecore, AEM, or an aging WordPress install for one reason more than any other: fear of losing search traffic. The fear is fair. Most traffic drops after a migration come from a handful of avoidable mistakes.

Start with an inventory, not a sitemap

Your XML sitemap lists the pages your CMS knows about. Search engines know about more: old campaign pages, PDFs, paginated archives, and URLs with parameters. Build the inventory from several sources:

  1. A full crawl of the current site
  2. Every URL with traffic in analytics over the last 12 to 16 months
  3. Every URL with external backlinks
  4. Every URL that appears in Search Console

Join them into one sheet. This is the source of truth for the rest of the project.

Decide the fate of every URL

Each row gets one of three decisions:

DecisionWhenWhat happens
KeepThe page earns traffic, links, or conversionsSame URL, or a 301 to its new URL
MergeSeveral thin pages cover one topic301 all of them to one stronger page
RetireNo traffic, no links, no business value301 to the closest relevant page, or a 410

Avoid redirecting large numbers of retired pages to the home page. Search engines tend to treat that as a soft 404.

Migrate content as structure, not HTML

Pasting old HTML into the WordPress editor carries over broken markup, inline styles, and accessibility problems. Map old fields to structured WordPress fields and blocks, and script the migration with WP-CLI so you can run it again whenever the source changes.

Test redirects against the full list

Before cutover, run every URL in your inventory against staging and confirm each returns the expected status and destination. Look for redirect chains, loops, and mixed http and https hops.

Keep what search engines rely on

  • Title tags and meta descriptions for high-traffic pages
  • Canonical tags pointing at the new URLs
  • Structured data, including any you had before
  • Internal links updated to final URLs, not redirected ones
  • hreflang tags if the site is multilingual

Watch closely after launch

Submit the new sitemap, then check Search Console coverage, crawl errors, and rankings for your top pages every day for the first few weeks. Small issues found in week one are easy to fix. The same issues found in month three are not.

If you are planning a move to WordPress, our CMS migration service covers this end to end.

Back to all posts

Plan your next WordPress project with an engineer

Tell us what you are working on. A senior engineer replies within one business day with next steps, not a sales script.

Start a conversation