Analytics

The Analytics section shows how people and crawlers use your published docs. It needs no cookie banner: nothing is stored on the reader's device, and no IP address is saved.

Choose a range#

Pick 24 hours, 7 days, 30 days or 90 days. The default is 7 days. Short ranges chart by hour and longer ones by day, in UTC. Results are cached for five minutes. A new site shows a notice until its first visit arrives.

What you see#

Panel	What it shows
Views	Pages viewed by people. A page load counts when the server answers it, and moving to another page inside the site counts through a small beacon. Hovering a link to prefetch a page does not count.
Visitors	Unique people in the range.
AI and bot visits	Requests from crawlers and automated tools. They are kept out of Views and Visitors.
Views and visitors	The two numbers over time.
Top pages	Your most read pages. If a page exists, its title links directly to its editor in the dashboard.
Referrers	The sites that sent readers to you. Visits without a referring site are grouped as Direct.
Countries and Devices	Where readers are and whether they use desktop, mobile or tablet.
Not found (404)	Paths readers asked for that do not exist, so you can fix broken links or add a redirect target.
AI and bot crawlers	Which bots fetched pages and files, and how many of each.

Crawlers#

Docup recognizes AI agents such as GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, CCBot, Bytespider, Amazonbot and meta-externalagent, and search crawlers such as Googlebot, bingbot, Applebot, DuckDuckBot and YandexBot. Other automated traffic is grouped as other bots.

The panel separates pages from files. Crawlers that read the files Docup generates, sitemap.xml, robots.txt, llms.txt, llms-full.txt and the Markdown copy of each page, show up there. Use it to confirm that AI tools can find your docs. To control which crawlers are allowed, see Search and sharing.

How privacy works#

Docup counts visitors without identifying them.

• A visitor ID is a hash of the project, the browser's user agent, the network address and a random daily salt.
• The salt is replaced every day, so the same person gets a different ID tomorrow and cannot be followed across days.
• Neither the address nor the user agent is stored. Only the hash, the page, the referring site, country, device type and the response status are recorded.
• Sites are counted by project, not by address, so changing your address does not mix your history with another site's.

Limits#

Setting / Metric	Limit
Cache duration	5 minutes
List items shown	50 rows
Salt retention	2 days
Path length limit	256 characters