Measurement, control 11 of 17
M-11 Measure human AI referrals separately from bot traffic
User visits, crawler requests and server-side agent fetches are different events. Referrer data can be incomplete and does not reveal all AI influence.
- Priority
- Optimisation.
- Hard gate
- No
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Business usefulness and conversion readiness
Why it matters
Crawler visits and real people arriving from ChatGPT are different things, and mixing them inflates the numbers and hides what users actually do. Without a separate channel, you cannot see which landing pages receive these visitors or whether they turn into leads and revenue. Keeping them apart lets you judge the value of ChatGPT as a source of customers.
Evidence to review
- Analytics configuration, representative requests and reconciled conversion events.
How to implement
- Maintain a reviewed source/medium classification.
- Filter known bots without assuming every AI-associated visit is automated.
- Track useful landing-page outcomes and lead quality.
- Do not promise a particular UTM parameter or classify all direct traffic as AI-driven.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
Evidence needed: analytics segmentation for ChatGPT referral traffic and its conversion.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.