Answer
Requests triggered to retrieve a page for a live user workflow.
Track AI bot requests server-side, discover the pages they inspect, and separate verified crawlers from unverified traffic.
Talivia classifies recognized requests by their documented purpose instead of putting every automated visitor into one noisy total.
Requests triggered to retrieve a page for a live user workflow.
Crawlers that discover pages for search and retrieval systems.
Automated crawling described for model development or improvement.
Advertising, product, or documented traffic outside the other groups.
See which paths are requested most, whether they return useful responses, and which crawlers are behind missing pages or unexpected traffic.
Turn on the separate crawler data set in website settings.
Keep the key in a server-side environment variable.
Review activity by crawler, page, status, and time.
Use the reviewed directory to compare crawler purpose, recognition tokens, official guidance, and available verification sources.
A crawl request does not prove that an AI answer cited or recommended your page. Talivia reports the server event and available verification evidence without inventing attribution.
The server integration sends a minimal request event. Talivia classifies it again with the canonical User-Agent registry and raises verification confidence when a trusted source IP matches provider-published ranges.
No. Crawler requests live in a separate data set and never increase visitors, sessions, conversions, or revenue totals.
No. The integration sends the path, method, User-Agent, optional status, and optional trusted source IP. It does not send page bodies, cookies, query strings, or authorization headers.
No. A crawl only shows that a matching client requested the URL. It does not prove indexing, citation, recommendation, or model use.
Add your website, install the server package, and keep bots separate from human analytics.
Add your website