AI traffic tracking
Connect your website to record detected AI crawler requests and referrals from AI assistants. Configure the connection in Project Settings -> Tracking setup, then read its evidence in Sources -> AI traffic.
Tracking starts after installation. It does not backfill earlier visits or prove that an AI model indexed, trained on, or cited a page.
Choose a collection method
| Your site | Setup | Coverage to expect |
|---|---|---|
| WordPress | Cleotic AI Traffic plugin | Requests that reach WordPress, with optional browser referral capture |
| Vercel | Production Log Drain | Eligible page requests included in the delivered logs |
| Bunny CDN | Pull-zone log forwarding | Eligible page requests served through the configured pull zone |
| Other platforms | HTML snippet | Referrals and identified AI browsers that execute JavaScript |
Browser tracking cannot see crawlers that only fetch HTML. Server-side coverage depends on which requests reach the provider and are forwarded to Cleotic.
Connect a site
- Open Project Settings -> Tracking setup and click Connect a site.
- Choose WordPress, Vercel, Bunny CDN, or HTML snippet / Other.
- Enter the owned domain and an optional name, then click Create and continue.
- Follow the Connect instructions for the platform.
- Copy and install any credential before leaving the panel, then click Finish setup.
The site is saved when you continue from Site details. Use Finish later if installation is unfinished, then Continue setup to return.
Create a separate tracking site for each distinct subdomain, such as example.com and blog.example.com. Cleotic normalises a leading www. when matching domains.
Install the HTML snippet
Choose HTML snippet / Other, then copy the generated HTML from Connect. Add it before the closing </body> tag on the pages you want to track, deploy the change, and confirm installation in the panel.
Visit a deployed page in a browser. A same-domain beacon can verify the connection even if that visit is ordinary traffic. AI traffic rows appear only when there is matching AI evidence.
If verification does not appear, check that the snippet is on the deployed page and that browser or site policies have not blocked its request.
Provider guides
Understand connection status
| Status | What it means | Next step |
|---|---|---|
| Needs setup | The record exists, but setup is incomplete | Continue setup |
| Waiting for signal | Configuration is saved; verification is pending | Check the provider connection and send a matching request |
| Connected | Cleotic has received a matching connection signal | Review AI traffic for the selected date range |
Connected does not mean every visitor is tracked or that an AI crawler has visited. Review actual event evidence separately.
Manage a connection
Use Review setup or Manage connection to copy installation details or rotate a credential. WordPress keys and Bunny tokens are shown once. If one is lost, rotate it and update the provider configuration.
Changing a configured platform clears incompatible credentials and restarts verification. Existing analytics remain available.
Pausing a site keeps its configuration but stops recording incoming tracking data. Resuming does not recover visits dropped while paused. Delete a site only when you intend to remove it and its data.
Only active sites count towards capacity. See Plans and usage.
AI share and coverage
AI share needs a total-pageview denominator as well as AI events. The browser snippet records AI evidence, not a complete count of all pageviews. WordPress's AI events only mode also lacks that denominator.
If AI share is incomplete or unavailable, use crawler and referral counts within their collection limits. Do not interpret missing total-pageview data as 0% AI traffic.