They tried to help Google. Google read it as cloaking.

They tried to help Google. Google read it as cloaking.

A content site set up edge logic to serve a 'lean' version to Googlebot — stripped scripts, faster render — and the full experience to users. Well-intentioned. Six weeks later, rankings across the site slid 44% and key pages dropped to page 5.

The symptom didn't look like a penalty at first — no manual action. But the rendered HTML Google saw and the page users saw had diverged enough that Google's quality systems flagged inconsistency.

Turns out the 'lean' bot version had drifted. Developers updated the user experience — new sections, new internal links, restructured content — but kept patching the bot version separately, and it fell behind. Googlebot was indexing a months-old, thinner copy of every page. Two pipelines, two truths, and the gap looked like deception.

We killed the bot-specific path entirely. One SSR output, identical for everyone, optimized for both.

Google reconciled the now-consistent pages over six weeks. Rankings recovered from -44% to +3% versus pre-incident in ten weeks. And the team deleted a whole category of bug: 'did we update the bot version too?'

Serving bots a different page isn't optimization. It's a divergence that eventually reads as a lie.