Pages to improve this month
Combine Search Console and Analytics, find pages losing traffic or revenue, and see what to do first.
How to use
- Review total revenue and its change.
- Open the page list: the first rows offer the greatest impact.
- Open the hint below the page address and follow the recommendation.
| Source / medium | Total users | Engagement | Key events | User conversion |
|---|
| Page▾ | Google Search Console GSC | Google Analytics GA4 | ||||
|---|---|---|---|---|---|---|
| Clicks | Impressions | CTR | Position | Visits | Actual revenue | |
Where revenue comes from
Additional detail: monthly trend and each channel's contribution.
GA4 sessions vs GSC clicks: why the two numbers never match
Search Console counts clicks on a Google result. GA4 counts sessions — visits that group events on the site. They are different objects, so the two numbers never match, and chasing equality is a waste of time.
Seven mechanisms create the gap — the session window, other search engines, the tag, redirects, time zones, thresholds and URL parameters. The full answer: Search Console vs Google Analytics.
The practical rule: GA4 sessions usually run below GSC clicks, and that is fine. What matters is not the gap but its stability — a sudden change in the ratio means the measurement broke, not the traffic.
How to compare Search Console clicks with GA4 sessions
- Connect your Google account and pick the Search Console property and the GA4 property for the same site.
- Set the period. Compare like with like — week against week or month against month, not 7 days against 28.
- Run the report: pages are matched by URL, putting clicks, impressions and position from GSC next to sessions, engagement and key events from GA4.
- Look for pages where the ratio breaks the pattern: many clicks and almost no sessions is a measurement question; many sessions with weak engagement is a page question.
Next: pull a wider slice with the Search Console export, and find pages with weak CTR at a normal position with CTR Lens.
Next step