The noscript tag that quietly tanked a store

The noscript tag that quietly tanked a store

A fashion retailer added a noscript fallback 'for SEO.' Within a month, category pages started losing rankings instead of gaining them.

The intent was good: show plain HTML to crawlers without JavaScript. But Googlebot runs JavaScript. So which version did it use?

We rendered the page as Googlebot does — JS enabled. The full React catalog loaded fine. But the team's noscript block contained a stripped-down, hardcoded list of only 12 'featured' products with thin descriptions, meant as a graceful degradation.

Here's the subtlety: when Google renders with JS, it ignores noscript. But this site's main JS bundle had a slow-loading failure mode on Google's infrastructure roughly a third of the time — and when the bundle timed out, the noscript fallback was the only content. Google indexed the thin 12-product version intermittently, sending mixed quality signals.

Don't put thin content in noscript as a 'safety net' — it becomes your fallback identity when JS fails.

Fix: removed noscript, server-rendered the real catalog.

Result: category rankings recovered and gained, organic revenue +28% in two months.