Traffic
The two Traffic pages: Crawlers records AI bots reading your site, Visitors records humans who arrive from an AI answer.
Traffic is where Trakkr records what actually happened on your website, as opposed to what a model said in an answer. It has two ends. Crawlers records the AI bots that requested your pages. Visitors records the humans your analytics can trace back to an AI tool. Everything else in Trakkr is measured by asking models questions; Traffic is measured by reading server-side records of real requests.
Open Traffic when you need evidence rather than inference: whether AI can reach a page at all, which pages the bots keep coming back to, and whether any of that turns into people on your site.
Both pages need a paid plan, and each needs something connected before it shows anything. Traffic is not available in the white-label client portal.
The two pages
| Page | Route | What it records | What it needs connected |
|---|---|---|---|
| Crawlers | /traffic/crawler | Requests from AI bots, classified as Training, Indexing, Conversations, Agents or Other | A crawler source: Cloudflare, Vercel, Netlify, the WordPress plugin, a CDN or a server hook |
| Visitors | /traffic/analytics | Sessions whose source your analytics identifies as an AI tool, plus landing pages, key events and revenue | A Google Analytics 4 property, connected read-only over OAuth |
The two are independent measurements. A crawl does not cause a visit, and the pages do not claim it did. A page can be crawled hundreds of times and send nobody, or send visitors while your crawler source never recorded a request. Both of those are findings.
Start with Crawlers. It answers the cheapest question first (can AI read this at all?) and its findings are actionable without waiting for anyone to click.
Search Console sits alongside them
There is a third connection under Traffic, at /traffic/search-console. It is not in the sidebar; you reach it from Integrations in the sidebar, or from the prompts Trakkr shows when a page needs it. The page itself is just the connection: pick a Google Search Console property, and Trakkr syncs it.
What it adds shows up elsewhere. Once a property is connected, the crawler page drawer gains a Google search section with that page's average position, clicks, impressions and top query for the same window, so you can see the pages Google already ranks that AI never cites. Those are usually the best pages to fix first, and the comparison only exists once both sides are connected. Search Console uses its own read-only OAuth, separate from the Analytics connection.
How Traffic feeds Pages
Pages is where the two Traffic signals meet everything else Trakkr measures. Each page record carries a journey from Available through Reached, Understood, Relevant, Selected and Visited, and names the first stage that is weak.
Crawler requests are evidence for the early stages: a page nothing has fetched is not reachable, whatever your sitemap says. Visitor sessions are the evidence behind Visited. Citations, prompts and rankings fill in the middle. Traffic gives you the two ends; Pages tells you which end to work on.
Common questions
Do I need both connections?
No. Each page works on its own. Crawlers needs a crawler source, Visitors needs Google Analytics, and neither depends on the other. Connecting both lets Trakkr put crawl counts, citations and referral sessions on the same page row, which is where the useful comparisons live.
Why is Search Console not in the sidebar?
It is a connection rather than a dashboard. The page only lets you link a property, confirm the last sync and disconnect. The data it unlocks appears inside Crawlers, Pages and the work Trakkr suggests, so there is nothing to visit day to day.
Can my white-label clients see Traffic?
No. Client portal users are redirected away from every route under Traffic. The portal covers dashboard, prompts, competitors, citations, perception, pages, actions, reports and documents.
Does Trakkr add a script to my site?
No. Visitors reads your existing Google Analytics property through Google's API. Crawlers reads server-side request records from whichever source you connect. Nothing runs in your visitors' browsers, so nothing changes your page weight or Core Web Vitals.
Why does Trakkr never say a crawl caused a visit?
Because the records cannot support it. A crawler request log does not contain the conversation, and a referral session does not name the answer that produced it. Trakkr joins the observations by normalized page URL and time window and leaves the causal claim to you.