Skip to content
Doctor SEO
Free SEO audit

Google Analytics 4 for SEO: Setup, Configuration and the Reports That Matter

How to install Google Analytics 4, the ten settings that change your SEO data, and five workflows that end in a decision, with every menu path checked against Google's own help pages.

Google Analytics 4

Google Analytics 4 (GA4) is Google’s free analytics platform for websites and apps, and for SEO it does one job Search Console cannot: it tells you what visitors did after they arrived from Google. Search Console stops at the click. GA4 starts there, with engagement, key events and revenue per landing page. This page is for site owners and SEOs who want GA4 set up correctly the first time and used for decisions rather than dashboards.

The verdict first: install it, change three settings on day one, link Search Console, and stop expecting it to tell you which queries you rank for. Standard GA4 costs nothing; Google’s product page says it gives you the tools “free of charge”. The paid tier, Analytics 360, has no published price: its page offers only a “Talk to Sales” button (both checked 10 October 2026).

One documented fact changes how you read every organic report in GA4, and most setup guides skip it. Google’s default channel group definition says the Organic Search channel covers non-ad organic results “including Google’s AI Overviews and AI Mode”. Your organic sessions are a mixture of classic blue-link clicks and clicks from Google’s AI surfaces, and the default channel does not separate them. Standard Universal Analytics properties stopped processing data on 1 July 2023, according to Google’s own replacement notice, so GA4 is the only version of Google Analytics left to configure.

How to install Google Analytics 4: account, property, data stream, tag

Installing GA4 takes four steps in a fixed order: an account, a property, a web data stream, and the Google tag on your pages. Google’s setup guide gives the menu paths below, and the role you need at each step matters if someone else owns the account.

  1. Create the account. Go to analytics.google.com. On a first visit click Start measuring; otherwise open Admin, click Create and choose Account. Name it and set the data-sharing options.
  2. Create the property. In Admin, click Create and select Property (Editor role required). Enter a name, then pick the reporting time zone and currency. Choose these deliberately: they decide where your day boundaries fall in every report. Then pick industry, business size and intended use, and click Create.
  3. Add a web data stream. In Admin, under Data collection and modification, click Data streams > Add stream > Web. Enter your site URL and a stream name. Google recommends enabling enhanced measurement at this point. Click Create stream.
  4. Install the Google tag. Your Measurement ID, which starts with G-, sits under Stream details in the same Data streams screen. Then pick one route, as described in the next section.

Google says data can take up to 30 minutes to appear. Open the Realtime report, load your own site in another tab, and confirm that a user shows up before you touch anything else.

Installing the tag on WordPress

WordPress sites have two clean routes. Google’s setup page lists Site Kit, Google’s own WordPress plugin, among the CMS integrations where you only paste or connect a tag ID. The Site Kit listing on WordPress.org describes it as “the official WordPress plugin from Google” and showed 5+ million active installations and version 1.189.0 when checked on 10 October 2026. MonsterInsights is also listed by Google as a WordPress option.

The second route is manual. In Data streams, open your stream, click View tag instructions under Google tag, choose Install manually, and paste the snippet “immediately after the <head> on each page”, in Google’s words. On WordPress that means your theme’s header or a header-code plugin. If you already run Google Tag Manager, add the Google tag there instead. The one rule is to use a single route: two installs mean duplicated page views, and GA4 will not warn you.

The GA4 settings that matter for SEO, and the ones to leave alone

About ten GA4 settings change what your SEO reports say, and most of them are off or at their weakest value after setup. The table lists each one with the path Google documents, the value to choose and the reason. Everything not in the table can wait.

Setting Where (per Google’s help pages) What to do Why it matters for SEO
Data retention Admin > Data settings > Data retention Set event data to 14 months, the maximum on a standard property Only 2 or 14 months exist on standard properties; 26, 38 and 50 months are 360-only. It limits explorations and funnels, not standard reports
Enhanced measurement Admin > Data streams > your stream > Enhanced measurement Keep on; review each event Scroll, outbound clicks, site search, file downloads and video events arrive without code
Internal traffic Data streams > stream > Configure tag settings > Define internal traffic Define your office IPs; traffic_type defaults to internal Your own visits inflate engagement on the pages you edit most
Data filter Admin > Data collection and modification > Data filters Create an Internal Traffic filter, leave it in Testing first An active filter is permanent; up to 10 per property
Unwanted referrals Configure tag settings > List unwanted referrals Add payment processors and login domains Stops a checkout return trip from stealing credit from the organic landing page; up to 50 per stream
Key events Admin > Data display > Events, click the star Mark the 3–5 actions that mean business Up to 30 on standard properties; not retroactive
Search Console link Admin > Product links > Search Console links Link one web stream to one Search Console property Brings Google queries and landing-page search metrics into GA4
Annotations Any line chart in Reports, right-click a data point Annotate launches, migrations, updates Visible across every line-chart report; 1,000 per property
Reporting identity Admin > Data display > Reporting identity Leave it unless you have a reason Google says the choice “does not affect data collection or processing” and can be switched at any time
Google signals Admin > Data collection and modification > Data collection Leave off unless you need cross-device or ads features It governs data about signed-in Google users; check your consent obligations before turning it on

The two settings most guides get wrong

Data retention is usually explained as “GA4 deletes your data after two months”. That is not what Google documents. Its data retention page says the setting “only affects explorations and funnel reports” and “does not affect standard aggregated reports”. Your year-on-year Landing page report survives a short setting. What you lose is the ability to build a custom exploration over old event data, which is exactly the analysis you want after a traffic drop. Set 14 months on day one, because it does not reach back. Google also applies a fixed two-month retention to age, gender and interest data regardless of your setting.

Data filters are the other trap. Google’s internal traffic article says that once a filter is applied “the effect on the data is permanent”, and excluded data “will never be available in Analytics or BigQuery”. Leave every new filter in Testing for a few days, check the test dimension in a report, and only then activate it.

What enhanced measurement actually collects

Enhanced measurement is a switch on the web data stream that adds a set of automatic events. According to Google’s enhanced measurement page, these are: page_view; scroll, fired the first time a user reaches the bottom of a page (90% depth); outbound click; view_search_results, triggered by query parameters such as q, s or search; video_start, video_progress and video_complete for embedded YouTube videos; file_download; and form_start and form_submit. Site search is the one SEOs underuse: the terms people type into your search box are content gaps described in your visitors’ own words.

Five SEO workflows in GA4, each ending in a decision

A GA4 report is only worth opening if it can change what you do next. Each workflow below starts from a documented report or channel and ends in a rule of the form “if this, then that”. The thresholds are yours to set from your own site’s median; GA4 publishes no benchmark, and borrowed industry averages would mislead.

1. Organic engagement by landing page: rewrite or keep

The Landing page report lives at Reports > Engagement > Landing page, per Google’s report documentation. Its dimension is “the page path and query string associated with the first pageview in a session”, and it carries sessions, average engagement time per session and key events. Filter it to the Organic Search channel and add engagement rate. Google defines an engaged session as one that lasts longer than 10 seconds, has a key event, or has two or more page views (Google, dimensions and metrics).

  • If a page has many organic sessions and an engagement rate well below your site’s organic median → the page answers a different question from the one searchers asked. Rewrite the opening and the title promise first.
  • If engagement is at or above the median but key events are zero → the content works; the next step is missing. Add a call to action or internal links, not more words.
  • If both are healthy → keep it, and spend your time elsewhere.

2. Key-event attribution by organic landing page: what to protect

Once you have marked your key events (formerly called conversions; Google now reserves “conversion” for key events used in Google Ads, per its conversions vs. key events page), the same Landing page report shows which organic entry pages start sessions that end in a key event. Sort by key events, not sessions.

  • If a small set of landing pages carries most organic key events → those are the pages you never change without a test, never let go stale, and check first after a core update.
  • If a high-traffic organic page has zero key events after 90 days → either the event is not tracked on that template or the page attracts the wrong intent. Check tracking before rewriting.

Remember that marking a key event “doesn’t change historic data” (Google): the report only counts from the day you clicked the star.

3. Search Console inside GA4: snippet problem or page problem

Linking Search Console adds two reports, documented in Google’s Search Console integration article. Google Organic Search Queries shows queries with Search Console metrics. Google Organic Search Traffic shows landing pages “with associated Search Console and Analytics metrics” on one row. The collection is “unpublished by default”: find it under Library in the left navigation and publish it. You need the Editor role in GA4 and verified ownership in Search Console.

  • If a landing page has high impressions and a low click-through rate but good engagement once people arrive → the snippet is the problem. Rewrite title and meta description; leave the body.
  • If it has a healthy click-through rate and poor engagement → the snippet promises something the page does not deliver. Fix the page, or make the title honest.

4. AI-assistant referrals: what the AI Assistant channel can and cannot see

GA4’s default channel group contains an AI Assistant channel. Google’s channel definitions say it covers users arriving “from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok”. The mechanism is the referrer: if it matches Google’s list of AI assistants, GA4 sets the medium to ai-assistant, and the channel rule is “medium exactly matches ai-assistant”. Google’s own AI Overviews and AI Mode are excluded and counted in Organic Search instead.

That mechanism sets the decision. A visit from an assistant that sends no referrer cannot match the rule, so the channel can only count what was passed to it. How large AI-assistant traffic really is remains disputed, and GA4 alone cannot settle it.

  • If the AI Assistant channel shows sessions → open its landing pages. Those are the pages assistants cite or link; check that they are current and that the facts on them are dated.
  • If it shows none → record that as “none detected by referrer”, not as “none”, and do not reallocate budget on that reading alone.

5. Migration and update check with annotations

GA4 annotations, per Google’s annotations article, are created by right-clicking a data point on any line graph in Reports. They then appear “across all reports and report cards with line graphs”, with a limit of 1,000 per property and the Analyst role required. Google may also add system annotations for data-impacting events.

  1. Before a migration or redesign, annotate the launch date and export the organic Landing page report for the previous 28 days.
  2. Annotate confirmed Google updates by their published start and end dates, not by the day tools started showing movement.
  3. Two to four weeks after launch, compare organic sessions and key events per landing page against the export.
  4. If losses concentrate on URLs that changed → audit their redirects first. If losses are spread evenly across unchanged URLs → look outside the migration, starting with the update annotations.

Executable checklist: a GA4 property ready for SEO

  • Realtime report shows your own visit, and the tag is installed by exactly one route.
  • Reporting time zone matches the market you report on.
  • Event data retention reads 14 months.
  • Enhanced measurement is on, with site search parameters matching your site’s search URL.
  • Internal traffic is defined; the data filter was tested before activation.
  • Payment and login domains are listed as unwanted referrals.
  • Three to five key events are starred, with the start date written down.
  • Search Console is linked and the Search Console collection is published from the Library.
  • An annotation exists for every launch, migration and confirmed update since setup.
  • The AI Assistant channel is checked monthly in your acquisition reports, with its landing pages noted.

What GA4 cannot tell you

GA4 is a behaviour tool, and Google’s own documentation records where its numbers stop being complete. Each limit below is tied to the page where Google states it.

  • Which queries you rank for. Native GA4 has no Google query data. The linked Search Console reports supply it, with documented constraints: data arrives 48 hours after Search Console collects it, Search Console keeps 16 months, the reports “do not support time-series charts”, and Search Console metrics combine only with Search Console dimensions plus Landing page, Device and Country (Google). For query work, use Search Console itself.
  • Classic results versus AI features. Organic Search includes AI Overviews and AI Mode by definition (Google), and the default channel offers no way to tell them apart.
  • Rows hidden by thresholds. Google applies data thresholds to stop anyone inferring identity. The thresholds page names demographic data and site search query rows, which “may be withheld if there aren’t enough total users”, and says thresholds “are system defined. You can’t adjust them.” A wider date range can help.
  • Exact counts in large explorations. Sampling can apply when a query exceeds the quota, which Google gives as 10 million events per query for standard properties, flagged in the data quality icon with the percentage of data used (Google).
  • Users who declined cookies. Under consent mode, GA4 can model their behaviour only once the property collects at least 1,000 events per day with analytics storage denied for at least 7 days, among other prerequisites, and Google says meeting them “doesn’t guarantee eligibility” (Google). Modelled data is not included in BigQuery export.
  • Unlimited raw data for free. BigQuery export is available on standard properties, but with a daily limit of 1 million events, and storage and processing are billed on the BigQuery side beyond the sandbox (Google).
  • Anything before you configured it. Retention, key events and filters all work from the day you set them. None of them is retroactive.

Alternatives to Google Analytics 4

GA4’s main companion for SEO is Google Search Console, which owns the query and indexing data GA4 lacks; its tool page on this site is coming soon. For teams that want analytics outside Google, two open-source options are the usual candidates. Matomo says on its homepage that you can “self-host forever for free”, with a paid cloud version after a 21-day trial. Plausible says “No cookies, just insights”, offers a 30-day free trial and listed paid plans from $9 per month when checked on 10 October 2026. Neither imports Search Console data the way the GA4 link does, so an SEO workflow built on either still needs Search Console alongside it. The SEO tools hub lists every tool page as it publishes.

Where the course goes deeper

This page covers the tool: installation, settings and reports. The method behind measuring SEO, including what to report, how to read a drop and how to separate signal from noise, belongs to the SEO analytics and measurement level of the course. If you want an AI assistant to query your own GA4 and Search Console data, Level 8 has a lesson on connecting Claude to GSC and GA4 via MCP. For the crawling and indexing side that GA4 cannot see at all, start with the technical SEO level, and look up any unfamiliar term in the SEO glossary. A dedicated GA4 lesson is coming to the analytics level.

Sources