> ## Documentation Index > Fetch the complete documentation index at: https://docs.get3rd.com/llms.txt > Use this file to discover all available pages before exploring further. # Understanding traffic > See what AI does to your site's traffic: the people AI assistants send you, and the AI bots that read your pages. The **Traffic** page answers one question: what is AI doing to my site? It has two tabs, each fed by a different connection. > **AI referrals** > > People who clicked through from an AI assistant's answer to your site. Needs Google Analytics. > **Bot visits** > > AI bots that fetched your pages, and why. Needs your server logs. The two tabs tell one story. Bot visits shows which pages AI reads. AI referrals shows which pages AI sends people to. ## AI referrals Connect Google Analytics and choose a GA4 property. 3RD then shows how many people arrive from ChatGPT, Perplexity, Gemini and other assistants, which pages they land on, and whether they convert. | Section | What it shows | | - | - | | **AI-referred sessions** | Visits that arrived from an AI assistant, as Google Analytics recorded them. | | **Share of all sessions** | AI-referred sessions as a share of all your sessions in the period. | | **Engagement %**, **Conversions**, **Revenue** | How those visits behave, using the key events and currency set up in your GA4 property. | | **AI sessions and Visibility** | AI visits per model per day, with your 3RD Visibility as a dotted line, so you can see whether visibility and visits move together. | | **By country**, **By device** | Where AI-referred visitors are and what they use. | | **Top landing pages** | The pages AI sends people to, with AI sessions, top model and conversion rate per page. | Filter by model, device or country at the top of the tab. > [!TIP] > > The same per-page numbers appear as **AI-sent visits** on [Content → Site structure](https://docs.get3rd.com/drivers/content.md), next to how often AI bots visit each page. ## Bot visits Connect your server logs and 3RD shows which AI bots read your pages, how often, and whether they are genuine. We keep only visits from known AI bots and discard everything else. ### Why bots visit Every bot visit has an intent, based on what the bot's owner says the bot is for: | Intent | What the bot is doing | Example bots | | - | - | - | | **User query** | Fetching your page to answer someone's question right now. | ChatGPT-User, Claude-Web | | **Search indexing** | Building the index AI search answers draw from. | PerplexityBot | | **Training** | Collecting pages to train future AI models. | GPTBot, ClaudeBot, CCBot, Google-Extended, Bytespider | | **Other** | The owner doesn't publish what the bot is for. | | User query visits are the clearest sign that a page is used in AI answers. ### Confirmed bots Anyone can claim to be GPTBot. A visit is **Confirmed** when it came from an address the bot's owner publishes, so we know it's the real bot. Some owners, such as Anthropic, ByteDance and Common Crawl, publish no address list, so their visits show as **Not confirmed**. That doesn't mean they are fake. A visit is **Suspicious** when the owner publishes addresses and the visit came from somewhere else, so something is pretending to be that bot. ### What the tab shows | Section | What it shows | | - | - | | **Bot visits** | Every page and file known AI bots fetched in the period. | | **Live answer visits** | How many visits came from bots answering someone right now. | | **Confirmed bots** | The share of visits we could confirm came from the real bot. | | **Pages delivered** | The share of bot requests that got the page, directly or through a redirect. Missing pages, blocks and errors count against it. | | **Bot visits over time** | Visits from each AI bot per day. | | **Bot intent** | Visits split by intent. | | **By bot** | Each bot's share of all bot visits, what it visits for, and whether it's confirmed. Click a bot to see the pages it asked for most. | | **Pages and files visited** | Every page and file AI bots asked for, with its status, visits per intent and when a bot last came. Click a page to see each visit. | ### Pages bots couldn't get When a bot gets a missing page (404), a block or an error instead of your page, the page shows its status in **Pages and files visited** and moves to the top. A **Not found** badge opens the issue **Bots are asking for pages that don't exist** in [Agent readiness](https://docs.get3rd.com/drivers/agent-readiness.md#bots-are-asking-for-pages-that-dont-exist). Other statuses open the page so you can see what the bot got, what the page answers now, and what to do. After you fix it, 3RD checks again the next time a bot asks for the page. ## Connect your data **1. Google Analytics for AI referrals** Connect Google Analytics from the **AI referrals** tab, or from **Settings → Integrations**. Then choose the GA4 property for your site. See [Data sources](https://docs.get3rd.com/integrations/data-sources.md). **2. Server logs for Bot visits** Open the **Bot visits** tab, or go to **Settings → Integrations**, and connect **Vercel server logs**. You create a Log Drain in Vercel that sends your request logs to 3RD. This needs a Vercel Pro or Enterprise team. > [!NOTE] > > Connect your server logs with Vercel or Cloudflare. Hosted somewhere else? Tell us where from the **Bot visits** tab and we'll help you connect it. ## Related * [Agent readiness](https://docs.get3rd.com/drivers/agent-readiness.md): whether AI agents can reach and read your site, tested from the outside * [Content](https://docs.get3rd.com/drivers/content.md): Site structure pairs bot visits and AI-sent visits per page * [Data sources](https://docs.get3rd.com/integrations/data-sources.md): everything you can connect This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.