How I rebuilt a rubbish removal site and doubled its organic traffic

In June 2026 I rebuilt itsdone.com.au for conversion. It is the same site I had recovered after Google flagged it for social engineering content, two and a half years earlier, which is its own story.

In the two months after it went live, Australian organic sessions went from 184 to 376 and leads went from 32 to 74. The site went from ranking on page one for 654 searches to 997.

The rebuild in question. One offer, the phone number and the quote button above the fold, and the trust signals a local services buyer actually checks.

What the rebuild changed

By 2026 the site had come through a hack, a disinfection and a long recovery, and it ranked. That gave the second rebuild a narrower and more interesting brief than the first one had: turn the visibility into phone calls.

A hero that answers “who am I calling”. Rob is an owner-operator with a small crew and a branded truck. A stranger deciding whether to let someone into their driveway wants to know that before anything else, so the homepage leads with him, his crew and the truck, above a single offer, the phone number and a quote button. It runs as a short muted video, so the first thing a visitor sees is a real crew and a real truck moving.

Item pages for the searches people actually type. Nobody searches for “waste solutions”. They search for “mattress removal Melbourne”. So I built dedicated pages under /what-we-take/ for the item types that carry that intent: mattresses and beds, whitegoods and appliances, furniture, e-waste, and paper and cardboard. Each one gets the room to answer what an item search actually asks, in that order: whether you take it, how the job works, and what it costs. They also complete a structure the service pages were already built for, because their “what we take” cards point straight at these URLs.

Navigation that surfaces the money pages. A Residential and a Commercial megamenu panel put every service page one hover from anywhere on the site, which helps a visitor going straight for what they need and pushes internal links at the pages earning the rankings. Built without a plugin and without touching the parent theme.

Short videos on every service page. Each service page carries a brief clip of that work being done, on the page where someone is deciding whether to call. Thirty seconds of footage shows what the job looks like more directly than a paragraph describing it.

A quote form on the page, not behind a click.

Every service and item page now ends with the whole form, sitting inline where someone who has just finished reading about their exact problem can act on it without a click in between. Phone is required and email is optional, because this is a business people ring. The photo upload lets Rob quote accurately without driving out to look at a pile of furniture, which takes the slowest step out of the sale.

This one can be isolated, because the contact page kept its own separate form throughout. Across the same two windows, callback requests through the service page forms went from 8 to 23, while submissions on the contact page went from 10 to 10. The same traffic reached both forms and only the one I moved responded.

A call and quote bar fixed to the bottom of the mobile view. Most of this traffic is someone standing in a garage looking at a pile of furniture, on a phone, with a hand free. A sticky bar with a call button and a quote button means the action is never more than one thumb away, wherever they have scrolled to. Phone link clicks went from 14 to 41 over the same windows, which is faster than the traffic underneath them grew.

Built as a theme, not assembled in a page builder. The site runs on a custom child theme with no ACF, no page-builder plugin and no framework licence. The entire plugin list on the front end is a contact form, a honeypot and Tag Manager. The trade is deliberate: every template, every piece of schema and every byte on the page is something I can edit directly, with no plugin abstraction in the way.

Reviews, collected on purpose. Rob had years of happy customers and no habit of asking any of them to say so. I talked him into asking routinely, as part of finishing a job, and those reviews now run through the service and item pages where a first-time buyer is deciding whether to trust him.

Pick the window before you pick the number

The rebuild went live on 28 June 2026. So a June-versus-July comparison straddles the launch, and a calendar month is the wrong unit for measuring something that happened mid-month.

I compare the two windows either side of the launch date instead: 1 May to 27 June against 28 June to 25 August. Fifty-eight days before, fifty-nine after. The extra day is stated rather than trimmed; it cannot account for a doubling.

Every GA4 and Search Console figure below is filtered to Australian users. This business quotes jobs in metropolitan Melbourne and cannot serve anyone else, so that is the population worth counting. It changes the numbers more than it sounds like it should, for reasons I come back to below.

What happened to traffic and leads

Channel	Before	After	Change
Organic Search	184	376	+104%
AI Assistant	1	36	from nothing
Referral	1	17	from nothing
Direct	21	189	see below

Direct is in the table for completeness and has a section of its own further down. I checked it and do not count it as real growth.

Leads went from 32 to 74 across the site, counted by the reporting pipeline I built for it. That is 41 phone link clicks, 23 callback requests and 10 contact page submissions, against 14, 8 and 10 in the window before, so the whole figure reconciles to three named events rather than one aggregate anyone has to take on trust.

Search Console agrees independently, on the same windows and the same filter: organic clicks 153 to 300, up 96%. It counts differently and lands eight points below GA4’s +104%. Two systems that count differently landing eight points apart is better evidence than either figure alone, and I quote the Search Console number because it is the conservative one.

What happened to rankings

Clicks and sessions are outcomes. The thing underneath them is how many searches the site actually shows up on the first page for.

	Before	After	Change
Queries ranking on page one	654	997	+52%
Queries ranking in the top three	167	284	+70%
Queries with any impression at all	3,546	4,909	+38%

“First page” here means average position 10 or better across the window, over every query Search Console will show me. That definition matters, because the number changes enormously depending on where you put the floor. Anyone quoting a page-one figure without saying which they mean is quoting a number that cannot be checked.

One more, and it is the number I would put first if I had to pick one. August 2026 was the strongest organic month in all 43 months the property has ever recorded: 277 Australian organic sessions, against a previous best of 210 in May 2025. August 2026 is a complete month, so that is a whole month measured against a whole month.

The channel that did not exist before

The AI Assistant row is small enough to skip past, and worth stopping on. It went from 1 session to 36, and those 36 produced 14 lead actions. Set against the other channels over the same window:

Channel	Sessions	Lead actions	Per session
Organic Search	376	40	10.6%
Direct	189	17	9.0%
AI Assistant	36	14	38.9%

Lead actions per session, which is the same basis as every other rate in this article. It is the highest-converting channel on the site by a wide margin, on the smallest volume, which is how a new channel usually looks.

It also did not exist here before the rebuild, in the literal sense. January to May 2026: no AI assistant sessions at all. June: one session and no leads. July: 13 sessions and 5 lead actions. August: 25 sessions and 11 lead actions, across a complete month.

Two things I would not take from that. The rebuild is not what created the traffic, because AI referrals grew across the web through 2026 and a single site cannot separate its own effect from the trend. And the sample is small enough to move a long way: 36 sessions, 31 of them from ChatGPT, and all 14 lead actions came from ChatGPT. Perplexity and Gemini sent five sessions between them and no leads.

What the rebuild does explain is what happened once that traffic arrived. People coming from an AI assistant already know what they want, and the site was clear enough to be quoted by one.

“Is that just the season?”

Rubbish removal has a season, so this is the right question, and most case studies cannot answer it. This one can, because the property holds four years of data and the test is the same window pair in every one of them. Australian organic sessions, every year:

Year	May + June	July + August	Change
2023	117	130	+11%
2024	182	220	+21%
2025	390	284	-27%
2026	194	430	+122%

2023 is the hack year, so I throw it out rather than let a broken year flatter the average.

That leaves one clean year up 21% and another down 27%. There is no reliable seasonal uplift between these windows. Averaged, the season runs slightly against the comparison, at an index of 0.97. Applying it, July and August 2026 should have come in around 188 sessions. They came in at 430, and August 2026 is a complete month here, measured against complete months in every other year of the table.

The business does vary by season. The season does not explain this.

Was it the rebuild, or the articles?

Seasonality is the objection people raise. This is the better one.

A content programme ran through the same window: new articles and substantial rewrites of existing ones, each with a short explainer video on a YouTube channel I set up for them, each pushed automatically to Pinterest, LinkedIn and Google Business Profile by pipelines I built rather than licensed. Blog URLs earning Australian impressions went from 22 before the rebuild to 75 after.

So the rebuild was not the only thing driving traffic in those two months. The content programme was running alongside it, both of them mine, which makes the split a question about which lever did what rather than about who gets the credit. The two cannot be separated cleanly from this data.

What the articles do not explain is the conversion side. They were not the thing that took callback requests from 8 to 23 while the contact page sat at 10, because both forms were in front of all of that traffic equally, new readers included. A content programme lifts the top of the funnel. It does not change what happens when someone decides to act, and that is the half of this the rebuild owns outright.

What the conversion rate did

Organic leads went from 29 to 40. The organic conversion rate fell over the same period, from 15.8% to 10.6%, and the cause is the content programme rather than anything in the rebuild.

Blog pages were the landing page for 118 of the 376 organic sessions after the rebuild, against 21 of 184 before. Someone reading about their council’s hard rubbish dates is answering a question, not booking a truck. Take the article landings out of both windows and the pages built to sell hold their rate: 17.8% before, 15.5% after. A content programme adds traffic at the top of the funnel faster than it adds intent, and a blended rate reflects that.

Worth knowing for anyone measuring this: GA4 credits article landings with a single lead action across the whole period, from the piece on Melbourne tip fees. Session-scoped attribution only sees somebody who reads and acts in the same visit, so a reader who finds an article in July and rings in September arrives as a new session on a different page. The articles are contributing leads that this report cannot size.

Why the traffic looked flat

Everything above is filtered to Australian users. Unfiltered, total sessions across the same two windows went from 1,006 to 1,021. One per cent. Report that and you conclude the rebuild did nothing for traffic.

	Before	After	Change
Australian sessions	209	627	+200%
Non-Australian sessions	797	394	-51%
Total, unfiltered	1,006	1,021	+1%

Read the Australian row for its direction rather than its size, because part of it is a Direct channel I do not trust, which is the next section.

The non-Australian half did not fall by accident. I put Cloudflare and country IP blocking in front of the site in the first week of July, deliberately, and for a business that only quotes in Melbourne that traffic was never going to become work. So two deliberate changes, one growing the audience that matters and one removing the audience that does not, cancelled each other in the only number most people look at. The total is not lying. It is answering a question nobody asked.

Two notes, because both are fair objections. The country filter is a reporting choice applied when the report runs, not a collection rule, so it reaches back across the property’s whole history and the four-year table above is filtered identically in every year of it. And the filter guts GA4 while barely touching Search Console, whose organic clicks go 156 to 153 before and 300 to 300 after, which tells you the traffic it removed was not arriving through search.

Checking the channel that grew fastest

Australian Direct sessions went from 21 to 189, the largest movement anywhere in this data, so it got the same breakdown the countries did.

Sixty-one of those 189 sessions landed on the homepage on desktop and produced one lead between them. In August alone that row is 44 sessions and none. A few more arrive with no landing page recorded at all. This is a business people find on a phone and ring, so desktop traffic that types in the address and never calls is most likely Rob and me, checking the new pages on the desktops we built them on.

So it is left out of everything above. Strip Direct from both sides and Australian sessions still go from 188 to 438.