35 Days: SEO Score 28 to 97, One Page Reaches #1 in Australia
A long-established Melbourne cleaning business - IICRC-certified, 12+ years operating, 4.0/5 Google rating from 44 reviews - was running on a slow, technically broken WordPress site that was actively hurting their business. Despite real-world reputation and capability, organic search delivered almost nothing.
In 14 days we rebuilt the site from the ground up on a code-first, AI-search-ready foundation. Three weeks later, one of the new service pages was ranking #1 in Australia for its primary keyword.
The client’s identifying details have been anonymised at their request. All metrics are verified from Google Search Console, Google Analytics 4, Ahrefs, and PageSpeed Insights.
This case study walks through the before-state, the 14-day rebuild, the 35-day breakthrough, the active monitoring that caught 21 alerts in week 5, and the compounding trajectory from here.
Before: WordPress Was Actively Hurting the Business
The client had been running on WordPress for years. Despite a steady flow of repeat customers and word-of-mouth, the site itself was dragging on the business:
| Metric | WordPress baseline (90 days pre-migration) |
|---|---|
| Total organic Google clicks | 93 |
| Indexed pages | ~200 (with 806 rejected by Google) |
| Mobile PageSpeed | 56/100 |
| SEO health score | 28/100 |
| External JavaScript files | 55 |
| Total script tags | 103 |
| Page weight (homepage) | 549 KB before images |
| Form submissions per quarter | 2 |
| Visible PHP errors on live site | yes |
The business relied almost entirely on direct traffic (returning customers typing the URL) and word-of-mouth. Organic search was delivering almost nothing.
The Diagnosis: Six Compounding Failures
A comprehensive audit identified six issues each individually limiting performance - and compounding when combined.
1. Visible PHP errors on the live site. Trust-destroying for visitors. Trust-destroying for Google.
2. Mobile PageSpeed score 56/100. Google penalises slow mobile experiences in rankings, and slow sites lose mobile users at the doorstep before any content even renders.
3. No structured data. Google had no machine-readable signal about the business, its services, or its location. Knowledge Panel impossible. Local-pack visibility limited.
4. 806 rejected pages in Search Console vs ~200 indexed. A bloated WordPress installation full of noise that Google was actively rejecting - wasting crawl budget on pages that should never have existed.
5. Zero dedicated service pages. Carpet cleaning, end of lease, tile and grout, duct cleaning, and 30+ other services had no individual keyword-targeted pages. All collapsed onto a single generic “Services” page.
6. Catastrophic technical bloat. 55 external JavaScript files, 103 script tags, 549 KB homepage weight before images. The kind of infrastructure that makes every SEO improvement marginal.
The Rebuild (Days 1 to 14)
Rather than patching the existing WordPress site, we rebuilt from the ground up on a modern static-output framework deployed to a global edge network.
Three phases, two weeks
Phase 1 (Days 1 to 3): Migration & Technical Foundation. Reduced external scripts from 55 to 2, page weight from 549 KB to under 80 KB. Added security headers, automated CI/CD, edge-level redirects.
Phase 2 (Days 3 to 7): Content & SEO Architecture. Built 34 dedicated service pages, 143 optimised blog posts, an industry glossary (19 defined terms), 11 schema types deployed sitewide, comprehensive robots.txt with 20 named AI crawlers allow-listed, and llms.txt for AI search readiness.
Phase 3 (Days 7 to 14): Post-Launch Optimisation. Six specialist SEO audits. 25+ issues closed. 42 broken redirects repaired. Keyword cannibalisation addressed across 30 blog posts. Priority pages submitted for re-indexing.
Technical transformation: before vs after
| Metric | WordPress (Before) | Code-First Site (After) | Improvement |
|---|---|---|---|
| External JavaScript files | 55 | 2 | -96% |
| Page weight (homepage) | 549 KB | ~80 KB | -85% |
| Time to first byte | >800ms | <100ms | 8 times faster |
| Mobile PageSpeed | 56/100 | 99/100 | +77% |
| Schema types deployed | 0 | 11 | full coverage |
| AI crawler allowances (robots.txt) | 0 | 20 named | AI-search ready |
After: The 14-Day Result
The new site went live on 30 March 2026. Two weeks later the SEO score had moved decisively and the foundation was holding under traffic growth.
| Score dimension | WordPress | At Launch | Improvement |
|---|---|---|---|
| Technical SEO | 37/100 | 90/100 | +149% |
| Content & E-E-A-T | 24/100 | 79/100 | +229% |
| Schema (Structured Data) | 18/100 | 88/100 | +389% |
| Sitemap & URL Health | 38/100 | 92/100 | +142% |
| GEO (AI Search Readiness) | 19/100 | 82/100 | +332% |
| Performance | 31/100 | 95/100 | +206% |
| Overall | 28/100 | 90/100 | +221% |
Daily impressions stepped from ~250 (pre-migration) to ~550 (week 1 post-launch). Sessions were already trending. The breakout service page - targeting a low-volume, low-competition specialist keyword - had landed at position 9 (page 1).
Most rankings were still in flight. The 14-day mark was an inflection, not a destination.
The Breakthrough: 21 More Days, One Page Reaches #1 in Australia
This is the defining result of the engagement.
The breakout service page reached position #1 in Australia for its primary keyword by day 35 (week 5 post-migration). Three weeks earlier it had been at position 9. Five months earlier on the WordPress site it had been at position 25.
For the broader keyword cluster the page targets:
| Keyword pattern | AU Position | Monthly volume |
|---|---|---|
| Primary specialty service term | 1 | 50 |
| Service term, singular variant | 3 | 80 |
| Service term + city | 4 | 70 |
| Professional service role | 6 | 20 |
| Service category + “near me” + adjacent term | 7 | 10 |
Five of the top seven AU keywords now point to a single page. That page alone drives 36% of all organic clicks across the entire site (50 of 140 in the latest 90-day window).
Other service pages built in the rebuild are accumulating impression volume in the background - high-volume, mid-page positions that represent the next tranche of traffic to convert:
| Service page | 90-day impressions | Avg position | Status |
|---|---|---|---|
| Service page A | 4,148 | 23.6 | Page 3, title/CTR optimisation pending |
| Service page B | 2,137 | 72.5 | High volume, deep, link-building target |
| Service page C | 1,970 | 33.5 | Approaching page 3 |
| Breakout page | 1,911 | #1 Ahrefs primary | Page 1 secured |
| Service page E | 1,881 | 57.4 | High volume, mid-page |
| Service page F | 1,872 | 37.3 | Climbing into top 10 |
The pattern matters: dedicated service pages drive results - but not all equally. Identifying which pages convert and replicating that pattern is more important than building more pages.
Active Monitoring: 21 Alerts Caught in Week 5
This is the section that distinguishes a launch-and-walk-away engagement from a real one.
By day 35, automated daily and weekly monitoring across Google Search Console, Google Analytics 4, Ahrefs, and PageSpeed Insights had logged 21 alerts across the site. Sample triages:
| Alert | Page | Detail |
|---|---|---|
| Position drop 74.6 spots | /contact-us/ | 42.1 to 116.7 in a single week |
| Position drop 40.1 spots | /services/ | 11.5 to 51.6 |
| Position drop 37.5 spots | A specialty service page | 18.0 to 55.5 |
| Position drop 31.3 spots | Another service page | 20.2 to 51.5 |
| Impression drop 85% | A core service page | 243 to 36 |
| Engagement rate drop | site-wide | 20.9% to 16.6% |
These would have been invisible without monitoring. A typical agency engagement ends at launch and the client only learns about a 74-spot Contact Us drop weeks or months later - when the lead pipeline has gone quiet.
The remediation pattern for each alert:
- Cross-reference with Ahrefs to confirm the drop is a real ranking change, not GSC-data noise
- Inspect the page in GSC for indexing status, mobile usability, crawl errors
- Check the redirect map and cannibalisation cluster for the page
- Ship the fix (canonical, redirect, content rewrite, internal-link audit) within days
- Re-monitor in the next weekly run
Hygiene work shipped during the day-14 to day-35 window:
- 93-URL 404 cleanup: legacy WordPress paths flagged in GSC that weren’t in the original redirect map were added at the edge, eliminating crawl-budget waste on dead URLs
- 136-domain disavow file uploaded to Google covering toxic referring domains (mostly low-quality blogspot/wordpress farms from the pre-migration era - 4 to 8 week reprocess window)
- Four cannibalisation redirects consolidating signals from competing blog posts into the canonical service pages
- Brand-query cannibalisation flagged - the brand name was being split across five different pages; canonical and internal-link audit pending
None of this work was speculative. Every action was driven by GSC, GA4, or Ahrefs signal.
Where They Are Now: 35 Days In
Sessions, users, and conversions have all moved decisively in the 90-day window straddling the migration:
| Metric | Previous 90 days | Current 90 days | Change |
|---|---|---|---|
| Total Sessions | 679 | 1,703 | +151% |
| Active Users | 628 | 1,592 | +154% |
| New Users | 612 | 1,575 | +157% |
| Page Views | 873 | 2,129 | +144% |
| Form Submits | 2 | 8 | +300% |
| Form Starts | 11 | 16 | +45% |
Form submissions tripled - and form starts grew faster than submissions, which means more users are arriving and engaging with the form than before. That’s a CRO optimisation target for the next phase, not a sign of degradation.
Mobile engagement is 2.5 times desktop engagement (35.6% vs 14.2%). As local SEO matures and AI search citations begin to land, mobile share will grow further, which compounds quality.
The technical foundation is holding under traffic growth
Mobile PageSpeed: 99/100 sustained at day 35. Desktop: 100/100. Page weight: ~80 KB. No regressions introduced during 35 days of content and SEO work. That’s the test of a real foundation versus a launch-day gloss.
What’s Compounding From Here
Three mechanisms continue to compound from the day-35 baseline:
1. The breakout-page pattern is replicable. The breakthrough page didn’t reach #1 by accident - it had a clear topical authority signal, a low-competition target keyword, and clean technical foundations. Other high-impression service pages above are candidates to replicate the pattern. Service pages A and B are next in the pipeline.
2. AI search citations begin landing in 30 to 90 days. ChatGPT, Perplexity, and Google AI Overviews crawl Google ranking results plus structured data. The site is now built to be cited rather than just listed. First citations expected late May to late July 2026.
3. Disavow processing completes in 4 to 8 weeks. The 136-domain disavow file uploaded on day 35 takes Google several weeks to fully recompute. Once complete, the backlink profile shows quality-only signals - supporting the next domain-rating tick (DR 13 to 14 or 15 is the realistic 90-day target).
The headline transformation in one line: an ageing WordPress site with 28/100 SEO health, 56/100 mobile PageSpeed, and 2 form submissions a quarter became a code-first site at 97/100 SEO, 99/100 mobile, 8 form submissions in 90 days, and one page ranking #1 in Australia - in 35 days, on a real Melbourne cleaning business - and the curve is still climbing.
Could Your Site Do This?
This case study is a working example of what a code-first, AI-search-ready foundation plus active monitoring can do. Measurable, compounding, grounded in real data.
If your site is on WordPress and scoring below 60 on Google PageSpeed, missing structured data, invisible in ChatGPT and Perplexity, generating few or no form submissions, or running on an agency that “shipped and walked away” - the same methodology applies.
We work code-first (no WordPress, no page builders), AI-search ready from day one, with active monitoring (daily and weekly automated reports across GSC, GA4, Ahrefs, and PageSpeed) and integrated SEO and paid ads under one operator. We’ll beat your current website + hosting + SEO spend - send us your current bill. Email-first communication: written response within one business day, no phone calls.
See our SEO services or read more on the blog about the technical foundations behind these results. Running paid alongside SEO? Read our inherited Google Ads account rescue and paid-vs-organic overlap audit case studies for the paid-side equivalent of the same intent-led methodology.
Frequently Asked Questions
Q: Why is the client’s industry detail and brand name anonymised?
The client requested anonymisation while we build out a portfolio of named case studies. Once five or more clients give written permission, we’ll publish those alongside verifiable brand and industry detail. The metrics here remain verifiable through the underlying audits.
Q: What does “active monitoring” actually mean in dollars?
The 21 alerts on day 35 included a single-week 74-spot drop on the Contact Us page. Without monitoring, a 6 to 8 week delay before that’s noticed is normal - meaning 6 to 8 weeks of fewer enquiries from a primary conversion page. The cost of monitoring is a tiny fraction of the cost of a single missed-quarter lead pipeline.
Q: How does this case study square with the price-beat guarantee?
The price-beat guarantee is exactly what it says: we’ll beat your current monthly website + hosting + SEO spend. The output above is what we deliver for that lower price - full rebuild, ongoing monitoring, alert triage, hygiene work, content and CRO optimisation. Send your current bill and we’ll show you the line-by-line.
Q: How much of this is replicable on a small business with no existing rankings?
The technical foundation (PageSpeed, schema, code-first build) is universally replicable - every site can hit 99/100 mobile if built code-first. The “#1 in Australia” outcome depends on a low-competition primary keyword in the business’s niche; that varies by industry. We identify whether your niche has that opportunity in the free competitor analysis before any work starts.
Q: Is the same approach right for an established business already ranking well?
If you’re already ranking, the bigger lift is from the active monitoring layer rather than the rebuild layer. The 21 alerts, the 93-URL cleanup, the 136-domain disavow - those are the kinds of issues an established site accumulates and that a launch-and-walk-away engagement misses. Audit-only engagements are available where a full rebuild isn’t needed.
Q: What happens if Google changes its algorithm?
Clean code, structured data, fast loading, useful content, clear topical authority - these are exactly what every Google algorithm update has rewarded. Active monitoring catches any specific change before it compounds. Algorithm updates that punish thin content, slow sites, or template-built filler don’t punish well-built sites.
Want a free competitor analysis on your own site? Get in touch - we’ll analyse your current site against your top 3 competitors and show you exactly where the gaps are. No obligation, no sales calls.
All metrics independently measured and tracked through 4 May 2026 (35 days post go-live, cutover 30 March 2026).
Could your site do this? Get a free competitor analysis.
Send us your URL. We'll analyse your current site against your top 3 competitors and email you the gaps. No phone calls, no sales reps.