Search Console says five clicks. Your analytics report shows three sessions. Before calling the difference two lost visits, check what each system counted.
Count the right thing
A Search Console click records an interaction with a Google Search result under Google’s counting rules. An observed landing means your measurement setup recorded the arrival. A session groups activity according to your analytics tool’s rules. These are different units, not interchangeable names for a visit.
Walk through five clicks
In this synthetic example, two clicks lead to observed landings in session A. Two more start distinct sessions B and C. The fifth has no observed landing in the fixture. We do not know whether the visitor arrived. The counts are five clicks, four observed landings and three sessions. The difference of two between clicks and sessions is not a count of missing arrivals.
# Synthetic example. None means arrival was not observed.
clicks = ["A", "A", "B", "C", None]
landings = [session for session in clicks if session is not None]
counts = (len(clicks), len(landings), len(set(landings)))
assert counts == (5, 4, 3)
print(*counts)
5 4 3
Compare the same pages
Search Console generally assigns page data to the canonical URL Google selects. Analytics can report the URL on which a session actually started. A redirect, a language variant or a query string can split the landing report differently. Check Google’s selected canonical and the actual destination. Keep the original URLs before grouping verified equivalents; do not erase query parameters that change the page.
Align the reporting window
Compare complete days and record both time zones. Search Console’s standard Performance report labels days in Pacific Time; an analytics property can use a different zone. A click near midnight can land in a different daily bucket. Also match the property scope and search type. For this comparison, use Google organic web search rather than all organic traffic, and check whether each export is complete.
Investigate a change, not a ratio
First compare trends for the same URL group and complete reporting window. If the gap changes abruptly, look for a dated change in redirects, consent, tags or classification. Use an approved test visit to verify the destination and the event that your tool actually receives. Keep unknowns unknown: aggregate Search Console data cannot identify which individual click lacked an analytics event.
