Back to Lastfind

Traffic: which AIs read your site, and what they send back.

The AI crawlers that visit your site, the pages they read, the errors they hit and the visits LLM answers send back (AI Traffic), from your Cloudflare.

Traffic reads your site’s own Cloudflare analytics: no tag, no script and nothing installed on the site. It is available on every Lastfind plan. Your site must be served through Cloudflare (its DNS proxied, the orange cloud). When the zone answers only other hosts of your domain (a landing-page subdomain, say) and not your site, Traffic says so and names them: turn on the proxy for your site’s DNS records, or connect the zone that serves it.

Connect Cloudflare#

  1. In Lastfind, open Settings, then Traffic, and choose Create token in Cloudflare. Cloudflare opens its token form already filled in, read only: Account > Account Analytics > Read; Zone > Analytics > Read; Zone > Zone > Read.
  2. Under Zone Resources, keep all zones or pick your site’s zone. Choose Continue to summary, then Create Token.
  3. Copy the token and paste it in Lastfind: it is checked with Cloudflare at once. Then choose your site’s zone.

The token only reads analytics: it cannot change anything in your Cloudflare account. Lastfind checks it with Cloudflare before saving it, stores it encrypted and never shows it again. Workspace admins replace it or disconnect in Settings, Traffic; disconnecting deletes the token at once and keeps the days already collected. Revoking the token in Cloudflare also stops the collection, and the screen asks to reconnect in Settings.

What the screen shows#

On connecting, Lastfind reads the last 30 days, then one more day every day, so the history grows past the 31 days Cloudflare keeps. The header’s period applies; the AI, topic, tag and brand filters do not. Traffic has three pages in the sidebar: Overview, AI Bots and AI Traffic. Together they show the AI bot visits and their share of all visits, the pages they read, the distinct bots and their companies, the error rate (404, 403 and 5xx), the visits by purpose (training, search, user request) per day or week, every bot with its visits, pages, errors and last visit, the most read pages and whether a monitored answer cited them, and what your site answered the bots.

AI Traffic, on paid Cloudflare plans (Pro and above): the visits that arrive from links in LLM answers (ChatGPT, Perplexity, Claude, Gemini, Copilot and others), the ranking of the LLMs that send them, their days and the pages they land on, and whether a monitored answer cited those pages. The Overview’s Visits by purpose chart switches between bot visits and visits from LLMs. On the Free plan Cloudflare does not report where visits came from, so those parts say so instead of showing zero. Landing pages are read from 13 November 2026 on.

Open a bot, an LLM or a page to see only its figures, or choose a day in a chart to read only that day. The page’s title then names what is open, and the path in the top bar leads back. The bot and LLM filters are in the filter bar, and each view has its own address to share. When the zone reports your site’s pages, the pages read and the most read pages are only those, never robots.txt, scripts or images.

Limits#

Bots are recognized by the name they declare (their user agent), which anyone can fake. The figures are estimates from Cloudflare’s sampled analytics. A day keeps up to 10,000 combinations of bot, page and status for the AI bots, the most visited first, and another 10,000 for the search engines’ crawlers (Googlebot, Bingbot, Applebot), so their volume never hides an AI bot. Today’s figures are partial until the next day’s collection.