Moving from a site builder, a custom CMS or an aging platform to WordPress can unlock better editing, more flexibility and lower long-term costs. It can also wipe out years of search visibility if done carelessly. The good news is that traffic loss during a migration is usually caused by a handful of predictable mistakes. If you plan to migrate your website to WordPress, the process below will help you keep the rankings you have earned.
Why migrations lose traffic
Search engines rank individual URLs, not “your site” as a whole. When URLs change without redirects, content gets thinner, or important pages disappear, the signals those pages accumulated are lost. The most common causes are:
- Old URLs returning 404 errors instead of redirecting.
- Page titles, meta descriptions and headings changed or dropped.
- Content shortened or merged during the rebuild without a plan.
- Internal links still pointing to old addresses.
- The new site accidentally blocked from search engines at launch.
- Significant drops in page speed or mobile usability.
Every phase below is designed to prevent one of these.
Phase 1: Take inventory before you migrate your website to WordPress
Before any design work starts, capture exactly what exists today.
- Crawl the current site with an SEO crawler to list every URL, title, meta description, H1 and status code.
- Export performance data from Google Search Console and your analytics tool, so you know which pages bring traffic, rank for valuable queries and attract backlinks.
- Record backlinks to the site using Search Console’s links report, so you know which URLs other sites reference.
- Save copies of the old content and metadata. Once the old platform is switched off, this information can be hard to recover.
From this, mark your most valuable pages. These get the most care throughout the project.
Phase 2: Build the URL map
The URL map is the single most important document in a migration. It is a spreadsheet listing every old URL and where it will live on the new site.
| Old URL situation | Action on the new site |
|---|---|
| Page kept, same URL possible | Recreate it at the identical path |
| Page kept, URL must change | 301 redirect old URL to new URL |
| Two pages merged into one | Redirect both to the merged page |
| Page removed, relevant alternative exists | Redirect to the closest relevant page |
| Page removed, no alternative | Allow a 404 or 410 deliberately, but never for pages with traffic or backlinks |
WordPress gives you a lot of control over URLs through permalink settings, page hierarchy and custom post types, so it is often possible to keep many paths exactly as they were. Where it is not, redirects carry most of the value across. Avoid redirecting everything to the homepage; search engines tend to treat that like a missing page.
Phase 3: Move the content properly
How you transfer content depends on the source platform. Some have export formats that WordPress importers can read; others need custom import scripts or careful manual work. Whatever the method, check that:
- Titles, meta descriptions and headings carry over, or are improved deliberately rather than lost.
- Images are migrated into the WordPress media library, not hot-linked from the old platform that will be shut down.
- Image alt text comes across.
- Internal links are updated to the new URLs instead of relying on redirects.
- Structured content such as products, team members or projects is modeled properly, often with custom post types, rather than pasted into generic pages.
Do not use the migration to rewrite everything
It is tempting to rewrite all copy at the same time. Large content changes on top of a platform change make it hard to tell what caused any ranking movement. Where possible, migrate first and refine content afterwards in planned stages.
Phase 4: Pre-launch checks on staging
Build and test on a staging site that is protected from indexing. Before launch, verify:
- Every URL on the map either loads correctly or redirects with a single 301 hop.
- Title tags, meta descriptions and canonical tags are present and correct.
- An XML sitemap is generated and lists the new URLs.
- Forms, tracking codes and conversion events work.
- Key pages load quickly on mobile. If they do not, our guide to making WordPress load faster is a good starting point.
Phase 5: Launch day
- Take final backups of both the old and new sites.
- Switch DNS or deploy the new site at a quiet time for your business.
- Remove any “discourage search engines” setting and staging password protection.
- Activate the redirect rules and test a sample of old URLs immediately.
- Submit the new sitemap in Search Console. If the domain itself is changing, also use the Change of Address tool.
- Keep the old platform’s data accessible until you are confident nothing is missing.
Phase 6: Monitor the weeks after
Some ranking fluctuation after a migration is normal while search engines recrawl the site. What matters is spotting real problems quickly:
- Check Search Console daily at first for crawl errors and 404s, then weekly.
- Compare traffic to your top pages against the pre-migration baseline.
- Fix any missing redirects as soon as they appear.
- Watch for pages that drop sharply and compare their old and new content.
When the migration is part of a bigger change
Sometimes a “move to WordPress” is also a move to selling online, adding a customer portal or integrating with business systems. In those cases, the platform decision deserves its own analysis. Our comparison of WooCommerce vs Shopify may help if e-commerce is involved.
Migrate with a team that has a plan
SiteWright Technologies handles WordPress migrations end to end: content inventory, URL mapping, imports, redirects, technical SEO and post-launch monitoring. Find out more about our WordPress development services or get in touch to scope your migration.


