Quick answer: A properly executed migration preserves rankings: map every URL to its new home with 301 redirects, carry over titles, meta descriptions, and structured data, keep your sitemap fresh, and verify in Search Console. Rankings typically dip 0–2 weeks during reindexing, then recover — and often improve, because Core Web Vitals jump on the new platform. The drops you've heard about come from three specific, avoidable mistakes.
"Will I lose my Google rankings?" is the number-one objection to leaving WordPress — reasonably, because organic traffic is often the site's most valuable asset. The truthful answer: Google doesn't rank WordPress; it ranks URLs with content and signals. Keep the URLs answering, keep the content and metadata intact, and the platform underneath is invisible to the algorithm. Here's the complete checklist.
Before: inventory everything Google knows about
- Crawl your own site (Screaming Frog, or your migration partner does it) — every URL, title, meta description, H1, canonical, and internal link.
- Export Search Console data — your actual ranking pages and queries. The pages earning traffic get white-glove treatment; the 40 tag archives nobody visits may not deserve to survive.
- Inventory structured data — recipe, product, FAQ, article markup — often generated invisibly by SEO plugins. It must be rebuilt natively on the new site, not forgotten.
- Note your redirect history — old redirects from previous redesigns must keep working (redirect chains flattened, not stacked).
During: the redirect map is the whole game
Every URL that exists today gets exactly one of two fates: it keeps working at the same address, or it 301-redirects to its successor. No 404s, no redirect chains, no "we'll catch them later."
The cleanest migrations keep URL structures identical (/blog/post-name stays /blog/post-name) — modern platforms handle arbitrary URL schemes, so WordPress's structure is not a constraint. Where structure must change, the map is explicit: one old URL → one new URL, 301, tested. Titles, descriptions, canonicals, hreflang, and OG tags carry over per page — not regenerated from a template.
After: verify, don't assume
- Resubmit the XML sitemap in Search Console the day you switch.
- Watch Coverage and Page indexing reports for two weeks — 404s that slipped through show up here first.
- Re-run PageSpeed: this is where the good news lands. Migrations we model typically move PageSpeed scores from the 30–50 range into the 90s, and Core Web Vitals are a confirmed ranking signal.
- Keep the old hosting alive (cheap plan) for a month as a safety net for anything missed.
The three mistakes that actually cause ranking drops
- The lazy blanket redirect — everything 301s to the new homepage. Google treats mass many-to-one redirects as soft 404s; the pages' equity evaporates. This single mistake accounts for most "migration killed our SEO" stories.
- Forgetting the invisible pages — image URLs that rank in image search, PDF files, category pages with backlinks. The crawl inventory exists precisely to catch these.
- Launching noindexed — the staging site's
noindextag ships to production. Ranking loss within days, entirely self-inflicted. It's one line in the launch checklist.
None of these are exotic — which is the point. Ranking loss is not an inherent risk of leaving WordPress; it's the signature of a migration done without a map.
What usually happens instead
For well-executed migrations the pattern is: a small wobble during reindexing (days, not months), then a return to baseline, then gradual gains as Core Web Vitals, cleaner markup, and faster server responses compound. Google's own documentation describes site moves as a normal, supported operation — with 301s, "site moves typically don't cause lasting traffic loss."
FAQ
How long does reindexing take after a migration? Most sites see Google recrawl and settle within 1–2 weeks. Larger sites take longer; the Search Console coverage report shows progress daily.
Do 301 redirects lose PageRank? Not meaningfully — Google has confirmed 301s pass full PageRank. Redirect chains (A→B→C) do waste crawl budget and dilute signals, which is why old redirects are flattened during migration.
Can I keep my exact URLs when leaving WordPress? Almost always yes — modern platforms have no opinion about your URL structure. Keeping URLs identical is the default in our migrations precisely because it makes the redirect map trivial and the SEO risk near zero.
Every LastPatch migration includes the full crawl inventory, one-to-one redirect map, and 30 days of post-launch Search Console monitoring — it's in every tier. Questions about your specific site? Book a free 20-minute call.