Where did the referral actually land?

Separate platform concentration from page quality. Every metric comes from the CSV in this browser.

Aggregate referral rows

Synthetic sample loaded7 required columns

Landing-path evidence

NOT RUN

-AI SESSIONS

TOP PLATFORM SHARE

-SEARCH LEAKAGE

-SEARCH CONVERSION

-DIRECT CONVERSION

-LARGEST MONTHLY SWING

SESSION ROUTING BY LANDING CLASS

Run the sample to expose the conversion-gap equation.

Parser ready

Traffic is only the first handoff.

Platform share tells you where visits originate. Landing leakage tells you whether the system found the right page. Conversion yield tells you whether the site finished the job.

Classify before comparing

Internal search is an input category, not an inferred URL pattern. Map your export deliberately.

The gap is descriptive

Applying the direct-page rate to search sessions is a scenario, not proof that routing caused the difference.

Watch monthly concentration

A large referral source can move sharply after a platform change. Keep SEO and first-party acquisition visible beside it.

AI Referral Landing Audit Explainer

Your browser does not support video.

Read the explanation

AI referral traffic often drops visitors onto generic internal search results rather than target conversion pages. When you click Run audit, the tool digests your raw referral rows locally. In this synthetic sample, internal search detours account for 44.4 percent of traffic, converting at just two percent compared to over eleven percent on direct landing pages. The engine computes your modeled conversion gap by multiplying that rate difference across all search sessions, revealing unrealized potential before you export evidence.