AI Crawler Access Check
See whether AI crawlers like GPTBot, ClaudeBot and Gemini can actually reach your website.
GEO starts with crawl access. If AI can't read it, it can't cite it.
The first thing to check is whether AI crawlers can reach your page at all.
AI answer engines like ChatGPT, Perplexity and Google AI Overviews fetch web pages directly and read the content. If they can't get in, citation never even starts. This free tool checks whether AI crawlers can actually read your website.
Why check region by region?
AI crawlers reach websites through servers located in several regions. So even when the question is asked in one country, the actual page request may come from the US, Europe, or elsewhere. Even if your business isn't global, if you care about GEO or AEO you should confirm crawl access from multiple countries, not just one.
Frequently asked questions
How does this check work?
It reads robots.txt to see whether each bot is allowed in, then requests the page the way an AI bot would to see whether it is actually blocked.
What decides "reachable" versus "blocked"?
The HTTP status code. When a request sent with a bot's user agent returns 200 it counts as reachable; anything else, such as 403, 429, or 503, counts as blocked.
Why do some bots come back "undetermined"?
Because robots.txt can't answer for them and they aren't in the measured set. That covers bots that ignore robots.txt entirely, bots that only honor their own token, and bots whose compliance is disputed. Whatever you write in robots.txt won't change their behavior, so rather than guessing "reachable" we leave them undetermined. This applies to link-preview and infrastructure bots.
Why test region by region?
Because WAF and CDN blocking rules are frequently keyed to the region of the requesting IP.
I disallowed a bot in robots.txt but the result says reachable.
robots.txt is a request to stay out, not a lock on the door. Bots that ignore it keep reading anyway. Those are the ones marked "Ignores" in the robots column. To actually stop them you need a rule at the WAF or server level.
Isn't it better to block AI training bots?
That's a policy call, and this tool doesn't judge it. The reason categories are split out is that blocking training bots and blocking answer bots produce completely different outcomes. The first keeps you out of training data; the second costs you the chance to be cited as a source in AI answers. Configurations meant to stop training but that also stop answer bots are genuinely common.
I got "partially blocked". Where do I start?
Look at which categories are affected first. AI answers and search are the high-priority ones. Then look at what did the blocking. If it's robots.txt, edit robots.txt. If it's a WAF geo or bot rule, allowlist that bot's user agent or IP ranges.
Where does the bot list come from?
From a bot catalog weekerp maintains, grouped into AI answers, user fetch, training, search, link previews, ads, tooling, infrastructure, and other. New bots are added as they appear. The full list is public: https://cdn.weekerp.com/weekerp-files/file/config/bot.json (last updated 2026-08-13) The catalog version and the number of bots checked are also shown with your results.
Do you store the URL or the results?
The tool checks the public response for the URL you enter, and it never asks for an email or a login to show you the result.
Connect weekerp and make your site easier for AI to read
From AI bot access to technical SEO and GEO, build an environment where AI reads your site properly.