Technical SEO
Improving Crawl Efficiency for Large Websites
GPTBot, PerplexityBot, and ClaudeBot don't crawl anything like Googlebot. Server logs from six sites show just how differently.
Key takeaways
- AI crawlers requested far fewer pages per visit than Googlebot across every site in the sample.
- Most AI crawlers appeared to skip content that depended on client-side JavaScript rendering.
- Crawl frequency for AI bots did not correlate cleanly with how often Googlebot visited the same pages.
The question
Most technical SEO crawl-budget advice is written entirely around Googlebot. I wanted to know whether that advice transfers to AI crawlers, or whether they need their own playbook.
How I tested it
I pulled 30 days of raw server logs from six mid-size sites across different industries and isolated requests from GPTBot, PerplexityBot, ClaudeBot, and Googlebot for comparison. I cross-referenced crawled URLs against each site's sitemap and checked which pages relied on client-side rendering for their main content.
What I found
Across all six sites, AI crawlers requested a small fraction of the pages Googlebot requested in the same window, often under 10 percent. They also showed a strong pattern of avoiding pages where the main content only appeared after JavaScript execution, consistent with limited or no JS rendering on their end.
Crawl frequency for AI bots did not track Googlebot's crawl frequency closely. Some pages Googlebot visited daily saw an AI crawler only once in the entire 30-day window, with no obvious pattern explaining which pages got skipped.
What this means in practice
If a page matters for AI citation, server-side rendering (or at minimum ensuring critical content is present in the initial HTML) is worth prioritizing over crawl-budget tricks that were designed for Googlebot specifically. Getting crawled is only step one — for how I track whether that content actually converts into citations over time, see the citation-rate tracking methodology.
Where this could be wrong
Six sites is a reasonable sample for a first pass, not a definitive one, and crawler behavior for these bots is not publicly documented in detail, so some of this is inference from request patterns rather than confirmed capability.
References
- Server log analysis, 6 sites, 30-day window. Raw log data, April to May 2026.
Frequently asked questions
Should I block AI crawlers to save server resources?+
Only if you don't want to be cited by that engine. AI crawler request volume was low enough in this sample that server load was rarely the actual constraint.
Does this apply to Googlebot too?+
No, Googlebot behaved as expected in this sample and generally does execute JavaScript, though not always immediately. This finding is specific to the AI crawlers tested.
Get notes like this before they're published.
SubscribeMore from Research
Building a Repeatable Way to Measure AI Citation Rate
Most citation rate numbers people quote are one-off screenshots. This is the tracking methodology I built so the number means something over time.
Jul 2026
Why AI Search Doesn't Always Follow Google Rankings
I assumed the page ranking first would get cited first inside AI Overviews. After pulling 400 queries, that assumption barely held up.
Jul 2026