Blank HTML and SSR Checker for AI-Built Sites

What this check catches

A browser can execute JavaScript and build a polished page after load while the original response contains little more than an empty root element. That gap matters when a crawler, preview bot, or slow device does not run the same client code.

Why it matters before launch

Important headings, copy, links, and metadata may be absent from the initial response. The page can look fine to its owner while search and social systems receive incomplete evidence.

Common warning signs

• View Source contains an empty app or root container
• The H1 and main copy appear only after JavaScript runs
• Social previews show no title, description, or image
• Disabling JavaScript leaves an empty or unusable page

How to inspect it

1. Fetch the public URL and inspect the returned HTML body
2. Compare View Source with the rendered Elements panel
3. Confirm the title, description, H1, CTA, and important links exist in the response
4. Test a production deployment instead of a builder preview

How to fix it

1. Enable server rendering or static generation for the homepage
2. Move essential metadata to the framework metadata or document-head API
3. Render primary copy and navigation on the server
4. Keep client JavaScript for enhancements that do not hide core content