Live dashboard
Aggregated data from the tracker at track.jsseo.dev. Rebuilt at landing build time (daily). Individual hit details and IPs are not exposed — this is rollup only. See /data for raw data and citation.
Snapshot
Tracker data generated at 2026-05-18T15:47:34.459Z.
Build fetched it at 2026-05-18T15:47:34.574Z.
- 271 hits total
- 271 in last 24h
- 271 in last 7 days
- 6 distinct bot classes
- 16 distinct cells
By JS content pattern (v0.4 primary axis)
One row per js_content_pattern. Pattern definitions in the
methodology.
| pattern | hits | last 24h | bot classes | page types | ✓ verified bots |
|---|---|---|---|---|---|
clean |
91 | 91 | 4 | 5 | 16 |
(legacy/non-cell) |
86 | 86 | 5 | 1 | 8 |
mixed |
25 | 25 | 2 | 1 | 4 |
js-fetched |
14 | 14 | 2 | 1 | 2 |
click-reveal |
12 | 12 | 2 | 1 | 2 |
hash-routing |
11 | 11 | 2 | 1 | 2 |
js-images |
11 | 11 | 2 | 1 | 2 |
late-loaded |
11 | 11 | 2 | 1 | 2 |
js-links |
10 | 10 | 2 | 1 | 2 |
Pattern × ua_class survival matrix
Each row: (pattern, bot class) pair, with hit count and verification breakdown.
Once Layer 3 client-side beacon lands, this view gains
js_executed_pct column showing real visibility per pattern × bot.
Until then, hit counts tell us coverage but not whether the bot saw content.
| pattern | ua_class | hits | last 24h | ✓ | ✗ |
|---|---|---|---|---|---|
clean |
human |
65 | 65 | 0 | 0 |
clean |
gptbot |
16 | 16 | 16 | 0 |
clean |
google-readaloud |
6 | 6 | 0 | 0 |
clean |
google-inspection |
4 | 4 | 0 | 0 |
click-reveal |
human |
10 | 10 | 0 | 0 |
click-reveal |
gptbot |
2 | 2 | 2 | 0 |
hash-routing |
human |
9 | 9 | 0 | 0 |
hash-routing |
gptbot |
2 | 2 | 2 | 0 |
js-fetched |
human |
12 | 12 | 0 | 0 |
js-fetched |
gptbot |
2 | 2 | 2 | 0 |
js-images |
human |
9 | 9 | 0 | 0 |
js-images |
gptbot |
2 | 2 | 2 | 0 |
js-links |
human |
8 | 8 | 0 | 0 |
js-links |
gptbot |
2 | 2 | 2 | 0 |
late-loaded |
human |
9 | 9 | 0 | 0 |
late-loaded |
gptbot |
2 | 2 | 2 | 0 |
mixed |
human |
21 | 21 | 0 | 0 |
mixed |
gptbot |
4 | 4 | 4 | 0 |
By verification method
How each hit's bot-class claim was confirmed. rdns = Google/Bing/Apple.
ip-range = OpenAI/Perplexity/Anthropic. none = explicit
auto-unverified (anthropic-legacy). (none/pending) = no verification
path or queue still pending.
| method | hits | ✓ | ✗ | ? | last 24h |
|---|---|---|---|---|---|
(none/pending) |
231 | 0 | 0 | 231 | 231 |
ip-range |
39 | 39 | 0 | 0 | 39 |
rdns |
1 | 1 | 0 | 0 | 1 |
By pathway
Batch crawlers (indexing) vs on-demand fetchers (LLM responding to user prompt) vs AI search infrastructure (search) vs ads-related crawlers (ads). Transitional taxonomy until end-of-Phase-1 refactor.
| pathway | hits | last 24h |
|---|---|---|
n/a |
220 | 220 |
batch |
40 | 40 |
on-demand |
11 | 11 |