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 site crawls, and Google Search Console showing 145 URLs flagged as "not indexed." Either one taken at face value suggests a site-level indexing failure. Both were tool-side noise, and the diagnostic value was in not acting on them.

Ahrefs returning 1 URL. When a third-party crawler suddenly returns near-zero results, the usual causes are: robots.txt blocking the crawler, a template-level noindex, crawl-settings misconfiguration, or server-side bot throttling. Worked through each in order. No AhrefsBot block, no template noindex, crawl settings clean. The actual cause was LiteSpeed Cache's bot management aggressively rate-limiting AhrefsBot. GSC showed 59 pages indexed normally — Google had no problem with the site. The issue was tool-specific, not site-specific.

145 "not indexed" URLs in GSC. Looked like a real coverage problem. Wasn't. The 145 were UTM parameter variants — URLs auto-generated by a Jetpack plugin as tracking parameters got appended to existing pages. Google was logging the parameter variants as separate URLs and flagging them as non-indexed. Reporting noise, not missing content.

Stack: Google Search Console, Ahrefs, LiteSpeed Cache config review, manual URL pattern analysis, Jetpack plugin diagnostics.

Outcome: 0 real indexing problems. Ahrefs throttling documented for client review (intentional vs. default). GSC parameter noise documented as non-actionable. The most expensive mistake in technical SEO is treating noise like a problem and making changes that weren't necessary — GSC remains the authoritative source for indexing status; third-party crawlers don't.

Tags: Technical SEO, GSC, Ahrefs, LiteSpeed, Jetpack, indexing diagnosis, false positives