Monitor
Traffic
See the people who reach your site from AI answers, search and social, and the AI crawlers reading it, from Site Tracking and Google Analytics.
The Traffic page shows who arrives on your site from AI answers, search and social, and which AI crawlers are reading it. Visibility tells you whether AI names you; Traffic tells you whether that turns into visits. Open it from Traffic in the Monitor section of the sidebar.
Two sources
The page is fed by one or both of these. They see different things, so many brands connect both.
Many AI apps strip the referrer when a visitor clicks a link. Both sources still attribute the visit when the link carries a campaign tag, as ChatGPT's do, and Site Tracking also recognises the Gemini app on iPhone by its in-app browser. A link with neither lands in Direct in both, and nothing can tell it came from an AI answer. That is why the Google Analytics view carries a note about referrers. Site Tracking also records visits GA4 does not: the crawlers, visitors whose browser blocks the GA4 tag, and visitors who decline analytics consent when your consent banner holds the tag back.
Connecting a source
When neither source has data in the selected date range, the page reads Connect a traffic source and shows a card for each:
- Site Tracking: Set up Site Tracking opens the install page. Once the brand has an active site key, the card reads Continue install instead. See Verify your install.
- Google Analytics: Continue with Google starts the connection, then you pick the GA4 property. Once a property is connected, the card reads Connected — first sync in progress until GA4 data appears in the date range, including after a sync that failed or found no matching sessions. See GA4 not syncing.
Once one source has data in the date range, the page shows it. The Site Tracking / Google Analytics switch appears when Site Tracking has visits in the range and a GA4 property is connected. Otherwise the page shows one source and offers the other as Add Site Tracking or Add Google Analytics. The date range defaults to the last 30 days.
Site Tracking view
This view needs the brand to have an active site key. Without one, the brand's recorded visits are hidden, not deleted, until a new key exists. See Site keys.
The header shows how many visits this brand has recorded this month against its monthly allowance, in the form N / M visits this month, counting bots and people together. The allowance depends on your plan, and visits over it are still recorded. See Plans and limits.
Opportunities
When the Action Center holds open recommendations built from your traffic and citation data together, up to three appear here, most impactful first. View and View all open the Action Center. The strip is hidden when there are none.
The four cards
- Human Visits: people landing on your site from a web browser, across every source channel, with the number of channels that sent anyone. A browser claiming a version no up-to-date browser runs counts as Other bots instead (how that is decided).
- Agent Visits: every visit captured, bots and humans combined, with the change against the previous period.
- Verified Bots: the share of checkable bot visits whose address matched the range the bot's operator publishes, shown with the count behind it. Visits Ranqo cannot check, from people and from bots it has no published ranges for, are left out rather than counted as suspect.
- Pages Crawled: the distinct paths on your site that received at least one visit in the window, from bots or people.
Where people come from
- Human traffic by channel splits human visits into AI Platforms, Search, Social, Direct, Email and Other. Click a channel for its detail. Its Countries card, captioned Where visitors are coming from, counts the visits whose report carried the visitor's country; see Privacy.
- Human visits by AI platform breaks the AI channel down by assistant.
What the bots are doing
- Agent visits trend plots visits per day, people included, stacked by Intent or by Vendor. In the Vendor view, people and other bots make up the Unknown band.
- Agent intent splits visits by why they came:
- Training: crawlers collecting pages to train models.
- Indexing: AI search indexers building the index they cite from.
- Agentic: fetches made on demand because a person asked an assistant something.
- Social Preview: link-preview generators and automated browsers.
- Search Engine: traditional search crawlers.
- Other bots: clients that are not web browsers and are not in the bot catalog, such as scripts, SEO tools' crawlers and uptime checks, and browser user agents claiming a version no up-to-date browser runs (how that is decided).
- Human (AI Referral) and Human (Direct): people, sorted by whether an AI assistant referred them.
- Agents detected lists each bot with its operator and whether its visits were verified, with people as rows of their own (AI-referred visitors and Direct visitors) and the bots outside the catalog as one Other bots row.
- Funnel by AI platform places each AI platform on a path from training crawls, to indexing crawls, to agentic fetches, to human visits. Each stage is a stronger signal than the one before. The label on each row, such as Indexed, no agentic yet or Citing + driving traffic, says how far that platform has got with your site.
- Top Crawled Paths ranks the pages with the most visits, from bots and people together.
- Live Feed shows the most recent visits and refreshes on its own, with the agent, the page and, when known, the visitor's country and the platform that sent it.
Site Access runs on its own after your tracking runs and fetches your site as each crawler it tests, so its requests appear here too, most of them as visits from those crawlers. See Ranqo's requests in Site Tracking.
See How Ranqo classifies visits and the crawler catalog.
Google Analytics view
This view shows human sessions that GA4 attributes to the AI platforms and search engines Ranqo recognises as sources; see how sources are recognised. The header shows Last synced with the time of the last sync attempt, a failed one included, and a Sync now button. GA4 data also syncs once a day on its own while the connection is healthy.
- Sessions: the sessions from those AI platforms and search engines in the window.
- Engaged Rate: the share of those sessions that GA4 counts as engaged.
- Conversions: the conversions GA4 recorded in them.
- Sessions over time: daily sessions by platform.
- Sessions by source: the split across AI platforms and search engines, each marked AI or SEARCH.
- Top landing pages: where those sessions began. The number beside each page is not its session count for the date range: each day's stored row holds the page's sessions for the whole period that day's sync fetched, and the card adds those rows up, so the number usually runs higher. Check the counts in GA4 itself.
Sessions, Engaged Rate and Conversions show no comparison with an earlier period. When a sync fails or Google stops accepting the connection, a banner titled Google Analytics sync error or Google Analytics connection expired shows the reason and offers Reconnect. It appears only while the page has data to show; with none in the date range, the connect cards show instead. See GA4 not syncing.