WordPress Migration Case Study: How a News Blog Kept Its Rankings

Migration case studies are everywhere, but most skip the details that matter: what actually happened to rankings, how long recovery took, and what went wrong along the way. This case study covers a WordPress news blog with over 200 published posts, steady organic traffic, and a realistic migration timeline. Every data point comes from Google Search Console, PageSpeed Insights, and server logs — no cherry-picked metrics.

The blog ran WordPress for three years. It had a custom theme, 23 active plugins, a managed hosting plan costing $49 per month, and a growing maintenance burden that was eating into publishing time. The owner spent more hours per week updating plugins and troubleshooting compatibility issues than writing new content.

The migration target was a headless blog platform with edge rendering, built-in SEO scoring, and zero server maintenance. The goal was simple: stop spending time on WordPress upkeep without losing the organic traffic that took three years to build.

WordPress migration timeline showing four phases: audit week, migration weekend, monitoring month, and full recovery at six weeks
The complete migration timeline

The starting point: a WordPress news blog in numbers

Before changing anything, the owner documented every metric that mattered. This baseline became the benchmark for measuring migration success or failure.

Metric

Before Migration

Published posts

214

Monthly organic sessions

8,400

Avg. position (top 50 keywords)

14.2

Pages indexed in Google

231

Core Web Vitals (LCP)

4.1 seconds

Core Web Vitals (CLS)

0.18

Core Web Vitals (INP)

380 ms

Monthly hosting cost

$49

Active plugins

23

Time on maintenance per week

3–4 hours

The site was not in crisis. Traffic was stable, rankings were reasonable, and the hosting was reliable. But the owner recognized a pattern: every month brought another plugin conflict, another security advisory, another afternoon spent debugging instead of writing. The slow decline that WordPress blogs experience had already started — LCP was above the 2.5-second threshold Google recommends, and CLS was failing.

Why migrate now instead of later

Three factors pushed the decision from "eventually" to "this month":

  1. Core Web Vitals failures. Google had been sending Search Console warnings for months. LCP at 4.1 seconds meant every page failed the "Good" threshold. The site was losing ranking opportunities to competitors with faster pages.
  2. Plugin security incident. A vulnerability in a popular contact form plugin exposed the admin panel to brute-force attacks. The plugin had been auto-updated, but the update introduced the vulnerability. Fixing it required rolling back, finding an alternative, testing, and redeploying — six hours of work.
  3. Publishing workflow friction. The Gutenberg editor loaded slowly on the managed host, saving took 2–3 seconds per block, and preview required a full page refresh. Writing a 2,000-word article took 30 minutes longer than it should have because of editor lag.

The owner had already read the migration guide and the SEO preservation checklist . The question was not whether to migrate but how to do it without losing three years of SEO investment.

Pre-migration audit: what we checked before touching anything

The audit took one evening. Every step exists to catch problems before they become ranking losses.

  1. URL inventory. Exported all 231 indexed URLs from Google Search Console. Every URL needed a 1:1 match or a 301 redirect on the new platform.
  2. Redirect audit. The WordPress site already had 17 redirects from previous slug changes. Each redirect needed to work on the new platform too — a redirect chain (old → WordPress redirect → new) kills PageRank.
  3. Internal link map. Crawled the site with Screaming Frog. Found 1,847 internal links across 214 posts. These links would break if any slug changed without a redirect.
  4. Image inventory. 892 images across all posts, hosted on the WordPress server. Every image URL needed to keep working or redirect to the new CDN location.
  5. Structured data check. The Yoast plugin generated Article schema and breadcrumb schema. The new platform needed to generate equivalent structured data or Google would lose rich result eligibility.
  6. Backlink profile. Ahrefs showed 340 referring domains pointing to 89 unique pages. These external links could not be changed — the new platform had to serve the same URLs or redirect them.
💡

The single most important pre-migration step is the URL inventory. Export your indexed pages from Search Console (Pages → Indexed → Export). If even one high-traffic URL returns 404 after migration, you lose that page's entire ranking history. The full SEO migration checklist has 25 steps organized by phase.

Before and after performance comparison showing Core Web Vitals improvements: LCP from 4.1s to 0.8s, CLS from 0.18 to 0.02, INP from 380ms to 45ms
Performance transformation after migration

The migration: one weekend, four phases

The entire migration happened over a Saturday and Sunday. The WordPress site stayed live during the process — nothing was taken offline until the new site was verified.

Phase 1: Content import (Saturday morning, 2 hours)

The WordPress REST API exported all 214 posts with their full content, categories, tags, featured images, and publication dates. The one-click WordPress importer pulled everything in a single operation. The headless migration guide details the three import methods — we used the automated one.

What transferred automatically:

  • Post titles, body content, and formatting
  • Publication dates (preserving the original publish timestamps)
  • Categories and their hierarchy
  • Featured images (re-hosted to the edge CDN automatically)
  • URL slugs (1:1 match with WordPress slugs)
  • Excerpt text

What required manual work:

  • Shortcodes : 12 posts used WordPress shortcodes for embedded content. These rendered as raw shortcode text after import and needed manual cleanup.
  • Plugin-generated content : Table of contents, related posts, and star ratings generated by plugins did not transfer. The new platform handles TOC and related posts natively.
  • Custom widgets : Sidebar widgets (recent posts, category lists, newsletter signup) needed to be recreated in the new theme configuration.

Phase 2: SEO verification (Saturday afternoon, 3 hours)

This was the most critical phase. Every SEO signal had to match or exceed the WordPress version.

  • URL structure : Verified all 214 slugs matched exactly. The import preserved flat slugs (e.g., /post-title). WordPress date-based URLs (/2024/03/post-title) needed 301 redirects to the flat slug — the platform created these automatically during import.
  • Meta titles and descriptions : The Yoast metadata imported correctly. Spot-checked 20 high-traffic pages against the Search Console baseline.
  • Canonical tags : Each page generated a self-referencing canonical. Verified with a crawl of 50 sample pages.
  • Sitemap : The new platform generated a sitemap at /sitemap.xml with all 214 posts. Compared against the WordPress sitemap — same URLs, same structure.
  • Robots.txt : Verified the new robots.txt allowed all crawlers and pointed to the sitemap.
  • Structured data : Tested 10 pages with Google Rich Results Test. Article schema, author, datePublished, and dateModified all present.

Phase 3: Performance testing (Saturday evening, 1 hour)

Ran PageSpeed Insights on the 20 highest-traffic pages before switching DNS. The results made the decision easy:

Metric

WordPress

New Platform

Change

Largest Contentful Paint

4.1 s

0.8 s

−80%

Cumulative Layout Shift

0.18

0.02

−89%

Interaction to Next Paint

380 ms

45 ms

−88%

Total Blocking Time

1,200 ms

50 ms

−96%

Speed Index

5.2 s

1.1 s

−79%

Performance Score

38

98

+158%

Edge rendering eliminates the WordPress bottleneck: PHP processing, database queries, and origin-server round trips. Pages are served as static HTML from the nearest Cloudflare edge node. The platform comparison breaks down why architecture matters more than features for long-term SEO.

Phase 4: DNS cutover (Sunday morning, 30 minutes)

The DNS change was the point of no return. The process:

  1. Changed the domain's DNS A/CNAME records to point to the new platform.
  2. Set TTL to 300 seconds (5 minutes) 24 hours before the switch, so the old long TTL expired.
  3. Verified the site loaded correctly from multiple geographic locations using a DNS checker.
  4. Submitted the updated sitemap in Google Search Console.
  5. Requested indexing for the 10 highest-traffic pages to accelerate re-crawling.

The WordPress site remained accessible at a temporary URL for 90 days as a fallback. This is non-negotiable — if something goes catastrophically wrong, you can point DNS back within minutes.

What happened to rankings: the six-week timeline

This is what most case studies skip. Rankings do not transfer instantly. Here is exactly what happened, week by week.

Six-week ranking recovery timeline showing initial dip, stabilization, and recovery: week 1 minus 15%, week 2 minus 8%, week 3 recovery to baseline, week 6 plus 12% above original
Ranking recovery timeline after WordPress migration

Week 1: The expected dip

Organic traffic dropped 15% in the first week. This is normal and expected for any domain migration. Google was re-crawling pages, re-evaluating Core Web Vitals, and processing the DNS change. Search Console showed increased crawl activity — Googlebot was visiting 3x more pages per day than usual.

The temptation to panic is real. But a 15% dip in week one is within the normal range for a well-executed migration. A badly executed migration shows 40 to 60% drops and does not recover.

Week 2: Stabilization

Traffic recovered to 92% of the pre-migration baseline. Core Web Vitals data in Search Console started updating — the new "Good" scores were replacing the old "Poor" scores. Three pages that had lost positions started climbing back.

Weeks 3–4: Recovery and the first gains

Traffic returned to the pre-migration level and then exceeded it by 4%. The Core Web Vitals improvement was now fully reflected in Search Console. Five keywords that had been stuck at positions 11–15 moved to positions 8–10 — the first page. This was not coincidence: Google confirmed in 2021 that page experience signals (including Core Web Vitals) are used as a ranking factor.

Weeks 5–6: New baseline

Traffic settled at 12% above the pre-migration baseline. The gains came from three sources:

  • Core Web Vitals boost : Pages that now passed all three CWV metrics gained a small but consistent ranking advantage.
  • Faster crawling : Googlebot could crawl more pages in less time because each page responded in under 100ms instead of 2–4 seconds. More pages indexed, more impressions.
  • Reduced bounce rate : Faster pages meant visitors stayed longer. Average session duration increased from 1:42 to 2:15, and bounce rate dropped from 68% to 54%.

Before and after: the complete comparison

Metric

Before (WordPress)

After (6 weeks)

Change

Monthly organic sessions

8,400

9,408

+12%

Avg. position (top 50 keywords)

14.2

11.8

+17%

Pages indexed

231

228

−1% (3 thin pages de-indexed)

Core Web Vitals pass rate

0%

100%

All pages pass

LCP (p75)

4.1 s

0.8 s

−80%

Monthly hosting cost

$49

$0

−100%

Active plugins

23

0

No plugins needed

Weekly maintenance hours

3–4

0

Zero maintenance

Time to publish a post

45 min

15 min

−67%

What went wrong during migration

No migration is perfect. Three things went wrong, and each one has a lesson.

Problem 1: Twelve posts with shortcodes rendered incorrectly

WordPress shortcodes like [gallery], [caption], and a custom [pullquote] shortcode rendered as raw text after import. The platform imported them faithfully — as text — because shortcodes are a WordPress-specific feature with no universal equivalent.

Fix : Manually edited 12 posts over two hours. Replaced [gallery] with native image blocks, [caption] with image captions, and [pullquote] with blockquotes. This is unavoidable — shortcodes are the tax you pay for using WordPress-specific features.

Problem 2: One redirect was missing

A post that had been renamed in WordPress two years ago had a redirect from the old slug to the new one. The import transferred the post with its current slug, but the old redirect was not automatically created. Google still had the old URL indexed.

Fix : Found the missing redirect by comparing the Search Console URL inventory against the new sitemap. Added the redirect manually. The old URL started returning 301 within minutes. Lesson: always compare your pre-migration URL list against the live site, not just the sitemap.

Problem 3: Image lazy loading changed the above-the-fold experience

The WordPress theme loaded the first image eagerly (no lazy loading for the hero image). The new platform lazy-loaded all images by default, including the first visible one. This briefly worsened LCP for pages where the hero image was the largest contentful paint element.

Fix : Set the featured image to eager loading in the theme configuration. LCP returned to sub-second on affected pages.

Seven lessons from this migration

  1. Document everything before you start. The URL inventory, redirect list, internal link map, and performance baselines saved the migration. Without them, there is no way to verify success.
  2. Keep WordPress running in parallel. The 90-day parallel period is insurance. It costs $49 (one month of hosting, then cancel) and buys peace of mind. If rankings had dropped 50% instead of 15%, DNS could have been pointed back in minutes.
  3. Expect the week-one dip. Traffic drops 10 to 20% after any well-executed migration. Set expectations with stakeholders before the switch. A dip is normal; a cliff is a problem.
  4. Check shortcodes before migrating. Search your WordPress posts for square brackets. Every shortcode needs a plan: manual replacement, removal, or a native equivalent on the new platform.
  5. Verify redirects with your pre-migration URL list. Sitemaps only show current URLs. Your pre-migration list shows what Google has indexed, including URLs that redirect. Both must resolve correctly.
  6. Submit the sitemap immediately after DNS cutover. This tells Google to re-crawl now instead of waiting for the next scheduled crawl. Request indexing for your top 10 pages to accelerate recovery.
  7. Monitor for 90 days, not 90 hours. Some ranking changes take weeks to materialize. Check Search Console weekly for three months. Only then can you call the migration complete.
Migration success checklist with seven verification steps: URL match, redirects, metadata, structured data, performance, sitemap, and monitoring
Post-migration verification checklist

Would they do it again?

The migration took one weekend. WordPress maintenance was taking one weekend every month. The math is obvious in hindsight.

Six months after migration, the blog has published 47 new posts — more than the previous six months on WordPress. The time saved on maintenance went directly into writing. Publishing is faster because the editor loads instantly, saves in real time, and preview is immediate.

The SEO improvements were a bonus. The real win was reclaiming the time that WordPress was consuming. For bloggers considering the same move, the WordPress migration guide walks through every step, and the SEO checklist ensures nothing falls through the cracks.

Does this apply to your WordPress blog?

This case study describes a 200-post news blog. Your situation differs, but the principles transfer:

  • Small blogs (under 50 posts) : Migration is simpler. Fewer URLs to verify, fewer internal links to check, fewer images to transfer. The same checklist applies, but it takes hours instead of a weekend.
  • Large blogs (500+ posts) : The process scales linearly. More posts means more verification time, but the importer handles volume automatically. The risk is proportionally higher — a single missed redirect on a high-traffic page costs more.
  • E-commerce blogs : If your blog is part of a WooCommerce store, migrate only the blog content. Keep WooCommerce for the store. Run the blog on a subdomain (blog.yourdomain.com) or as a separate section.
  • Multi-author blogs : Author pages and attribution transfer during import. Verify author archives generate correct structured data on the new platform.

The one constant across all sizes: SEO fundamentals do not change because you changed platforms. The platform handles the technical SEO (speed, structured data, canonical tags). You handle the content SEO (keyword targeting, internal linking, content quality). Migration is the technical part. The content part continues as before.

The cost of migrating versus staying on WordPress

Migration has a one-time cost measured in hours. Staying on WordPress has an ongoing cost measured in money and time.

Cost category

WordPress (annual)

After migration (annual)

Hosting

$588 ($49/mo)

$0 (free plan)

Plugin licenses

$180 (premium plugins)

$0

Maintenance time

156–208 hours

0 hours

Security monitoring

$60 (Sucuri/Wordfence)

$0 (built-in)

CDN

$120 (Cloudflare Pro)

$0 (included)

Total annual cost

$948 + 156–208 hours

$0 + 0 hours

The migration itself cost approximately 12 hours of work spread over one weekend. At the old rate of 3–4 hours per week on WordPress maintenance, the migration paid for itself in three to four weeks. The self-hosted vs managed comparison details why the maintenance gap exists architecturally.

Frequently asked questions

How long did the entire migration take?

Twelve hours of active work over one weekend. The audit took one evening (Friday), the import and verification took Saturday, and the DNS cutover happened Sunday morning. Rankings recovered fully in six weeks.

Did any pages permanently lose rankings?

Three thin content pages (under 200 words each) were de-indexed by Google after migration. These pages had been barely indexed on WordPress too — they were not contributing meaningful traffic. Every page with real content recovered its rankings within six weeks.

What tools were used for verification?

Google Search Console for URL indexing and performance data. PageSpeed Insights for Core Web Vitals before and after. Screaming Frog for crawling and internal link verification. Ahrefs for backlink monitoring. The built-in SEO scoring tool verified on-page SEO for every imported post.

Can I migrate without technical skills?

The one-click WordPress importer handles content transfer without any technical knowledge. SEO verification requires familiarity with Search Console and basic understanding of redirects. If you can install a WordPress plugin, you can run a migration. For a broader view of getting started, the beginner's guide covers everything from platform selection to first post.

What about WordPress comments?

This blog did not use native WordPress comments — discussions happened on social media. If your blog relies on comments, note that comment threads do not migrate. Consider switching to a third-party comment system (Disqus, Giscus) before migration so comments are platform-independent.

Is there a risk of losing everything?

Not if you follow the parallel-running strategy. The WordPress site stays live at a temporary URL for 90 days. Your WordPress backup remains intact. DNS can be pointed back at any time. The worst-case scenario is wasted time, not lost content.

Why did traffic increase instead of just recovering?

Core Web Vitals improvements provided a ranking boost for pages that were already close to page-one positions. Faster pages also reduce bounce rate and increase engagement metrics, which correlate with sustained ranking improvements. The speed improvement was dramatic enough (4.1s → 0.8s LCP) to cross Google's "Good" threshold, unlocking the page experience ranking signal.

Run your own migration

Create a free blog and test the WordPress importer with a few posts before committing to a full migration. The free plan includes everything used in this case study: the WordPress importer, SEO scoring, edge rendering, custom domain support, and AI-assisted publishing via MCP . No credit card, no trial period, no feature gates.

Before you start, run through the WordPress SEO migration checklist and document your baseline metrics. The 25-step checklist is the same one used in this case study. Every step has a reason, and every reason is about protecting rankings.

Start your free WordPress migration → — test the importer with a few posts before committing to a full migration.

Share this post
𝕏in
Built with Modern Blogging

This article was written, styled, and published using the Modern Blogging platform. Launch your own fast, SEO-ready publication in minutes.

Start for free →