What it is
This check looks at how much actual, visible text content a page delivers in its underlying HTML — the raw material search engines and other automated tools read, before any JavaScript on the page has had a chance to run and fill things in. A page counts as "effectively empty" here when that raw content is minimal or missing entirely, even if the page looks completely normal and full of content once it's finished loading in a browser.
This gap between what a browser eventually shows and what's present at the start is common on sites built with certain modern website frameworks, where the content is generated by JavaScript after the initial page loads rather than being included from the start.
Why it matters
Most search engines can run JavaScript and often do eventually see the fully loaded version of a page — but not always, not immediately, and not with unlimited patience. A page that depends entirely on JavaScript to show any content at all is taking an unnecessary risk with how reliably it gets read, crawled, and indexed, compared to one that includes real, readable content from the very first response.
It's also a useful early warning sign for a bug rather than a design choice — a page that's supposed to show content but returns nearly nothing in its raw HTML sometimes indicates something is failing silently on the server side, not just a slow-to-load design.
How to fix it
- View your page's raw HTML source (right-click → "View Page Source", which shows what's delivered before JavaScript runs) and check whether your main content actually appears there in text form.
- If it's missing from the raw source but visible in the normal browser view, your content is likely being generated entirely by JavaScript after the page loads.
- If you're using a modern JavaScript framework, look into "server-side rendering" or "static site generation" options, which produce a version of the page with real content already included, rather than relying purely on the browser to build it.
- If this is unexpected (you didn't build the site to work this way), check for a server error or failed build step that might be causing the page to render with none of its intended content.
- Re-run your Launch Readiness check after making changes to confirm real content is now detected in the page's raw HTML.