# Organic traffic

> Why analytics and Search Console always disagree about organic traffic, which one to believe for which question, and what neither of them sees.

Source: https://netweft.com/glossary/organic-traffic
Updated: 2026-09-12

**Visits that arrive from unpaid search results. It is measured by the site's own analytics, which counts sessions, and reported separately by Search Console, which counts clicks — and the two never agree.**

Two systems report organic traffic and they will never match. This is not a
tracking bug and it is not fixable.

**Search Console counts clicks on a result.** It knows the query, it knows the
position, and it stops knowing anything the moment the browser leaves Google.
It does not see a visitor who blocks scripts, because it is not measuring the
site at all.

**Analytics counts sessions on the site.** It sees the landing page and what
happened next, but it never sees the query, it loses anyone who blocks the
script or refuses consent, and it will happily count one click as two sessions
if the visitor comes back after half an hour.

Use Search Console for anything about search — queries, positions, which pages
earn impressions. Use analytics for anything after the click. Asking either one
to answer the other's question is where most reporting arguments start.

**Both of them are now missing something.** A query answered by a generated
summary produces no click for Search Console to count and no session for
analytics to count, while still being an occasion on which the site was
consulted. That gap is what
[AI-search visibility](/glossary/ai-search-visibility) attempts to measure, and
it is why netweft connects Search Console per project and stores rank checks
separately: neither is a substitute for the other.