- Issue: The page returns empty or near-empty HTML
- Impact: Nothing for non-rendering crawlers to index; severe visibility loss
- Fix: Server-render real content into the initial HTML
- Detection: Crawler, View Source, page-experience tools
What this issue means
The raw HTML the server returns is essentially empty — a shell with a script bundle and little or no content. The page looks complete in a browser because JavaScript builds it, but the initial document is hollow.
Why it matters
This is the most severe form of the rendering problem. Crawlers that do not execute JavaScript — which is most AI crawlers — receive nothing to index. Even Googlebot, which renders, treats the page as low priority and may delay or skip it. An empty HTML shell is functionally invisible to the systems that decide whether you appear in search and AI answers (see the receipts).
How to fix it
- Move to server-side rendering or static generation so the initial HTML contains your content (SSR vs CSR).
- Ensure critical content — headings, body, key data — is in the document, not injected later.
- Verify with View Source and a
curl -A "GPTBot"fetch.
Related: SSR vs CSR · The Forgotten HTML
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
