Title: Foundash AI Access Check Author: boiledpotat0 Published: August 29, 2026 Last modified: August 29, 2026 --- Search plugins ![](https://ps.w.org/foundash-ai-access-check/assets/banner-772x250.png?rev=3671068) ![](https://ps.w.org/foundash-ai-access-check/assets/icon-256x256.png?rev=3671068) # Foundash AI Access Check By [boiledpotat0](https://profiles.wordpress.org/boiledpotat0/) [Download](https://downloads.wordpress.org/plugin/foundash-ai-access-check.1.0.1.zip) * [Details](https://wordpress.org/plugins/foundash-ai-access-check/#description) * [Reviews](https://wordpress.org/plugins/foundash-ai-access-check/#reviews) * [Installation](https://wordpress.org/plugins/foundash-ai-access-check/#installation) * [Development](https://wordpress.org/plugins/foundash-ai-access-check/#developers) [Support](https://wordpress.org/support/plugin/foundash-ai-access-check/) ## Description People increasingly ask an AI assistant to recommend a business instead of searching for one. Before an assistant can recommend you, it has to read your website. Your AI visibility starts here. If ChatGPT, Claude, Perplexity or Google’s AI cannot reach your pages, nothing else you do for AI search matters, because there is nothing for them to read. Plenty of sites block those assistants without the owner ever knowing. Security plugins, host defaults and robots.txt rules can all turn AI crawlers away while ordinary visitors see nothing wrong. If that is happening to you, no amount of good content will help, because nothing is being read. This plugin checks, from your own dashboard: * Whether the agents that fetch your page **when a customer asks** (OAI-SearchBot, ChatGPT-User, Perplexity-User, Claude-SearchBot) are being served or refused * Separately, whether the crawlers that **collect pages to train on** (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are being served or refused * Whether your **robots.txt** tells any of them to stay out * Whether WordPress’s own **“Discourage search engines”** setting is on * Whether your front page carries a **noindex** tag telling engines not to list it * Whether your front page has **structured data** for an assistant to lift facts from * Whether you have an **llms.txt** file It then gives you one plain sentence saying where you stand. #### Honest about what it finds A refused crawler is not always a deliberate block, so this plugin does not shout about one. It also requests your site as Googlebot as a control. If Google is being refused too, you have a broken bot rule rather than an AI policy, and the plugin says exactly that, because that problem is bigger and costs you traffic today. It only counts 401, 403 and 429 as a deliberate refusal. A 400 is a malformed request and a 500 is your server erroring, and calling either a block would be misleading. The robots.txt reader follows the real rules rather than guessing. A commented-out line is not a block. A rule written for your site as a whole does not apply to a crawler that has its own rules further down. An Allow that cancels a Disallow is respected. Each of those, done carelessly, invents a block that is not there. Every result shows the raw HTTP code and the exact robots.txt line behind it, so you can verify any claim it makes rather than taking it on trust. #### Two different crawlers, two different consequences Most tools in this space report one number for “AI crawlers” and leave you to assume the worst. There are really two kinds, and only one of them decides whether you can be recommended. Some agents fetch your page at the moment a person asks an assistant about your business. If those are refused, the assistant has nothing to read and cannot describe or recommend you. That is worth fixing. Others collect pages in bulk to train models on. Refusing those is a deliberate choice a lot of sites now make, and on its own it does not stop anyone recommending you. This matters more than it sounds. Across 293 local business websites checked in August 2026, 15 refused an AI crawler in robots.txt, and 14 of those 15 refused only the training crawlers while deliberately allowing the search-time agents by name. Reporting those 14 as “blocked from AI” would tell a business it is invisible when it is not. So this plugin tells you which kind you are refusing, and only raises an alarm for the kind that costs you something. #### Why there is no score Other plugins in this space hand you a number out of 100 and a letter grade. This one does not, on purpose. Every question it asks has a real answer. A crawler was served or it was refused. A robots.txt rule exists or it does not. Averaging answers like those into a grade throws away the part you can actually act on, and it makes a short list of plain facts look like a measurement it is not. You get the facts instead: which crawlers were served, which were refused, the HTTP code each one returned, and the exact robots.txt line behind any claim. Every one of them is something you can check yourself. #### What it cannot tell you **Requests come from your own server.** If your site sits behind a CDN or firewall and your server bypasses it when calling its own address, a block at that edge will not appear here. Checking from outside your hosting is the only way to be sure. **A slow site gets a partial answer.** The whole run is held to a wall clock budget so it cannot outlast PHP’s execution limit and leave you with a blank admin page. If your site is slow to answer requests from itself, the run stops early, the rows it never reached say “Could not test” instead of guessing, and it tells you it stopped. **Google-Extended is reported from robots.txt only.** There is no such crawler to refuse. Google reads your pages as Googlebot and then consults the Google-Extended rule to decide whether that content may feed Gemini and AI Overviews. Any tool that reports an HTTP status for Google-Extended is reporting a request it invented. #### Privacy The plugin only requests your own site. It sends nothing to any third party, requires no account, no API key and no signup, and stores nothing beyond a one hour cache of your last result. ## Screenshots [⌊A site refusing every AI crawler while still serving Googlebot. Because Google is being served, this is an AI-specific rule rather than a broken bot setting, and the plugin says which.⌉⌊A site refusing every AI crawler while still serving Googlebot. Because Google is being served, this is an AI-specific rule rather than a broken bot setting, and the plugin says which.⌉[ A site refusing every AI crawler while still serving Googlebot. Because Google is being served, this is an AI-specific rule rather than a broken bot setting, and the plugin says which. [⌊A site all four assistants can read, with structured data for them to lift facts from. Every row carries the HTTP code behind it, so any claim can be checked.⌉⌊A site all four assistants can read, with structured data for them to lift facts from. Every row carries the HTTP code behind it, so any claim can be checked.⌉[ A site all four assistants can read, with structured data for them to lift facts from. Every row carries the HTTP code behind it, so any claim can be checked. [⌊WordPress's "Discourage search engines" setting does not put anything in robots. txt. Since WordPress 5.3 it adds a noindex tag instead, so a tool that only reads robots.txt cannot see it at all.⌉⌊WordPress's "Discourage search engines" setting does not put anything in robots.txt. Since WordPress 5.3 it adds a noindex tag instead, so a tool that only reads robots.txt cannot see it at all.⌉[ WordPress’s “Discourage search engines” setting does not put anything in robots. txt. Since WordPress 5.3 it adds a noindex tag instead, so a tool that only reads robots.txt cannot see it at all. ## Installation 1. Upload the plugin folder to `/wp-content/plugins/`, or install it through the Plugins screen. 2. Activate it. 3. Go to **Tools > AI Access**. ## FAQ ### Does this send my data anywhere? No. It makes requests to your own website and nothing else. There is no account, no API key and no tracking. ### It says AI crawlers are blocked. How do I fix it? First check which kind. If the plugin says you are refusing only the training crawlers, nothing is broken and there may be nothing to fix; that is a choice, and it does not stop an assistant recommending you. Only a refused search-time agent actually costs you anything. If a search-time agent is being refused, it depends where the block is, and the plugin tells you which. If it is WordPress’s own setting, go to Settings > Reading and untick “Discourage search engines from indexing this site”. Worth knowing, because most write-ups still get this wrong: since WordPress 5.3 that switch no longer writes Disallow: / into robots.txt. It adds a noindex tag to your pages instead, so crawlers read them and are then told not to list them. A tool that only reads robots.txt cannot see it at all. This plugin checks the setting, the tag and robots.txt separately, and tells you which one is responsible. If robots.txt is the problem, edit the file or the plugin generating it. If your server is returning 403, the cause is usually a security plugin, a firewall rule, or your host’s bot protection. Cloudflare in particular has a setting that blocks AI crawlers, and it is on by default for some accounts. ### Will this get my business recommended by ChatGPT? No, and be wary of anything claiming it will. Whether an assistant names you depends on reviews, directories, your reputation across the web and how each engine weighs its sources. None of that is under any plugin’s control. What this tells you is whether you are in the running at all. A site that cannot be read cannot be recommended, so this is the floor, not the ceiling. ### Why does it check Googlebot? As a control. If your site refuses AI crawlers but serves Googlebot, that points at an AI-specific rule. If it refuses both, you have a general bot problem that is hurting your Google ranking as well, which is more urgent. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Foundash AI Access Check” is open source software. The following people have contributed to this plugin. Contributors * [ boiledpotat0 ](https://profiles.wordpress.org/boiledpotat0/) [Translate “Foundash AI Access Check” into your language.](https://translate.wordpress.org/projects/wp-plugins/foundash-ai-access-check) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/foundash-ai-access-check/), check out the [SVN repository](https://plugins.svn.wordpress.org/foundash-ai-access-check/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/foundash-ai-access-check/) by [RSS](https://plugins.trac.wordpress.org/log/foundash-ai-access-check/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.1 * Separates the agents that read your page when a customer asks from the crawlers that collect pages to train on, and only raises an alarm for the first kind. Adds ChatGPT-User as a request and Perplexity-User and Claude-SearchBot as robots. txt checks. Version 1.0.0 reported a training opt-out as “ChatGPT: blocked”, which reads as “you are invisible” when the site is still perfectly readable at the moment a customer asks about it. That was measured, not guessed: of 293 local business sites, 14 of the 15 refusing an AI crawler in robots.txt refused only the training crawlers and allowed the search-time agents by name. #### 1.0.0 * First release. Crawler access checks for ChatGPT, ChatGPT Search, Claude and Perplexity using each one’s real user agent, robots.txt parsing with correct group precedence, detection of WordPress’s “Discourage search engines” setting, structured data detection, llms.txt detection, and a Googlebot control. robots. txt and llms.txt are read at the domain root, so a WordPress install in a subdirectory is checked against the file crawlers actually read. Structured data is read by decoding the JSON-LD rather than pattern matching it, so a type written as a list is counted. Runs are held to a wall clock budget and report themselves as incomplete rather than timing out. Detects a noindex tag on the front page, which is what WordPress’s “Discourage search engines” setting has actually set since WordPress 5.3, and what an SEO plugin may set on its own. ## Meta * Version **1.0.1** * Last updated **1 day ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Tags * [AI](https://wordpress.org/plugins/tags/ai/)[ChatGPT](https://wordpress.org/plugins/tags/chatgpt/) [crawler](https://wordpress.org/plugins/tags/crawler/)[schema](https://wordpress.org/plugins/tags/schema/) [seo](https://wordpress.org/plugins/tags/seo/) * [Advanced View](https://wordpress.org/plugins/foundash-ai-access-check/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/foundash-ai-access-check/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/foundash-ai-access-check/reviews/) ## Contributors * [ boiledpotat0 ](https://profiles.wordpress.org/boiledpotat0/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/foundash-ai-access-check/)