Know which searches bring you clicks, not just where you rank.

What did people type before they found me?

Search Console answers that, and the view reads it for any window you pick. Choose the last 7, 30 or 90 days, 6 months or 12 months, or set your own dates. Every window ends yesterday, because today is a partial day in every Google source and a half day at the edge reads as a collapse. Three tiles carry clicks, impressions and click-through rate. Under them sits a rankings table sorted best position first: query, rank, prior rank, change and searches. Lower is better, and inside ten is the first page. The table runs up to sixty queries. A query with fewer than three impressions in the window is left off, because a single stray impression is not a ranking. Below it sit the top fifteen queries by clicks, the top fifteen pages, and clicks by device and by country.

Compare against the previous period or the same period last year, or turn comparison off. Every row then carries its prior value, so a move in the change column is a real move and not the arrival of a new phrase; a phrase with no prior value is marked new. Average position is weighted by impressions, so a query seen two thousand times moves it far more than one seen twice. Click Export and the range you picked downloads as a CSV, with the comparison window beside it.

Clicks are the number that separates ranking from earning. A page can hold the top ten for a phrase and send you nobody, and a position chart on its own reads that as a win. So the table carries clicks beside every position, the tiles carry clicks, impressions and click-through rate together, and the leads your own forms recorded sit on the Leads view beside all of it. A position here is Search Console's average for the query on your own property rather than a rank tracker's guess.

Google releases this data two to three days after the searches happen, and the view says so. A note on the view reads that the most recent days in the range are still filling in, so an empty right edge on the chart is Google's lag, not a drop in traffic. Appearances in Google's AI Overviews are measured here, through Search Console, not on the answer-engine view.

How do I compare with the companies I lose jobs to?

Where market data is enabled for your account, the view adds the wider keyword market: the phrases your trade competes on, your rank on each, searches a month, a difficulty score out of 100 and the page that ranks. Rising here means people who have never heard of you finding you. Click a row for the detail.

Three competitive tables sit beneath it. Ranking movement lists up to six keywords you gained and four you slipped on, with the change in places, so repeated losses on one topic say where to reinforce. Competitor keyword gaps list the phrases a competitor ranks for and you do not yet, with who ranks and where; each gap is a page or post your team can build. Competitor paid keywords list what nearby companies pay Google for, with an estimated cost per click, a demand signal your team weighs for your own campaigns or aims organic content at.

This is a paid data layer from a third-party provider, refreshed on a 24-hour cache, and it renders only where your account enables it. When a cycle brings no movement, the table says so instead of showing an old move. The search view itself is on all tiers.

What should I check in the demo?

Open demo.trulata.com. It opens straight away, with your name and email to open it. The company is fictional and every number is illustrative, but the engine code is the same code every client instance runs. Open the SEO view. Click a keyword row: the detail opens with position, change, volume and the page that ranks. Click Export in the top bar and the table downloads as a CSV. The Google reviews card, the keyword market tables and the Search Console range picker are not in the demo. On a live account each renders only when its source is connected or its layer is enabled, so an absent card is honest, not broken.

Then hold it to the ceiling. The position column is Search Console's average position for your pages in Google's web results, Google's own count across every appearance in the window rather than a single daily check. Search Console runs two to three days behind, and volume is Search Console impressions in the window, so it carries the same lag. Organic sessions come from GA4 and run hours behind. The Refresh button starts a new pull, from 2 seconds to a little over 3 minutes, and reloads the page when the stamp moves. Every path through it ends in a reloaded page, and the two-to-three-day release of Search Console data stays Google's. The header stamp says when the data was pulled.

Every click on this view reads or requests. The write paths from the screen are a keyword, content or targeting request to your team, logged, and a website change request, also logged; the change itself is made through your site's, your listing's or your ads account's own API and lands in its history. The security page lists every write path.