Linking Search Console to GA4: what you get and what you do not

You get two GA4 reports that join Google organic clicks and impressions to your landing pages. You do not get Search Console data in every GA4 report, and you do not get per-user joins.

• Adds: Google organic search queries report. It shows queries, clicks, impressions, average position, and the landing page for that query.
• Adds: Google organic search traffic report. It shows landing pages with clicks, impressions, CTR, and blends in GA4 engagement and key events.
• Keeps: GA4 session and event data as is. Organic search visits still sit in the Organic Search default channel group.
• Keeps: Search Console lag and query anonymisation. You will not see every query and yesterday’s data can be partial.
• Does not add: user-level joins between a query and a later signup. GA4 reports here are page-level, not person-level.
• Does not change: attribution for key events. GA4 still defaults to data-driven, with first click and last click available in comparisons.

1. 1

   Check Search Console and GA4 admin access

   You need verified ownership in Search Console for your domain or URL prefix, and Editor or higher in the GA4 property.

2. 2

   Open Admin, then Product links, then Search Console

   In GA4, go to Admin. Under Product links choose Search Console. Click Link.

3. 3

   Pick the Search Console property

   Choose the site property that matches your GA4 data stream’s domain. Confirm the association.

4. 4

   Select the web data stream

   Pick the GA4 web data stream for your site. Save the link.

5. 5

   Publish the reports to your Library

   Go to Reports, then Library. You should see Google organic search queries and Google organic search traffic. Publish them to your navigation if you want them in the left menu.

After linking, data shows with Search Console’s reporting delay. Today’s and sometimes yesterday’s numbers can be incomplete. Look back a few days for stable figures.

Find them under Reports, then Library, under the Search Console topic. You can add them to your sidebar. Here is what each one is for on a small product site.

• Google organic search queries: start with a query such as "invoice app free". See clicks and impressions, the linked landing page, and average position.
• Google organic search traffic: start with a landing page such as /pricing. See its Google clicks and impressions next to GA4 sessions, engagement, and key events.

These reports join by landing page. They answer page-level questions. For people-level paths, use product analytics that ties a person’s first landing page to later events.

Use queries to judge intent, and landing pages to judge outcomes. Scan for mismatches you can fix in a sprint.

1. 1

   Open Google organic search queries

   Sort by clicks. Add a secondary dimension for Landing page if it is not already visible. Filter to pages you own, such as /guides/ or /pricing.

2. 2

   Group by page in your head

   Look at repeated landing pages across many queries. Example: /guides/getting-started appears for "how to invoice" and "create invoice online".

3. 3

   Check the page in Google organic search traffic

   Open the companion report and find /guides/getting-started. Compare its Search Console clicks with GA4 sessions, engagement and key events.

4. 4

   Decide the change on page

   If clicks are healthy and key events are near zero, add a clear CTA and an internal link to /signup. If impressions are high but CTR is low, update the title and meta description.

5. 5

   Map queries to copy

   For queries like "invoice app pricing", make /pricing answer the question with plan names, monthly and yearly toggles, and a feature list that matches the query language.

A fixed page looks like /pricing that moved from a vague "Choose a plan" to "Pricing for freelancers and small teams" and added plan summaries that match the top queries.

They will never line up exactly. Do not try to force a match. Use them to tell one story together, not to audit each other.

• A click can start no session. The user bounces before GA4 loads, has JavaScript blocked, or declines consent where it is required.
• A session can follow several clicks. GA4 counts one session if a person clicks your result twice and only one visit registers.
• Consent tools drop sessions. In the EU, analytics that set cookies need consent. Cookieless modes exist, but many sites still undercount.
• Sampling and thresholds change small numbers. GA4 can sample large explorations and hide rows that could identify a person.
• Channels differ by rules. GA4 Organic Search is based on referrer and medium such as google / organic. Search Console counts only Google Search clicks.
• Attribution models differ. Data-driven, first click and last click spread credit differently across visits before a key event.

Search Console data lands slower than GA4 event data. Expect a delay. Look back a few days for stable query and click counts.

Some queries are withheld to protect privacy. You will see landing page totals that do not sum to the exact query list. Use the pages as your anchor, not the exact query mix.

• Which landing pages win Google clicks but fail to trigger key events? Example: /guides/getting-started with many clicks and no signups. Fix the page flow.
• Which pages convert well from all traffic but get no Google clicks? Example: /pricing drives signups from direct but shows few clicks. Add internal links and improve titles to earn more impressions.
• Which queries send low-intent traffic to a product page? Example: "what is invoicing" landing on /pricing. Create a top-of-funnel explainer and link to it.
• Which informational pages bring people who later sign up? You will see the page has GA4 key events on the same session. For later signups by the same person, use product analytics.
• Which countries or devices drive weak CTR for a page? Break down in the queries report and adjust copy, screenshots or currency display on that page.
• Which branded queries hide a product gap? If "yourproduct pricing" drives clicks to /pricing and key events dip, your prices or plan names may confuse people.

If you need the report that asks "which landing pages bring people who later sign up", and joins a person’s first landing page to a later product event, use product analytics. Page analytics does not do that join.

1. 1

   Find pages with clicks and no key events

   In Google organic search traffic, sort by clicks. Add a comparison for key events equals zero. Inspect the top pages.

2. 2

   Triage each page

   Open the page. Check the fold, the CTA, the signup path. Add a short, specific CTA to /signup or /pricing. Link related guides.

3. 3

   Fix intent mismatch

   If the top queries are questions, add a clear answer and an explainer section. Move pricing and signup lower, or link to a guide first.

4. 4

   Improve CTR for high impressions, low clicks

   Back in Google organic search queries, sort by impressions. If CTR is weak, update the title to match the query and refine the meta description.

5. 5

   Promote converting pages that get no clicks

   Check pages with high key events per session. Add internal links from /blog/, add them to the main nav, and link from /guides/ pages that rank.

A fixed page looks like /guides/invoice-template that added a short comparison to your /pricing and a single primary CTA, raising key events while keeping the guide useful.

Key events are conversions in GA4 terms since 2024. Mark the events that matter, such as sign_up, trial_start or purchase, as key events. Then read the search reports with attribution in mind.

• Default attribution is data-driven. It splits credit across visits. A Google organic visit might get partial credit even if the last visit was direct.
• Use comparisons for first click and last click. In GA4 you can compare attribution models. See how much credit Organic Search gets when it is first touch or last touch.
• Landing page still matters. Even with model differences, pages that start strong journeys tend to keep showing higher key events across models.
• Report what you can defend. When you share results, say which model the figures use as of 2026.

Consent affects counts. In the EU, analytics that set cookies need consent under ePrivacy. Cookieless configurations and server-side measurement exist. Every rate from consented sessions undercounts.

Keep your UTM tagging clean. UTMs belong on links you place elsewhere, such as your newsletter or a partner’s post. Never use UTMs on internal links, they start a new session and break attribution. If a UTM URL is indexed, use a canonical tag to the clean URL.

Use GA4’s search reports for page-level joins. Use product analytics when the question is person-level, such as which first landing pages bring people who later sign up days later.

• Funnels from a landing page to a signup event. Build a funnel from a pageview on /pricing to sign_up. Break it down by initial referring domain to isolate Organic Search.
• Cohorts by first landing page. Track activation or purchase by people who first landed on /guides/invoice-template.
• Event properties for context. A $pageview carries the path and referring domain. You can join this to later product events for revenue attribution to search.

Revenue attribution to search needs the payment event joined to the person and their first landing page. A report built from that answers what a search click earns.