Skip to content
RankX AI
RankX AI Docs
Traffic

Traffic

What Google reports about your site through Search Console and Analytics, how it differs from RankX AI's own measurements, and why a figure can be refused.

Traffic is what Google reports about you: clicks, impressions, position and index coverage from Search Console, and sessions, page views and landing pages from Analytics. Both connections are read-only, and RankX AI never writes to either.

It is deliberately separate from Google Results, which is what RankX AI measures itself. A tracked position is RankX AI checking one keyword; Search Console's average position is Google's own aggregate across every query that produced an impression. The two measure different things, and reading them as interchangeable is the most common analytical mistake in this part of the product.

The four screens

ScreenWhat it answers
Traffic OverviewThe headline, both connections in one place
Search ConsoleWhich queries and pages, and how the totals are moving
Google AnalyticsSessions, page views, landing pages, and who is on the site now
IndexingWhich pages Google has indexed, and why the others are not

Two behaviours that matter more than the setup

Both refuse rather than reporting zero. A connection is in one of four states and only one yields figures. In the other three RankX AI shows a message naming the state and the remedy, because "no traffic" and "we cannot see your traffic" are different facts and only one is about your website. See why traffic data is missing.

Search Console publishes on a two to three day delay at source. The last day or two being absent is a healthy connection reporting honestly. RankX AI marks those days provisional, counts them separately, and never plots them as a decline. They will rise.

Why indexing is here

Clicks and impressions only exist for pages Google has already indexed. A page left out of the index is invisible in every other screen in this section: it looks exactly like a page nobody visits.

Indexing is the screen that closes that gap, and it is the one to check when a page you published is not showing up anywhere.

Reading Traffic against the rest of RankX AI

The sections answer different questions, and the interesting findings live in the gaps between them:

  • Ranks well, no clicks. Check whether an AI Overview is showing on those queries. Search Console's opportunities view measures the click difference where one appears, and refuses to conclude on a sample too small to support one.
  • Clicks falling, positions stable. Usually a change in what the results page looks like rather than a change in where you sit on it.
  • Traffic changed and nothing obvious explains it. Read the site timeline alongside it. It records what RankX AI changed and when, and it states plainly what it cannot see: an edit made directly in WordPress, a plugin update or a hosting incident is invisible to it.

Setting the connections up

Search Console and Analytics are connected in the Website's Integrations settings, with OAuth, read-only.

Dedicated setup pages for Search Console and Analytics are not published yet. They are written the day RankX AI's Google consent screen is published, because until then a connection has to be reauthorised on a short cycle, and documenting the setup without saying so would be a promise the product cannot keep. The connections work, the screens below are documented in full, and the four availability states are correct regardless.

Where to go next