Every real visitor sees a fully-built page. That doesn't guarantee Google does — and the gap between the two is easy to miss because it's invisible in every normal way of checking a page.
A browser downloads a page's raw HTML, then runs its JavaScript, which can build or rewrite large parts of the page before you ever see it. When you open dev tools and inspect the page, you're looking at the rendered result — after JavaScript has already done its work. That's not what a crawler with a limited JavaScript budget necessarily sees.
Google has gotten much better at rendering JavaScript before indexing, but it isn't instant and it isn't guaranteed to fully complete on every page, every time — especially on sites with heavier or slower client-side rendering. If the raw HTML response has no heading and almost no text, and everything meaningful is built client-side, that page is at real risk of being indexed as thin or blank.
The normal ways people check a page — opening it in a browser, inspecting the DOM in dev tools — both show the fully rendered result, not the raw response a crawler initially receives. The only way to see what a bot with limited JS execution actually gets is to look at the literal HTML response before any script runs.
We check the raw HTML response against the rendered page automatically, so this doesn't stay hidden.
Run a free check on your own site →