What happened
Around July 17, Windowsforum.com received a partial manual action for thin content with little or no added value — message WNC-651700 — aimed squarely at its /threads/ section. That section holds 168,290 visible threads and more than 500,000 posts accumulated over two decades. Google attached no example URLs to the notice.
The theory that's traveling: SEO Gagan Ghotra pointed at the forum's AI chatbot staff account, which has posted 111,050 replies since March 2023, and suggested the auto-replying bot is what tripped the action. Google hasn't confirmed it, and nobody outside Google can.
The site owner's counterpoint deserves weight too. Two sections that are more obviously thin — a syndicated headline feed and an archived knowledge base, together 11,927 threads and inactive for three years — were left untouched. Whatever Google's classifier keyed on, it wasn't a simple thinness sweep.
Why this matters
Strip out the speculation and one hard fact remains: an automated account wrote six figures' worth of indexable pages on this domain, and the domain ate a manual action. Do the arithmetic — the bot authored roughly a fifth of everything posted in twenty years, in about three. That output rate is exactly what AI publishing tools promise, and exactly what a thin-content classifier feeds on when the replies restate the question instead of answering it.
For store owners the mapping is direct. AI product descriptions generated at scale, auto-published Q&A blocks, chatbot answers saved as indexable pages, AI-written review responses — all of it is your content in Google's eyes. There is no 'the bot did it' appeal lane in the manual actions report. Whoever clicked enable owns the output.
Note what the vagueness means in practice: no example URLs, untouched sections that look worse, no confirmed trigger. You can't reverse-engineer where Google's line sits. The only variable you control is the input side — what you let automations publish, and at what bar.
What to do about it
Inventory everything that auto-publishes on your store
List every tool with write access to indexable pages: AI description generators, auto-FAQ builders, chatbot transcripts, review auto-responders, community or UGC sections. If you can't name them all in one sitting, that gap is your first finding.
Sample the output and grade it cold
Pull 20 machine-written pages and ask one question per page: does this say anything a shopper couldn't get from the product name alone? Restated specs and padded boilerplate are precisely the pattern Google's notice describes. Rewrite or noindex whatever fails.
Open the manual actions report today
Search Console → Security & Manual Actions. Partial actions target one section and can sit unnoticed while the rest of the site behaves normally. Windowsforum's notice was dated around July 17 — go check whether anything is sitting in yours.
Gate new automation behind a value bar
Default new AI-generated pages to noindex until a human passes them, or cap publishing volume to what you can actually review. An automation that publishes 111,000 of anything unreviewed is a liability, whatever its accuracy rate.