Migrating Your Website Without Losing Traffic: A Pre-Launch Checklist
If you are about to redesign, replatform, or move your site to a new domain, this is the post that keeps your phone from ringing two weeks later with a panicked “our leads dropped to zero.” I have run migrations for Pakistani businesses — Lahore manufacturers, Karachi e-commerce stores, Islamabad SaaS startups — since 2009, and I can tell you that website migration without losing traffic is almost never about the design. It is about the boring plumbing underneath: redirects, URLs, and the dozen checks most agencies quietly skip because the client cannot see them.
This checklist is for business owners and marketing leads who have already decided to move and now need to do it without torching the organic traffic they spent years (and real PKR) building. No theory. Just what to verify before you press launch.
Why Migrations Lose Traffic in the First Place
Google ranks individual URLs, not “your website” as a vague concept. Every page that ranks has accumulated trust signals tied to its exact address. When you change that address — or kill the page entirely — and fail to tell Google where the value moved, the ranking evaporates. That is the entire game.
The three migration types each break traffic differently:
- Redesign on the same URLs. Lowest risk. If your URLs stay identical, you are mostly protecting content and technical signals.
- Replatform (WordPress to Shopify, custom PHP to Webflow, etc.). High risk, because the new platform almost always generates a different URL structure. This is where a replatform without ranking loss succeeds or fails on redirect mapping.
- Domain change (rebrand, .com.pk to .com, HTTP to HTTPS done badly). Highest risk if redirects are incomplete or chained.
Honest truth: even a perfect migration usually sees a temporary 10-20% dip for a few weeks while Google re-crawls and re-evaluates. Anyone promising “zero impact, instantly” is selling you something. The goal is a shallow, short dip that recovers — not a cliff you never climb back from.
The Pre-Launch Foundation: Crawl and Document the Old Site
You cannot preserve what you have not measured. Before anyone touches the new build, freeze a complete picture of the current site. This is the single most skipped step, and it is the one that makes everything else possible.
Pull a full crawl of every live URL
Use Screaming Frog (the free version covers up to 500 URLs; the paid licence is around PKR 60,000–70,000 per year and worth it for anything bigger). Export every indexable URL. Then cross-reference against Google Search Console’s Pages report and your XML sitemap, because a crawler only finds what is linked — orphan pages that still rank will not show up otherwise.
Rank your URLs by what actually matters
Pull your top landing pages from Google Analytics (GA4) and Search Console by organic traffic, conversions, and backlinks. You are building a priority list. The page driving 40% of your inquiries deserves obsessive attention; a 2019 blog post nobody reads does not. Document:
- Top 50–100 URLs by organic sessions and conversions
- Pages with external backlinks (these carry authority you must not lose)
- Current title tags, meta descriptions, and H1s
- Current rankings for your money keywords as a baseline
Save this. Post-launch, it becomes your scorecard. Without a baseline you are guessing, and guessing is how a “successful relaunch” quietly becomes a six-month traffic decline nobody connects to the migration.
Redirect Mapping: Where Most Migrations Live or Die
This is the heart of website migration without losing traffic, so I will be blunt about it. A redirect map is a spreadsheet: every old URL in one column, the exact new URL it should point to in the next. One row per old URL. No gaps.
Do the mapping manually for important pages
Automated “redirect everything to the homepage” plugins are the number one cause of post-migration ranking loss I get called in to fix. When you send 800 old URLs to the homepage, Google treats those as soft 404s and drops them. Every old URL should map to the most relevant equivalent on the new site — old product page to new product page, old service page to new service page. If a page genuinely has no equivalent, map it to the closest parent category, not the homepage.
Use 301, not 302
A 301 redirect migration is permanent and passes the large majority of ranking signal to the destination. A 302 is temporary and tells Google “keep the old URL indexed.” Developers default to 302 constantly because it is the framework default. Check every redirect returns a literal 301 status code. This is non-negotiable.
Eliminate redirect chains and loops
If old URL A redirects to B, and B redirects to C, you have a chain. Each hop leaks a little authority and slows crawling. Map every old URL directly to its final destination in one hop. After launch, re-crawl your redirect list specifically to catch chains your CMS introduced (trailing slashes and HTTP-to-HTTPS hops are the usual culprits).
Test the redirect map before it goes live
Stage the redirects on a test environment or run them through a list-mode crawl. Confirm: every old URL resolves, returns 301, lands on a live 200-status page, and the destination is actually relevant. Spot-check your top 20 money pages by hand. I have seen a flawless 2,000-row map ruined by one regex rule that broke the highest-converting page.
URL Preservation: Keep What You Can
The cleanest redirect is the one you never need. If you are redesigning rather than replatforming, fight to keep your existing URL structure. A redesign that preserves URLs is dramatically lower-risk than one that “improves” them.
I regularly talk clients out of cosmetic URL changes. Renaming /services/web-design to /what-we-do/web-design because it “reads nicer” buys you nothing and risks real traffic. If the new platform forces a structure change, keep the slug stable wherever possible — same words, same hierarchy depth. The point of a strategy that aims to preserve SEO redesign outcomes is restraint: change what serves the user, leave the addresses alone.
When you must restructure, keep these consistent with the old site:
- Trailing slash convention (pick one, enforce it sitewide)
- Case (lowercase URLs, always)
- HTTPS and the www / non-www choice (pick one canonical version)
- Language and region paths if you serve Urdu and English versions
The Technical Safeguards Agencies Skip
A pretty new site can rank worse than the old one for reasons the client never sees. Here is the unglamorous checklist that separates a real migration from a lipstick-on-a-corpse relaunch.
Block the staging site from indexing — then unblock at launch
Staging environments must be noindexed or password-protected, or Google indexes your half-built test site. The disaster I see most often is the reverse: the team forgets to remove the noindex tag or the blanket Disallow: / in robots.txt when they go live. Your beautiful new site quietly tells Google to ignore it. Check the live robots.txt and a sample of page source the moment you launch.
Preserve on-page SEO content
Designers love trimming copy for “cleaner” layouts. That copy is often why the page ranks. Carry over title tags, meta descriptions, heading structure, body content, image alt text, and structured data (schema). If you genuinely improve content, fine — but do it deliberately, not as a side effect of a redesign.
Update internal links and canonicals
Internal links should point at the new URLs directly, not bounce through redirects. Update your navigation, footer, and in-content links. Confirm every page’s canonical tag points to itself on the new domain, not the old one — a stale canonical pointing back to the dead site is a silent killer.
Regenerate and submit a clean XML sitemap
Generate a fresh sitemap containing only live, indexable, 200-status URLs on the new structure. No redirected URLs, no 404s. Submit it in Search Console immediately after launch to speed up re-crawling.
Mind site speed on real Pakistani devices
Test the new build on a mid-range Android over a typical mobile connection, not just your office fibre on a MacBook. A redesign that ships heavier images and bloated scripts will hurt both rankings and conversions. Most of your traffic is on phones; if it is slow on a Redmi over 4G in Faisalabad, it is slow for your customers. Solid technical execution here ties directly into ongoing search engine optimization results.
Launch Day and the First 30 Days
Launch is the start of monitoring, not the finish line. Run this on the day you go live and keep watching:
- Verify the new site in Search Console (and if you changed domains, use the Change of Address tool).
- Re-crawl the new live site and check for unexpected 404s, 302s, broken redirects, and noindex tags.
- Spot-check your top 20 URLs manually: do they load, redirect correctly, and keep their content and titles?
- Submit the new sitemap and request indexing for your most important pages.
- Watch the Crawl Stats and Coverage reports daily for the first week, then weekly.
- Track rankings and organic traffic against the baseline you saved. A small dip is normal; a steep, sustained drop means a redirect or indexing problem to fix now, not later.
Keep the old URLs’ redirects live for at least a year — ideally permanently. Backlinks pointing at old URLs can keep sending value for years, and the redirect is what forwards it.
Frequently Asked Questions
How long until my traffic recovers after a migration?
For a clean, well-executed migration, expect a small dip for two to four weeks while Google re-crawls and re-indexes, with recovery to baseline (or better) within four to eight weeks. Larger sites and domain changes take longer. If you see no recovery after eight weeks, something in the redirect or indexing setup is broken and needs investigation.
Will I definitely lose rankings if I redesign my website?
Not if you preserve URLs, carry over content and on-page SEO, and map any changed URLs with 301 redirects. A redesign that keeps the same URLs and content is low-risk. The danger is treating SEO as an afterthought — losing copy, breaking URLs, or leaving a noindex tag live. Planning the redesign with SEO in from day one is how you keep your rankings.
Can I just redirect all old pages to my new homepage?
No, and please do not. Google treats bulk redirects to an irrelevant homepage as soft 404s and drops those pages from the index, so you lose the rankings you were trying to protect. Each old URL must point to its most relevant equivalent. Mapping it properly is tedious but it is the whole point.
Do I need a new SSL certificate when I migrate?
If you are moving to HTTPS or a new domain, yes — and make sure every internal link and redirect uses HTTPS to avoid mixed-content warnings and extra redirect hops. Most reputable Pakistani hosts include a free Let’s Encrypt certificate, so this should not be a real cost, just a checklist item you must not forget.
How much does a professional migration cost in Pakistan?
It depends entirely on size and complexity, but the redirect mapping and SEO safeguards are a small fraction of the total redesign budget — and skipping them to save a little can cost you far more in lost organic leads. Treat the SEO migration work as insurance on the traffic you already paid to build. We are happy to scope it transparently before you commit.
Should I migrate during my busy season?
Avoid it. Schedule migrations during your slowest period so that the temporary dip and any issues that surface land when stakes are lowest. For most retail and e-commerce clients in Pakistan, that means not migrating right before Eid, wedding season, or a major sale.
Talk to One Source Soft Before You Launch
A migration is one of the few projects where the difference between “done right” and “done fast” is invisible until your leads dry up — and by then it is expensive to fix. If you are planning a redesign or replatform, get the redirect map and SEO safeguards reviewed before launch, not after the traffic drops.
Our team has handled website migration without losing traffic for businesses across Pakistan since 2009, and our approach to web design and development bakes URL preservation and redirect strategy into the build from the start rather than bolting it on at the end. You can see how real clients rate that work in our public Google reviews.
Book a free migration audit and consultation — we will crawl your current site, flag the URLs at risk, and tell you honestly what your migration actually needs. No jargon, no scare tactics, just a clear plan to move your site without losing what you have built.
Related reading
What to Look for in a Website Maintenance Plan (Before You Sign)
A senior dev's guide to what a website maintenance plan must include before you sign — real inclusions, upsell traps, and honest PKR pricing for Pakistani businesses.
Read article →Headless vs Traditional WordPress: When the Complexity Is Worth It
Headless WordPress vs traditional: a senior take on when decoupling is a real performance and security win — and when it is expensive over-engineering. PKR pricing included.
Read article →How Long Does It Really Take to Build a Website? A Realistic Timeline
How long to build a website, broken down by phase — plus the client-side delays (content, approvals) that quietly turn a 6-week project into 5 months.
Read article →