Google Search Console vs Google Analytics: what each one knows
You use both. Search Console shows the results page: queries, impressions, clicks, positions. Google Analytics 4 shows your site after the click: sessions, pages, events, conversions. Here is how to read them together and not chase ghosts when numbers disagree.
By Théophile Louvart, founder of Porteur · Updated 13 September 2026 · Markdown
What each tool actually knows
Search Console is pre click. It measures how your pages show and get clicked on Google Search. It reports queries, pages, impressions, clicks and average position. It also covers indexing, sitemaps, Core Web Vitals and enhancements. It does not know what users did on your site.
Google Analytics 4 is post click. It measures sessions, pages, events and conversions on your site. It is event based. It does not see the search queries that led to the visit. It can show the source as google or organic, but not the exact query in reports.
So, Search Console answers which searches show and click your pages. Analytics answers what those visitors did next. Use both for the full picture.
Why impressions rise without clicks
An impression is your page seen on a results page. It may be far down and never clicked. If you broaden coverage or rank on more variants, impressions go up first. Clicks lag until positions and snippets improve.
Example: you ship /guides/getting-started. It ranks at average position 18 for “your product tutorial”. You see 9,000 impressions and 40 clicks in 28 days. That is normal for page two. Fix the title and add internal links. Aim for striking distance terms at positions 11 to 20 first.
Why Search Console and Analytics never match
- Different clocks: Search Console uses search event time. Analytics uses session time on your site.
- Different units: clicks vs sessions. One person can click twice. One session can include many pageviews.
- Filtering and consent: Analytics can miss users who decline consent or block scripts. Search Console still counts the click.
- Attribution rules: Analytics groups events into sessions and channels. Direct may override organic when users return.
- URL differences: tracked page in Analytics may differ from indexed URL in Search Console after redirects or parameters.
- Sampling and thresholds: both protect privacy in edge cases, so small numbers can be hidden or rounded.
Expect gaps, not equality. Look for trends and direction, not one to one matches on a day. Compare at the page level over 28 days or longer for signal.
What to read in Search Console
- Performance report by page: which URLs get impressions, clicks and positions.
- Performance by query: which searches drive clicks, and which sit at positions 11 to 20.
- CTR by query: where your result shows but underperforms for its rank.
- Countries and devices: splits that can hide wins or losses.
- Position change: pages that moved up or down in the last 28 days.
Example: /pricing has 3,200 impressions, 64 clicks, average position 9.2, CTR 2.0 percent. That CTR is weak for a first page term. Improve the title and meta description to match the query intent. Add review snippets only if they are valid and earned. A fixed page will read position 7.8, CTR 4.5 percent, and more clicks in the next 28 days, a typical direction, not measured.
Also check indexing and Core Web Vitals. If your LCP on mobile is above 2.5 seconds or CLS above 0.1, fix speed first on the slow templates. Slow pages bleed clicks and conversions after the visit too.
What to read in Google Analytics 4
- Traffic acquisition: organic sessions and users trend, not raw click counts.
- Landing pages: which URLs start sessions and what their engagement rate and conversions are.
- Events and conversions: signups, checkouts, demos. Tie them to landing pages.
- Page value proxies: session duration, scroll or key actions on /pricing, /signup and docs.
- Geo and device splits: does mobile organic underperform on conversion vs desktop.
Example: /guides/getting-started starts 500 organic sessions in 28 days with 3.2 pages per session, but 0.2 percent conversion to signup. Add a clear CTA block and an inline signup widget. In the next 28 days you want to see similar sessions but a higher conversion rate on that page’s cohort.
Join them by page, step by step
Pick a landing page
Choose one URL that matters, for example /pricing or /docs/integrations/slack.
Pull Search Console for that page
Open Performance, filter by Page equals that URL. Note impressions, clicks, average position, top queries for the last 28 days.
Pull Analytics for the same URL
Open Landing pages. Filter to that path. Note organic sessions, engaged sessions, conversions for the same 28 days.
Compare direction, not totals
Clicks will be greater than sessions in many cases. Judge if more impressions led to more sessions and if conversions moved with them.
Write one action
If position is 12 to 15, plan on-page fixes and internal links. If position is 3 to 5 but CTR is low, fix title and snippet. If traffic is fine but conversions are weak, fix the page UX.
Recheck in 28 days
Repeat the same filters and windows. Log changes and outcomes by page in a sheet.
This pairs the search demand to on site outcomes. It avoids arguing about totals and focuses you on decisions per page.
Typical mismatches and what to do
| What you see | Likely cause | What to check | Action |
|---|---|---|---|
| Search Console clicks up, Analytics sessions flat | Consent or blocking reduces tracked sessions | Consent banner, tag firing, ad blockers on your audience | Server side or consent mode setup, ensure pageview fires on first load |
| Impressions surge, clicks flat | New coverage at low positions | Average position and query mix | Improve internal links, titles, and add intent matching content |
| Clicks up, conversions down | Wrong audience or intent mismatch | Landing page content vs query terms | Adjust copy, add next steps, split by query theme |
| Analytics organic sessions up, Search Console clicks flat | Brand navigations or non search sources counted as organic | Channel definitions and query mix | Tighten UTM use, check brand vs non brand in Search Console |
| Search Console shows clicks to a URL you do not track | Redirects or parameter variants | Index coverage and canonical, Analytics page path normalisation | Consolidate URLs, set canonical URLs, update Analytics filters |
| High CTR but low time on page | Snippet promises more than the page delivers | Landing page content depth | Add the answer above the fold and clear next actions |
Which to use for which decision
- Find what to write next: Search Console queries and positions. Spot striking distance terms at positions 11 to 20.
- Fix a falling page: Search Console position trend and CTR, then Analytics landing page conversions.
- Judge SEO impact: Analytics conversions from organic on the changed pages only.
- Debug indexing or drops: Search Console coverage, sitemaps and enhancements.
- Prioritise speed fixes: Search Console Core Web Vitals by page template, then validate in PageSpeed Insights.
You will spend more time in Search Console when planning content and snippets. You will spend more time in Analytics when improving signup and checkout flows. Switch based on the question in front of you, not habit.
A worked example with /pricing
You run yourproduct.com. /pricing matters. In Search Console, the page shows about twelve thousand impressions and 180 clicks, average position 8.4, CTR 1.5 percent in 28 days. This is a typical illustration, not measured. Top queries are “yourproduct pricing”, “yourproduct cost”, “yourproduct plans”.
In Analytics, /pricing starts 150 organic sessions, 70 engaged sessions, 9 signups. Conversion rate from this landing page is 6 percent. The clicks to sessions ratio is roughly one to one, given consent loss and bounces. Focus on CTR first, because position is already on page one.
- Change title to “Pricing for YourProduct: simple plans”. Keep under about 60 characters.
- Tighten meta description to state the plan names and free trial.
- Add internal links from /features and top docs to /pricing.
- Add a comparison table higher up so users see value fast.
Recheck in 28 days. You want CTR closer to peers at that rank. If CTR rises and sessions rise but signups stall, shift to the on page offer and proof. If CTR does not move, revisit the title against the exact queries from Search Console.
Side by side
Google Search Console
search.google.com/search-console
Seeing search performance and index status on Google, pre click.
Good at
- Queries by page and page by queries
- Impressions, clicks and average position
- Coverage issues, sitemaps, enhancements
- Core Web Vitals by URL and template
Choose it when You need to know how Google shows and clicks your pages, which queries you rank for, and what to fix to be indexed and eligible.
Not for On site behaviour, sessions, events, conversions, or non Google search engines.
Google Analytics 4
analytics.google.com
Measuring on site behaviour after the click with an event based model.
Good at
- Sessions and engaged sessions
- Pages and user journeys
- Events and conversions
- Channel level acquisition trends
Choose it when You need to understand what organic visitors do on your site and how that turns into signups, checkouts or other goals.
Not for Search queries, impressions, ranking positions, or indexing on Google.
Use both. Plan content and SERP improvements in Search Console. Measure product and conversion outcomes in Google Analytics 4. Compare them by landing page over 28 days, not by daily totals. When the question is “which searches should we target”, open Search Console. When the question is “did those visitors convert”, open Analytics.
Questions
Yes. As of 2026, Search Console is the main way to see your site’s search performance and indexing on Google. It is free. It reports pre click data such as queries, impressions, clicks and positions.
Yes, for outcomes. Use Analytics to see sessions, engagement and conversions from organic. Use Search Console to find queries and positions. Plan in Search Console, measure business impact in Analytics.
It is accurate for trends and for its own definitions. It counts clicks on search results, not your site sessions. Small numbers can be hidden for privacy. Expect differences by a few units when compared to on site tools.
Google Analytics 4 replaced Universal Analytics. GA4 is event based. If you used UA before, expect different reports and session logic. Search Console did not change to match it, so the two still do not align.
You can view Search Console landing page data in Analytics when linked, but it does not make the numbers match. Use the link to see search metrics next to site metrics. Still do page level checks in each tool.
A click may bounce before your script loads. Consent may block tracking. One person can click twice and start one session. Date and device filters may differ. Align the window and compare trends by page.
Sources
Check my site, free
Paste your homepage URL to get a free check that reads your site and rivals on your searches in about thirty seconds and shows three findings whole.
- Free check, no card
- Read-only, your own accounts
- Readable by your agent
Read next
- GuideHow to use Google Search Console in ten minutes a week
- GuideThe Search Console performance report, column by column
- GuideWhat an impression means in Search Console, and what it does not
- GuideWhat is a good click-through rate in search, by position
- GuideLanding page SEO: one page, one search, one promise
- GuideWebsite conversion rate: from the visit to the signup
- GuideThe Search Console API: pull your own search data
- GuideLinking Search Console to GA4: what you get and what you do not