How to use
01
Enter the page URL
Paste the address you want to inspect and press Fetch as crawler. The tool requests the page server-side, the same first step every search bot takes.
02
Read the two stats
Check KB HTML for page weight and words indexable for how much real text survived stripping. A tiny word count on a content page is your red flag.
03
Compare the two tabs
Switch between Plain text and Raw HTML to see what a crawler extracts versus what your server actually sent, and copy the text out for review.
Why Search Engine Spider Simulator
- See exactly what a search engine crawler receives as raw HTML.
- Plain-text view shows the indexable content (no JS rendered).
- Catch client-rendered SPAs that ship empty HTML.
Common questions
What does the spider simulator strip out of my page?
Script blocks, style blocks, and every HTML tag. What remains is the plain text a basic crawler would treat as your page content. If your headline or product copy is missing from that view, it was injected by JavaScript rather than served in the HTML.
How do I see page as googlebot for a staging site?
The URL has to be publicly reachable, since the fetch comes from our server. Password-protected staging environments will return their login page instead. Deploy to a temporary public URL or an unlisted preview to test before launch.
Does this googlebot simulator execute JavaScript?
No, and that's deliberate. Real Googlebot can render JS in a second wave, but the first thing every crawler evaluates is the raw response. If your content only exists after rendering, you're betting on that second pass, and many other bots never make it.
Why is the words indexable number so low on my JavaScript site?
Because a single-page app typically serves a stub: a root div, some script tags, and little else. The text you see in a browser is assembled client-side after load. Consider server-side rendering or prerendering so the initial HTML carries your actual content.
Is the Raw HTML tab the complete server response?
It shows the first 50 KB, which covers most pages, and a note appears with the full size when a page runs longer. The stats above always reflect the entire response, not the truncated view.
What's a healthy KB HTML figure in the search engine spider simulator?
There's no single threshold, but lean pages tend to sit under a few hundred KB of markup. If you're shipping multiple megabytes of HTML, crawl efficiency and parse time both suffer. Weigh the size against how many indexable words you got for it.
Which problems does fetching a page as a crawler catch fastest?
Empty client-rendered shells, copy hidden behind JavaScript, boilerplate outweighing real text, and bloated markup. It's also a quick way to confirm cloaking isn't happening, since you're looking at the same response a bot receives.