<b>A login wall Google could see through — into nothing</b>

<b>A login wall Google could see through — into nothing</b>

A community platform had 40,000 discussion threads, rich with exactly the long-tail content that should print organic traffic. Google indexed them as nearly empty pages. Average word count Google recorded: 60. Actual: 1,200+.

The threads rendered behind a client-side auth check. On load, the app fired an auth request; while it resolved, it showed a skeleton. For logged-out visitors — which Googlebot always is — the auth call returned "unauthenticated," and the app rendered a teaser plus a "Sign in to read replies" prompt. The full thread content was fetched only after auth succeeded.

The content wasn't truly gated — it was public, indexable, intended for SEO. But the rendering logic withheld it from anyone not logged in, and Googlebot is never logged in.

We server-rendered the full public thread content for unauthenticated requests and kept interactive features behind auth.

—Word count Google indexed: 60 → 1,240 avg
—Long-tail organic entries: +380% in 10 weeks

If your render logic treats Googlebot like a guest who must sign in, it will index the welcome mat, not the room.