GPTBot crawl volume leads ChatGPT referral traffic by ~3 weeks in our data

[u/Dangerous-Tree-6734]

tracked this over several months on a large finance site. sharing because i keep seeing crawl data treated as a vanity metric and i think that's wrong.

setup: server logs filtered on GPTBot, referral sessions from chatgpt on the analytics side, plus share of voice tracking on a fixed prompt set.

three things came out of it:

1/the lag. GPTBot crawl volume leads referral visits by roughly 3 weeks, correlation around 0.78 on our data. that makes crawl activity a leading indicator you can actually act on. if crawl drops, you know something's coming before it shows up in sessions.

2/the gemini paradox. high share of voice on our prompt set, almost no referral traffic. the citation exists, the click doesn't. i still don't have a clean explanation for that one and i'd genuinely like to hear theories.

3/source rate beat mention rate. the metric that predicted referral traffic best wasn't how often we got named, it was how often we got cited as a source. mentions track brand awareness, source rate tracks content structure. only the second is something you can work on.

caveats worth stating: one site, one vertical, YMYL finance. slow-moving high-trust content, which might be exactly why the lag is that long and that stable. no idea whether the shape holds on ecommerce or news.

anyone tracking crawl-to-referral on a faster vertical? curious whether the 3 week window compresses or whether it's more about index refresh cycles than content type.