The noscript tag they thought was a safety net

The noscript tag they thought was a safety net

A startup wrapped their CSR app's critical content in as an 'SEO fallback.' Logic: if JS fails, Google reads the noscript. Indexing stayed thin; -0% movement for six weeks on a launch.

The investigation killed the myth. Googlebot executes JavaScript. So it never falls back to noscript — noscript renders only when JS is disabled, which for Googlebot it isn't. The team had duplicated content into a tag Google structurally ignores, while the real CSR content arrived too late to index.

Turns out noscript is a fallback for the no-JS user, not a feeding mechanism for a JS-capable bot. As an SEO tactic, it's aimed at the wrong audience. Real SSR puts content in the HTML for everyone; noscript hides it from the renderer that matters.

They deleted the noscript hack and server-rendered the critical content for real.

Indexed text per page tripled; the launch page went from position 22 to 7, +24% organic in seven weeks. Noscript answers a question Googlebot never asks. SSR answers the one it does.