Your Search Console report shows clicks to a guide. That tells you people reached it from Google Search. What happened after they arrived?
Use the landing page report in Google Analytics 4 (GA4) to look at visits that started on that guide. Filter for Google organic search, then review engagement and any actions you have actually configured to measure. The result is a short list of pages to inspect, not a verdict that a page is good or bad.
Start with the right question and date range
Choose one question: Which pages bring people from Google Search, and what do those visitors do next? Set a complete date range and record it. If the site has only a handful of visits, use the report to find pages to inspect. Do not rank pages by tiny differences in engagement or key events.
Open Reports → Engagement → Landing page in GA4. If the report is not in your navigation, use the report search or ask someone with report-editing access to locate it. A landing page is the first page viewed in a session. Google's Landing page report guide explains that the report is session-scoped: the same person can start separate visits on different pages.
The Pages and screens report answers a different question: it can include pages people viewed after they entered the site. Here we need the page where the visit began.
Limit the report to Google organic visits
The default Landing page report can include email, direct, social and
other traffic. Google's help page says you can add Session
source / medium as a secondary dimension to see the source for
each landing page. For a Google Search review, focus on
google / organic. If your interface supports a report
filter, filter on those session values and keep a note of the exact
filter. Google's
Search Console and Analytics guide.
Why be this precise? GA4's Organic Search channel
can include more than Google Search. Google's own comparison guide uses
Session source = google and
Session medium = organic when examining Google organic
visits. If your goal is all search engines, use Organic Search
and label the review accordingly. Default
channel definitions.
If you use both a channel filter and source/medium, check that the resulting rows match the audience you intended. Keep the same filter when you compare periods.
Read three signals together
Export or record the landing page, sessions, average engagement time per session, and key events if you have set them up. Average engagement time per session is one of the metrics Google lists for this report. A key event is an action your GA4 property has been configured to mark as important. For a service site, it could be a confirmed enquiry or booking; a button click alone may say less about an actual prospect. If no suitable event exists, write not measured. Do not interpret zero as proof that nobody enquired. Google's Landing page report lists these metrics and their setup requirements.
GA4 can only count visits and key events when its tag runs; consent choices can leave some visits unrecorded. On seowithvishnu.com, the analytics tag loads only after a visitor chooses Allow analytics, so this site's GA4 counts understate visits. The Search Console and GA4 discrepancy guide explains the measurement gap.
Read the row as a prompt to investigate:
| Observation | What to inspect next |
|---|---|
| Visits arrive, but average engagement time per session looks low | Read the first screen on a phone. Does it answer the searcher's task and make the next step clear? Check traffic mix and the sample size before rewriting. |
| Visitors spend time on the page, but a useful next action is not measured | Check whether the page has a relevant next step and whether the event fires under the site's consent settings. Measurement needs checking before naming a conversion problem. |
| A page has few or no recorded Google organic sessions | Check its Google Search visibility in Search Console and whether GA4 tracking is working. The GA4 row alone cannot tell you which is responsible. |
For a fictional example, imagine an SEO consultant's guide to choosing a canonical URL and a service page about technical audits. The guide may bring visitors who need a quick answer; the service page may attract fewer, more specific enquiries. Comparing only average engagement time would hide the different jobs of those pages. First decide what each page is meant to help a visitor do, then check whether the page and your measurement support that job.
Use Search Console for the question GA4 cannot answer
GA4 tells you about recorded on-site visits. Search Console tells you how pages appeared and were clicked in Google Search. If a page has little GA4 traffic, check its Search Console pages and queries before assuming the content failed. Clicks and sessions will not match exactly. When you need a third, different count, see Google Search referrers in server logs and inspect the landing-page request.
My recommendation is to leave GA4 sessions out of a Search Console click-through-rate calculation. The tools have different scopes and counting rules. Google's comparison guide identifies Search Console as the source for search performance and Analytics as the source for behaviour on the site; it also advises matching filters when comparing the two.
If the page is visible in Search Console but the landing-page experience seems weak, use the one-page improvement guide to inspect the opening, task fit and next step. If the page is scarcely visible, first diagnose discovery, indexing or query fit. A fresh call to action will not solve an indexing problem.
Leave with one page-level decision
For each page you review, write four lines:
- Audience: Google organic visits, or all organic search visits? Include the exact GA4 filter and date range.
- Observation: What did GA4 record? Is the count large enough to compare meaningfully?
- Cross-check: What does Search Console show for the same page and a comparable complete period?
- Action: Improve a reader-facing gap, repair measurement, investigate search visibility, or watch until more evidence arrives.
Change one thing you can explain and record when it went live. Compare complete periods later, allowing for low volume and changes in traffic mix. If you want help prioritising pages and checking the measurement, book an SEO consultation.
Google Analytics and Search Console documentation reviewed 13 November 2026. The consultant example is fictional; no results for this site or a client are claimed. This site's GA4 counts understate visits because the tag loads only after consent.
TAKE THE NEXT STEP
Put the questions to work.
Use the free content audit planner or discuss a focused review of one important page.
Need help with a wider search challenge? Explore SEO consulting.
