Tech for Retail 2025 Workshop: From SEO to GEO – Gaining Visibility in the Era of Generative Engines

Back to blog

How to measure GEO & SEO with Google Analytics and GDPR consent

SEO

Discover Incremys

The 360° Next Gen SEO Platform

Request a demo
Last updated on

1/11/2026

Chapter 01

Example H2
Example H3
Example H4
Example H5
Example H6

This page is for marketing directors, SEO managers and editorial leads who read GA4 while part of their visitors refuse audience measurement. It covers Google Analytics and the GDPR through the effects on your figures: what consent, modelling and data retention change in your reports, how to spot a measurement break, and which indicators to keep so you can still make decisions.

 

The general framework of the tool, its KPIs and how to read channels are set out in the Google Analytics guide.

 

Google Analytics and the GDPR: What to Bear in Mind to Measure GEO and SEO Under Consent

 

In B2B, the challenge is no longer to install GA4, but to make measurement reliable now that it has become more fragile: consent, browser restrictions, modelling, collected parameters. These constraints directly affect your editorial decisions:

 

  • which pages to optimise first;
  • which content to produce or update;
  • which channels really drive enquiries;
  • how to explain a performance change without jumping to the conclusion that SEO is the issue.

 

Compliance Depends on Your Configuration, and So Does Your Reading

 

GA4 compliance is not a simple yes/no label: it depends on your purposes, how you collect consent, your retention periods and the parameters you send. The legal framework (banner, lawful basis, transfers) is a matter for your DPO and your CMP. For the analyst, the consequence is practical: every configuration choice changes the share of traffic observed, and therefore the figures you compare from one month to the next.

 

The goal is not to recover all the data, but to keep a few robust indicators and a consistent analysis method despite consent constraints.

 

What Consent Refusal Changes in Analysis, Attribution and Reporting

 

Once part of your visitors refuse audience measurement, several effects appear in your reports, even though real behaviour has not changed:

 

  • Less stable attribution: an artificial rise in direct traffic, incomplete journeys between the first visit and the key event.
  • Under-reported key events: forms, clicks and micro-actions from visitors who refused do not appear.
  • More apparent "new" users: GA4 is less able to recognise a browser from one day to the next.
  • Absolute levels that are harder to interpret: trends remain comparable, unless your CMP or consent mode changes mid-period.

 

The full diagnosis of a swelling direct channel, consent included, is covered in the article on direct traffic in Google Analytics.

 

What Each Measurement Change Does to Your Reports

 

A sudden shift in GA4 comes from a measurement change before it comes from an audience change. The table below links each change to its symptom, the check that confirms it and the resulting decision:

 

Measurement changeSymptom in GA4CheckDecision
New CMP or new bannerBreak in sessions and users on a fixed dateSwitchover date in the change logOnly compare periods after the switchover
Basic Consent ModeKey events and sources clearly downTags blocked without consent, checked in DebugViewRead as a trend, not as an absolute level
Advanced Consent Mode with modellingSmoothed volumes, shifting channel sharesConsistency with Search Console and the CRMDo not optimise a page on a reconstructed signal
Retention cut from 14 to 2 monthsEmpty explorations beyond two monthsData retention setting of the propertyAlign retention with your decision cycle
Blockers and browser restrictionsDirect traffic up, more apparent new usersTrend in organic clicks in Search ConsoleDo not conclude that SEO has dropped
Change to tagging or eventsKey event that drops or doublesDebugView and change logFix it before reading any trend

 

No before/after comparison holds as long as one of these changes falls within the period.

 

Cookies and Browser Recognition: Why "New" Users Increase

 

GA4 relies on cookies to recognise a browser, connect interactions within the same journey and link acquisition to events. The analytics cookie is not set in three cases:

 

  • the user refuses the "audience measurement" purpose in the CMP;
  • your implementation blocks the tag until consent is given (basic mode);
  • a browser or extension prevents the cookie from being set.

 

When you change your consent logic, retention settings or tag firing rules, you change how GA4 recognises a browser. The typical effect is more apparent "new" users and less continuity from one day to the next, even if real volume has not necessarily changed. Ratios calculated on observed sessions, such as bounce rate and engagement rate, may also shift after a consent change.

 

Consent Mode v2: Basic Mode, Advanced Mode and Modelling

 

Consent Mode adapts tag behaviour based on the user's choice. The two modes do not produce the same figures:

 

  • Basic mode: tags do not fire without consent, and refused visits disappear from reports.
  • Advanced mode: cookieless signals are sent when consent is refused; its legal position is less clear-cut.
  • Modelling: GA4 fills part of the gaps, which preserves the macro view (trends, channel contribution) at the cost of some uncertainty.

 

On low-volume segments, thresholds may also hide some report rows. Setting up the consent mode is your implementer's job, and its implementation is covered in the Google Tag Manager cluster.

 

Data Retention: 2 or 14 Months, and What It Changes for Explorations

 

Two durations are often confused. Cookie lifespan, on the browser side, depends on the specific cookie and your technical setup. Data retention, on the GA4 side, is configured in the interface: 2 or 14 months at the time of writing. Retention is what limits the depth of explorations: with a short setting, an analysis over several quarters becomes impossible in Explorations.

 

Choose your retention period according to your decision cycle, not by default:

 

  • Seasonality: comparing a period with the same period the previous year requires the long setting.
  • Sales cycle: a long B2B cycle requires going far back between the first visit and the enquiry.
  • Publishing cadence: measuring the effect of a batch of content over several months requires keeping the history.

 

Retain data only for as long as the purpose requires, and record the rationale for the setting in your change log.

 

Interpreting Reports After Modelling

 

After enabling a consent mode with modelling, reports remain readable, provided you avoid these classic mistakes:

 

  • Comparing absolute levels before and after without noting the consent change: you may attribute a tracking-driven shift to SEO.
  • Over-optimising a page or channel based on a reconstructed signal, without corroborating it with Search Console, the CRM, logs or at least consistent trends.
  • Choosing between two similar pages on a modelled figure: the finer the segment (one page, one source, one week), the more the estimated share weighs.

 

A modelled figure remains an estimate: it serves to follow a trend. The useful safeguards are well known: a change log, like-for-like comparison periods, and prioritising key events and engagement over overly granular metrics.

 

Swelling Direct Traffic Is Not an SEO Signal

 

When measurement is constrained, some visits lose their source and fall into direct traffic. The aim is to avoid conclusions such as "direct traffic is up, so SEO must be down" when you have simply lost source information for one of three possible reasons:

 

  • a change of consent setup or CMP;
  • a browser restriction or a blocker;
  • an untagged campaign link.

 

Tagging discipline makes campaigns easier to read: the source / medium / campaign naming convention and its checks are detailed in the UTM tag guide. Internal traffic, duplicate tags and cross-domain tracking fall under the tracking hygiene covered with direct traffic.

 

Keeping a Measurement Change Log

 

The change log is the highest-return tool for reading data under consent: it lets you explain a KPI shift without restarting a full audit. Each entry records:

 

  • the date of the change;
  • its nature (CMP version, consent mode, tags, events, retention);
  • the reason for the change;
  • the expected impact on reports.

 

Indicators to Prioritise When Consent Reduces Measured Volume

 

When volume drops, not all indicators degrade in the same way. Some remain reliable as trends, others become misleading as soon as the refusal rate varies:

 

IndicatorReliable under partial consent?Reading
Trends on a comparable scopeYesBasis for decisions, outside measurement changes
Key events (enquiries, downloads)Yes as a trend, under-reported as a levelPreferable to micro-events
Engagement rate, engaged sessionsMostly yesRatio calculated on observed sessions
New usersNoInflated when the browser is no longer recognised
Share of direct trafficNoA rise first signals lost source information
Micro-events and very fine segmentsNoToo much estimation to choose between two pages
Search Console impressions and queriesYes, independent of the site's cookiesPre-click reading, to cross-check with GA4 pages

 

Cross-Checking With Search Console for Pre-Click Reading

 

Search Console does not depend on the consent collected on your site: impressions, queries and pages are still measured when GA4 loses part of the visits. Cross-checking links the query, the landing page and the intent, and lets you verify that a drop seen in GA4 also exists before the click. The normal gaps between the two tools are explained in the article on the difference between Search Console and Google Analytics.

 

Measuring GEO Contribution When Some Visits Escape GA4

 

GEO amplifies a trend already visible in SEO: part of the value happens without a click, through citations in generative engine answers. If consent also reduces measured volume, you risk underestimating authority-building content that is read and cited but less trackable.

 

The method remains the same as for SEO:

 

  • focus on trends and quality signals rather than volumes;
  • align GA4 (post-click) with Search Console (pre-click);
  • track visits from AI assistants separately.

 

This traffic is read with a custom channel group built on the source, described in the article on Google Analytics for SEO.

 

Track Few Indicators, but Stable Ones

 

The more constrained measurement becomes, the more you should reduce your dashboard to indicators that withstand breaks: the key event trend, engagement rate and content contribution. Keep 3 to 5 decision KPIs and leave the rest for diagnosis, rather than multiplying fragile metrics that move with every CMP setting.

 

Personal Data and Minimisation: What You Never Send to GA4

 

Collecting only what supports a decision is the highest-leverage step, for compliance as well as for readability. Fewer events and parameters also means less noise to interpret when part of the visits disappears.

 

Prohibited Data in Analytics

 

The principle: no information that directly identifies a person, and no sensitive data, should pass through URLs, parameters, event names, form fields or imports. In practice, never send:

 

  • email addresses, phone numbers or names in a URL or a query parameter;
  • internal identifiers tied to a named individual (HR IDs, patient IDs);
  • health data, opinions, detailed financial data or any sensitive content in an event.

 

For a B2B form, send a neutral event such as form_submit and store the details in your CRM, not in the audience measurement tool.

 

Limiting Collection to What Supports a Decision

 

In B2B editorial contexts, minimisation comes down to three choices:

 

  • prioritising a handful of intent events (clicks to pricing pages, demo requests, downloads);
  • avoiding event parameters that could contain personal data;
  • keeping audience measurement and marketing strictly separate, with distinct consent where required.

 

IP masking alone is not enough: GA4 processes other online identifiers, such as cookie or device identifiers, which remain personal data. So decide upfront which events steer editorial performance (reading, intent-driven clicks, forms) and which are merely nice-to-have collection.

 

Depending on Your Situation

 

Depending on what you want to do with your GA4 data under consent, another article in the cluster takes over:

 

 

To read GA4 and Search Console side by side and track content contribution despite measurement gaps, the Incremys Performance Reporting module integrates both sources via API, without adding an extra layer of data collection.

 

FAQ: Google Analytics, Cookies and the GDPR

 

Does Consent Distort My Figures?

 

Consent does not distort trends, but it reduces and skews absolute levels. Refused visits are missing or modelled, direct traffic swells, apparent new users increase and key events are under-reported. Compare like-for-like periods and check that no CMP change falls within the interval.

 

Why Is My Direct Traffic Increasing?

 

Direct traffic usually increases because visits have lost their source, not because your audience has changed. A consent refusal, a browser restriction or an untagged campaign link is enough to push a visit into direct traffic. Check the trend in organic clicks in Search Console before concluding that SEO has dropped.

 

How Reliable Is Modelling?

 

Modelling is reliable for following a trend or the relative contribution of channels, not for choosing between two similar pages. It fills part of the refused visits through estimation, with an uncertainty margin that grows on fine segments. Corroborate any modelled signal with Search Console, the CRM or consistent trends before acting.

 

How Long Does GA4 Keep My Data?

 

GA4 keeps detailed data for 2 or 14 months, depending on the setting chosen in the property at the time of writing. This period limits the depth of explorations and should not be confused with cookie lifespan on the browser side. Choose it based on your seasonality, sales cycle and publishing cadence, and record the rationale.

 

What Does Consent Mode v2 Change for SEO Analysis and Key Event Measurement?

 

Consent Mode v2 adapts tags to the user's choice and therefore changes what you see. In basic mode, refused visits disappear; in advanced mode, cookieless signals feed a modelling process. Trends remain readable, but key event levels become estimates that should be read with caution.

 

What Data Is the Tool Not Allowed to Collect?

 

GA4 must not receive any information that directly identifies a person, nor any sensitive data. This rules out email addresses, phone numbers and names in URLs, parameters, events or imports. A simple rule works well: if a data point is not essential to an SEO or GEO decision, do not send it.

 

How Do You Measure GEO Impact if Some Visitors Refuse Cookies?

 

Measure GEO impact by combining GA4 for post-click and Search Console for pre-click, then focusing on trends. Isolate visits from AI assistants with a custom channel group built on the source. Finally, monitor the performance of content that is likely to be cited, even when its measured visits decline.

Discover other items

See all

Next-Gen GEO/SEO starts here

Complete the form so we can contact you.

The new generation of SEO
is on!

Thank you for your request, we will get back to you as soon as possible.

Oops! Something went wrong while submitting the form.