> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomicagi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Search Overview

> Start here to understand AI traffic direction, source quality, and which pages need action first

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/data/ai-search/app-ai-search-overview-top.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=8d6c47f8fedce0a36aeb18c2d677a589" alt="AI Search Overview top section with AI clicks and total conversions trend" width="1536" height="1024" data-path="images/data/ai-search/app-ai-search-overview-top.png" />
</Frame>

Use this page as your weekly control center for AI Search. It tells you where performance is moving before you jump into deeper pages.

<div className="atomic-info-callout">
  <p>
    <strong>Important:</strong> Review this page first, then drill down. It
    prevents teams from optimizing the wrong source or page.
  </p>
</div>

## Questions this page should answer

1. Are AI clicks and conversions moving in the same direction?
2. Which AI sources are helping most, and which are weakening?
3. Which pages should we prioritize first this sprint?

## Before you analyze

* Set the same date range you will use on the other AI Search pages.
* Compare against an equivalent prior period.
* Start unfiltered so you see the global pattern first.

## What this page gives you

* A top trend for `AI clicks` and `Total conversions`.
* A `By source` table to compare AI engines.
* A `By page` table to see which URLs drive AI traffic quality.

## How to read the top trend correctly

* `AI clicks`: sessions coming from AI platforms.
* `Total conversions`: tracked outcomes after those visits.

Read both together:

* Clicks up, conversions down: traffic quality or intent fit is weak.
* Clicks flat, conversions up: landing page quality likely improved.
* Clicks down, conversions down: visibility or prompt coverage problem is likely.

<div className="atomic-highlight-card">
  <p>
    <strong>Key signal:</strong> If clicks and conversions both decline, start
    with visibility and prompt coverage checks before page-level edits.
  </p>
</div>

<div className="atomic-example-card">
  <p>
    <strong>Example:</strong> If ChatGPT clicks drop 22% and conversions drop
    18% in the same week, first review Visibility and Prompts for that source
    before changing landing pages.
  </p>
</div>

## How these metrics are calculated (simple)

### AI clicks

AI clicks are the total sessions attributed to supported AI referrers in the selected date range.

### Total conversions

Total conversions are the selected GA4 conversion events generated by those AI-attributed sessions.

## By source section

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/data/ai-search/app-ai-search-overview-tables.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=e88b1919df19b8efe8ec71c309c6e28d" alt="AI Search Overview By source and By page tables" width="1536" height="1024" data-path="images/data/ai-search/app-ai-search-overview-tables.png" />
</Frame>

Use `By source` to decide engine focus for the week:

* Prioritize sources with strong conversion efficiency.
* Flag sources with sharp drop in clicks and conversions.
* Avoid over-investing in sources that drive volume but no business impact.

## By page section

In the same table view, use `By page` to choose URL-level actions:

* Pages with high AI clicks and weak avg. time need better on-page clarity.
* Pages with stable traffic but falling outcomes need message refinement.
* Pages with improving outcomes are templates for replication.

## Quick weekly checklist

1. Confirm top-line direction from clicks and conversions.
2. Pick one growth source and one declining source.
3. Pick three URLs for immediate improvement.
4. Route deeper analysis to the right page: Visibility, Prompts, Pages, or Citations.

## How to use filters

* Use date range first to keep reporting consistent.
* Narrow by one segment at a time when validating a hypothesis.
* Do not compare mixed filter sets in the same decision.

## What to fix first

| Pattern in Overview data         | What it usually means                       | Recommended action                               |
| -------------------------------- | ------------------------------------------- | ------------------------------------------------ |
| Clicks down and conversions down | Visibility or prompt relevance loss         | Check `Visibility` and `Prompts` first           |
| Clicks up, conversions flat      | Traffic quality mismatch                    | Improve destination pages and intent alignment   |
| One source drops sharply         | Platform-specific issue                     | Investigate `Generative engines` and competitors |
| Stable traffic, weaker avg. time | Content experience mismatch after the click | Improve page structure and value clarity         |

## Team routine

1. Weekly: run Overview first before any deep dive.
2. Bi-weekly: compare source efficiency changes.
3. Monthly: report AI Search contribution to business outcomes.

## Keep in mind

* AI traffic can be volatile in short windows.
* Conversion lag can hide recent improvements.
* Top-line trend is useful only when paired with source and page context.

## Where to go next

* [Generative engines](/data/ai-search/generative-engines)
* [Visibility](/data/ai-search/visibility)
* [Pages](/data/ai-search/pages)
* [Prompts](/data/ai-search/prompts)
* [Citations](/data/ai-search/citations)
* [Sentiment](/data/ai-search/sentiment)