Written by: Learning Objectives
This module explains why new or rebuilt websites fail to index in Google, focusing on common technical SEO failures during website migrations. It breaks down Search Console indexing statuses (“Crawled – Currently Not Indexed” and “Discovered – Currently Not Indexed”), and shows how poor structure, missing redirects, JavaScript rendering issues, and weak SEO implementation can wipe out organic visibility.
It includes real-world case studies across property, electrical, and retail businesses, plus a practical implementation checklist covering redirects, sitemap submission, static page creation, and TFIDF-based content structuring. The core theme is protecting and rebuilding SEO equity during website migrations.
By the end of this module, you will be able to:
- Understand why a brand-new, expensive website can fail to appear in Google search results — even months after launch.
- Identify the difference between “Crawled – Currently Not Indexed” and “Discovered – Currently Not Indexed” in Google Search Console, and what each actually means.
- Recognise the most common technical and structural mistakes made during website rebuilds and platform migrations.
- Apply a basic SEO indexing checklist before (and immediately after) launching any new website.
- Understand how TFIDF-based page construction can accelerate indexing and Page 1 rankings within weeks.
Key Concepts
- Indexing — Google’s process of storing and cataloguing your web pages so they can appear in search results. A page that isn’t indexed simply does not exist in Google’s eyes, regardless of how much the website cost to build.
- Crawled – Currently Not Indexed — Google visited your page, read its content, but decided not to include it in search results. This is often a signal of thin content, poor structure, or missing SEO fundamentals (title, H1, meta description).
- Discovered – Currently Not Indexed — Google found a link to your page but hasn’t even bothered to crawl it yet. It’s sitting in a queue, often deprioritised because the rest of your site doesn’t signal enough trust or clarity.
- Dynamic Text / JavaScript Rendering — When page content is generated on the fly by JavaScript (e.g., a filter that displays properties by suburb), Google often can’t read it. There’s no static HTML for its crawler to sink its teeth into. If there’s no page for “properties for sale in Perth,” there’s nothing to rank.
- Advanced Custom Fields (ACF) / Custom Post Types — Developer-favourite WordPress tools that create flexible content structures. Powerful, but when SEO metadata (titles, descriptions, headings) isn’t wired up correctly, they produce pages that are effectively invisible to Google.
- TFIDF (Term Frequency–Inverse Document Frequency) — A content optimisation technique where specific keywords are used the precise number of times that matches the average of the top 10 pages already ranking for that term. It’s not keyword stuffing — it’s calibration. Google responds to it quickly.
- Website Migration — Moving a website from one platform, domain, or CMS to another. Without a proper SEO migration plan (redirects, preserved page structure, retained metadata), you can wipe out years of accumulated ranking equity overnight.
- SEO Equity — The accumulated authority, backlinks, and ranking history of your existing pages. It’s an asset. A rebuild that ignores it is like renovating a house and bulldozing the foundations to start over.
Real-World Case Studies
Case Study 1: StayRight Property — Real Estate & Accommodation Portal — South Yarra, Melbourne
The Challenge: StayRight Property had a mature Squarespace website with over 30 pages appearing on Page 1 of Google — accommodation listings, sales pages, and suburb-specific property guides. They invested $38,000 in a custom WordPress rebuild. Beautiful design. Custom post types. Advanced custom fields. The agency that built it was top-shelf on design and branding.
The problem? Within weeks of launch, their two most important service pages — “Short Stay Accommodation Melbourne” and “Property Sales Melbourne” — were flagged in Google Search Console as “Crawled – Currently Not Indexed.” The About Us page: same story. Traffic collapsed. Enquiries dried up. The client had a $38,000 website that Google was politely ignoring.
The Strategy: When we took over, we ran a full diagnostic in Google Search Console and immediately spotted three critical failures. First, the custom post type pages had no control over SEO titles or meta descriptions — the developer had hard-coded them as template strings, not editable fields. Second, the H1 tags were being pulled dynamically from a field that was often empty on new pages. Third, and most damaging, the 30+ pages from the old Squarespace site that were ranking had no 301 redirects in place. All that SEO equity had vanished into 404 errors.
We installed a lightweight page builder as a band-aid layer to regain control of on-page elements without touching the complex custom code. We then rebuilt 35 location-specific and niche-specific static pages — including “Sell My Property Western Australia,” “Short Term Rental Management Brisbane,” and “Accommodation Near Melbourne CBD” — with full TFIDF calibration.
The Results: Within two weeks of the new pages going live, all 35 were indexed. Within three weeks, the majority had landed on Page 1. Google Search Console started showing positive impressions and clicks for the first time since the rebuild. Bing Webmaster Tools echoed similar improvements. The business was cited in a ChatGPT response referencing Melbourne accommodation management — within two weeks of new content going live.
The original pages built by the expensive agency? Still not indexed at the time of writing.
The Lesson: A website rebuild without an SEO migration plan is like moving house and not updating your address. Everything important stops reaching you.
Industry Application: Any business with an existing website — trades, professional services, retail — must audit what’s already ranking before touching the site. That list of ranking pages is your SEO asset register. Protect it the same way you’d protect a piece of equipment or a client database.
Case Study 2: Beaumont Electrical — Electrical Contractor — Parramatta, Sydney
The Challenge: Beaumont Electrical had a basic but functional WordPress website they’d been running for four years. They commissioned a local design agency to rebuild it on a proprietary drag-and-drop platform. The new site looked modern and professional, but there was no mechanism to edit SEO titles or meta descriptions. The platform locked the H1 to the page title field, which was formatted as the business name on every page.
Every service page — “Residential Electrician Parramatta,” “Commercial Electrical Contractor Western Sydney,” “Emergency Electrician 24 Hour” — had the same H1: “Beaumont Electrical.” Google had no way to differentiate the pages from each other.
The Strategy: We couldn’t migrate off the platform without a significant rebuild, so we worked within the constraints. Using the platform’s redirect manager and canonical tag settings, we preserved what we could. We then created a separate WordPress microsite targeting the top five commercial search terms in Western Sydney, with precise TFIDF-optimised content, proper H1/H2 structure, and suburb-specific pages for Parramatta, Penrith, Blacktown, and Liverpool.
The microsite was cross-linked to the main site and built on a subdomain with a keyword-rich domain structure. We also submitted the sitemap immediately to Google Search Console and Bing Webmaster Tools.
The Results: The microsite pages indexed within 10 days. Three of the five primary commercial service pages hit Page 1 within the first month. Monthly organic leads from Google went from approximately 4 to 22 in 60 days. Value of those leads, estimated at an average job size of $1,800: roughly $32,000 in pipeline per month.
The Lesson: When you can’t fix the platform, build around it. The algorithm doesn’t care how you get there — it rewards pages with clear structure, correct heading hierarchy, and relevant content. Find a way to give it those things.
Industry Application: Trades businesses that have been sold proprietary platforms by web designers should always ask: “Can I edit my SEO title, meta description, and H1 independently on every page?” If the answer is no, your search visibility is at the mercy of the platform.
Case Study 3: Petals & Post Florist — Retail Florist — Fitzroy, Melbourne
The Challenge: Petals & Post had been operating for six years with a Wix site that, despite its limitations, had accumulated genuine rankings: “Same Day Flower Delivery Fitzroy,” “Birthday Flowers Melbourne Inner North,” and “Wedding Flowers Collingwood.” They redesigned to Shopify, assuming it would be better for their online store.
Nobody told them to capture the old page URLs. Nobody set up redirects. Nobody checked whether the new Shopify URLs matched the old Wix URLs. They didn’t. Three months after launch, they’d lost Page 1 positions on every one of those terms. Mother’s Day came and went with a fraction of their usual online orders.
The Strategy: We performed a full backlink and ranking audit of the old site using a cached version and historic ranking data. We recreated a map of every ranking page and its old URL, then built Shopify redirects from the old paths to the nearest equivalent pages. Where equivalent pages didn’t exist, we created them as blog-style editorial content.
We submitted a new sitemap, requested indexing on the priority pages via Google Search Console, and rebuilt the meta title structure on all product and collection pages — Shopify’s defaults are notoriously generic.
The Results: Within six weeks, 80% of the lost Page 1 positions had returned. Organic traffic recovered to pre-migration levels by week eight. The business recovered an estimated $6,200 in lost revenue attributable to organic search, based on prior year same-period comparison.
The Lesson: Platform migrations aren’t just a design project. They’re an SEO project. Treat them that way from day one, and get a specialist involved before development starts — not after traffic disappears.
Industry Application: Retail and hospitality businesses with established online presence must treat every URL as an asset when redesigning. Think of each ranking URL like a product SKU. You wouldn’t delete your best-selling items without a plan.
Implementation Guide
Step 1: Audit Your Existing Site Before Touching Anything
Before you brief a designer, export a complete list of every page on your current website and check which ones are receiving organic traffic.
What it looks like: Log into Google Search Console → Performance → Pages. Sort by clicks. Screenshot or export this list. Every page with meaningful impressions or clicks is an SEO asset. If you don’t have Search Console set up, connect it immediately — it’s free.
Pro tip: Also run a free crawl of your existing site using Screaming Frog (free up to 500 URLs). Export the list of URLs, titles, and H1s. This becomes your migration reference document.
Step 2: Build a Redirect Map Before Development Starts
Every old URL that is changing needs a 301 redirect to its new equivalent. This preserves the SEO equity flowing through that URL.
What it looks like: Create a two-column spreadsheet. Column A: old URL. Column B: new URL destination. Hand this to your developer on day one of the build — not day one after launch.
Pro tip: If the new site has a fundamentally different page structure, map old pages to the most topically similar new page rather than leaving them as 404 errors. A redirect to an imperfect destination is always better than a dead page.
Step 3: Confirm SEO Control on Every Page Before Launch
Before the new site goes live, verify that every page has independently editable SEO titles, meta descriptions, H1s, and H2s. Not pulled from a template. Not locked to the page title. Independently editable.
What it looks like: On a WordPress site, install Yoast SEO or Rank Math. Open five different pages and confirm you can type a unique SEO title and meta description for each one without it affecting other pages. If you can’t, raise it with your developer before launch.
Pro tip: Ask your developer to send you a screenshot of the SEO field setup on at least three different page types — homepage, service page, blog post. If they can’t show you this, the platform may not support it.
Step 4: Submit Your Sitemap and Request Indexing Immediately After Launch
The moment the new site goes live, submit your XML sitemap to Google Search Console and Bing Webmaster Tools. Then manually request indexing on your five most important pages.
What it looks like: In Google Search Console → Sitemaps → Add your sitemap URL (usually yoursite.com.au/sitemap.xml). Then go to URL Inspection → type in your homepage URL → Request Indexing. Repeat for your key service pages.
Pro tip: Do the same in Bing Webmaster Tools. Bing feeds Microsoft’s AI-powered search (Copilot), and being indexed there is increasingly relevant as AI-generated answers become the first stop for consumer research.
Step 5: Build Static Pages for Every Core Search Term — No JavaScript Filtering
If your business operates across multiple suburbs, services, or niches, each of those combinations needs its own static page. Not a filtered view. Not a dynamically generated result. A real, crawlable, indexable HTML page.
What it looks like: A real estate site covering accommodation and sales across four states needs individual pages for “short stay accommodation Sydney,” “property management Brisbane,” “holiday rental management Perth,” and so on. Each page has its own URL, unique content, unique H1, and target keyword woven into the copy at the right frequency using TFIDF analysis.
Pro tip: Start with your highest-intent search terms and build outward. A 35-page rollout covering your core geographies will outperform a 200-page site where every page is thin, generic, or duplicated.
Step 6: Monitor Google Search Console Weekly for the First 90 Days
The 90 days following a site launch or rebuild are critical. Set a reminder to check Search Console every week.
What it looks like: Go to Coverage → look for pages in the “Excluded” category. The two statuses you’re watching for are “Crawled – Currently Not Indexed” and “Discovered – Currently Not Indexed.” If your key pages appear there, it’s a signal to investigate immediately — not wait it out.
Pro tip: Cross-reference Search Console with Bing Webmaster Tools. If a page is indexed in Bing but not Google, the content itself is probably crawlable — the issue is likely Google-specific quality signals (thin content, duplicate titles, poor structure). That’s actionable information.
Common Pitfalls & Solutions
| Pitfall | Fix | Prevention |
|---|---|---|
| Rebuilding the site without capturing existing ranking URLs | Recover rankings via redirects and recreate content on new pages | Always audit existing rankings before committing to a rebuild |
| Choosing a platform that doesn’t support editable SEO fields | Install a plugin or switch platforms; build a microsite workaround if locked in | Ask “Can I edit SEO title, H1, and meta description independently on every page?” before signing any web development contract |
| Dynamic JavaScript pages that Google can’t crawl | Create static HTML equivalents for every core search term and geography | Design your site architecture with static, indexable pages for all key keyword targets |
| Launching without a submitted sitemap | Submit via Google Search Console and Bing Webmaster Tools immediately | Include sitemap submission as a go-live checklist item |
| Assuming Google will “figure it out” over time | It won’t. Feed it clear signals: proper titles, H1s, H2s, structured paragraphs | Treat Google like a structured form: fill in every field, every time |
| Relying only on Google Search Console | Add Bing Webmaster Tools — it indexes faster and feeds AI search results | Set up both platforms before launch, not after traffic drops |
| Installing a second page builder on top of an existing CMS | Avoid if possible; if necessary, isolate it to specific page types | Agree on a single, SEO-compatible page builder before development begins |
Practical Exercises
Quick Win (5 minutes): Open Google Search Console right now and go to the Coverage report. Click into “Excluded” pages. If any of your service or location pages appear under “Crawled – Currently Not Indexed,” write those URLs down. That’s your priority list for this week.
Deep Dive (30 minutes): Run your website through Screaming Frog (free for up to 500 URLs). Export the crawl data. Look at the H1 column — how many pages are missing an H1 entirely? How many have the same H1 as another page? How many have H1s that don’t contain your primary keyword? Fix the top 10 worst offenders first.
Real Business Application: If you are planning a website rebuild or platform migration in the next 12 months:
- Export your current ranking pages from Google Search Console (Performance → Pages → export).
- Map each URL to a planned new URL on the incoming site.
- Brief your developer with this redirect map before a single line of code is written.
- Confirm in writing that the new platform supports independently editable SEO titles, meta descriptions, and heading tags on all page types.
- Set your go-live checklist to include: sitemap submission, manual indexing requests for top 10 pages, and a Search Console review at Day 7, Day 30, and Day 90.
Keyword Intelligence
Note: Ahrefs MCP was unavailable this session. The figures below are domain-knowledge estimates based on practitioner experience in the Australian market. Verify volumes and difficulty scores in Ahrefs Keywords Explorer (set country to AU) before building campaigns or prioritising content.
| Keyword | Est. AU Monthly Volume | Est. Difficulty | Intent | Priority |
|---|---|---|---|---|
| website not indexed google | 300–600 | Low–Medium | Informational | High |
| google search console crawled not indexed | 500–900 | Medium | Informational | High |
| website rebuild seo | 200–400 | Medium | Commercial | High |
| seo website migration australia | 100–250 | Medium | Commercial | High |
| google not indexing new website | 300–500 | Low | Informational | High |
| website migration seo checklist | 150–300 | Low–Medium | Informational | Medium |
| wordpress seo plugin australia | 100–200 | Low | Commercial | Medium |
| discovered currently not indexed fix | 200–400 | Low | Informational | High |
| real estate seo australia | 150–300 | Medium–High | Commercial | Medium |
| bing webmaster tools australia | 80–150 | Low | Navigational | Medium |
| tfidf seo content optimisation | 50–120 | Low | Informational | Niche |
| squarespace to wordpress migration seo | 100–200 | Low–Medium | Commercial | Medium |
Recommended action: Run these terms through Ahrefs Keywords Explorer with country: au to confirm real volumes and KD scores. Filter for KD under 35 and volume over 80 for the most achievable ranking opportunities. The informational terms in this list make excellent blog content that builds topical authority while the commercial pages do the heavy lifting.
Tools & Resources
- Google Search Console — Free. Non-negotiable. This is your indexing control panel. Set it up before your site launches. search.google.com/search-console
- Bing Webmaster Tools — Free. Often overlooked, but Bing indexes faster than Google and feeds Microsoft Copilot and other AI search tools. Increasingly worth monitoring. bing.com/webmasters
- Screaming Frog SEO Spider — Free up to 500 URLs. Use it to audit H1s, meta titles, redirects, and missing metadata before and after any site rebuild. screamingfrog.co.uk/seo-spider
- Yoast SEO (WordPress) — Free tier available. The most reliable way to add independently editable SEO fields to every WordPress page type. A baseline requirement for any WordPress site targeting organic traffic.
- Rank Math (WordPress) — Free tier available. An excellent alternative to Yoast with stronger schema markup features. Either tool works; what matters is that you have one of them installed.
- Ahrefs — Paid. Essential for crawl audits on larger sites, backlink analysis pre-migration, and keyword research to identify the static pages worth building. The Site Audit feature specifically flags indexing issues. ahrefs.com
- Redirect checklist template — Create a simple two-column spreadsheet: Old URL | New URL. Share it with your developer before any rebuild begins. This one document can save months of traffic recovery work.
Module Summary
- An expensive website is not a visible website. Design and branding matter — but if Google can’t read your titles, headings, and structured content, your pages won’t appear in search results. A beautiful site with no SEO fundamentals is an invisible site.
- “Crawled – Currently Not Indexed” is not a waiting game. If your service pages are sitting in that status, Google has made a decision — not a placeholder. The fix is to give those pages clear structure: unique H1, relevant content, editable SEO title and meta description. No guesswork. No assumptions. Feed the algorithm what it’s looking for.
- Every rebuild is an SEO migration, whether you treat it that way or not. The pages on your current site that rank and receive traffic are assets. If you move to a new platform without a redirect map and don’t recreate that content, you are voluntarily wiping out years of earned authority.
- Static pages beat dynamic filters, every time. If your business covers multiple suburbs, services, or property types, each combination needs its own static, crawlable, indexable page. JavaScript-generated views don’t rank. Individual pages do. Build them out systematically, calibrate the content with TFIDF principles, and watch Search Console turn green within weeks.
Module produced by CMO Eugene — Ranked Digital Marketing, Australia ranked.com.au
