Allow GPTBot and PerplexityBot in robots.txt
12 money-page URLs are invisible to the engines that read them
Product · Measure
Agent Analytics reads your server logs and shows which AI bots crawl your pages, which pages they never reach, and how long it takes a new page to go from published to cited.
The numbers
Every module below answers part of it: who crawls you, what they get, which pages they miss, and how fast a new page earns a citation.
Total AI bot fetches of your site in the last 30 days.
Across 8 crawlersFetches by bots that read a page while answering. The signal before a citation.
56% of all AI crawlsPages an AI crawler actually fetched, out of 142 indexed.
56 pages never crawledMedian days from publishing a page to the first AI bot fetch.
8 days to first citationLive demo data: Ledgerly, an expense management brand, June 10 to 16, from raw server logs.
Crawler traffic · Module 01
Answer crawlers fetch a page while an assistant is writing an answer, so they arrive right before a citation. Training crawlers harvest for the next model. Agent Analytics separates the two, so you know which traffic actually matters today.
Daily AI bot fetches. Answer crawlers solid, training crawlers muted.
OAI-SearchBot, PerplexityBot, Claude-User, ChatGPT-User, Googlebot. A spike here usually precedes a citation.
GPTBot, Google-Extended, ClaudeBot. They shape the next model, not today's answers.
Filter the whole product by crawler type. Most AI analytics tools report one blended bot-traffic number, which hides the only half that moves a citation.
The crawlers · Module 02
Eight AI crawlers, each mapped to the assistant it serves, with volume, share, last-seen time and whether your robots.txt lets it in.
Every AI bot seen in your logs, and the assistant it feeds.
New crawlers appear as vendors ship them. When one is blocked, Agent Analytics tells you which pages it could not read.
Citation pipeline · Module 03
Every page moves through four stages: published, discovered by any bot, fetched by an answer crawler, then cited. The funnel shows how many pages make it and exactly where the rest drop out.
Where 218 published pages sit today.
Month-end close guide/guides/month-end-close
Click any stage in the app to filter straight to the pages stuck there.
Page coverage · Module 04
A page AI cannot fetch cannot be cited. Coverage lists every URL with the bots that fetched it, the status code they got, and whether your last edit has been re-crawled yet.
Every URL, the bots that fetched it, and what to do next.
Silent failures · Module 05
A blocked bot, a 404 or an unrecrawled edit costs you citations quietly. Nothing breaks, no alert fires, you just stop appearing. Agent Analytics surfaces each one with the fix.
12 money-page URLs are blocked in robots.txt. The engines that answer pricing questions cannot read them.
Review the diff →One guide returns 404 to bots while rendering fine for people. A redirect fixes it.
Inspect →You rewrote the page 3 days ago. The last bot fetch predates it, so AI still quotes the old copy.
Request re-crawl →A new comparison page has been live 2 days with no answer crawler on it. Its citation cannot land yet.
Ping crawlers →Every issue here routes to Action Center as a fix the agent can ship, with a rollback point saved.
From signal to fix
Agent Analytics finds them, Action Center ships them. Technical crawler work is the safest thing to automate, so the agent handles it and saves a rollback point.
12 money-page URLs are invisible to the engines that read them
Gives answer engines a canonical map of your best pages
One guide is unreadable to bots while fine for people
“We found ClaudeBot had been 403'd on our blog for four months. Nobody knew, nothing alerted, we were just missing from Claude. One rule change and the citations came back in nine days.”
Questions
Prefer's AI crawler analytics. It reads your server log files and shows which AI bots crawl your site, which pages they miss, what status codes they get, and how long a new page takes to earn a citation.
GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Googlebot and Google-Extended today. New crawlers are added as vendors ship them.
Answer crawlers like OAI-SearchBot and PerplexityBot fetch a page while an assistant writes an answer, so they arrive just before a citation. Training crawlers like GPTBot harvest pages for future models. Only answer traffic moves today's answers.
Not the answer crawlers. Blocking them removes you from AI answers entirely. Training crawlers are a separate choice, and Agent Analytics lets you see the traffic from each before you decide.
Publish it in your sitemap, link to it internally, list it in llms.txt, and make sure robots.txt allows the answer crawlers. Agent Analytics shows the median time to first crawl so you can tell whether a page is late.
No. Agent Analytics is log file analysis, so it reads server or CDN logs directly. That means it sees bot traffic that never runs JavaScript, which is most AI crawler traffic.
Search Console reports Googlebot and Google's index. Agent Analytics reports every AI crawler, including GPTBot, PerplexityBot and ClaudeBot, and ties each fetch to whether the page went on to be cited in an AI answer.
See how answer engines describe your brand today, and where the openings are to outpace the competition.