Pages render as thin, empty HTML before JavaScript runs
A single-page application, or SPA, builds its content in the visitor's browser using JavaScript, rather than sending fully built HTML from the server. This check found multiple pages on this site returning very thin HTML, under 3KB, meaning the content is only rendered client-side, after JavaScript runs. Search engine and AI crawlers that don't fully execute that JavaScript see an empty shell instead of your actual content. Pages that aren't pre-rendered on the server get essentially zero SEO credit and are not eligible to be cited by AI search tools, because those crawlers are looking at the empty shell, not the content that eventually appears for a human visitor. Your developer should turn on server-side rendering or static pre-rendering, a feature most modern frameworks support with a configuration change rather than a rewrite. Budget two to four hours per group of similar page types, sometimes called a route group.
Why this matters
Pages that aren't pre-rendered on the server get essentially zero SEO credit and are not eligible to be cited by AI search tools, because those crawlers are looking at the empty shell, not the content that eventually appears for a human visitor.
How to fix it
Your developer should turn on server-side rendering or static pre-rendering, a feature most modern frameworks support with a configuration change rather than a rewrite. Budget two to four hours per group of similar page types, sometimes called a route group.