Skip to content

Guides / Technical migration protocol

Website migration SEO checklist (2027): the 4-phase zero-drop protocol.

Organic traffic drops after a website redesign, CMS switch, domain change or hosting move are almost never caused by 'Google re-evaluating the design': they come from unmapped legacy URLs, two-hop redirect chains, staging noindex leaks, dropped FAQPage/Service JSON-LD or slower mobile LCP. At Geeklab, migration SEO governance is built into every custom WordPress rollout or scoped standalone from R11,000 to R30,000.

By Jared Coleman & Evert Jansen Van Vuuren / 4-phase cutover protocol / Migration QA from R11,000 / Prices in rand

01 / Pre-launch to Day 30

Every check required across T-30 days, staging parity, cutover day and post-launch.

Whether you are moving from Webflow or HubSpot CMS onto WordPress, consolidating regional subdomains, or migrating hosting infrastructure (as we did moving our own 111-page site onto Pressable), run these four phases in strict sequence.

Migration phaseWindowNon-negotiable engineering & SEO deliverables
Phase 1: Full URL & authority inventoryT-30 to T-15 daysExport 16-month Google Search Console pages/queries, GA4 landing pages, backlink target URLs (including retired paths) and current XML sitemaps into one master URL sheet.
Phase 2: Staging parity & single-hop 301 mapT-14 to T-2 daysLock staging behind noindex, nofollow + Disallow /; verify 1-to-1 title/H1/copy intent parity on top 80% traffic URLs; test every 301 rule so zero legacy paths chain through 2+ hops.
Phase 3: Cutover day & edge verificationLaunch day (0 to 4 hrs)Remove staging guards; verify SSL on apex and www; confirm 200 OK + self-referencing canonicals across every sitemap URL; test robots.txt for Googlebot and OAI-SearchBot; submit XML sitemaps in GSC.
Phase 4: Post-cutover log & GSC monitoringDays 1, 3, 7, 14 & 30Audit 404/500 logs daily in week 1, patch unmapped inbound backlink URLs within 24 hours, verify Core Web Vitals field data and check non-brand position stability in GSC.

02 / Where migrations break in 2027

Four silent mistakes that legacy 2022 migration checklists miss.

Modern B2B domains rely on structured entity graphs and AI crawler access alongside classic HTML links. Overlooking these four items regularly costs 25% to 50% of non-brand impressions within three weeks of launch.

01

Redirecting retired pages to /

Dumping 40 old service or blog URLs onto the homepage triggers soft-404 treatment in Google Search Console and discards topic authority. Map each URL to its closest topical equivalent or serve an intentional 410 Gone.

Zero homepage catch-alls

02

Breaking @id JSON-LD & /llms.txt

Changing Organization, LocalBusiness, Service or FAQPage @id URIs or forgetting to deploy /llms.txt and /llms-full.txt resets entity continuity across Google and AI answer engines.

Preserve entity graph IDs

03

Geo-locking broadened titles

Designers often rewrite proven commercial <title> tags into vague slogans or lock national service pages to a single city, tanking click-through rates overnight.

Keep <=60c commercial titles

04

Staging guard or analytics leaks

Either staging gets indexed before launch (creating duplicate URLs) or blog_public=0 / noindex survives onto live production. Automate environment checks via WP_ENVIRONMENT_TYPE.

Automated staging guard

03 / Redirect & status governance

Which HTTP status code to use for every URL in your spreadsheet.

Every legacy URL in your crawl inventory should be assigned one explicit rule before DNS or theme cutover.

Legacy URL scenarioCorrect status / ruleWhy it matters
Active commercial, case study or guide page keeping same slug200 OK (exact path preserved)Fastest zero-volatility outcome; always keep working slugs unchanged unless forced by rebrand.
Renamed slug or consolidated service/guide topicSingle-hop 301 Moved PermanentlyPasses link equity and rankings directly to the replacement canonical URL without hop loss.
Retired thin announcements, expired promos or junk tags with zero links/clicks410 GoneTells Googlebot to drop dead bloat from crawl budget faster than a 404 without polluting active hubs.
Internal CTA links carrying tracking query strings (/lets-talk/?intent=...)rel="nofollow" + clean self-canonical on targetPrevents parameterised CTA permutations from diluting internal PageRank or creating crawl traps.

04 / Proof in production

Built from high-stakes certification, industrial and multi-region rollouts.

When ISTQB relies on organic search for 936,208 annual clicks across global software testing markets, or TMMi DACH and iSQI roll out regional certification architectures, redirect and schema discipline is mandatory.

01

Pre-cutover staging guard

On every Geeklab staging site we deploy an automatic environment guard (gl-staging-guard.php) that enforces noindex, blocks outbound wp_mail() and suppresses analytics tags until live cutover.

Zero staging leaks

02

Automated post-cutover link & schema QA

Within an hour of DNS or template cutover we crawl 100% of sitemap URLs to verify 200 OK, unique <title>/<h1> pairs, zero duplicate @id nodes and sub-2.5s mobile LCP.

Verified on 120+ live URLs

03

Standalone migration QA or full build

Already have an internal dev team building your new site? Hire Geeklab for standalone migration SEO governance (R11,000 to R30,000) to sign off the redirect map and staging build before launch.

Independent launch sign-off

Questions

Common questions answered directly.

Straight answers on scope, budgets, timelines and platform trade-offs.

How much organic traffic is normal to lose after a website migration?

When URLs, search intent, internal links, structured data and mobile speed are preserved (or improved) with single-hop 301s, minor 1-to-3-week fluctuations are normal, followed by net growth. Sustained 25%+ drops after 30 days almost always point to a fixable technical defect.

Should we change our domain name and redesign our website at the exact same time?

If business timelines allow, separating a domain change from a structural template/content overhaul makes diagnosing any GSC indexation quirk far cleaner. If a rebrand forces both simultaneously, preserve 1-to-1 URL path parity wherever possible.

How long must 301 redirects stay active after a migration?

Keep 301 redirects for legacy URLs that hold external backlinks or bookmarks in place indefinitely (at minimum 12 to 24 months) at the server or MU-plugin level so external citations never decay into 404s.

Can Geeklab audit our staging site before our developers push it live?

Yes. Our R11,000 Technical SEO Audit (or R30,000 Full Search Audit for large multi-market consolidations) can be run directly against your staging environment and redirect map two weeks before cutover.

Keep reading

Related guides and services.

Compare adjacent platforms, pricing breakdowns and delivery pages before locking in your scope.

01

Website redesign guide: scope, UX and B2B rollout

How to plan stakeholder discovery, architecture, copy and design before migration.

Read redesign guide
02

B2B rebranding and website rollout guide (2027)

Coordinating a visual identity refresh or name change with domain and search continuity.

Read rebrand guide
03

WordPress Core Web Vitals guide (2027): 111-page speed study

Ensure your migrated templates launch at 95+ mobile Lighthouse from day one.

Read speed study

Launch without ranking loss

Planning a CMS switch, rebrand or host move?

Share your current domain and target launch date. We will review your URL footprint and scope either a full WordPress migration or standalone pre-launch SEO QA.

Somerset West & Loulé · Zero-drop cutover governance

  • Websites
  • Design
  • Marketing & growth
  • Search & AI