Serve analytics[01]
Serve analytics
Which agents read which pages of your site, and how much lighter your Markdown was than the page they'd otherwise have parsed. Filled in by the SDK's middleware — nothing to add to your pages.
One visit, one row
[02]- route
- /pricing
- bot_name
- GPTBot
- user_agent
- GPTBot/1.2 (+https://openai.com/gptbot)
- ip_country
- US
- payload_bytes
- size of the .md
- html_bytes
- size of the page
The middleware sends the route and user-agent with your site key; Onto names the bot, reads the country from the request, and copies the two sizes from the page's synced file. A user-agent it doesn't recognise is kept as Unknown.
What the page shows
[03]SectionShowsPlan
TotalsVisits, distinct agents, bytes and tokens saved, for the range you pickAll
TimelineVisits per day for the last 7 daysAll
AgentsVisits per agent — the top 8, then the restAll
RoutesYour 8 most-read pages and when each was last readAll
RecentThe latest 8 visitsAll
CountriesWhere visits come from, top 12Pro and up
Unknown agentsThe 12 commonest user-agents it couldn't name — worth a lookPro and up
ExportAll of it as CSVPro and up
How long it's kept
[04]PlanRange you can see
Free30 days
Pro365 days
Business, EnterpriseEverything
The range picker offers 7, 30 and 90 days, a year, or all — up to your plan's range. Nothing is deleted when you're on a smaller plan; upgrade and the older visits are there.
Reading it right
[05]Because
Visits include youRequests with
?onto or Accept: text/markdown are recorded too — so are your own checks.A visit isn't always MarkdownThe visit is noted before the
.md is looked up, so a page with no .md still counts.Tokens and dollars are estimatesBytes saved ÷ 4 for tokens, priced at a fixed $15 per million — a yardstick, not your bill.
Edge latencyShown, but not measured yet.