GSC Coverage Noise vs. Real Indexing Problems (MWOV)
Two alarming-looking signals surfaced for MWOV at the same time: Ahrefs returning only 1 URL on consecutive crawls, and GSC flagging 145 URLs as “not indexed.” Either one taken at face value suggests a site-level indexing failure. Neither was. Both were tool-side noise — and the diagnostic value was in not acting on them.
The Situation
Two separate data points surfaced simultaneously for MWOV that looked alarming on first read: Ahrefs returning only 1 URL on consecutive site crawls, and Google Search Console showing 145 “not indexed” URLs. Either one of those, taken at face value, suggests something is seriously wrong. Together, they looked like a site-level indexing failure.
Neither was.
Diagnosing the Ahrefs Issue
When a third-party crawler suddenly returns near-zero results, the cause is almost always one of four things: the crawler is blocked by robots.txt, there's a template-level noindex tag, there's a misconfiguration in the crawl settings, or the server is throttling the bot.
I worked through each in order. No AhrefsBot block in robots.txt. No template-level noindex. Crawl settings in Ahrefs looked fine. That left server-side bot management.
The actual culprit: LiteSpeed Cache's bot management was aggressive enough to rate-limit the Ahrefs crawler to the point it gave up after the first URL. GSC showed 59 pages indexed normally — Google had no problem accessing the site. The issue was tool-specific, not site-specific.
Diagnosing the GSC “Not Indexed” URLs
The 145 non-indexed URLs in GSC looked like a real coverage problem. They weren't. They were UTM parameter variants — URLs auto-generated by a Jetpack plugin as tracking parameters were appended to existing page URLs. Google was logging the parameter variants as separate URLs and flagging them as non-indexed.
These weren't real pages. They didn't represent missing content. They were reporting noise created by the way the plugin generated UTM links.
What Actually Needed to Be Done
For the Ahrefs issue: review LiteSpeed's bot management settings to determine whether the throttling was intentional or a default that needed adjustment. No structural site changes required.
For the GSC issue: document as non-actionable. The parameter variants aren't harming performance. They're cluttering the coverage report, which is worth addressing long-term, but there's no urgent fix.
The Takeaway
The most expensive mistake in technical SEO isn't missing a problem. It's treating noise like a problem and making changes that weren't necessary. Cross-referencing third-party crawler data against GSC before acting is a non-negotiable step — the tools have their own failure modes, and GSC is the authoritative source for indexing status.
Key Findings
- Ahrefs returning 1 URL was caused by LiteSpeed Cache bot management, not the site
- GSC reported 59 pages indexed by Google — no real indexing failure
- 145 “not indexed” URLs in GSC were Jetpack-generated UTM parameter variants
- Parameter variants were noise, not missing content
- No structural changes recommended — tool noise documented as non-actionable
- GSC remains the authoritative source for indexing status; third-party crawlers don't
More from the case study shelf
Scary-looking GSC report?
A $500 SEO Health Check separates real indexing problems from reporting noise — and tells you what's worth acting on.
Book Your Health Check → ← Back to all case studies Or see the full services & pricing →Want diagnostic work like this?
Whether you need a full GSC audit, a coverage report walkthrough, or someone to tell you whether the data you're seeing is real or noise — I'd love to hear what you're working on.