AI Traffic Dashboard Insights

AI Traffic now separates AI and non-AI tracked visits, highlights top AI landing pages, groups traffic by crawled page type, and surfaces anomalies.

A Clearer AI Traffic Dashboard

AI Traffic Analytics now makes it easier to understand which tracked visits came from AI systems, which pages are earning that traffic, and what changed compared with the previous period.

What's New

AI Share And Non-AI Tracked Visits

The dashboard now separates tracked traffic into:

  • AI traffic: AI bot crawls plus AI platform referrals
  • Bot crawls: visits from known AI crawlers
  • AI referrals: visitors referred from AI assistants and answer engines
  • Non-AI tracked visits: snippet-tracked visits that did not match AI bot or AI referral patterns

The overview also shows AI share of tracked visits, so you can see how much of your measured traffic stream is AI-driven.

Period-Over-Period Movement

Cards and charts now include period-over-period context. Use this to spot whether AI traffic, referrals, bot crawls, and non-AI tracked visits are growing or shrinking against the prior comparable period.

True Top AI Landing Pages

The Top Pages table is now ranked by AI traffic, not generic tracked traffic. This helps you find the docs, guides, comparison pages, and other assets that AI systems crawl or send visitors to most often.

Page Groups From Crawl Classification

Page groups use DevTune's crawl classification, such as docs, guides, blog, pricing, changelog, and other page types. This shows which content categories are carrying AI traffic rather than forcing every page to be inspected one by one.

Traffic Facts And Anomaly Alerts

The dashboard now reuses Command Center traffic facts to explain notable movement, and it surfaces conservative anomaly alerts when AI traffic, bot crawls, or AI referrals spike or drop against the previous period.

Performance Notes

The updated dashboard reads from hourly traffic rollups and bounded page summaries. It avoids raw event scans on the main dashboard path, so the additional views should stay lightweight as traffic volume grows.