Summary
A connected-marketing SaaS with a domain rating of 78 and 1.34 million backlinks looked like a finished organic property: 34,412 clicks from 1.94 million impressions in 50 days. Its blog’s front door returned a 404 while 179 posts sat in the sitemap, its flagship money page converted impressions at 0.39%, and much of its reported traffic wasn’t its own demand. Big properties don’t fail loudly; they leak.
When the totals are so big nobody looks underneath
Domain rating is a 0-to-100 score of how much authority a site has earned from links. A 78 is rare air.
This company had it, along with a link profile most marketers would trade a year for. Its Search Console showed nearly two million impressions in 50 days and 63.8% of the clicks coming from non-brand searches, the kind that find new customers.
It had never had an AI-search read. And nobody had walked the site as a buyer would, because when the totals are that large, the assumption is that the machine is working.
The blog that didn’t have a front door
The company’s blog URL returned a 404. Not a redirect, not a slow page. Nothing.
Meanwhile, 179 blog post URLs sat in the sitemap, and each individual post loaded fine. The posts existed. The hub that would link them together, pass authority between them, and tell Google they belonged to one body of work did not.
Those posts collectively drew 340,964 monthly impressions, orphaned behind a dead page. None of the 180 blog URLs carried a last-modified date, so Google had no signal about which were fresh.
That’s not a content problem. It’s a plumbing problem, and it was sitting under a third of a million monthly impressions.
The money page that under-earned
The company’s flagship acquisition page, a free tool that feeds the paid funnel, took 1,904 clicks from 486,174 impressions. A 0.39% rate. Its head terms sat at positions 9 to 11, the bottom of page one, converting at 0.14% to 0.51%. The single biggest term, “qr code generator,” showed 98,128 times and earned 135 clicks.
For a page whose job is to start the funnel, that’s the leak that matters most. On 486,174 impressions, every tenth of a percentage point of click rate is roughly 486 more people entering the funnel, on the same rankings.
The traffic that wasn’t theirs
Then the finding that changed how the company read its own dashboards. A large share of the site’s click volume came from pages its customers had built on the platform, not from the company’s own marketing funnel.
Three customer-content paths accounted for more than 20,000 of the 34,412 clicks. The query-level tells were unmistakable: a Korean restaurant name drawing 1,092 clicks, a New York landmark drawing 23,360 impressions.
The traffic number the company reported to itself was substantially not its own demand. Planning on it meant planning on customers’ audiences. The real funnel was smaller than the dashboard said.
One thing done right
Not every finding was a problem. The site’s robots file carried an explicit allow-list for 14 AI agents, and its plain-language crawler file ran 3,041 bytes of real positioning.
Across the eight domains I scanned that quarter, it was best in class. That’s a strength to protect, and the audit said so.
What shipped
A hosted technical and AI-search audit. A strategy document covering roughly 3,000 keywords, prioritizing organic, ideal-customer terms and explicitly not paid ones.
A measurement of AI share of voice against competitors. And every technical and content finding delivered as an itemized list with a named owner, because an enterprise fix with no owner is a fix that doesn’t happen.
Keeping it repeatable
This audit ran on my Audit Engine, the same one behind every audit I ship: one codebase that turns a domain into a report where every claim carries its evidence and its confidence, and a quality gate that has to pass before anything deploys. Fifteen client audits have run through it, and it’s what let nine client-ready proposals go out in a single day that July.
At a glance
- The niche: QR-code and connected-marketing SaaS, domain rating 78, 1.34 million backlinks.
- The problem: Technical (blog hub returning 404 with 179 posts orphaned, no last-modified dates), on-page (money page at 0.39% click rate), measurement (customer content inflating reported traffic).
- What was built: A hosted technical and AI-search audit, a roughly 3,000-keyword organic strategy, an AI share-of-voice measurement, itemized findings with named owners.
- Implementation: My Audit Engine on first-party Search Console over 50 days, a live crawl and backlink data; delivered for ownership review.
- Results: 340,964 monthly impressions identified behind the 404; the 486,174-impression money page quantified; the company’s own-demand baseline corrected.
- Built with: my Audit Engine.
