Documentation
Blended report: Search Console and GA4 together
Join Search Console clicks with GA4 sessions, key events and revenue page by page, and estimate what each search query is worth to the site.
Blended (GSC + GA4) puts a site's Search Console and Google Analytics 4 numbers side by side: clicks, impressions, CTR and position next to sessions, engagement, key events and revenue. It joins Search Console pages to GA4 landing pages, so you can see what each ranking page does after the click, and it can estimate the sessions, key events and revenue behind each search query.
Organic traffic only, by default
The GA4 side opens on the google / organic segment, so it measures the same traffic as Search Console as closely as GA4 can. The segment is named under the Sessions card. You can change it with GA4 filters, to all traffic or your own source / medium list. The Search Console side follows the usual Search Console filters and date range, and the GA4 segment does not affect it.
The cards and the trend chart
Eight cards come first: Clicks, Impressions, CTR and Position from Search Console, then Sessions, Engagement Rate, Key Events and Revenue from GA4, each with its change against the comparison period. The Blended traffic trend draws Search Console clicks, GA4 sessions and GA4 key events (on the right axis) over the same dates, by day for ranges up to 90 days, by week up to 200 days and by month beyond.
The two lines should move together. When they part, look for a cause on one side: sessions falling while clicks hold steady is worth checking against recent changes to your GA4 tag or consent banner.
Blended landing pages
Click Load blended pages to run the join. It reads up to 25,000 rows from each side, which is why it waits for you. Every Search Console page and every GA4 landing page is reduced to its path: the host, query string and fragment are removed, the path is decoded and a trailing slash is dropped. Rows with the same path are added together and then matched.
| Match | Meaning |
|---|---|
| Matched | The path has Search Console data and GA4 sessions in the segment |
| GSC only | Search Console has data for the path, GA4 has no sessions starting there |
| GA4 only | GA4 has sessions starting on the path, Search Console has nothing for it |
Four cards count Matched pages, GSC only and GA4 only, and give Sessions per click across all rows. The table lists Page, Clicks, Impressions, CTR, Position, Sessions, Sessions / Click, Engagement, Key Events, Revenue and Match, with a tab for each status. It keeps the 5,000 paths with the most clicks and sessions combined and sorts them by clicks.
Why a page fails to match
- Canonical URLs. Search Console gives a page's clicks to the canonical URL Google chose for its duplicates, and a redirect after the click does not change which URL gets them (What are impressions, position, and clicks?). GA4 records the path the visitor actually landed on. Duplicates and redirected addresses can therefore appear as GSC only on one path and GA4 only on another.
(not set). GA4 landing pages recorded as(not set)cannot be joined and are left out.- Several hosts. Because the host is removed, a Domain property covering several subdomains merges pages that share a path, such as each subdomain's home page.
- Missing tag. A GSC only page with plenty of clicks may be a page where the GA4 tag does not load.
Query value attribution
Click Run attribution to estimate what each search query is worth. AutoPSEO reads Search Console's query-and-page rows for the period (up to 25,000) and, for every matched page, splits that page's GA4 sessions, key events and revenue between the queries that sent it clicks, in proportion to each query's share of the page's clicks.
For example, say a page had 100 clicks, 60 from "crm for startups" and 40 from "best startup crm", and GA4 recorded 90 organic sessions and 9 key events starting on it. The first query is credited with 54 estimated sessions and 5.4 key events, the second with 36 and 3.6. A query that sends clicks to several pages collects a share from each of them.
The table lists Query, Clicks, Impressions, Position, % of Clicks (its share of all clicks in the table), Pages (how many of your pages appeared for it), Top Page (the one with the most clicks), Est. Sessions, Est. Key Events and Est. Revenue, sorted by estimated sessions, up to 5,000 queries. Matched pages only hides queries whose pages could not be matched, since those carry no estimate.
What the estimate assumes
- Every click on a page is worth the same, whichever query it came from. A buying query and a research query that send equal clicks get equal credit.
- The queries Search Console lists for a page account for all of its clicks. When they do not, the queries that are listed share the page's whole result between them.
- The estimate covers the current period only, without a comparison.
Treat the figures as a way to rank queries by value, not as measurements. To track one key event exactly, use Key Events.
How AutoPSEO helps
AutoPSEO's content engine chooses what to write and when to refresh from Search Console data (Maintenance). Blended shows whether the visitors those articles bring stay, convert and buy, and the attribution table points at the queries worth a new or better page.