# Statistics

> Web statistics for every site, read from the access logs: visitors, pages, sources, campaigns, countries and devices, with no script to install and no cookies.

Source: https://www.corepanel.net/docs/client-panel/statistics/
Last updated: 2026-11-09
Part of the CorePanel documentation — https://www.corepanel.net/docs

---

**Statistics** shows each site's visitors, the pages they read and where they came from.
It works on every site from the day it is created, including sites you just migrated: it
reads the server's access logs, so nobody installs a script and visitors see no cookie
banner. Figures update every ten minutes.

![The client panel's Statistics page in Classic Blue for corepanel.io over the last 30 days, on the Visitors view; a Bots view sits beside it. Four figures across the top: 6,592 visitors (up 14%), 20,105 pageviews (up 14%), a 41% bounce rate (down 3 points) and 48,552 bot requests, with an arrow that opens the Bots view. Below, a line chart of daily visitors between about 130 and 280. Two cards follow: Pages, with / on top at 3,980 views, then /shop/, /blog/how-to-choose-a-tent/ and further down /checkout/; and Sources, with Direct, Google, ChatGPT, Instagram, a newsletter campaign, Bing and Perplexity. The sidebar shows Statistics selected under Domains.](https://www.corepanel.net/_astro/client-panel-stats-light.wKnNR1xT.png)

- **Pick a site and a range** at the top: today, yesterday, 7 days, 30 days, this month,
  last month or 12 months.
  The small arrow next to each figure compares the finished days of the range with the
  same number of days just before them; it does not appear for today, or before there is
  enough history to compare. Bounce rate changes in points.
- **Sources** names where each visit came from: a search engine, a social network, an AI
  assistant (ChatGPT, Perplexity, Claude…), a webmail, another site or nowhere (**Direct**).
  Links tagged with `utm_source`, `utm_medium` and `utm_campaign` show up under
  **Campaigns**.
- **Visitors and Bots** are two views of the same site. Recognised search engines, AI
  crawlers and other automated clients do not count as visitors; the **Bot requests**
  figure shows how many requests they made, and clicking it opens the
  [Bots](#bots-and-ai) view, where you see who they are and can block them.
- **Aliases** are counted under the site they point to.

## Filters

Click any row of a list to narrow the whole page to the visits it names. Click
**ChatGPT** in Sources and every figure, the chart and the other lists show only the
visits that came from ChatGPT: which pages they read, from which countries, on which
devices. Add a second row to combine both; each filter appears above the figures, with
an **×** to remove it.

![The Statistics page for corepanel.io over 30 days, filtered by two chips beside the Visitors and Bots switch: Page /shop/ and Source ChatGPT, each with a remove button, and a Clear link. The four figures now count only those visits: 1,452 visitors, 4,423 pageviews, a 41% bounce rate and 1,710 visits, which takes the place of bot requests while a filter is on. The chart and the Pages, Sources, Countries and Devices lists are narrowed the same way.](https://www.corepanel.net/_astro/client-panel-stats-filtered-light.eMXXPeIf.png)

- **A page filter** keeps the visits that viewed that page at any point. Any other filter
  looks at where the visit started: its source, campaign, country and device.
- **Filters apply to visitors only.** Bots and errors are requests, not visits: while a
  filter is on, the bot figure is replaced by the number of visits, and the Bots view
  shows the whole site. The filters stay set and come back when you return to Visitors.
- **12 months** shows the whole site: filters work on ranges of up to 90 days, the
  detail the panel keeps per visit.
- The filters are part of the address, so a link to the page opens it filtered, and
  **Back** removes the last one you added.
- When some days of the range have no per-visit detail (before it began, or a day busier
  than the panel keeps detail for), a note under the lists says filtered figures are short.
- A long range with several filters on a very busy site can take too long; remove a
  filter or pick a shorter range.
- After a day closes, its rarest pages, sources and campaigns are grouped under
  **Other**, in the lists and in the filters alike.

## Bots and AI

The **Bots** view, next to **Visitors** at the top of the page, counts requests rather
than visits: what crawlers fetch, and the site's [errors](#errors). Its figures are the
bots' requests, their share of the site's requests, the data they were sent and the
site's server errors, over a chart of bot requests. Below, the
**Bots & AI** card lists every crawler that visited the site, with its requests, the data
it was sent and a small chart of that transfer per day. **Most crawled** lists the pages
bots fetch most, with their transfer.

![The Bots view of the Statistics page in Classic Blue for corepanel.io over 30 days. Four figures: 48,552 bot requests (up 43%), 27% of requests (up 8 points), 9.5 GB of bot transfer and 3 server errors, over a line chart of daily bot requests between about 1,100 and 2,000. The Bots & AI card says 9.5 GB to bots, 62% of transfer, and has two switches: Block AI training, turned on, and Block AI assistants, off. Its table lists each bot with its category, requests, a small shaded chart of transfer per day beside its total, and a Block switch: GPTBot (AI training, 3,100 requests, 769 MB), Meta-ExternalAgent (743 MB) and ClaudeBot (240 MB) switched on and dimmed because their category is blocked; Googlebot and bingbot (Search) off; AhrefsBot (SEO) on and dimmed because the WAF already blocks it; ChatGPT-User (AI assistant) off; and Other declared bot, which has no switch. Below, side by side, Most crawled, led by /catalogue-2026.pdf at 2.1 GB, and the Not found (404) list, led by /wp-login.php.](https://www.corepanel.net/_astro/client-panel-stats-bots-light.uHwBmSU2.png)

- **Block AI training** turns away the crawlers that collect pages to train AI models
  (GPTBot, ClaudeBot, CCBot, Meta-ExternalAgent…). **Block AI assistants** turns away the
  ones that fetch a page because someone asked an assistant about it (ChatGPT-User,
  Perplexity-User…): blocking them also keeps the site out of those answers.
- **Each bot's switch** blocks that bot alone. Blocking a search engine asks first: the
  site drops out of its results.
- A blocked bot gets a *403 Forbidden* on every page except `/robots.txt`. The block
  matches the bot's name and never bans an address, so people who share that address
  are not affected.
- **AhrefsBot, SemrushBot, MJ12bot and DotBot** show as blocked already: the
  [WAF](https://www.corepanel.net/docs/security/waf) turns them away on its own (rule BOT-003, answering *412*),
  unless the administrator turned that rule off.
- Generic entries such as **Other declared bot** have no switch, because they name no
  single client.
- Transfer per bot starts on the day the server was updated to this version; the card
  says so until the range is all after it.

## Errors

**Not found (404)** lists the missing addresses people asked for, which shows broken links
and old URLs worth redirecting. **Server errors (5xx)** lists the addresses that failed.
Both count every request, from people and bots alike, and live in the Bots view next to
**Most crawled**, because most 404s come from crawlers and scanners probing for files the
site never had.

## How visitors are counted

A visitor is one browser on one site on one day. The panel recognises them by a code made
from their address and browser with a random value that is deleted a day or two after the
day ends, so it never stores IP addresses and a visitor cannot be followed from one day to
the next. Each visit is kept as its starting page, source, campaign, country and device,
the pages it viewed, and a number that only tells that day's visitors apart.
Two people behind the same connection and browser count as one.

## What it cannot see

- **Pages served by a CDN cache** (Cloudflare, for example) never reach the server, so a
  site behind one shows fewer visits than it gets.

Days follow the server's time zone. Statistics are kept day by day for 90 days and month
by month for two years.