How to combine Google Analytics and Search Console data
By the Analistable team · Updated · 5 min read
Search Console knows queries, impressions and clicks; GA4 knows sessions and conversions. Join them on the landing page: Search Console reports full URLs (https://example.com/pricing), GA4 reports paths (/pricing), so strip the domain first. GA4's built-in Search Console link shows both by landing page, but to connect queries to conversions you need to join exports yourself.
Part of our guide: How to join spreadsheets on a common column
What each tool can tell you
| Search Console | GA4 | |
|---|---|---|
| Unit | Clicks and impressions in Google Search | Sessions, users, events on your site |
| Search queries | Yes | No |
| Conversions / revenue | No | Yes |
| Page identifier | Full URL | Landing page path (+ query string) |
| Data retention | 16 months | Depends on property settings; reports keep aggregated data |
Option 1: GA4's built-in Search Console link
In GA4 Admin → Product links → Search Console links, link the property. Then in Reports → Library, publish the Search Console collection. You get two reports: Queries (Search Console metrics by query) and Google organic search traffic (Search Console clicks next to GA4 engagement and conversions by landing page).
The limit: queries can't be combined with GA4 metrics in these reports. You can see which pages convert and which queries get clicks, but not which queries lead to conversions.
Option 2: join the exports
- In Search Console, open Performance, set the date range, open the Pages tab and export. (The interface exports up to 1,000 rows; use the API or the BigQuery bulk export for more.)
- In GA4, open Reports → Engagement → Landing page, filter Session default channel group = Organic Search, set the same date range and download the CSV.
- Clean the key: in the Search Console sheet, add
=REGEXREPLACE(A2, "^https?://[^/]+", "")(Google Sheets) or, in Excel,=MID(A2, FIND("/", A2, 9), 500)to turn the URL into a path. - Join on the path with XLOOKUP or Power Query Merge.
| Landing page | GSC clicks | GSC position | GA4 sessions | GA4 conversions | Conv. per 100 clicks |
|---|---|---|---|---|---|
| /pricing | 1240 | 4.1 | 1105 | 62 | 5 |
| /blog/merge-csv-files | 3810 | 6.8 | 3392 | 21 | 0.6 |
| /tools/compare-spreadsheets | 950 | 9.3 | 861 | 34 | 3.6 |
Sessions are lower than clicks partly because of consent and ad blockers, and because a click and a session are counted differently. Compare ratios between pages rather than expecting the numbers to match.
Estimating conversions per query
Export queries with pages from the Search Console API (dimensions page and query). For each page, share its GA4 conversions across its queries in proportion to clicks:
=XLOOKUP([@Path], GA4[Landing page], GA4[Conversions], 0) * [@Clicks] / SUMIFS([Clicks], [Path], [@Path])It's an estimate — it assumes every query converts at its page's average rate — but it ranks queries by likely business value far better than clicks alone.
URL details that break the join: trailing slashes (/pricing vs /pricing/), upper-case letters, and query strings in GA4's “Landing page + query string” dimension. Normalise both sides the same way.
| Query | Clicks | Share of page clicks | Estimated conversions |
|---|---|---|---|
| spreadsheet merge tool pricing | 700 | 56.5% | 35 |
| merge excel online cost | 400 | 32.3% | 20 |
| combine sheets tool price | 140 | 11.3% | 7 |
| Total | 1240 | 100% | 62 |
The estimates always add back up to the page's GA4 total, which is a quick check that the SUMIFS denominator covers every query row for that page. Expect the query export's clicks to sum to less than the page export: Search Console leaves anonymised queries out of query-level data, so share conversions across the queries you can see and treat the result as a ranking, not an exact count.
Normalising URLs on both sides
| Problem | Search Console value | GA4 value | Normalised key |
|---|---|---|---|
| Protocol and domain | https://example.com/pricing | /pricing | /pricing |
| Trailing slash | https://example.com/blog/ | /blog | /blog |
| Upper case | https://example.com/Guides/Join | /guides/join | /guides/join |
| Query string | https://example.com/pricing | /pricing?plan=team | /pricing |
| Fragment | https://example.com/faq#refunds | /faq | /faq |
In Google Sheets, one formula handles most of these: =LOWER(REGEXREPLACE(REGEXREPLACE(A2, "^https?://[^/]+|[?#].*$", ""), "(.)/$", "$1")). It removes the domain, any query string or fragment, and a trailing slash except on the home page /. Apply the same steps to GA4's landing page column. If you track several hostnames (www and non-www, or subdomains), keep the hostname in a separate column so pages with the same path on different sites don't merge.
Doing the join in Power Query
- Load both exports with Data → Get Data → From File → From Text/CSV (remove GA4's comment lines at the top with Remove Top Rows if present).
- In the Search Console query, add a custom column that strips the domain, for example
Text.AfterDelimiter([Top pages], "/", 2)prefixed with "/", then Format → lowercase and trim a trailing slash. - Apply the same lowercase and slash steps to GA4's landing page column.
- Home → Merge Queries with Search Console first, Left Outer, and expand Sessions and Key events from GA4.
- Save it. Next month, replace the two files with fresh exports of the same reports and click Refresh.
Column names in both exports vary by language and interface version, so check the header names in your files before writing the custom column. For general join mechanics see joining two tables in Excel.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Almost nothing matches | One side still has the full URL | Strip protocol and domain from Search Console URLs |
| Home page doesn't match | Slash removal turned / into an empty string | Only remove a trailing slash when the path is longer than one character |
| GA4 shows (not set) as a landing page | Sessions that started without a page view | Exclude it; it has no Search Console equivalent |
| Pages in GA4 but not Search Console | Traffic came from Discover, News or other engines in the Organic channel | Filter GA4 to source google, or accept the gap |
| Conversions look too high for a page | GA4 export not filtered to organic sessions | Add the Session default channel group filter before exporting |
Doing it without spreadsheets
Analistable connects to Google Analytics and Search Console and loads both reports into an in-browser database, so you can ask “which pages have high impressions but low conversion?” and get the joined table back. Related: finding pages that are losing clicks, merging GA4 with ad cost data and combining several GA4 properties.
Frequently asked questions
- Can I see Search Console queries in GA4?
- Yes, after linking Search Console in GA4 Admin and publishing the Search Console collection. The Queries report shows Search Console metrics only, not GA4 conversions.
- Why don't Search Console clicks match GA4 sessions?
- They measure different things: clicks in Google Search vs sessions recorded on your site. Consent banners, ad blockers and session rules all reduce GA4's count.
- How do I join GA4 and Search Console by URL?
- Strip the protocol and domain from Search Console URLs so they match GA4's landing page paths, normalise trailing slashes and case, then use XLOOKUP or a merge.
- Which date range should I use for both exports?
- Exactly the same dates in both tools, ending a few days ago because recent Search Console data is still being processed. Check that the GA4 property's time zone matches the dates you expect.
- Should I join on landing page or page path?
- Landing page. Search Console counts the page a searcher clicked to, which is the session's first page in GA4. Joining on all page views would credit pages visited later in the session.
- Can I get more than 1,000 rows from Search Console?
- Not from the interface export. Use the Search Console API, Looker Studio's Search Console connector or the BigQuery bulk export for larger sites.