Fetches a page from our server and shows what its raw HTML contains: the text, headings and links a crawler receives before any JavaScript runs. It warns when a page is an empty shell that the browser fills in, which most AI crawlers and some search crawlers cannot read. For founders who build with a JavaScript framework and want to know what machines actually see.
How to use it
Enter the address of a public page. You can leave out https://.
- Type or paste the page address and press Run check.
- Read the verdict and the text excerpt: this is what a crawler without JavaScript gets.
- Compare it with what you see in the browser. Anything missing from the excerpt is added by scripts.
- If content is missing, render it on the server or pre-render the page, then run the check again.
How Reavlo tests this
This tool runs on our server, because a browser cannot fetch another site's page. Nothing about the request is stored or logged: not the address, not the page.
Fetching. One request for the page, following redirects, with a size cap and a time limit. Addresses that point to private or internal networks are refused before any connection is made. Very large pages are read only up to the cap, and the tool says so.
Reading. The HTML is parsed as a browser parser would, but no script is run and no stylesheet is applied. The visible text is everything outside script, style, noscript, template and head. Headings, links, lists, images and scripts are counted.
The verdict. A page is readable when its raw HTML has at least 200 visible characters. Below that it is js-only when it has no headings and loads scripts or has a noscript element, which is the usual shape of a client-rendered shell, and thin otherwise. These are signals, not proof: a short page can be correct, and a long page can still hide one part behind scripts.
Limits. The tool does not run a headless browser, so it cannot show what appears after JavaScript runs, and it cannot tell which parts of a readable page are added later. It reads one page, not the whole site. Google can render JavaScript, but rendering is deferred and other crawlers often do not do it at all.
Questions
Is the address I enter stored?
No. The address goes to our server only to fetch the page, and neither it nor the page is stored or written to a log. Analytics records only that the tool ran, never the address.
Does Google read JavaScript content?
Google can render JavaScript, but it does so in a second step that may come later, and rendering can fail. Content that is already in the HTML is the most reliable way to be indexed.
Do AI crawlers run JavaScript?
Most do not. They read the HTML your server sends, so a page that is an empty shell looks empty to them.
My page is readable but part of it is missing. Why?
The tool shows the raw HTML only. A section added by a script after load will not be in the excerpt. Check whether the text you care about appears there.
How do I fix an empty shell?
Render the content on the server or at build time, using the server rendering or static generation your framework offers, so the text is in the HTML the server sends.