How do you move off WordPress without losing SEO?

Why do WordPress migrations hurt SEO in the first place?

The problem is not that you are leaving WordPress. Google does not care what platform your site runs on. The problem is that migrations typically change URLs, remove pages, break internal links, and wipe out meta data, all at once. Google has been building trust in your old URLs for months or years. When those URLs disappear without a forwarding address, Google has to decide whether your site still exists and whether the new pages deserve the same trust. Without redirects, the answer is often no, and rankings fall.

WordPress is also a frequent source of its own SEO baggage: category archive pages, tag pages, date archives, author pages, and dynamically generated URLs that you may never have noticed but that Google has indexed. When you leave, every one of those indexed URLs needs a plan.

What should you audit before touching anything?

The migration starts before a single line of new code is written. Your first job is to understand exactly what Google currently knows about your site. Skipping this step is the reason most WordPress migrations damage rankings.

• Export a full crawl of your current site. Use a tool like Screaming Frog, Sitebulb, or even Google Search Console's URL inspection to build a complete list of every URL Google has visited. This includes blog posts, category pages, tag archives, and any auto-generated WordPress pages you may have forgotten.
• Pull your Search Console index coverage report. This shows you which URLs Google actually has indexed. Cross-reference it with your crawl. Any URL in Google's index needs a redirect plan.
• Download your current meta data. If you used Yoast, Rank Math, or another SEO plugin, export your title tags, meta descriptions, and canonical URLs before you touch anything. These plugins store that data in the WordPress database, and once you shut down WordPress, that database is no longer easily accessible.
• Note your current rankings for key terms. Write them down or save a ranking report. This gives you a baseline to compare against after the migration so you know if something went wrong and where.
• Identify your highest-value pages. The pages that drive the most traffic or generate the most leads need extra care. If any redirect goes wrong, you want to catch it fastest on these pages.

Should you keep your WordPress URL structure or change it?

This is the most consequential decision in the whole migration. Keeping your URLs identical is the lowest-risk option because it eliminates the need for most redirects. If your WordPress site had /services/ and your new site also has /services/, there is nothing to redirect. Google follows the same URL and finds the same content.

The temptation when building a new site is to reorganize everything, rename pages, and create a cleaner structure. That is fine, and sometimes genuinely necessary, but every URL change is a redirect that needs to be set up and tested. If you are migrating 200 blog posts with new slug conventions, that is 200 individual redirects that each need to work correctly on launch day.

A practical approach: keep the URL structure for your high-traffic, high-value pages exactly the same. Restructure lower-traffic pages if you need to, but document every change. The goal is to make the redirect map before you build the new site, not after.

One WordPress-specific trap: the /category/ prefix in blog URLs. WordPress often creates URLs like /category/news/post-title/. If your new site uses /blog/post-title/, you need a redirect from every old category-prefixed URL to its new equivalent. It is tedious but not complicated, and it is essential.

How do you set up 301 redirects when leaving WordPress?

A 301 redirect tells Google and browsers that a URL has permanently moved. Google passes most of the ranking signals (historically described as link equity or PageRank) from the old URL to the new one through a 301. A 302 (temporary redirect) does not reliably pass those signals, so use 301s for every page you are migrating permanently.

Where your redirects live depends on your new platform:

• Custom hand-coded site on a server you control. Redirects go in an .htaccess file (Apache) or an nginx.conf block (Nginx). Your developer handles this as part of the build. Every redirect is a single line: Redirect 301 /old-url/ https://yourdomain.com/new-url/.
• Static site on Netlify or Cloudflare Pages. Both platforms support a plain-text _redirects file or a configuration block where you list old and new URLs. It is simple to set up and very reliable.
• Moving to a new CMS. Most modern CMS platforms have a redirect management section built in. Add each redirect there before launch.

Build your redirect map as a spreadsheet with three columns: old URL, new URL, and status code (301 for all permanent moves). Test every redirect before you flip the domain to the new site. The fastest way to test is to load the old URL in a browser after the new site is live and confirm you land on the right new page.

How do you move your WordPress SEO meta data to the new site?

Every page on your new site needs a title tag and meta description that at minimum matches what WordPress was serving before. If you are improving them, that is fine, but do not leave pages with missing or generic titles after launch. Google re-crawls your site and if it sees title tags missing, it generates its own, which are often worse than what you had.

The export process depends on your WordPress setup:

• Yoast SEO: The Yoast SEO plugin has a built-in export tool that generates a CSV of all your meta data. Use it before you shut WordPress down.
• Rank Math: Rank Math can export its SEO data similarly. Check the plugin's tools section for the export option.
• No SEO plugin: If you were relying on WordPress's default title generation, pull your title data from a crawl tool instead. The crawl will show you what Google has been seeing.

Beyond basic meta data, check whether your WordPress site was using structured data markup. Schema for local businesses, FAQs, breadcrumbs, or articles needs to be replicated on the new site. A hand-coded custom build gives you precise control over every schema block, which is often cleaner than what a WordPress plugin generates automatically.

What does the actual launch day process look like?

A smooth WordPress migration launch follows a specific sequence. Doing things out of order is where teams create problems that take weeks to untangle.

1. Confirm your new site is fully built and tested on a staging URL. Do not launch a half-finished site and redirect traffic to it.
2. Double-check your redirect map against the live site. Walk through every redirect in the spreadsheet and confirm the destination page exists and loads correctly on staging.
3. Update your DNS to point to the new host. DNS propagation takes up to 48 hours in the worst case, though it is usually faster. During propagation, some visitors will see the old site and some will see the new one.
4. Once DNS has propagated, verify all redirects are working. Load a sample of old URLs and confirm they land correctly. Check your 404 error log on the new server for any misses.
5. Submit your new XML sitemap to Google Search Console. Go to Search Console, select your property, navigate to Sitemaps, and submit the new sitemap URL. Remove the old WordPress sitemap if it is still listed.
6. Request indexing for your most important pages. In Search Console, use the URL Inspection tool to request that Google recrawl your key pages immediately rather than waiting for the regular crawl cycle.
7. Set up a monitoring check for 404 errors. Search Console's Coverage report will show crawl errors within a few days. Check it daily for the first two weeks.

What WordPress-specific SEO issues do you need to clean up before migrating?

WordPress generates a lot of URLs that many site owners do not know exist. Before you migrate, you should decide what to do with each of these categories, because they are likely in Google's index.

• Category and tag archive pages. WordPress creates /category/name/ and /tag/name/ pages automatically. If you have been running a blog, Google has probably indexed many of these. If your new site has no equivalent, redirect them to the blog index or to the most relevant page.
• Date-based archives. WordPress generates /2023/04/ style archive pages. These rarely have SEO value, but if they are indexed, redirect them to your blog index to avoid 404s.
• Author pages. /author/username/ pages are created automatically. Redirect them to your about page or your blog index.
• Pagination URLs. /blog/page/2/ and similar paginated URLs may be indexed. Redirect them to the blog index or to the canonical first page.
• Attachment pages. WordPress creates a separate page for every uploaded image at /?attachment_id=123. If these are indexed (they often are on older sites), redirect them to the image's parent post or to the home page.
• The /wp-login.php and /wp-admin/ URLs. These do not affect SEO, but they are also gone once you leave WordPress. No action needed, but they should 404 cleanly, not redirect somewhere confusing.

Where should you actually move to when you leave WordPress?

This is the question that matters most long-term, and the answer depends on what you actually need. The platform decision shapes your ongoing costs, your performance, and how much maintenance the site demands. There are a few honest options:

A custom hand-coded site is the highest-performance outcome. There are no plugins to patch, the files are small enough to load in under a second, and SEO is built into the structure rather than bolted on by a plugin. This is what FineWright builds. The trade-off is that you need a developer to make changes, which is why a care plan matters.

Squarespace is a more polished builder option with decent SEO defaults and a cleaner interface than WordPress. If you are deciding between it and a custom build, the Squarespace vs a custom website guide covers where each one wins and where each one falls short.

Shopify is worth considering if your reason for leaving WordPress was WooCommerce headaches. If you are running a store, the Shopify vs a custom website comparison is worth reading before you commit.

For a broader look at how all the platform options compare, including where custom builds beat every builder, the platforms and ways to build section of the guides covers the full landscape.

The platform you move to changes how your redirect setup works, how your meta data is managed, and how much ongoing maintenance the site needs. Pick the destination before you start the migration, not during it.

How long does it take for rankings to recover after leaving WordPress?

If the migration is done correctly, most sites see a minor fluctuation in the first two to four weeks while Google re-crawls and reassesses the new site, followed by a return to roughly the same rankings. Some sites see improvement fairly quickly, especially if the new site loads significantly faster or has cleaner HTML than the old WordPress build.

If rankings are still measurably lower after six to eight weeks, the most common culprits are:

• A redirect that was missed, sending a previously indexed URL to a 404.
• Title tags or meta descriptions that were not carried over, or were changed to something weaker.
• The new site being noticeably slower than the old one, which is rare when moving to a clean custom build but possible when moving to a heavy new platform.
• Internal links on the new site pointing to old WordPress URLs that now redirect, creating an extra hop that slightly dilutes link signals.
• The new site having significantly less content than the old one if pages were consolidated without redirects.

Search Console's Coverage and Performance reports are your diagnostic tool. If specific pages dropped, look up their old URLs in Coverage and confirm the redirects are in place and returning 301 status codes, not 302s.

Frequently asked questions

Will my Google rankings drop when I move off WordPress?

A temporary dip is possible while Google re-crawls your new site, but if you implement 301 redirects correctly, preserve your URL structure where possible, and migrate all title tags and meta descriptions, the rankings typically recover within a few weeks. The bigger risk is an unplanned migration with broken URLs and missing redirects, which can cause lasting damage.

How long do I need to keep my old WordPress site live during a migration?

You do not need to keep WordPress itself live, but you do need your redirects in place and working from day one. If your new host can serve the 301 redirects, you can shut down WordPress immediately after launch. Keep monitoring Google Search Console for crawl errors for at least 60 days after the switch.

Do I need to resubmit my sitemap to Google after leaving WordPress?

Yes. Submit your new sitemap through Google Search Console as soon as the new site is live. This signals to Google that your site has been updated and prompts a faster re-crawl. Remove the old WordPress sitemap from Search Console if it is still listed.

What happens to my WordPress plugins and their SEO settings when I migrate?

Plugins like Yoast or Rank Math store your SEO meta data in the WordPress database. Before migrating, export that data manually or use a plugin to generate a CSV of your title tags, meta descriptions, and canonical URLs so you can replicate them exactly on the new platform. The plugins themselves do not transfer.

Can I move off WordPress to a custom hand-coded site and keep my SEO?

Yes, and a well-built custom site often improves SEO because it loads faster, has cleaner HTML, and carries no plugin bloat. The migration process is the same: audit your current URLs, export your meta data, build the new site with matching or redirected URLs, implement 301s, and monitor Search Console. FineWright builds custom sites with SEO baked into the foundation from the start.

What is the single most common SEO mistake when leaving WordPress?

Launching the new site without 301 redirects in place. When Google follows an old URL and hits a 404, that page loses its ranking signals. If dozens of pages go to 404 at once, the overall site can drop significantly in search results. Set up and test every redirect before you flip the domain switch.