Free checker · SEO and Visibility
Google Crawler Simulator.
Fetches the raw HTML with nothing executed and shows the text, headings and links a crawler gets on its first pass — which is all most AI answer engines ever get.
The page is fetched once with no JavaScript executed — the same raw HTML a crawler receives on its first pass.
Check done
Want someone to fix what this found?
Finding a problem and fixing it are different jobs, and the second one is ours. Send the result over and you get back what it would take to put right — scoped and priced, from the person who would do the work, within one business day.
What this tool measures
This shows the page as it arrives: the raw HTML, with no JavaScript executed. The text, the headings and the links in that response are what a crawler gets on its first pass.
Googlebot does render JavaScript, so this is not the whole story for Google. But it renders on its own schedule, sometimes days after the first crawl, and it drops renders under load. Meanwhile the crawlers behind AI answers — ChatGPT's browsing, Perplexity, and most link preview bots — largely do not render at all. So “the content is visible in my browser” and “the content is in the HTML” are different claims, and the gap between them is the most common reason a modern, good-looking site is quietly outperformed by an older one.
How to use it
Enter a page whose content matters — a service page, a product, an article. Then compare the word count here against what you see in your browser. A page that reads as eight hundred words and serves forty is a client-rendered page, and the difference is being added after the response.
Use the links view to check the navigation. If a site's menu is built by JavaScript, the served HTML has no link graph at all, and a crawler landing on any page finds no way onward.
How to read the result
Word count is the headline. Under fifty words in the response usually means an app shell — an empty div and a bundle. Over three hundred means the content is there and every crawler can read it immediately.
The heading outline is worth more than it looks now that being quoted in an AI answer is a traffic source. Answer engines extract passages, and a page that is one undifferentiated block is hard to quote from. Clear headings that each answer something are what make a page citable.
Empty anchor text on links is usually an icon or an image link with no alt. Anchor text is one of the strongest available signals about what a destination page is about, and an empty one throws it away.
What to do next
If the content is not in the HTML, the fix is server-side rendering or static pre-rendering for the pages you want found. Every major framework supports it. This is a build configuration change rather than a rewrite, and it is usually the single highest-leverage technical change available to a client-rendered site.
If the content is in the HTML and the page still does not perform, the problem is not technical and no amount of crawler work will move it. That is a genuinely useful thing to learn in thirty seconds.
Questions people ask
Google renders JavaScript, so does this matter?
It matters less for Google than it used to and more for everything else than it used to. Google renders on a delay and not always. AI answer engines, which are an increasing share of how people find things, mostly do not render. Content in the response is available to all of them on the first pass.
My page looks empty here but ranks fine. Why?
Because Googlebot rendered it later and indexed the rendered version. That works, and it costs you crawl budget and time-to-index, and it leaves you invisible to every crawler that does not render. It is a working arrangement rather than a good one.
Is this the same as Search Console's URL Inspection?
No, and they are complementary. URL Inspection shows the rendered HTML after Googlebot has run the JavaScript, which is the end state. This shows the response before that, which is the starting point. The difference between the two is exactly the content that depends on rendering.
Does a low word count hurt rankings?
Not on its own — plenty of short pages rank because they answer the question completely. What hurts is a mismatch: a page competing against thousand-word competitors on a topic that genuinely needs a thousand words. Length is a symptom of coverage, not a target.
Where to go from here
- Meta Tag and Open Graph Checker — Check the head of the same page, which is also served before rendering.
- Image Alt Text Checker — Images in the served HTML and the alt text they carry.
- Keyword Density Checker — Paste the extracted text and see what the page is actually about.
- The thinking behind the SEO audit checklist — Rendering and indexing in a full audit.
The guide behind this tool
Built by GoDesign FZE, who build server-rendered sites that crawlers can read.
Get in touch
Want someone to just do this part?
The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.
- You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
- A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
- One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan
Would rather type than fill in a form?
Message on WhatsApp