The question it answers
Do visitors from ChatGPT, Perplexity and Google read past the first page, and where does a visit end?
What it is
Server-side sessionized journeys: where each visit entered from (ChatGPT, Perplexity, Google, direct, social…), the page they landed on, how many pages they walked, and the full ordered path. Click any journey to replay the exact route.
Navigation journeys showing entry sources and the ordered path visitors walked (example data)
Entry → path → exit
The full ordered route each visit took, replayable click-by-click.
AI-source attribution
See which AI engines send visitors who actually go deeper.
Where journeys stall
Find the page that ends the session and fix it.
A concrete example
In the example project, the journeys list shows 40 journeys in the period, and the Traffic tab sums them up as 2.1 pages per journey with 45% single-page visits. One visit from chatgpt.com landed on /blog/launch-week and walked 6 pages, while visits from github.com that landed on /pricing left after 1. Click a journey to see its full path. The figures are example data.
Why it matters
A pageview count tells you someone arrived. A journey tells you whether it mattered. See which AI engines send visitors who read three more pages instead of bouncing, which landing pages pull people deeper, and exactly where the path breaks down, so you know which sources are worth chasing.
More of the platform
CiteMET Score →
A live A+ to F grade for how readable your site is to search and AI crawlers, with a list of what to fix.
AI-Crawler (AEO) Analytics →
See which AI crawlers fetched which pages, next to human and search traffic.
GitHub → Edge Hosting →
We connect your repo and you publish when you're ready. Each deploy builds from your repo and appears in the deployment history, with Redeploy Now.