Dashboards explained

Each site has a set of views. All of them share a date range (with a comparison to the period before) and filters: pick a page, a source, a country or a device anywhere and the whole view follows.

People

Your readers: confirmed pageviews in real browsers, with bots, hosting networks and your own team taken out.

• Pageviews, sessions and pages per session over time.
• Top pages, with time on page and scroll depth, so you can tell pages people read from pages they leave.
• Sources: search engines, social sites, referrals, campaigns and AI assistants, each with the pages they sent readers to.
• Countries, devices and languages.

Crawlers

Every request your server answered that was not a person, from the Worker SDK or proxy mode. The snippet alone cannot see crawlers, so this view is empty until one of those is set up.

• Who: each named crawler and AI fetcher, grouped by kind (search, AI, SEO tools, monitors, scrapers), with verified search engines marked.
• What they read: the pages each one fetched and how often, and which pages no crawler has reached.
• AI: the AI fetchers next to the readers AI assistants sent you, so you can see what an assistant read and what it sent back.

Internal

Your own team's visits, tools and checks, kept out of the other views. Useful to confirm a deploy check ran, and to see that your own browsing is not inflating your numbers.

Behaviour

What readers do across pages, from the journeys the snippet records:

• Paths: the most common routes through the site, and a Sankey diagram from an entry page or towards a goal.
• Goals: how many sessions reached each goal, and from where. See Goals and A/B tests.
• Experiments: each A/B test's variants side by side.

Groups of fewer than five sessions are never shown, so a path cannot single out one person.

Search

Your Google Search Console and Bing Webmaster data beside your traffic: queries, impressions, clicks and positions, by page. Connected with your own credentials; see Search Console and Bing.

Bot protection

What bot protection decided: requests served, challenged and refused, by rule, by crawler and by network, and how many challenged visitors passed. In log mode it shows what it would have done, so you can tune the rules before turning them on.