> ## Documentation Index > Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt > Use this file to discover all available pages before exploring further. # Reading AI Traffic > Read the AI Traffic Overview, Crawls & fetches, and Referrals views to interpret retrieval evidence and the undercounted visible tail of AI referrals and conversions. AI Traffic shows what AI systems and their users do with your site. Retrieval and citation evidence lead the story; referral sessions and conversions are the undercounted visible tail. ## Open AI Traffic 1. Open your project 2. In the sidebar, open **Insights › AI Traffic** 3. Stay on **Overview**, or select **Crawls & fetches**, **Referrals** or **404 Demand** ## Overview **Overview** answers where demand is strong and where it leaks. A headline sentence states the window's training crawls, answer fetches, referral sessions and conversion events. ### AI traffic signals One card per stage of the journey: | Card | What it counts | Link | | - | - | - | | **Training crawls** | Requests from training crawlers | **Crawls & fetches** tab | | **Citations** | Primary citations in the window, across your tracked prompts | **Insights › Visibility** | | **Answer fetches** | Requests from answer fetchers responding to a live question | | | **Referral sessions** | AI-attributed analytics sessions | **Referrals** tab | | **Conversions** | Selected GA4 key events or PostHog events and actions from AI referral sessions | **Results** | Where a source is not connected, the card shows no number instead of a zero, and **Manage sources →** opens **Settings › Integrations**. When findings from AI Traffic have been queued as work, a link above the cards reports how many related fixes are waiting in **Actions**. ### Top pages A page table with **Page**, **Answer fetches**, **Referral sessions** and **Conversions** columns, ranked by answer fetches plus referral sessions for the window. ## Crawls & fetches **Crawls & fetches** is the machine-traffic view. The headline and the two cards, **Training crawls** and **Answer fetches**, count verified requests: requests whose sending address DevTune confirmed against the networks the claimed operator publishes. Under each card, a muted line counts the rest as unknown (the address could not be checked) and identity mismatches (the address contradicted the claimed operator). See [AI Traffic Overview](/ai-traffic/overview#privacy) for why a request can stay unknown. The reporting dates appear below the cards. If only the tracking snippet is connected, the **Answer fetches** card reads **Server-side sensor required**, because the snippet cannot see server-side answer fetches. Select **Connect a sensor** to add Cloudflare or edge middleware. Below the cards: * **Daily crawls & fetches** - one bar row per class, each bar split into verified, unknown and identity-mismatch requests * **Platforms** - **Platform**, **Training crawls** and **Answer fetches**, ordered by verified requests. A platform with identity mismatches carries a note with how many requests claimed it from outside its published ranges. * **Recent answer fetches** - answer-fetch records grouped by hour, with today's answer fetches by platform ## Referrals Referrals leads with three metrics: **Referral sessions**, **Conversion events** and **Share of visitors from AI**. Sessions come from the selected analytics provider, GA4 or PostHog, and are not people. Conversion events are the selected GA4 key events or PostHog events and actions reported for AI referral traffic, not unique customers. Selected events that weren't tied to a website visit, such as events your server sends, can't be credited to AI, so their count is listed separately under **Conversion events**. **Daily referral sessions** charts the same window. **Share of visitors from AI** is the share of all sessions on your site that came from an AI answer over the same window: AI-referral sessions over all sessions, from the selected analytics provider (GA4 or PostHog). The line under the value names the provider. It is shown whenever the provider has imported every day of the window and recorded visits. Sessions that may have come from an AI answer but couldn't be traced, because their source or site is unknown, aren't counted as AI, and a line under the value says how many. Otherwise it reads **Not measured**, never 0%, and says whether you need to connect GA4 or PostHog, wait for the provider to finish importing the period, or whether no visits were recorded. The change from the previous period appears only when both periods have a share. The reporting dates appear above the metrics. Recorded totals can include partial source coverage; an unavailable measurement is never presented as zero. If the analytics provider needs attention or conversions have not been selected, select **Analytics in Integrations** in the source notice. * **Direct sessions per day** shows GA4's full daily direct sessions with the measured-page actual and baseline overlay. AI-correlated lift stays separate from referral counts and does not establish causation. See [Direct traffic](/ai-traffic/direct-traffic) for coverage and classification rules. * **By AI engine** shows the session, conversion-event and engagement breakdown from the selected provider, ordered by conversion events and then sessions. Events per session is not the proportion of people who converted. Missing measurements remain unavailable for each engine. A link beside it opens the **Measured actions** tab in **Results**, where live actions are measured over their own before/after windows. * **By page** lists each **Landing page** with its **Source**, **Sessions Δ** and **Conversion events**, ordered by sessions. Previous, next and page-size controls move through the results; changing the reporting window starts at the first page. Expand a landing page to see its current and previous average engagement time, engagement rate, and page value. Page value is the page’s share of AI-referred conversion events weighted by engagement rate; it is unavailable when either measure is missing. The API `GET /v2/projects/{projectId}/traffic/referrals` and MCP `devtune_get_ai_referrals` return the same engine breakdown in `engines`, alongside the paginated landing pages and the actual reporting dates in `window`. `overview.referralCoverage` reports `sessionsCurrent`, `sessionsPrevious`, `conversionsCurrent`, and `conversionsPrevious`. A false flag means the corresponding observed counts may be partial or unavailable. Compare periods only when both flags for that metric are true; this applies to overview, engine, and page counts. `visitorShare` carries the same share of visitors from AI as a fraction from 0 to 1, with `priorShare`, `source`, `providers`, `window` and `coverage`. `unattributedSessions` counts the sessions that may have come from an AI answer but couldn't be traced, and `partial` is true when that count is above 0 (`priorUnattributedSessions` and `priorPartial` for the previous period). `share` is null with a `coverage.reason` when no provider is connected, a day has not been imported or no visits were recorded. ## Page performance Open **Insights › Audit** and select the **Pages** tab to compare Google Search Console clicks with AI citations for the same pages. Select a page to see its evidence, search impressions and position, citability, and next action. Pages are recommended by opportunity; use the sort selector to order them by a metric instead. ## 404 Demand The **404 Demand** tab in **Insights › AI Traffic** is the detail view for missing-page demand. It reports a 30-day snapshot. Only a server-side crawler sensor, Cloudflare or edge middleware, sees requests for missing pages; the site snippet does not. A project with no traffic setup at all is sent to **Settings › Integrations** instead, and a project with only the snippet sees no 404 demand here. ### Project relevance 404 Demand ranks missing paths by assessed fit with your project, then by traffic demand. Each content finding shows whether it is relevant, adjacent, uncertain, or unrelated, with a reason. Use **Sort by request volume** to compare the loaded findings by their observed requests. The assessment uses your project context. Missing context, an ambiguous path, or an unavailable assessment appears as uncertain. After you change project context, prior assessments become uncertain until the next demand refresh reassesses them. Request counts and sensor coverage remain measured traffic evidence. Suggested actions use the same assessment: relevant paths receive full relevance weight, adjacent paths half, and uncertain paths a quarter. Clearly unrelated paths do not generate automatic suggestions. These weights set priority; they do not estimate visits or outcomes. Before drafting content, the 404 Demand triager checks existing content and whether the path fits the product. ### Search Console coverage A saved Search Console row does not by itself verify every day in a reporting window. Dex and the search-rollup API/MCP response distinguish unavailable verification, partial evidence, verified zero, and complete totals. When coverage is partial, they report the available coverage dates and keep full-window totals unavailable. Historical rows without verified connection provenance are reported separately and do not count toward those totals. Use the dates returned with each source: search rollups end yesterday in Pacific time, while other dashboard windows can include today. Recent Search Console days may still be awaiting publication. ## Empty State Until a sensor is connected, cards show no number rather than a zero. Select **Manage sources →** or **Connect a sensor** to open **Settings › Integrations**, connect a sensor, and wait a few minutes for data to appear. ## Reporting window Choose 7, 30 or 90 days beside the tabs. The window applies to **Overview**, **Crawls & fetches** and **Referrals**. A **Δ** column compares the selected window against the one before it. ## Best Practices ### Monitor Bot Crawl Patterns Track which AI bots crawl your site most frequently. If important content pages are not being crawled, review your `robots.txt` to ensure AI bots are not blocked from accessing key pages. ### Track Referral Growth AI referral traffic is a lagging signal that some AI-driven visitors reached your site through attributable links. Growth in visible referrals can support the wider retrieval and visibility picture, but it does not measure total AI-driven demand. ### Pair with Visibility Use AI Traffic alongside Visibility to connect retrieval evidence with its visible downstream tail: * **Visibility** shows whether AI platforms mention and cite your content in their responses * **AI Traffic** shows what AI systems retrieve and the referral sessions and conversions that can be attributed AI referrals are systematically undercounted because most AI-driven visitors arrive as direct traffic. Treat referrals and conversions as lagging, visible evidence rather than a complete linear funnel. ### Review Top pages The **Top pages** table shows which content has the most visible AI activity. Use this to: * Identify content with the most visible AI activity * Understand which types of content attract the most AI-referred visitors * Prioritize content updates for pages that receive heavy AI traffic ## Troubleshooting ### No Data Appearing * Verify the tracking snippet is installed correctly (check page source) * Confirm **Snippet and middleware collection** is switched on in **Settings › Integrations** * Check that ad blockers are not blocking requests (set up a proxy if needed) * Wait a few minutes for initial data to appear ### Low Bot Traffic * Check your `robots.txt` file for rules that might block AI crawlers * AI bot crawling frequency varies by platform and is not under your control ### Low Referral Traffic * Low referral traffic does not measure total AI-driven demand because most AI-driven visitors arrive as direct traffic * Review **Insights › Visibility** to see if your presence rate is high but referrals are low * Consider improving your content to be more actionable, encouraging users to visit your site ## Next Steps * **[AI Traffic Setup](/ai-traffic/setup)** - Connect or repair a sensor * **[AI Traffic Overview](/ai-traffic/overview)** - Understand what gets tracked and why * **[Visibility](/search-tracking/overview)** - Monitor what AI platforms say about you and who they cite * **[Explore](/analytics/search-analytics)** - Analyze your AI visibility trends This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.