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

# Which of my pages receive the most AI-driven traffic?

> Rank landing pages by observed sessions from recognized AI referrers, then review page context and attribution limitations.

## Direct answer

Use **Measure > Page Performance** or Referrer Analytics to rank landing pages by sessions whose referrer is classified as an AI platform. Keep the selected period, property, and traffic unit visible, and analyze citations as a separate dataset.

## Data required

Use connected analytics or referrer records, AI-platform classification, landing-page URL, session date, engagement or conversion fields if available, and URL normalization rules. For context, use separate Qwairy citation and crawler records.

## Workflow

<Steps>
  <Step title="Validate the connection">
    Confirm the analytics property, timezone, consent setup, URL normalization, and selected traffic unit.
  </Step>

  <Step title="Rank landing pages">
    Choose a period and sort pages by observed AI-referred sessions. Separate totals, users, and conversions rather than treating them as interchangeable.
  </Step>

  <Step title="Inspect platform mix">
    Review which recognized AI referrers are associated with each landing page and whether one source dominates the total.
  </Step>

  <Step title="Add page context">
    Compare citation URLs, crawler observations, and page purpose separately to form hypotheses about the traffic pattern.
  </Step>
</Steps>

## Interpretation

A leading page is a frequent landing page for recognized AI referrals in the selected analytics dataset. It is not necessarily the most cited page, the best-converting page, or the page that caused the referral. A recorded citation does not confirm a click.

## Possible next actions

* If a high-traffic page has weak engagement, test whether its content and call to action match the incoming audience need.
* If a strategic page receives no recognized AI referrals, verify URL grouping and referrer availability before changing content.
* If one platform dominates, test platform-specific landing-page and answer context rather than generalizing across providers.

## Limitations

Referrers may be missing or stripped, and analytics settings can change counts. URL parameters, redirects, and canonicalization can split page totals. Qwairy observes only connected data and cannot reconstruct every AI-assisted visit.

## Related pages

<CardGroup cols={2}>
  <Card title="Source URLs in Looker Studio" href="/looker-studio/sources/source-urls">
    Analyze URL-level data using the documented source.
  </Card>

  <Card title="Page Performance" href="/documentation/measure/page-performance">
    Review per-page product context.
  </Card>

  <Card title="Exports" href="/documentation/workspace/exports">
    Export the filtered dataset.
  </Card>

  <Card title="Websites influencing answers" href="/use-cases/sources/which-websites-influence-ai">
    Analyze recorded citations separately.
  </Card>

  <Card title="Pages cited by AI" href="/use-cases/sources/pages-with-most-ai-citations">
    Compare citation URL observations.
  </Card>

  <Card title="Is AI driving traffic?" href="/use-cases/impact/is-ai-driving-traffic">
    Assess referral traffic and attribution.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.