DryOutHub got flagged for "low value content." My first instinct was to write more content. That instinct was wrong, and figuring out why took longer than it should have.
The content was never thin
The site has real structure: a Water Damage Restoration hub and a Mold Remediation hub, each with genuine depth — cost breakdowns, insurance coverage questions, burst-pipe response steps, basement flooding categories, restoration timelines, equipment explanations, red flags to watch for in a contractor. On the mold side: testing, growth patterns after water damage, attic and crawl-space and HVAC contamination, DIY-versus-professional guidance, inspection standards, IICRC certification, insurance angles again. Forty-eight pages, genuinely differentiated from each other, not templated filler.
So when the flag came in, adding a 49th page felt like the obvious move. It wasn't the actual problem.
The real issue was never visible in the content itself
The actual cause turned out to be a site-wide robots.txt configuration issue — something blocking proper crawl access, sitting completely outside the content layer. No amount of new articles would have touched it, because the problem was never what the pages said. It was whether anything could reliably reach them in the first place.
I was treating a plumbing problem like a room needed repainting.
Once the actual configuration was fixed, Search Console confirmed it directly — the sitemap read as a clean success, all 48 pages indexed, no ambiguity left to interpret.
What this actually changed about how I work
The lesson wasn't "check your robots.txt," even though that's the literal takeaway. The real lesson was about where I look first when something's wrong. Content is the visible layer — it's what I wrote, what I can reread, what feels like the thing to improve. Infrastructure is invisible until you go looking for it specifically. My default was to fix the visible thing, not the actual thing, and those aren't always the same target.
I've since gone back and checked the same class of issue across other properties in the network — not because I assumed they were broken the same way, but because "invisible infrastructure problem wearing a content-quality flag as a disguise" turned out to be a real, repeatable failure mode, not a one-off.