The cookie banner that ate an entire blog

The cookie banner that ate an entire blog

A European health site saw organic traffic crater 60% the week they shipped a new consent management platform. Nothing else changed.

The site rendered fine. The articles were intact. But the consent vendor's script wrapped the entire page render in a gate: content only mounted after a consent decision was recorded.

Googlebot doesn't click 'Accept.' It loaded the page, the consent script blocked the main content render waiting for a decision that never came, and the rendered DOM was a full-screen consent overlay with no article behind it. Google indexed thousands of pages as near-identical 'we value your privacy' screens — and collapsed them as duplicates.

Consent-gated rendering is one of the most damaging JS-SEO patterns precisely because legal and frontend teams ship it without SEO in the room.

Fix: content rendered server-side always; the consent banner overlaid on top without blocking the underlying HTML, and analytics/marketing scripts stayed gated.

Result: traffic recovered to -8% within three weeks, fully back plus 6% by week nine. The legal requirement and the index coexisted fine — they were never actually in conflict.