Chetver shows which bots from ChatGPT, Claude, Gemini, Perplexity and other AI visit your site, why they come, what they read — and where they hit a block or an error.
The check needs no account and no card. Bot requests start once you connect your site, from $29 a month.
Example data: kvitkova-lavka.example, a fictional shop on the Max plan, 30 days. A bot request is not a human visit and not a recommendation in an AI answer.
See how many requests each company made, how that changed over the month, and when it last came by. New bots are flagged, and any major AI that hasn’t visited sits at the bottom of the list.
Example · kvitkova-lavka.example · 30 days
Some bots train AI on your site’s text, others build an index for AI search. And during a live request, an assistant opens pages in the middle of a conversation with someone — you see exactly which ones.
Example · kvitkova-lavka.example · 30 days
Every day we check robots.txt — the file of rules for bots. If it shuts out the bots of ChatGPT, Claude or Perplexity, a marker on the chart shows the day requests dropped, and “To improve” tells you exactly what to fix.
Example · “Access blocked” scenario · 30 days · chart from Pro
If a page gives bots “not found” or a server error, “Pages” (from Pro) shows which page, how many times and since when. Errors are visible through the WordPress plugin, the PHP connector and AI Page — the pixel can’t see them.
“To improve” flags a robots.txt block and pages that won’t open: a daily homepage check and a weekly site check find them. You can also turn on emails about new to-dos from the check — at most once a day.
If a page gives bots a server error or several “not found” responses, an “Urgent” decision shows up in the morning: what happened, since when, and where to fix it.
Example · kvitkova-lavka.example · September 29
Once the problem is gone, the decision closes on its own. Not urgent? Snooze it for a week or dismiss it as “not a problem”.
Every Monday: up to three open decisions, urgent ones first.
The Chetver Connect plugin installs without a developer: download it from your dashboard, install it in WordPress and paste in the connection code. Not on WordPress? Use the PHP connector (set up by a developer) or the pixel.
Example · first connection in the dashboard
Sees: Sees every bot request that reaches WordPress or PHP, and whether the page opened.
Doesn’t see: Doesn’t see requests that never reach WordPress or PHP: ones answered by a cache, a CDN, site protection or the web server itself.
The plugin needs WordPress 6.5+ on PHP 8.1+ (not multisite); the connector works on sites running PHP 8.1+.
Sees: Sees bots that load images — on any site where you can add code.
Doesn’t see: Doesn’t see bots that don’t load images, or page errors.
Sees: A page about your business for AI, on an aipage subdomain — we see every AI bot request to it.
The plugin and connector send only the page address, bot name, time and response code — no IP addresses, cookies, URL parameters or form data — and they don’t slow your site down. The pixel fires on every page load, so it records human visits too — see the questions below for what exactly.
We collect the data on every plan. The difference is how much of it you see, and whether we prepare “Decisions” every morning.
For AI bot requests
Three tiles: how many requests, which bot types and how many errors.
Everything in Basic, plus — for AI bot requests
Everything about bot requests shown above on this page, except “Decisions”.
Everything in Pro, plus — for AI bot requests
Tips on what broke and where to fix it — every morning and in the weekly email.
This is the “AI bot visits” block on the “AI bot requests” page — on every plan
Didn’t find your answer? Write to support@chetver.com.
A site and any plan. If your site runs on WordPress, download the Chetver Connect plugin from your dashboard, install it, create a code in the dashboard and paste it into the plugin settings — about 2 minutes. For any other site, use the PHP connector (set up by a developer) or the pixel. And an AI Page on a subdomain counts requests by itself as soon as you publish it and add one DNS record for the subdomain.
No. The plugin and PHP connector send nothing while your site is responding to a visitor: they just queue the event and send it in a batch later. The pixel is a transparent 1×1 image.
The plugin and PHP connector send only AI bot requests — what exactly is described above, in “Connected in 2 minutes”. The pixel and AI Page record every request, human visits included: the browser or bot signature (User-Agent), the address the request came from (referrer), the page, the country and city, and the IP address only as a hash.
Requests show up as soon as bots visit: in the example there were 711 in the first 4 days. The site check (up to 30 pages weekly) and the daily homepage check work from day one. On Max, the first “Decisions” arrive after a week, and the comparison with last month once two months of data are in.
First open “Connections”: it shows when each source last sent data. If everything works, check robots.txt — it may have shut out AI bots (Chetver checks it daily). Bots may also take a while to find a new site.
By the signature the bot identifies itself with (User-Agent). It can be faked, so we never call bots “verified”. Bots we don’t recognize aren’t in the reports.
No. A request is a bot automatically fetching a page. It doesn’t count people and doesn’t prove an AI recommended you. Even a live request only means an assistant opened the page during someone’s conversation. What AI says about you is shown in “AI answers” on the Max plan. And we can’t make bots visit more often: each company decides for itself what to read and when.
Choose a plan — we’ll start collecting requests as soon as you connect your site. 30-day money-back guarantee.