Diagnostic
The Search Reporting Was Blind, and Nobody Had Checked
A schema-rich, technically clean nonprofit site that generated almost no search traffic. The cause was not the content. Their Search Console property had never been verified for the domain the site actually served on, so the reporting had been blind for months.
- Client
- A Los Angeles recovery-services organization
- Industry
- Recovery services and facilitator placement
- Location
- Los Angeles, California
The short version
- The client's read was simple: the site is not working.
- The site was fine. The measurement was not.
- Their Search Console history lived on a hostname the site had stopped serving from, and the surviving hostname had never been verified. Nobody was looking at real data.
- We verified the live property, submitted the first sitemap it ever had, and fixed four smaller correctness defects on the way through.
- Search history restarts from the fix date, so there is no before-and-after traffic number to quote. That is the honest state, and this page says so rather than reaching for one.
What was actually wrong
The organization places recovery group facilitators with treatment centers, and recruits already-certified coaches. Both are lines where a single enquiry is worth real money, so being findable matters more than volume.
They had a modern site with genuinely good structured data on it. What they did not have was enquiries, and the reasonable conclusion from the inside was that the site was the problem.
The question we were actually asked was whether the site needed rebuilding again.
What we built
The original build
A seven-page Next.js site, delivered as our earliest completed engagement, later extended into monthly maintenance and reporting.
The diagnostic
Before touching content, we checked whether anyone was measuring correctly. The site had consolidated onto one hostname; the Search Console property carrying all the history was the other one, and the live hostname had never been verified at all.
The fix
Verified the property for the hostname actually being served, then submitted the first sitemap that property had ever received: seventeen pages.
Four correctness defects found in the same pass
The llms.txt file was on a 24-hour cache, so corrections took a day to reach AI crawlers; the blog sitemap stamped published dates where the page's own structured data emitted modified dates; blog posts carried no breadcrumb markup; and several page-level entities floated outside the site's linked entity graph.
Then, and only then, content
Buyer-intent FAQs reordered so the questions an actual buyer asks sit at the top, plus a long-form post aimed at the segment that was missing entirely.
What the numbers say
Every figure below carries the source it came from and the date it was pulled. Where we do not have a number, the row says so instead of estimating one.
| Measure | Result | Source |
|---|---|---|
| Search Console coverage before the fix | No verified property for the hostname the site served on | Google Search Console, verified 2026-08-16 |
| Pages submitted in the property's first-ever sitemap | 17 | Google Search Console, 2026-08-16 |
| Correctness defects found and fixed in the same pass | 4 | Site audit, 2026-08-02 |
| Enquiries actually delivered in a 30-day window | 2, including one facility availability request | Transactional email log, 4 July to 2 August 2026 |
| Contact page behaviour | 5 of 7 recorded key events, averaging 1m47s on page | GA4, 30-day window ending 2026-08-16 |
| Search traffic change attributable to the fix | Not measurable yet. The verified property began collecting on 2026-08-16, so any comparison across that date measures the tracking starting, not the site improving. | Stated rather than estimated, on purpose |
What we did not do, on purpose
The decisions not to build something are usually the ones worth reading.
- We did not add more structured data. The site was already schema-rich, and more markup was not the constraint.
- We did not rewrite the content first. Rewriting before the measurement works means never knowing whether the rewrite did anything.
- We did not rebuild the site, which is what we were originally asked about. It did not need rebuilding.
- We did not quote a traffic improvement. The data to support one does not exist yet.
What we took from it
- After any hostname consolidation, re-verify the surviving host's Search Console property and resubmit the sitemap. Otherwise reporting goes silently blind, and it stays blind because the old property keeps showing plausible historical data.
- A client saying the site is not working is a symptom, not a diagnosis. Here it meant search acquisition, not conversion. The contact page was converting fine for the few people who reached it.
- The cheapest thing an agency can do for a client is check whether the numbers everyone is looking at are real.
Timeline
Original build delivered December 2025. Diagnostic and fixes: August 2026, inside the existing monthly retainer.
How it was priced
Website build, then an ongoing monthly care plan. We do not publish what an individual client pays, but every rate we charge is on the pricing page.
Questions about this engagement
Why is there no traffic improvement number on this page?+
Because there is not one yet that means anything. The corrected Search Console property only began collecting data on 16 August 2026. Comparing before and after that date would measure the moment tracking started, not the moment the site got better. We would rather publish the gap than a number that does not survive a follow-up question.
How does a Search Console property go unverified without anyone noticing?+
The old property keeps working. It still shows charts, still has history, and nothing on screen says the site has stopped serving from that hostname. The data simply flatlines, which looks identical to a site that nobody is searching for. That is what makes it worth checking explicitly rather than assuming.
Would a free AI Automation Audit have caught this?+
Yes. Verifying that measurement is actually working is part of the audit, and it is the kind of finding that costs nothing to fix and invalidates months of reporting if it is missed. The audit is free and written, with a quick turnaround.
Why is the client not named?+
We only name a client with written approval on file. Without it, every study here is anonymized by default, including the ones that went well. That rule does not bend for a good result.
What did this engagement cost?+
We do not publish what individual clients pay, because that is their business. We do publish every rate we charge, in full, on our pricing page. This work ran inside a website build followed by a monthly care plan.
What happens next on this account?+
The property now needs a few months of clean collection before anything can be claimed about rankings. In the meantime the gap is authority rather than markup: third-party citations and a Google Business Profile move this category, and more schema will not.
Want to know what is actually wrong with yours?
That is what the free audit is for. A written, fixed-scope diagnostic with a quick turnaround, ranked by impact against effort, yours to keep. You can also read the other case studies or see how we work with Nashville organizations.
Request Your Free Audit