---
title: Traffic
description: Understand AI visits, search crawlers, website request logs, and the integrations behind PromptEye Traffic.
---

Traffic brings together five views of what automated services do on your website. Open it from the product menu, then choose a tab for the question you are trying to answer.

| Tab | Use it when you want to… |
| --- | --- |
| [Overview](./overview/) | See the latest AI visit, traffic sources, changes over time, and whether AI visits lead to sessions in Google Analytics. |
| [AI Traffic](./ai-traffic/) | Find which AI services fetch your pages, what they reach, and whether requests run into errors. |
| [SEO Crawlers](./seo-crawlers/) | Review search engine and SEO tool activity separately from AI services. |
| [Logs](./logs/) | Trace individual identified bot requests by page, user agent, status, and time. |
| [Settings and setup](./setup/) | Install tracking or connect Google Analytics, Search Console, and a sitemap. |

The project selector determines which website the reports describe. The date and service filters are shared by the report tabs; changing them changes the numbers and lists you are looking at. Traffic keeps its own period, separate from Visibility and other screens. A custom date range can cover up to 60 days. The chart zoom is a closer view of the period already loaded, so it will not retrieve older events.

## How the data fits together

PromptEye records visits from bots it can identify after the tracking integration is installed on your site. That tells you about automated requests, not people viewing your site and not how often your brand appears in AI answers. Google Analytics can add a separate view of sessions that began from an identifiable AI referral. Search Console adds Google search clicks and impressions. These sources answer different questions, so their totals are not expected to match.

The **AI Traffic** tab here counts recorded visits of AI services to your website. It is not the same as the **AI Traffic** estimate on Visibility and Prompt Intelligence, which estimates the demand behind your monitored questions. Traffic also cannot tell you which prompt or AI answer led to a visit; it shows which service fetched which page and when.

If all the tabs are empty, first check **Settings and setup** for the selected project. A connected account alone does not install the website tracker: the tracker must be deployed, and an identified bot must visit the site before AI request data appears.

## A practical way to investigate

For example, after publishing a product guide:

1. Check **AI Traffic** to see whether assistant or crawler requests reached the new path.
2. Open **Logs** if you need to inspect the exact request and HTTP response.
3. Check **SEO Crawlers** and **Overview** to compare search crawler activity and Google search performance.
4. If Google Analytics is connected, review whether identified AI referrals led to sessions or key events. That is a clue about visits from AI tools, not proof of which answer mentioned the page.

For the details and limits of each report, use the tab guides in the sidebar.