Start with one landing page, not a site-wide total
A site-wide search click total can rise while the pages that matter to your business stay flat. To decide what to improve, start with one landing page and ask two different questions: are people seeing and clicking its Google result, and what happens after a visit reaches the website? Search Console and website analytics describe different stages, so their totals are useful side by side without being expected to match.
Google Search Console reports impressions, clicks, click-through rate (CTR), and average position for search results. WhoVisited records sessions and events that reach the tracker. In WhoVisited's Growth report, the Search Console integration requests page-level rows and shows impressions, clicks, CTR, average position, a previous-period comparison, and an optional website match. It does not import query rows or connect a search query to an individual visitor.
That boundary is useful: you can look for a page that deserves a content or measurement review without claiming that a particular Google query produced a signup. Google also assigns Search Console page metrics to its canonical URL for the result, which may differ from a URL variant a visitor eventually opens.
Read search visibility and on-site behavior as separate signals
- Impressions show that a search result link was shown under Google's counting rules. They are not page visits.
- Clicks count interactions with Google results. A click may not become a recorded website session if the page fails to load, tracking is blocked, consent is not granted, or the visitor leaves before an event is sent.
- CTR is clicks divided by impressions. Compare it with the page's average position and the previous period; neither metric alone explains why a result changed.
- Sessions and goal sessions come from activity collected on your site. A goal session contains the selected event or success-page signal; it is not automatically a unique person or completed order.
For example, imagine a synthetic pricing page with 1,000 impressions, 20 Search Console clicks, 15 recorded sessions, and 3 goal sessions. The figures suggest two separate checks: whether the result earns enough relevant clicks, and whether the arriving sessions find a path to the goal. They do not prove that the five-count gap is tracker loss or that the three goal sessions came from a particular query.
Use this sequence to choose the next page change
- Confirm the connected Search Console property belongs to the website you are reviewing. In Settings, verify the saved property and inspect the exact page URL in the Growth table.
- Find a page with enough impressions to make a comparison useful. WhoVisited's suggested check requires at least 100 current-period impressions; it flags zero clicks or a decline in clicks and CTR when the previous period also has at least 100 impressions. This is a review prompt, not a ranking diagnosis.
- Compare the current 28-day page row with the previous 28 days. If impressions are present but clicks or CTR are weak, inspect the search result title, snippet, and page intent. If impressions and average position are both low, check whether the page clearly answers a search need and whether Google can discover it.
- Then look at the Website match column. If sessions are present but goal sessions are low, inspect the page's next step, form or checkout flow, and whether the selected goal fires after a successful outcome.
- If Search Console clicks appear but the website match has no sessions, first verify the tracker on that landing page, the consent state, redirects, and the exact host and path. Treat the gap as a diagnostic clue, not a one-to-one reconciliation.
Change one thing at a time where practical, write down the page and hypothesis, and compare an appropriate later period. Search visibility can move for reasons outside a page edit, so keep the conclusion proportional to the evidence.
Know what WhoVisited means by a website match
The integration requests Google Search Console data grouped by page, not by query. For each page URL, WhoVisited checks that it belongs to the connected website and compares its HTTPS hostname with the website's allowed origin, including the supported www variant. It uses the URL pathname for the website match and ignores query strings and fragments. A trailing slash is normalized; path capitalization is not changed. A URL that cannot be matched is marked Separate instead of being forced into another page.
The matching sessions are grouped by landing path and the selected goal is counted at the session level. The displayed comparison is based on the saved Search Console date windows. Google defines those dates in Pacific Time, while website sessions are timestamped events; boundary differences and different collection rules mean the two systems remain directional context rather than an exact attribution join.
The integration shows up to 100 Search Console pages ordered by impressions and flags a response at Google's 25,000-row limit as partial. Google documents that the Search Analytics API may return top rows rather than every available row. A page missing from the table therefore does not establish that it had no search visibility.
Keep the conclusion useful and honest
Search Console can help you decide which page to inspect; WhoVisited can show whether sessions and selected goal events were recorded for its landing path. Neither system, as connected here, identifies which search query belongs to which browser or proves why a conversion changed. Use your product database for authoritative signup, booking, and payment totals, and use the paired page signals to plan the next investigation.
For the mechanics behind comparing the metrics, see the [guide to Search Console clicks and website sessions](https://whovisited.net/guides/search-console-clicks-vs-sessions). For the date freshness and saved-snapshot behavior in WhoVisited, see [why Search Console data can look stale](https://whovisited.net/blog/why-search-console-data-looks-stale).