Industry: Professional Services (Accounting) | Service: Web Development, Technical SEO services Vancouver | Timeline: 3 weeks
WordPress Migration Without Losing Rankings: A Step-by-Step Case Study
How we migrated a 340-page WordPress site to a new host and theme without losing a single ranking position.
We migrated a 340-page accounting firm’s WordPress site to a new hosting provider and custom theme with zero ranking loss, 14 minutes of total downtime and 287 301-redirects handling every URL change. Post-migration, Core Web Vitals scores improved from failing to passing across all metrics. Site migrations are one of the highest-risk SEO events a business can face; this case study documents exactly how we executed one without incident.
The Challenge
A mid-sized Vancouver accounting firm with 340 indexed pages needed to migrate from a shared hosting provider to a managed WordPress host while simultaneously replacing their outdated theme. The site generated $45,000/month in attributable new client revenue through organic search. A botched migration risked months of ranking recovery and significant revenue loss.
The complexity was substantial:
- 340 indexed pages including 180 blog posts, 45 service pages, 28 location pages and 87 resource pages
- The existing URL structure used a non-standard format: /category/year/month/post-name/
- The new theme required a simplified URL structure: /blog/post-name/ for posts and /service-name/ for service pages
- 142 inbound links from external sites pointed to specific pages that would change URLs
- The firm ranked position 1-3 for 23 high-value keywords including “Vancouver accounting firm,” “corporate tax planning BC” and “small business accountant Vancouver”
- Google Business Profile linked to specific landing pages that needed to be preserved
The client’s previous web developer had attempted a migration 18 months earlier and abandoned it after rankings dropped 40% within two weeks. They spent four months recovering. The client was understandably cautious and needed a documented, methodical approach.
Our Strategy
We followed a 4-phase migration protocol that we’ve refined across 30+ WordPress migrations. Every step was documented, tested and reversible.
Phase 1: Pre-Migration Audit (Week 1)
Before touching anything, we created a complete snapshot of the existing site’s SEO state:
- Full Screaming Frog crawl exported to spreadsheet: every URL, status code, title tag, meta description, canonical tag, H1, word count and internal link count
- Google Search Console export of all indexed pages, queries, positions and click-through rates
- Ahrefs export of all inbound backlinks with referring page, anchor text and target URL
- Complete database backup and file system backup stored in three locations
- Screenshot of every key page using a full-page capture tool for visual reference
- XML sitemap archived
- Robots.txt archived
- All Yoast SEO settings exported
- Google Analytics baseline report for the 90 days prior to migration
This audit document became our verification checklist post-migration. Every ranking, every page and every backlink target had a documented pre-migration state we could compare against.
Phase 2: Redirect Mapping (Week 1)
We built a comprehensive redirect map in a spreadsheet: old URL in column A, new URL in column B, redirect type in column C (all 301 permanent). The map covered:
- 287 URL changes from the structure update
- 53 pages being consolidated (thin content pages merged into comprehensive service pages)
- 12 pages being removed (outdated content with zero traffic and no backlinks)
- Every external backlink target verified to have a correct redirect in place
The redirect map was implemented in the server’s .htaccess file rather than a WordPress plugin. Server-level redirects execute faster and don’t depend on WordPress loading. We tested every redirect on the staging environment before touching production.
Phase 3: Staging Build and Verification (Week 2)
We built the new site on a staging subdomain with the new theme, migrated all content and verified:
- Every page rendered correctly with proper heading hierarchy (H1 through H3)
- All internal links pointed to correct new URLs
- Schema markup (Article, FAQPage, BreadcrumbList, LocalBusiness) was present and valid on every page
- Yoast meta data transferred correctly: title tags, meta descriptions, canonical URLs and focus keywords
- Technical SEO elements were intact: XML sitemap generation, robots.txt, hreflang tags
- Page speed met targets: LCP under 2.5s, CLS under 0.1, FID under 100ms
- All forms, CTAs and tracking codes functioned correctly
- SSL certificate configured and all URLs forcing HTTPS
The staging site was crawled with Screaming Frog and compared against the pre-migration audit. Any discrepancies were fixed before proceeding.
Phase 4: Migration Execution (Week 3)
We executed the migration during a Saturday at 2 AM Pacific when traffic was at its lowest. The sequence:
- Final database and file backup created
- DNS TTL reduced to 300 seconds 48 hours prior
- Maintenance mode enabled on old site
- Database migrated to new host
- Files deployed from staging to production
- DNS updated to point to new server
- SSL certificate verified
- Redirect rules verified with curl commands against every mapped URL
- Screaming Frog crawl of production site compared against staging crawl
- Google Search Console “Request Indexing” submitted for homepage and top 20 pages
- Updated XML sitemap submitted to Google Search Console and Bing Webmaster Tools
- Google Business Profile URLs verified and updated where necessary
Total downtime: 14 minutes from maintenance mode activation to DNS propagation completion. We monitored the site continuously for the following 72 hours.
Post-Migration Monitoring (Weeks 3-6)
We monitored daily for 30 days post-migration:
- Search Console crawl errors checked daily (zero 404 errors from Google’s crawler)
- Ranking positions tracked daily for all 23 high-value keywords via SEMrush
- Server logs analyzed for any 404s or redirect chains
- Core Web Vitals monitored through CrUX data
- Organic traffic compared daily against pre-migration baseline
At day 7, all 23 tracked keywords maintained their positions. At day 14, 18 of 23 keywords had improved by 1-3 positions due to the Core Web Vitals improvement from the new hosting and theme. At day 30, organic traffic was 12% above the pre-migration baseline.
Results
| Metric | Before | After (30 Days) | Change |
|---|---|---|---|
| Rankings Preserved (Top 23 Keywords) | 23/23 | 23/23 | 100% preserved |
| Total Downtime | N/A | 14 minutes | Minimal |
| 301 Redirects Implemented | N/A | 287 | 100% coverage |
| Post-Migration 404 Errors | N/A | 0 | Zero errors |
| Organic Traffic (30-Day Comparison) | Baseline | +12% | +12% growth |
| Largest Contentful Paint (LCP) | 3.8s | 1.4s | -63% |
| Mobile Lighthouse Score | 52 | 94 | +81% |
Key Takeaway
Website migrations don’t have to destroy rankings. They destroy rankings when they’re rushed, when redirect maps are incomplete and when nobody creates a pre-migration baseline to verify against. This migration preserved 100% of the client’s rankings because we documented everything, tested everything on staging and monitored everything post-launch.
The 287 server-level 301 redirects were the single most critical element. Every old URL had a mapped destination. Every external backlink target was accounted for. Every internal link was updated to point directly to the new URL (not relying on redirect chains). Our migration guide covers this methodology in full detail.
The bonus outcome: a 12% organic traffic increase within 30 days. The new hosting environment and custom-built theme improved Core Web Vitals significantly, and Google rewarded the performance improvement with better rankings for 18 of 23 tracked keywords. Migrations done right aren’t just risk mitigation. They’re an opportunity to improve your technical SEO foundation.
Frequently Asked Questions
How long do rankings drop after a website migration?
With a properly executed migration, rankings should not drop at all. When drops occur, they typically last 2-12 weeks depending on the severity of the issues. Common causes are missing redirects, changed URL structures without redirect coverage and lost schema markup. This client experienced zero ranking loss because every URL change was mapped with a 301 redirect and verified pre-launch. Our migration process is specifically designed to prevent ranking disruption.
Should I change my URL structure during a migration?
Only if the current structure is actively harming SEO (excessively long URLs, non-descriptive slugs, unnecessary date parameters). Every URL change requires a 301 redirect, and even with perfect redirects, there’s a small signal dilution during the transition period. This client’s URL change was necessary because the old structure included /year/month/ parameters that added no value. We simplified to /blog/post-name/ which is cleaner for both users and search engines.
How many redirects is too many?
There’s no maximum number of redirects. Google has confirmed that 301 redirects pass full link equity. The risk isn’t the number of redirects but redirect chains (redirect A pointing to redirect B pointing to redirect C). We ensure every redirect points directly to the final destination URL with no chains. This client’s 287 redirects execute at the server level in under 5 milliseconds each, with zero performance impact.
Want Results Like These? Get a Free Audit
If you’re planning a website migration and can’t afford to lose rankings, start with a free migration risk assessment. We’ll audit your current site, identify the critical SEO elements that must be preserved and outline a migration plan that protects your organic revenue.
Phone: 604-901-7668 | Email: info@quakemedia.ca
See more: Migration Guide | Web Development | Technical SEO Checklist | Free Audit
Related: Vancouver web hosting
Need help with this?
Quake Media helps businesses across Vancouver and Canada with SEO, PPC and custom web development. Get a free audit and see where your site stands.
