Free Bot View Checker
One of the free tools from KinetixSEO, an SEO and AI-citation (GEO) checker. Pick a crawler and see the response it actually receives — status, redirects, the tags it can read, whether robots.txt lets it in at all, and how much of your page exists only after JavaScript runs.
What the Free Bot View Checker checks
- The HTTP status, redirect and content type that specific crawler is served, fetched under its own published User-Agent
- Whether robots.txt permits that crawler to request the URL at all, and which rule blocks it if not
- The title, meta description, canonical, robots meta tag and H1 the crawler reads out of the response it gets
- Word count and internal link count in the response as that crawler receives it
- For a crawler that does not execute JavaScript, how many words on the page exist only after rendering — content it will never see
- Whether the site serves that crawler a different status, title or amount of content than it serves an ordinary client (a cloaking signal, reported as an observation rather than an accusation)
Frequently asked questions
What does this tool actually do?
It requests your page wearing a specific crawler’s published User-Agent string, then shows you the exact response that crawler receives — the HTTP status, any redirect, and the title, meta description, canonical, robots meta tag and H1 it can read out of that response.
Why does it matter which crawler I pick?
Because they behave differently. Googlebot and bingbot execute JavaScript before reading a page; OAI-SearchBot, PerplexityBot and Claude-SearchBot do not, so they only ever see the HTML your server sends. A page whose content is injected by JavaScript can rank in Google and be completely invisible to ChatGPT, Perplexity and Claude.
Does this prove my site is cloaking?
No, and it is deliberately not phrased that way. The tool reports whether the site served that crawler a different status, title or amount of content than it served an ordinary client. That difference is sometimes deliberate cloaking (a Google spam-policy violation), but it is far more often produced innocently by bot-protection services, geo routing or an A/B test. The tool states what differed; the judgement is yours.
Are you actually pretending to be Googlebot?
The request carries that crawler’s published User-Agent string, from our own IP address. It does not claim to come from Google’s network, and any site verifying crawlers properly (by reverse DNS, which is what Google and OpenAI both document) will correctly see it as not being the real bot. That is the honest way to run this check.
Why does it take a few seconds?
It makes three requests — the page as the crawler, the page as an ordinary client, and robots.txt — and loads the page once in a real browser to measure how much content only exists after JavaScript runs. That last step is what lets it tell you what a non-rendering crawler misses.
Related reading
Go deeper
This free check looks at one signal in isolation. KinetixSEO's paid report combines every signal below into one prioritised fix list and tracks it over time.
See the full paid report for this →