# AI Crawlers

> Cloudflare-backed bot analytics at /analytics/crawlers-which LLM crawlers hit your site, top paths, and why it matters for GEO.

Canonical URL: https://app.igeo.ai/docs/ai-crawlers-analytics

## Overview

AI Crawlers (/analytics/crawlers) shows how automated bots tied to AI companies request your pages — distinct from human visitors in AI Traffic (site tracker on /analytics).

Availability can depend on your subscription (for example starter plans may not include this screen).

- Crawler view — which bots hit your site, how activity trends over time, and which URLs they fetch most often.
- AI Traffic — real people arriving on your site (referrers, pages, geo, devices) after AI-led discovery.
- Together — compare what models pull from your domain with what real users actually visit.

## Cloudflare and this screen

Crawler charts and breakdowns are powered by data from Cloudflare for the zone you connect to igeo.ai. At the edge, Cloudflare sees requests from named bots (for example GPTBot, ClaudeBot, PerplexityBot) — igeo.ai maps those signals to LLM providers and surfaces volume over time, top paths, and top crawlers.

## Where to connect

Open AI Traffic (/analytics) and use the Cloudflare integration tab to link your account and choose the site (zone) you want analyzed. Until Cloudflare is connected and data is flowing, crawler analytics may be empty or minimal — the product may note when collection starts after the next scan cycle.

This is separate from the site tracker script on AI Traffic → Settings; that script targets human page views. Crawler analytics here come from edge visibility into bot traffic.

## What you're seeing

LLM operators send crawlers to fetch and refresh content that can flow into answers and citations. In the product you typically get:

Use the crawler filter in the toolbar to narrow to specific bots when you want a focused slice.

- Provider-oriented cards — bot volume grouped toward familiar LLM brands (plus a total).
- Trends over time — how crawler requests move across your selected date range.
- Top paths — URLs on your site that receive the most crawler requests.
- Top crawlers — which bot identities drive the most traffic.

## Why it matters

If models use what they can retrieve from your site, pages crawlers hit most often are strong signals for where to invest — content quality, structure, freshness, and technical basics (not blocking crawlers you care about).

- Prioritize URLs — top-path lists highlight where bots concentrate; align those pages with your GEO and editorial priorities.
- Understand bot mix — see which assistants or ecosystems pull from your domain most aggressively.
- Contrast with AI Traffic — crawler demand vs human visits tells you whether edge interest converts into real sessions.

## Filters

- Shared with AI Traffic — date range and (where applicable) provider and country controls match what you use on /analytics.
- Crawler filter — on this route, narrow to specific AI crawler identities when you need a targeted view.

## Related documentation

Use bookmarks to separate monitoring (prompts and answers), human site traffic, and edge crawler analytics.

AI Traffic

Human visits from AI-related discovery: tracker snippet, dashboards at /analytics — not crawler requests at the edge.

Sidebar navigation

Where AI Traffic, AI Crawlers, and the rest of the app live in the sidebar.

AI Crawlers

Open the product view this page describes.