You’ve got a new site ready to go and one question keeping you up at night: will the traffic survive?
It’s a fair worry. Website migration without losing SEO is one of the few jobs where doing nothing beats doing it badly. A careless move can undo years of rankings in an afternoon, and the damage often isn’t obvious until the enquiries dry up three weeks later.
This guide is for Australian small business owners moving to a new platform, a new domain, or just a new design on the same address. You’ll get the sequence that works, the checks that catch problems before launch, and an honest answer on how long recovery takes.
What Actually Causes Traffic Loss During a Migration
Google doesn’t punish you for rebuilding your site. It loses track of you.
Every page that ranks has a history attached to a specific URL: links pointing at it, trust built over time, a place in the index. When that URL changes and nothing tells Google where it went, the history doesn’t transfer. The new page starts from scratch.
Four things cause the bulk of real-world losses:
- Missing or lazy redirects. Old URLs that 404, or worse, all point at the homepage.
- A staging site left switched off. The
noindextag or blocked robots.txt that protected your test build goes live with it. - URLs that changed for no reason. A new theme or platform silently restructures
/services/plumbing/into/our-services/plumbing-gold-coast/. - Content quietly dropped. The new design has less copy, and the page that ranked on 900 words now has 200.
Notice that three of the four are avoidable with planning rather than budget. That’s the good news.
Before You Touch Anything, Build Your Baseline
You can’t prove a migration worked if you don’t know where you started. Do this before a single file moves.
Export 12 months of Search Console data. Queries, pages, clicks, impressions, average position. Google only keeps 16 months, and you’ll want this comparison for the next six.
Crawl the entire current site. Screaming Frog’s free tier handles 500 URLs, which covers most small business sites. Export every URL with its title, meta description, H1, word count and status code.
Note your top 20 pages by traffic. These are the ones you watch obsessively after launch. Everything else can wait.
Record your Core Web Vitals and average position. If rankings dip after launch, you need to know whether the new site is genuinely slower or whether it’s normal post-migration turbulence.
Save all of it in one folder with the date in the filename. Six weeks from now you’ll be glad it exists.
The Redirect Map Is the Whole Job
If you only do one thing properly, make it this.
Build a spreadsheet with four columns: old URL, new URL, redirect type, and notes. Every URL from your crawl gets a row. Every row gets a destination. A 301 redirect tells Google the move is permanent and passes the ranking signals across.
A few rules that save real pain:
One hop, never two. If /old-page/ redirects to /interim-page/ which redirects to /new-page/, you’re bleeding signal at every step. Point the old URL at the final destination directly.
Never mass-redirect to the homepage. Google treats a redirect to an irrelevant page as a soft 404 and ignores it. A discontinued service page should point at the closest surviving equivalent, or the category above it.
Don’t forget the non-page URLs. Images, PDFs, old blog categories, tag archives and paginated pages all accumulate links. Your price list PDF might be your most-linked asset.
Redirect the old domain forever, not for a year. If you’re changing domains, keep the redirects live permanently. Dropping them in 12 months throws away everything you protected.
What to Do With Pages You’re Deleting
Some pages should go. A 2019 blog post about a product you no longer sell doesn’t need a home.
If a deleted page has no backlinks and no traffic, let it 410 or 404. That’s a clean signal. If it has either, redirect it to the nearest relevant page. Check your backlink data before you decide, because a forgotten page can be carrying links you’d hate to lose.
Pre-Launch Checks on Staging
Your staging site should be a rehearsal, not a surprise. Run these while there’s still time to fix things.
| Check | What you’re looking for |
|---|---|
| Robots.txt | No Disallow: / left from development |
| Meta robots | No noindex tags on pages you want indexed |
| Canonical tags | Pointing at live URLs, not staging.yoursite.com.au |
| Page titles | Every page has one, and it isn’t “Untitled” |
| H1s | One per page, matching the intended topic |
| Word count | New pages within 20% of the old ones |
| Internal links | No hardcoded links back to the old domain |
| SSL | Certificate valid, no mixed content warnings |
| Analytics | Tracking code present on every template |
Canonical tags pointing at staging is the single most common launch-day disaster we see, and it’s silent. The site looks perfect while telling Google the real version lives somewhere it can’t reach.
Launch Day and the Two Hours After
Go live midweek, mid-morning. Never on a Friday afternoon. You want your developer awake and available for the next few hours, and you want a full business day to spot problems.
The moment the new site is live:
- Test 20 redirects by hand. Your top 20 pages from the baseline. Paste each old URL into a browser and confirm it lands on the right new page with a 301.
- Crawl the live site immediately. Compare against your baseline crawl. Look for missing pages, blank titles, unexpected 404s.
- Submit the new XML sitemap in Google Search Console and request indexing on your five most important pages.
- Check robots.txt and a random sample of canonical tags on the live domain, not staging.
- Confirm analytics is firing on a real page view.
If you’re behind a CDN, purge the cache before you test anything. Half of all “the redirect isn’t working” panics are a cached old page. Cloudflare makes this a single button, and most managed hosts have an equivalent.
The First 14 Days
Check Search Console daily for two weeks. You’re watching three reports.
Coverage. A small bump in 404s is normal as Google recrawls. A spike is a redirect you missed. Fix each one within 48 hours.
Performance. Expect impressions to wobble. A dip of 10% to 15% in the first fortnight is ordinary and usually self-corrects. A drop past 30% means something is structurally wrong, and the usual culprit is a noindex tag or a redirect chain.
Sitemaps. Confirm the new sitemap is processed and the old one is removed.
Don’t make other changes during this window. If you redesign the navigation in week two, you’ll never know which change caused what. Keep the site stable and let Google catch up. The same discipline applies to your ads — if you’re running Google Ads Gold Coast campaigns, update the destination URLs on day one rather than relying on redirects to carry paid traffic.
A Gold Coast Example
A Southport trades business came to us after moving from a 40-page site onto a new theme. Organic enquiries had dropped by roughly two-thirds in five weeks.
The rebuild looked fine. The problem was that the new theme had restructured every service URL, and the developer had set up exactly one redirect: the homepage. All 39 other pages returned 404s, including the suburb pages that generated most of their calls.
Rebuilding the redirect map took a day. Recovery took about seven weeks, and they landed at roughly 90% of the old traffic rather than 100%, because two pages had lost links in the gap. The whole episode cost more in lost work than the rebuild did.
The lesson isn’t that they used the wrong theme. It’s that nobody owned the redirect map.
The Real Timeline for a Website Migration Without Losing SEO
Honest numbers, because vague reassurance doesn’t help you plan.
| Site size | Typical dip | Full recovery |
|---|---|---|
| Under 50 pages, same domain | 0–10% | 2–4 weeks |
| Under 50 pages, new domain | 10–20% | 4–8 weeks |
| 50–500 pages, new domain | 15–25% | 2–4 months |
| Platform change plus restructure | 20–30% | 3–6 months |
These assume the redirects are right. If they aren’t, there’s no recovery curve — there’s just a new, lower baseline until someone fixes it.
A same-domain redesign where URLs don’t change is the lowest-risk move available. If your URL structure is already sensible, keep it. Changing /plumbing/ to /services/plumbing-gold-coast/ for tidiness is a real risk taken for a cosmetic gain.
What This Costs and Who Should Do It
For a site under 50 pages, the migration work itself is usually 4 to 8 hours: the crawl, the redirect map, the staging checks and launch-day testing. At Australian agency rates that’s $600 to $1,400 on top of the build.
It’s the cheapest insurance in the project. A rebuild can run $8,000 to $20,000, and skipping the SEO layer to save a few hundred dollars puts the whole investment at risk.
If you’re handling it in-house, the redirect map is the part to take seriously. Everything else on this page is a checklist you can follow. Mapping 300 URLs correctly takes patience and a tolerance for spreadsheets. Our Gold Coast web design team builds this into every rebuild, and our SEO services cover the monitoring afterwards.
On WordPress specifically, get your redirects into a plugin that survives theme changes rather than hardcoding them into a child theme, and confirm your host handles the traffic profile of the new build. Our notes on WordPress optimisation and managed WordPress hosting cover both. Once you’re live, a website maintenance plan catches the broken links that creep in over the following months.
The bottom line
Migrations go wrong for boring reasons, not exotic ones. Missing redirects, a staging noindex left switched on, and URLs changed without a reason account for nearly every disaster worth the name.
Build the baseline before you start, map every old URL to a new one, and check the staging site properly. Then leave it alone for a fortnight and let Google work through it. If you’re planning a rebuild, our website redesign checklist is worth reading alongside this, and how long it takes to build a website will help you plan the timeline around it.
Moving soon and not sure the plan covers the SEO side? Send through your current site and we’ll tell you where the risk sits.
FAQs
How do I migrate a website without losing SEO?
Map every existing URL to a 301 redirect before launch, then verify them the moment the new site goes live. Export Search Console data and crawl the old site first so you have a baseline. Check the staging build for noindex tags and staging canonical URLs, submit a new sitemap on launch day, and monitor Search Console daily for two weeks.
How long does it take to recover traffic after a website migration?
Most well-executed migrations recover within two to four weeks on the same domain, and four to eight weeks on a new domain. Larger sites or platform changes can take three to six months. A dip of 10% to 15% in the first fortnight is normal. A drop beyond 30% usually signals a technical fault rather than a recovery curve.
Do I need 301 redirects if my URLs aren’t changing?
No. If the URL structure stays identical and only the design changes, existing URLs keep their rankings and no redirects are needed. Still crawl the old site first to confirm nothing changed silently, as themes and page builders sometimes alter trailing slashes, category paths or pagination without warning.
Will changing my domain name hurt my rankings?
A domain change causes a temporary dip of roughly 10% to 20% even when handled correctly, with recovery typically taking four to eight weeks. Redirect every old URL to its new equivalent with a 301, keep those redirects live permanently, and update the property in Google Search Console using the Change of Address tool.
What is the most common website migration mistake?
Redirecting every old URL to the homepage. Google treats an irrelevant redirect as a soft 404 and passes no ranking signal, so those pages effectively disappear. The second most common mistake is leaving a noindex tag or a blocked robots.txt file on the new site after it goes live from staging.
Should I migrate my website and redesign the content at the same time?
Ideally not. Changing URLs, design and content together makes it impossible to diagnose what caused a ranking drop. Where the budget allows, migrate first with content intact, confirm rankings hold for two to three weeks, then update the copy. If both must happen at once, keep word counts within about 20% of the originals.
How do I check whether my redirects are working?
Paste an old URL into a browser and confirm it lands on the correct new page. Then use a crawler such as Screaming Frog to check the full list, looking for a 301 status with a single hop rather than a chain. Google Search Console’s Coverage report will also flag old URLs returning 404s within a few days of launch.
