A step-by-step SEO migration playbook for Indian service businesses—redirects, staging discipline, tracking continuity, and post-launch monitoring to protect rankings and leads.

Redesigns and platform migrations are when founders simultaneously want "a modern site" and "don't lose our Google leads." Those goals conflict unless SEO is operational—not a launch-week panic.

Indian service businesses often migrate from legacy WordPress or page builders to Next.js, merge city URLs, or rebrand domains. Each change can work. Each can drop pipeline for quarters if redirects and tracking are treated as cleanup tasks.

Pre-migration: inventory before aesthetics

Week −4 to −3

export all indexed URLs from Search Console Coverage + sitemaps
identify top 20 URLs by leads and revenue influence (not just traffic)
document current title/H1 intent per URL
map analytics events and conversion goals in GA4/GTM
capture baseline rankings for priority local and service terms

If you cannot list top money URLs, pause migration scoping until you can.

Redirect map: the document that saves you

Build a spreadsheet:

Old URL	New URL	Redirect type	Intent notes	Owner
/old-service	/services/seo	301	commercial	dev
/blog/legacy-slug	/blog/new-slug	301	informational	content

Rules:

prefer one-hop 301 redirects
never mass-redirect everything to homepage
retire URLs intentionally with 410 only when truly gone and low value
keep slugs stable when possible—especially for blogs with backlinks

For blog content living in public/blogs, preserve slug filenames unless consolidating with explicit redirects.

Staging tests that mirror production constraints

Before cutover:

crawl staging with blocked indexing (noindex) but internal crawl access
test redirect chains with curl or Screaming Frog
validate canonical tags on templates
run mobile PageSpeed on new money pages vs old baseline
confirm schema and internal links on city/service templates

Launching a beautiful staging site that fails INP on mobile trades one problem for two—see INP fixes for Next.js service sites.

Insight block: Migrations fail quietly first in long-tail local URLs—the pages that actually produce calls. Protect micro URLs, not only the homepage.

Cutover sequence (48-hour window)

T−24h: freeze content changes except migration blockers
T−0: deploy redirects, update sitemap, submit in Search Console
T+2h: smoke-test top 20 URLs, forms, tel/WhatsApp links, thank-you events
T+24h: monitor GSC crawl errors and 404 spikes
T+48h: compare lead volume and source tagging vs prior week (seasonality adjusted)

Keep paid campaigns on pause or reduced until core landing URLs pass message match and speed checks—see landing page experience fixes.

Post-migration monitoring (30 days)

Weekly review:

GSC Performance by page (old vs new URL groups)
404/redirect error reports
indexed page counts vs plan
lead rate by landing URL in CRM
branded vs non-branded query stability

Expect fluctuation for 2–6 weeks on competitive terms. Sustained cliffs on branded queries signal technical error, not "Google mood."

Communication plan during migration (often ignored)

SEO mechanics fail when stakeholders panic at normal volatility.

Prepare:

internal FAQ for sales ("URLs changed but leads are tracked here…")
customer-facing notice only if login areas or client portals move
paid campaign pause/resume checklist shared with performance team
single Slack/WhatsApp war room for 48 hours post-launch

Founders who communicate proactively see fewer "SEO is broken" fires when long-tail URLs fluctuate temporarily.

Rollback criteria

Define before launch:

404 rate on money URLs > X% for 24 hours → rollback redirects batch
lead volume down > Y% vs same weekday prior month → freeze new template deploys
branded query impressions collapse → emergency technical review

Write X and Y based on your baseline—generic thresholds mislead small samples.

Keep a redirect archive for 12 months minimum. Old backlinks, WhatsApp shares, and printed QR codes resurrect dead URLs long after launch week adrenaline fades.

Assign one person to own the redirect map during migration—not "the dev agency somewhere." Founders who delegate without a named internal owner discover broken paths weeks later in sales calls, not in crawl tools.

When to change URLs vs keep them

Keep URLs when: page ranks for high-intent terms, has backlinks, or drives steady leads
Change URLs when: consolidation removes true duplicates with merged superior content
Never change because: new CMS prefers prettier paths unless redirects are bulletproof

Internal linking suggestions

External references

Final takeaway

Migration SEO is redirect discipline plus measurement continuity—not a launch checkbox. Inventory money URLs, map 301s intentionally, test staging honestly, and monitor leads daily for the first month.

Planning a Next.js migration? Book a strategy call—we run migration audits with redirect maps tied to your lead history, not generic crawl exports.

Website Migration SEO Playbook for India: Avoid the Traffic Cliff Without Freezing Growth