Written by: Learning Objectives
A practical SEO migration guide explaining how website rebuilds and rebrands can destroy existing search visibility when redirects, content structure, and technical SEO are not protected. It covers redirect mapping, preserving ranking pages, maintaining on-page SEO, crawlable content, and how foundational SEO supports AI search visibility.
By the end of this module, you’ll be able to:
- Spot the single biggest mistake business owners make during a website rebuild or rebrand
- Explain why an “ugly but ranking” old site is worth more than most people think
- Build a redirect map that protects years of Google trust instead of resetting it
- Identify the on-page fundamentals (H1s, meta descriptions, alt text) that get lost in a rebuild
- Understand why foundational SEO now feeds AI citations too, not just Google’s blue links
Key Concepts
- Redirect (301) — A permanent instruction that tells Google and browsers “this page has moved, send everyone and everything here instead.” Think of it like a mail redirect at Australia Post: you don’t lose your mail, it just finds you at the new address. Skip it, and every visitor and every bit of Google trust just disappears into a 404.
- Domain maturity/trust — The accumulated history Google has built up about your site over years: how often it’s crawled, how reliably it loads, how users behave on it. It’s like a tradie’s licence and years on the tools — a brand-new operator with a shinier van still hasn’t earnt the same trust yet.
- The Google Sandbox — An unofficial trust period new domains sit in, where the site can rank but growth is capped until Google is confident it’s not a fly-by-night operation. New sites are like a new apprentice: capable, but not handed the big jobs until they’ve proven themselves.
- Thin content — Pages with little to no unique text, often auto-generated (tag pages, filtered category pages). Google treats them the way a customer treats a menu with no prices: not enough information to trust a decision.
- AI fan-out queries — When someone asks ChatGPT or Gemini a question, the AI silently splits it into several mini Google or Bing searches behind the scenes, then pulls answers from whichever indexed pages already rank. If you’re not indexed and ranking, you’re invisible to that whole process.
Real-World Case Studies
Case Study 1: Highlands Coastal Stays — Accommodation & Property — National (Hobart, Sandy Bay, Bondi)
The Challenge: Highlands Coastal Stays ran a national accommodation and property portal on an ageing Squarespace site. It wasn’t pretty, but it had 679 pages indexed in Google, built up over roughly a decade. When the owners commissioned a full rebrand onto a new domain and a custom WordPress build, nobody asked what the old site’s top pages actually were. Every one of those 679 URLs was headed for a blanket redirect to the new homepage.
The Strategy: We paused the launch before redirects went live. Every old page was mapped against Google Search Console data to find which ones carried real traffic, rankings, or backlinks. Roughly 150 priority pages (state pages, city pages, and niche listings such as heritage accommodation) were rebuilt with proper H1/H2 structure and unique supporting copy. Around 486 thin, auto-generated pages were rewritten rather than discarded outright. Only then did we build the 301 redirect map, old URL to closest-matching new URL — never to the homepage.
The Results: Within two months of the new site going live (before the redirects were even switched on), Google Search Console showed early signs of the new domain waking up: 347 referring domains, 14 keywords already in positions 1–3, 59 in the top 10, and 228 in the top 30, out of 889 tracked commercial terms. Bing Webmaster Tools also showed the new domain starting to get picked up by AI answer engines, roughly two months ahead of the typical timeline for a brand-new domain.
The Lesson: A rebrand or new domain doesn’t have to mean starting from zero — but only if someone stops to ask “what was working on the old site?” before deployment day.
Industry Application: Any business with a large page footprint — real estate, accommodation, multi-location retail, or franchise groups — is most at risk here, because there’s simply more surface area to lose.
Case Study 2: Bayside Financial Planning — Financial Services — Brighton, VIC
The Challenge: A financial planning practice in Brighton had around 50 indexed pages covering retirement planning, Centrelink guidance, and advisory services. The pages weren’t attractive, but several ranked well and brought in genuine enquiries. A new brand agency rebuilt the site as a single, sleek one-page design, folding all of that content into a handful of scroll sections with no individual URLs to redirect to.
The Strategy: We couldn’t fully undo the damage after the fact, but we rebuilt dedicated landing pages for the highest-value topics (retirement planning, Centrelink advice, SMSF guidance) and 301-redirected the old URLs to their closest new equivalents instead of the homepage. We also restored proper H1/H2 hierarchy and meaningful meta descriptions, which the single-page build had stripped out entirely.
The Results: Estimated recovery of roughly 60–70% of prior organic enquiry volume within four months of rebuilding dedicated pages, based on Search Console comparisons pre- and post-fix (exact recovery varies case by case and these figures are indicative, not guaranteed).
The Lesson: A one-page “pretty” website might look modern, but if it collapses ten ranking pages into one, you’re trading away a decade of topic-specific trust for a design trend.
Industry Application: Professional services firms — accountants, financial advisors, lawyers — often run lean sites with a handful of high-value pages. Losing even three or four of them can mean losing the enquiries that pay the bills.
Case Study 3: Ferntree Gully Tree & Garden Services — Trades — Ferntree Gully, VIC
The Challenge: A tree removal and garden maintenance business in Melbourne’s east had an old, dated WordPress site with static, keyword-rich category pages (“tree removal Ferntree Gully,” “stump grinding Upper Ferntree Gully”). A new developer rebuilt the site with a modern JavaScript filter system for services and suburbs — nicer to use, but the individual suburb-service combinations were no longer static, crawlable pages. They existed only as dynamic filter results.
The Strategy: Before launch, we identified every suburb-service combination that had previously ranked and rebuilt each as its own static, indexable page with real text on it — not just a filter result. We kept the filter tool for user experience but made sure Google (and AI crawlers) had a plain-text page to land on for each priority combination.
The Results: The rebuilt site retained close to its full set of suburb-service rankings within the typical 8–12 week stabilisation window, rather than the 4–6 month rebuild-from-scratch timeline a fully JavaScript-only structure would likely have required (based on standard post-migration recovery benchmarks).
The Lesson: A slicker user interface is only a win if a search engine — or an AI crawler doing research on your behalf — can still read the content behind it. Bots take the path of least resistance; if a competitor has a plain static page and you only have a JavaScript filter, they win the citation.
Industry Application: Any trade or local service business covering multiple suburbs (electricians, plumbers, landscapers, pest control) should be wary of “smart” filter or search tools that hide suburb-specific content behind JavaScript with no static equivalent.
Implementation Guide
Step 1: Pull your baseline before anyone touches the build
What it looks like: Log into Google Search Console and Google Analytics yourself (don’t wait for the developer to ask). Export your top pages by clicks, impressions, and conversions over the last 12 months.
Pro tip: Do the same in Bing Webmaster Tools. It’s the index ChatGPT draws from most heavily, and most Australian businesses have never even set up an account.
Step 2: Identify every page worth protecting
What it looks like: Cross-reference top-traffic pages, top-ranking pages, and any page with external backlinks (Search Console → Links → Top linked pages). These are non-negotiable — they must have a home on the new site.
Pro tip: Don’t judge a page by how it looks. An ugly page ranking on page one is worth more than a beautiful page ranking nowhere.
Step 3: Build a one-to-one redirect map before launch
What it looks like: A simple two-column spreadsheet — old URL, new URL — for every page identified in Step 2. Never map to the homepage as a catch-all; that reads to Google (and to your visitors) as a soft 404.
Pro tip: If the new site genuinely has no equivalent page, consider whether it should be rebuilt rather than dropped. Rebuilding is usually cheaper than the enquiries you lose by leaving a gap.
Step 4: Protect your on-page fundamentals during the rebuild
What it looks like: Check that every migrated page keeps (or improves) its H1, its supporting paragraph text, and its image alt text. Custom-coded platforms and page builders often strip these out by default.
Pro tip: Don’t just let the platform auto-generate titles and meta descriptions. Google will write its own if you don’t, but that hands over control you don’t need to give away.
Step 5: Launch the redirects, then watch daily for two weeks
What it looks like: Once redirects go live, check Search Console daily for 404 spikes, redirect chains, or a sudden crawl slowdown. Weekly checks are fine after the first fortnight.
Pro tip: Expect a stabilisation window of roughly two to three months before rankings settle — sometimes longer for larger sites. Don’t panic at week two; panic if nothing’s recovered by month four.
Step 6: Reconnect the plumbing for AI, not just Google
What it looks like: Submit your new sitemap to both Google Search Console and Bing Webmaster Tools. Make sure any content behind JavaScript filters also exists as a static, crawlable page.
Pro tip: Ranking in the top 10 of Google’s blue links correlates strongly with being cited by ChatGPT, Gemini, and Claude — because those tools lean on the same underlying trust signals. Foundational SEO is now doing double duty.
Common Pitfalls & Solutions
| Pitfall | Fix | Prevention |
|---|---|---|
| Every old URL redirected to the new homepage | Rebuild a proper old-URL-to-new-URL map, even after the fact | Never approve a launch without a redirect map reviewed first |
| Old page traffic/rankings never checked before rebuild | Pull 12 months of Search Console and Analytics data retroactively | Make this the very first step of any rebuild brief, not an afterthought |
| JavaScript filters replace static, indexable category pages | Rebuild priority suburb/service combinations as static pages | Ask your developer directly: “Will Google be able to read this without clicking?” |
| No H1/H2/meta control in the new template | Get theme-level access to edit these fields, or request it from the developer | Confirm on-page SEO control is part of the build spec before signing off |
| Thin, auto-generated tag pages carried over unreviewed | Audit and either rewrite or 410 (remove) them deliberately | Include a content audit as a standard rebuild deliverable |
Practical Exercise
- Quick Win (5 mins): Log into Google Search Console → Performance → Pages. Sort by clicks over the last 12 months. Screenshot your top 20 pages — these are the ones you can never afford to lose in a rebuild.
- Deep Dive (30 mins): Export your full list of indexed pages (Search Console → Pages → Indexed) alongside your top linked pages (Links → Top linked pages). Cross-reference the two lists and flag every page that appears in either — that’s your non-negotiable redirect list.
- Real Business Application:
- Trades: Check whether your suburb-service pages (e.g. “hot water repairs Blacktown”) exist as static pages or only inside a filter/search tool.
- Professional services: Confirm each core service (retirement planning, conveyancing, tax advice) has its own dedicated URL, not a shared scroll section.
- Retail/hospitality: Check whether product or menu category pages are crawlable text, or hidden behind a JavaScript-driven catalogue.
Tools & Resources
- Google Search Console — free, essential for pulling your pre-migration baseline and monitoring post-launch
- Google Analytics (GA4) — free, cross-check traffic and conversions against Search Console data
- Bing Webmaster Tools — free, increasingly important given its role feeding AI answer engines; check the AI Performance report if available
- Screaming Frog — free (up to 500 URLs) / paid, for crawling old and new sites to compare structure and metadata
- Redirect map template — a simple two-column spreadsheet (old URL, new URL) is enough; several free generators exist to convert this into platform-specific formats (WordPress, Shopify, Webflow, Squarespace)
Module Summary
- The single biggest rebuild mistake is redirecting everything to the homepage — or not redirecting at all
- An “ugly but ranking” old site carries more value than a beautiful new one with no history
- Protecting on-page fundamentals (H1s, meta descriptions, alt text, static crawlable content) matters as much as the redirect itself
- Foundational SEO now feeds AI citation too — showing up in Google and Bing’s top 10 makes you more likely to be cited by ChatGPT, Gemini, and Claude
Keyword Intelligence
Note: Live Ahrefs keyword data was not available for this session. The figures below are domain-knowledge estimates based on typical Australian search patterns for this topic and should be treated as indicative ranges, not verified live data.
| Keyword | Est. Monthly AU Volume | Est. Difficulty | Notes |
|---|---|---|---|
| website migration seo checklist | 90–150 | Low–Moderate | Strong intent-match for this module’s core topic |
| how to redirect old website to new website | 50–90 | Low | High relevance for SMB owners mid-rebuild |
| website rebuild lost seo rankings | 40–70 | Low | Captures owners searching after the damage is already done |
| 301 redirect explained | 200–350 | Low–Moderate | Broad awareness-stage term, good for a supporting glossary page |
| bing webmaster tools setup | 30–60 | Low | Ties into the on-the-horizon Bing/AI citation module |
| squarespace to wordpress migration seo | 20–40 | Low | Niche but highly qualified, low competition |
CMO Eugene — Ranked Digital Marketing, Australia
