Search Console position or GA4 organic conversions: what do you trust for SEO?

Average position from Search Console misleads more often than it helps in reports. It's impression-weighted, so if you start ranking for a bunch of new long-tail queries at position 30, the average can drop even while clicks and conversions go up. And a page moving from 12 to 8 on a query with 10,000 impressions can matter more than a jump from 40 to 5 on a query nobody searches.

GA4 has its own problems. Organic conversions depend on the channel grouping, last-click or data-driven attribution, and how much traffic lands as direct because of missing UTMs or dark social. So the two sources can disagree for perfectly legitimate reasons.

What works for me as a default is putting clicks and conversions by landing page in the headline and using position only as a diagnostic for specific queries. The part I'm less sure about is when GA4 shows organic conversions falling while Search Console clicks look flat. How do you decide which source to believe when they split, and how big a gap would make you check tracking before blaming the content?

Agreed that average position makes a poor headline, but I'd push it further: GA4 and Search Console aren't measuring the same thing, so the first check is whether they're even counting the same visits.

Search Console clicks come from Google's own logs. GA4 organic sessions depend on the browser loading the tag, on consent choices, and on the referrer surviving redirects. On a shop, the usual breakage is at checkout, where a payment provider or a cross-domain hop strips the referrer and the session gets reclassified as direct.

So before arguing over which number to trust, run this for the last 16 weeks, per landing page. Divide GA4 sessions with source/medium google/organic by GSC clicks for the same page and dates, then plot that ratio.

A gradual drift usually means a real change in demand or rankings. A sudden step, especially on a specific date, usually means something changed in your setup: a GTM publish, a consent banner update, a new domain or subdomain. If the ratio is stable but conversions fall, look at the checkout path and purchase event deduplication before touching content.

Position is still useful, but only per query and only for queries whose impressions held steady. Otherwise the query mix is doing the moving.

The ratio check is the right first step, but for local services the denominator is the weak spot. A clinic or plumbing firm often converts through a phone call that starts on the Business Profile listing, not on a landing page. GA4 organic sessions and GSC clicks both miss that path, so a falling GA4 organic conversion line can mean real demand is moving into the map pack and calls while the site looks flat.

I'd add the Business Profile as its own line in the comparison: calls, direction requests and website clicks from the listing, over the same 16 weeks. Use separate call tracking numbers for the website and the listing too, so a call from a service page doesn't get lumped in with one from the map.

For the step-change test, look at how widespread the drop is. If the ratio falls across every page on the same date, suspect measurement, like a tag change or a consent update. If only one template or directory moves, the problem is probably your setup on those pages.

Check the Search Console side before you build the ratio. The Performance report lumps all search types together by default, so Discover and Google Images clicks land in the same totals. Discover can swing hard on a single article, and those visits may show up in GA4 under a different channel or as a referral, depending on your rules. A page whose clicks rose because of Discover will look like a conversion problem in the ratio. Filter to the Web search type first, then compare.

Marco, I like the separate call numbers, but calls from the listing only reach your reporting if you import them somewhere. If they don't, your 16-week comparison is a site line against a line the stack can't see, and the "falling" GA4 line may just be a measurement gap rather than demand moving to the map pack. A quick test: see whether listing call volume changed on the same dates as the GA4 drop.

Also, Search Console data from the last two or three days is still settling, so don't read a fresh dip as a step change until it stops moving.

Kai, fair point on the call imports, and it undercuts how I framed this earlier. GBP visits can also skew the ratio in the other direction. A website link in a Business Profile is a Google referral, and GA4 often files it under google / organic even though Search Console never counts it as a search click. So a page can look like it converts better in GA4 than GSC supports, because some of its "organic" sessions actually came from the map pack.

An easy way to check is to add a UTM to the listing's website URL, something like utm_source=google&utm_medium=business_profile. Then in GA4, split out the sessions with that medium before you build the ratio. If GBP sessions are a big share of a page's google / organic traffic, the denominator problem is bigger than the tracking problem.

Also look at which page the listing's website URL points to, and whether it's one of the pages you're comparing. A clinic that links the homepage sends most of that traffic to a single page, and that can distort a per-page ratio.

Marco, the UTM tag does more than split the data. GA4's default Organic Search channel matches medium "organic", so a link tagged utm_medium=business_profile drops out of google / organic the day you add it. That means it filters new traffic as well as helping with diagnosis. Put the date in your annotations, otherwise the organic line will look like a measurement break.

Two things to check before you trust the split. Click the listing link in DebugView and confirm the session shows up under a different source/medium row. Then make sure the UTM survives any redirect on the target URL, because a 301 that drops the query string sends those visits straight back into google / organic.

I'd also run the per-page ratio on the period before the tag existed. That shows how much of each page's "organic" traffic came from the map pack, and that's the number you actually need before you change anything.

Jun, the tag fixes the split going forward, but the pre-tag baseline is still muddy. Map pack visits were sitting in google / organic before the change, so the before and after ratios aren't directly comparable and you can't just subtract the new sessions. Honestly I'd treat the old period as a range for those pages, not a single number.

Do you know which pages the listing URL pointed to before the tag, and whether any of them already had an unusually high GA4 to GSC ratio?