Next.js or a SPA: making it readable without JavaScript

Framework-rendered pages often switch to client rendering on some routes — typically the ones behind interaction — while the marketing pages stay server-rendered.

How to confirm it

Run this against your own domain:

for p in / /docs /pricing; do printf "%s " "$p"; curl -sS "https://example.com$p" | wc -w; done

How to fix it

Turn on SSR or static generation for every route that answers a question, verify each route with curl rather than the browser, and add a build-time check that fails when a route renders empty.

Where it fits

This is a symptom of a failed check — here it points at A2. The failure it belongs to is only one of fifteen; the full list is in the standard, and the fix order that avoids redoing work is in the repair guide.