Live Signals
Everything a search engine or an AI assistant does on this site is logged, and this page shows it: crawler visits, which engines arrive and for which pages, where real visitors come from, what the security layer blocks, and how all of it changes hour by hour and day by day.
We publish it for two reasons. Measurement is the part of search and AI visibility most agencies keep behind a login — we would rather show ours. And this is exactly the instrumentation we install on client sites, so what you see here is what you get.
The headline figures are written into the page when it is built, so they are readable without JavaScript; the charts and breakdowns fill in as you read.
| Source class | Hits | Share |
|---|---|---|
| Search engines | 109 | 86% |
| AI retrieval / citation | 6 | 5% |
| AI training | 12 | 9% |
| Other / unclassified | 0 | 0% |
| Engine | Hits | IPs | Last |
|---|---|---|---|
| Yandex | 125 | 105 | 11-22 11:00 |
| Amazonbot | 87 | 81 | 11-22 05:11 |
| 76 | 5 | 11-22 12:52 | |
| Bing | 67 | 52 | 11-22 12:33 |
| Applebot | 56 | 40 | 11-21 23:04 |
| GPTBot | 24 | 2 | 11-22 01:12 |
| OAI-SearchBot | 15 | 8 | 11-22 11:52 |
| meta-externalagent | 7 | 7 | 11-21 15:11 |
| DuckDuckBot | 4 | 1 | 11-22 02:23 |
| PerplexityBot | 4 | 3 | 11-21 07:10 |
Cards 1 to 3 use the calendar day in UTC and reset at 00:00 UTC. Cards 4 to 7 use a 7-day window, which currently holds 3 of 7 days of logs. Cards 8 to 14 use rolling windows: 24 hours unless the title says otherwise, and they do not reset. The headline figures are written into the page itself, so they read without JavaScript; the charts fill in live.
Visitors, measured in the browser
Page views, last 24 hours 1 · visitors 1 · events 0 · today (UTC): 1 views / 1 visitors
| Page | Views | Visitors |
|---|---|---|
/selftest | 1 | 1 |
| Referrer | Arrivals |
|---|---|
| No external referrers yet | |
Measured by /assets/stats.js in the visitor’s browser: no cookie, no persistent id, raw IP never stored, Do Not Track respected. The crawler figures above come from server logs and include bots; these count people. Data: stats.json · traffic.json · pages.json · updated 2026-09-27T17:55:02+00:00.
Visitors, measured in the browser
Page views, last 24 hours 22 · visitors 23 · events 0 · today (UTC): 17 views / 17 visitors
| Page | Views | Visitors |
|---|---|---|
/tools/workload-planner/ | 2 | 2 |
/ | 2 | 2 |
/reports/live/2026-11-20/ | 1 | 1 |
/reports/live/2026-11-15/ | 1 | 1 |
/reports/live/2026-11-14/ | 1 | 1 |
/article/why-your-faq-schema-isnt-showing-in-search-results.html | 1 | 1 |
| Referrer | Arrivals |
|---|---|
| No external referrers yet | |
Measured by /assets/stats.js in the visitor’s browser: no cookie, no persistent id, raw IP never stored, Do Not Track respected. The crawler figures above come from server logs and include bots; these count people. Data: stats.json · traffic.json · pages.json · updated 2026-11-22T13:05:01+00:00.
What Each Card Shows
- 1. Requests today (UTC) — every request in the calendar day UTC, then the paths requested most. Includes scanners, not-found requests and ordinary visitors.
- 2. Named crawler visits today (UTC) — requests from recognised search and AI engine user agents today, with the engine breakdown.
- 3. Crawler share today (UTC) — which engines account for today’s crawler traffic, as a share of today’s named crawler total. The number on the right is how many engines were seen.
- 4. Named crawler visits, 7-day window — the same count measured across a 7-day window, per engine.
- 5. Crawler share, 7-day window — engine share for that window. The number on the right is how many named engines were seen.
- 6. Day by day — named crawler requests per day in the window. Each bar is one calendar day (UTC); hover shows that day’s total requests and the crawler share. Scanner traffic is not counted in the bar.
- 7. Window summary — engine, request count, distinct IPs and last-seen time for every crawler in that window.
- 8. Latest crawler hits — the most recent requests: engine, path and time (UTC).
- 9. Search & AI referrers, last 24h — visits that arrived from a search or AI source, identified from the HTTP referrer. The window rolls and does not reset.
- 10. Security, last 24h — requests blocked by our crawler and scan policy (HTTP 403), and the scan paths that triggered it.
- 11. 404 responses, last 24h — requests for paths that do not exist. Almost all are automated probes for software this site does not run. Known probe patterns are blocked at the edge and counted under security; the paths here are the residue. They are not broken links on this site.
- 12. Top visitor IPs (masked), last 24h — the busiest sources with the last part of the address masked, plus the resolved country.
Crawler counts include only requests from recognised search and AI engine user agents. Requests to known scan paths (/.env, .git, /wp-*, /index.php and similar) are counted separately in the security metrics, and a request can appear in both. Aggregated counts, including requests that match no named engine, are published in live.json with matching definition fields.
How This Data Is Collected
- Source: our own web server logs, with Cloudflare real-IP resolution so country data reflects the visitor rather than the CDN edge.
- Crawler identification: from each request’s user agent string. No analytics product, no tracking cookies and no client data are involved.
- Privacy: visitor IP addresses are never published in full — the last part is masked and counts are aggregated.
- Refresh: log parsing runs every five minutes; this page re-reads the data every sixty seconds.
- Retention: rotated logs limit the trend window while the site is young, so earlier days roll off as new ones arrive.
- Why the numbers are small: the site launched recently. New crawlers appear over time — we would rather show a real small number than an impressive invented one.
Want this instrumentation on your own site? It is how every engagement starts. Get in touch.
