GA4 + Search Console Reporting: Turn Google's Data Firehose Into Weekly Decisions
Google Analytics 4 and Search Console are the most data-rich free tools in marketing, and most teams use maybe a tenth of them. Not because marketers are lazy; because both tools answer questions you have to already know to ask. GA4 will happily tell you engaged-session rates by channel; it will never volunteer that your best-converting landing page slipped off page one last Tuesday.
This is part two of The Connected Growth Stack. Here we get specific about the Google side: which numbers deserve a weekly look, how to read the two tools together, and how to turn Search Console's page-level data into a ranked to-do list instead of a wall of rows.
The GA4 metrics that actually matter weekly
GA4's biggest trap is abundance. For a weekly cadence, six numbers carry most of the signal: sessions and engaged sessions (volume and quality of visits), key events (the actions you actually care about), conversion rate by channel, average engagement time, and revenue if you're transactional. Everything else is diagnosis, not monitoring.
The channel split is where decisions live. A flat total can hide organic down 20% and paid up 20%; which is not "flat", it's a margin problem. In Lumetry's analytics board, every channel row carries its own period-over-period delta, so the redistribution jumps out before the total moves at all.
Reading GA4 and Search Console as one story
The two tools describe adjacent stages of the same journey: Search Console sees the SERP (impressions, clicks, position), GA4 sees what happens after the click (engagement, conversion). Divergence between them is diagnostic gold. Impressions up but sessions flat? You're gaining visibility on queries your titles aren't selling. Sessions steady but conversions down? The traffic is fine; the page or the offer changed.
Geography is another seam worth stitching. Search Console only reports by country, which is useless for a US-focused brand; GA4 tracks organic sessions by state. Read together, you get "our Texas organic traffic doubled after the Dallas press hit"; a sentence neither tool can produce alone.
The killer signal: pages losing impression share
Absolute impressions mislead. If your site's impressions grew 40% and a key page's impressions stayed flat, that page didn't hold steady; it lost ground. Impression share; a page's slice of the site's total impressions, tracked month over month; catches decay while it's still cheap to fix. It's the closest thing SEO has to an early-warning system.
This is the formula behind Lumetry's Search Console recommendations: every page is scored by estimated click upside multiplied by how fast it's bleeding share, so the list reads in work-this-first order. Pages ranking 11–20 with real impressions (one push from page one), page-one URLs earning half their expected click-through rate (title and meta problems), and utility pages are handled with separate rules so nobody gets told to rewrite the returns policy.
A 20-minute weekly ritual
Cadence beats depth. Twenty minutes, same time every week: scan channel deltas in GA4 (two minutes), check the top-priority recommendations on the Search Console board (five), read the one AI-generated brief that explains what moved and why (five), then turn the top two items into tickets (eight). That's the whole practice; the tooling's job is making those twenty minutes possible.
Next in the series: the commerce loop. Part three connects Shopify and Klaviyo so revenue, email and site behavior read as one funnel; and shows where the hidden money usually sits.
GA4 tells you what happened after the click, Search Console what happened before it. Read them together weekly, track impression share instead of raw impressions, and let a ranked recommendation list; not scrolling; decide what you fix first.