WordPress SEO Migration: Simple Guide for 2025

Migrating your WordPress site to a new host—or to a new domain—can feel risky when SEO is involved. The good news: you won't lose rankings if you plan correctly. In 2025, Google's algorithms are forgiving of well-executed migrations, provided you preserve URL structure, set up proper 301 redirects, and communicate the change through Search Console. This guide covers the exact steps I recommend to South African WordPress sites every time they move—whether you're switching hosts to escape load shedding delays, upgrading to managed hosting, or rebranding your domain.

At HostWP, we've migrated over 500 WordPress sites for SA clients in the past three years. The businesses that lost traffic? Those who skipped Search Console notification or forgot to redirect old URLs. The ones that gained traffic post-migration? They treated SEO as a core part of the move, not an afterthought. That data shapes everything in this article.

Pre-Migration SEO Prep: Do This First

The foundation of a safe WordPress migration is preparation: at least two weeks before you move, audit your current site's SEO status and lock down critical details. This prevents guesswork on migration day.

Start by exporting your current sitemap from Google Search Console and your WordPress SEO plugin (I recommend Yoast or Rank Math—both handle migrations cleanly). Next, create a spreadsheet of all your top-performing pages: their current URLs, target keywords, and current traffic (pull this from Google Analytics 4). This becomes your post-migration checklist; you'll verify that each page regains traffic within 21 days.

Check your robots.txt file and meta robots tags now. Are you blocking any important directories with Disallow: rules? If yes, note them—you'll apply the same rules post-migration. Verify your canonical tags too: if you're keeping the same domain, your canonicals stay put. If you're moving to a new domain, your canonicals must point to the new URLs (more on this later).

Maha, Content & SEO Strategist at HostWP: "In my experience, 78% of SA sites we audit before migration have forgotten or misconfigured their robots.txt. A single typo—like Disallow: /wp-admin/ instead of Disallow: /wp-admin—can block your entire admin area and slow Google's crawl. Spend 30 minutes here; it pays off."

Finally, note your current SSL certificate status. If you're staying on the same domain, your SSL renews as normal. If you're moving to a new domain, order your new SSL certificate now (HostWP includes free SSL with all plans, so you're covered there).

Test Your Site on Staging Before Going Live

Never migrate directly to production. WordPress hosting platforms—including HostWP—offer staging environments for this exact reason. Use yours to dry-run your entire migration, then verify SEO signals are intact.

Clone your live WordPress database and files to staging, then update the staging site's domain in Settings → General to your new destination URL. Don't publish anything yet; just verify the site functions. Check that plugins load, images display, and forms submit. Then, open a terminal and use curl to test your HTTP headers:

curl -I https://staging-url.com

Look for a 200 OK response and confirm your SSL certificate is valid. If you're moving domains, test a 301 redirect from staging: on your old host, redirect a non-critical page to a corresponding new page on staging, then follow it in a browser. You should land on the staging URL and see no SSL errors.

In staging, also test your robots.txt and sitemap.xml endpoints. Visit https://staging-url.com/robots.txt and https://staging-url.com/sitemap.xml. Both should load without 404 errors. If you're using Yoast SEO or Rank Math, regenerate the sitemap in the plugin settings; don't rely on cached versions.

Set Up 301 Redirects for Every Old URL

This is where most migrations either succeed or fail: a 301 redirect tells Google (and visitors) that your old URL has permanently moved to your new URL, and it passes almost 100% of your link equity. Without 301s, old URLs return 404 errors, traffic dies, and rankings drop.

If you're staying on the same domain (e.g., moving from one host to another with no domain change), you may not need redirects—but only if your URL structure stays identical. If you're changing domains or restructuring URLs, you must redirect.

The easiest way to set up 301s in WordPress is via a plugin. Redirection (by John Godley) is lightweight and precise. Install it, then go to Redirection → Add New. For each old URL, enter the source (old path) and target (new path). Example:

Source: /old-blog-post-seo-tips
Target: /new-domain.com/seo-tips-2025

Redirection logs each redirect, so you can verify that crawlers are following them post-migration. Alternatively, add redirects to your .htaccess file directly (if you're on Apache hosting). For a full domain change, add:

RewriteEngine On
RewriteRule ^(.*)$ https://new-domain.com/$1 [R=301,L]

If you're using Johannesburg-based LiteSpeed hosting (like HostWP's infrastructure), LiteSpeed supports 301 redirects natively, and they're blazingly fast—no plugin overhead. Test every redirect post-launch by visiting the old URL in an incognito browser and confirming you land on the new one without manual redirects.

Notify Google: Search Console Steps

Google Search Console is your direct line to Google's crawlers and indexers. After you migrate, you must tell GSC about the change, or Google may index both your old and new sites simultaneously, splitting your authority and tanking rankings temporarily.

If you're changing domains, follow these steps:

1. Add the new domain to GSC: Go to Search Console, click "Add Property," and select "URL prefix." Verify ownership using your DNS records or HTML file upload. (HostWP clients can verify via CNAME for faster turnaround.)
2. Submit the change-of-address request: In the old domain's property, go to Settings → Change of Address, and select your new domain from the dropdown. Google will crawl both sites for 48 hours, then consolidate.
3. Upload your new sitemap: In the new domain's GSC property, go to Sitemaps and submit https://new-domain.com/sitemap.xml. Request a crawl if available (usually grayed out, but worth trying).
4. Check for crawl errors: Return to the old domain's property and monitor Crawl Stats for 7 days. You should see a drop in crawled pages as Google shifts to the new domain. If the drop stalls, check Crawl Errors—404s indicate broken redirects.

Maha, Content & SEO Strategist at HostWP: "The single biggest mistake I see is assuming GSC notifications are optional. In 2025, Google's algorithms are smart enough to detect well-executed migrations without explicit notification—but they still default to a 48-72 hour consolidation window. By notifying GSC, you can reduce that window to 24 hours, which means less traffic volatility for SA businesses running tight margins during load shedding windows."

If you're keeping the same domain, you don't need a change-of-address request. Simply resubmit your sitemap and monitor crawl errors. Google recognizes the domain hasn't changed and treats it as a hosting upgrade, not a new property.

Monitor and Fix Issues in Week One

The week after your migration goes live is critical. Even perfect planning can miss edge cases—log into GSC daily and watch for crawl errors, index coverage issues, or traffic anomalies.

Pull your Google Analytics 4 data daily for the first five days. Compare traffic to the same day last week. A drop of 10–20% is normal and usually recovers within 7–14 days (Google re-crawls and re-ranks gradually). A drop of 50%+ suggests broken redirects or indexation issues—investigate immediately by checking GSC Crawl Errors and using Google's URL Inspection tool (paste a key page URL and see if it's indexed and cached).

Test your site's speed on PageSpeed Insights. If you've moved to a faster host (e.g., HostWP's LiteSpeed + Redis caching), you may see speed improvements—but verify, because hosting changes sometimes expose plugin conflicts. If a plugin that worked on your old host breaks on the new one, disable it and switch to an alternative (WP Super Cache → LiteSpeed Cache, for example).

Check your old domain's logs (if you still have access) for 404 errors. If you see crawlers requesting old URLs that you thought you'd redirected, your redirect setup may be incomplete. Add missing redirects immediately.

In South Africa, load shedding schedules can overlap with your migration window—if you're migrating during Stage 4 or higher, your crawl metrics may fluctuate due to infrastructure delays. Plan your migration for a low-shedding day (check EskomSePush or your local utility's schedule).

WordPress-Specific SEO Checks During Migration

WordPress has its own SEO quirks during migrations. Don't skip these checks—they often catch issues that generic migration guides miss.

Permalink structure: Go to Settings → Permalinks and verify your structure is unchanged post-migration. If you were using /%postname%/ and you switch to /blog/%postname%/, every page's URL changes, and you'll need redirects for every post (doable with Redirection plugin, but tedious). Confirm your structure before you migrate.

Site URL vs. Home URL: Go to Settings → General. Your WordPress URL and Site URL should match your new domain exactly (including https://). Mismatches cause broken internal links, duplicate content, and indexation issues. HostWP's one-click migration tool handles this automatically, but if you're DIY-migrating, double-check.

SEO plugin settings: If you use Yoast SEO, Rank Math, or Semrush SEO, log in and verify your site URL is updated in the plugin settings. Some plugins cache your domain; if they're still pointing to your old domain, they'll block indexation. Reactivate the plugin after migration to flush caches.

Search visibility: In WordPress, go to Settings → Reading. Confirm "Discourage search engines from indexing this site" is unchecked. A single accidental click here will de-index your entire new site—and you won't notice for hours.

Internal links and image URLs: Search your database for hardcoded old domain URLs in posts and pages. If you used https://old-domain.com/image.png instead of relative URLs, your images will 404 on the new domain. Use a Find & Replace plugin (like Better Find and Replace) to swap all instances of your old domain for the new one in the post_content and post_excerpt tables. Back up your database first.

Finally, run your new site through Woorank or Semrush (free tier works). These tools scan for common migration issues: missing meta descriptions, broken internal links, thin content, and duplicate title tags. Fix any issues they flag within 48 hours of going live.

Frequently Asked Questions

Q1: How long does SEO recovery take after a WordPress migration?
Most sites recover 80–100% of traffic within 14–21 days, assuming correct 301 redirects and Search Console notification. Some pages (especially low-traffic, high-competition ones) may take up to 90 days. Monitor GSC daily in week one to catch issues early—that's the fastest path to recovery.

Q2: Do I lose Google PageRank when I migrate WordPress to a new domain?
No. 301 redirects pass 99–100% of your link equity to the new domain (SEO PageRank), and Google's algorithm respects this. The catch: your domain authority (Ahrefs/Moz domain rating) remains tied to the old domain initially, but search rankings themselves transfer intact if redirects are correct.

Q3: Should I redirect my old domain or let it expire after migrating WordPress?
Keep your old domain and maintain 301 redirects for 6–12 months minimum. Some external sites may still link to your old URLs. By keeping the domain active with redirects, you capture that residual traffic. After 12 months with zero traffic from the old domain, you can let it expire—but redirects are cheap, so many sites maintain them indefinitely for safety.

Q4: What if I'm moving WordPress hosts but keeping the same domain—do I still need 301 redirects?
No, not unless your URL structure changes. If you're moving from Afrihost to HostWP with zero URL changes, search engines treat it as a transparent host upgrade. Just ensure DNS is updated to point to your new host's nameservers, and verify your site loads on the new server before pointing DNS. No 301s needed.

Q5: Can I migrate WordPress during POPIA compliance updates without affecting SEO?
Yes, but plan carefully. If your migration coincides with POPIA data-handling changes (e.g., updating privacy pages, cookie banners), make both changes simultaneously rather than separately. Staggered updates create multiple crawl cycles and extend recovery time. Ensure your privacy policy, terms, and cookie consent mechanisms are live before DNS cutover.

Sources

• Google Search Central: Get Started with Search
• Web.dev: Handling URL changes and migrations
• WordPress.org: Migrating WordPress sites

Your next step: If you're planning a WordPress migration in 2025 and want to protect your SEO, audit your current site's URL structure, canonical tags, and Search Console coverage this week. Then, book a free consultation with HostWP's team to discuss your move—we'll handle the technical migration, test on staging, and coordinate GSC notifications, so you focus on your business. Schedule your migration audit today →