GA4 is lying to Glasgow marketers: how to see the traffic Google is hiding

Why Google Analytics 4 no longer works for SEO in the UK

Walk down Ingram Street in Merchant City and you can pass six marketing agencies before you reach George Square. Every one of them is staring at the same broken GA4 dashboard and pretending it’s fine. It isn’t. GA4 was never built to answer SEO questions — it was built to log product events and feed Google Ads remarketing. Traffic per landing page, organic keywords, behaviour by source: all of it is either broken, hidden behind an anonymisation threshold, or simply gone. That’s not a hot take. That’s two years of watching Glasgow marketing leads try to close a report and give up before lunch.

Ask any in-house SEO working for a Glasgow scale-up such as a FreeAgent competitor, a Craneware supplier or a Skyscanner-adjacent affiliate. You open GA4, drill into Acquisition → Sessions, and more than half of your organic queries land as the useless placeholder (not provided). You cross-check against Search Console and the totals do not match. You try to see what someone who arrived on the article “best dentist Southside Glasgow” actually did — and GA4 hands you an aggregated funnel that will not separate channels cleanly. A monthly SEO report that used to take forty-five minutes now eats half a day, and by the time the client meeting starts nobody is convinced the numbers can be trusted.

Then there is the legal angle. The Information Commissioner’s Office (ICO) has not gone as far as CNIL in France or the Austrian DPA in ruling GA4 illegal, but its 2024 guidance on international transfers and its ongoing enforcement of PECR against sites that fire analytics before consent have made the “install GA4 and forget it” playbook indefensible. For a Merchant City marketing consultancy, this means: either you invest in a properly configured consent-management platform, or you accept that every visitor who taps “Reject All” immediately disappears from your reports.

What Semalt Analytics is and where the data comes from

Semalt Analytics is a data layer for SEO built on three sources that reinforce one another:

1. Google Search Console API v3 — the newer endpoint that returns up to sixteen months of history with daily granularity, well past the top-1,000 query cap of the UI.
2. Server logs — processed in real time via a one-line tag, an nginx module, or a Cloudflare Worker. This captures sessions GA4 misses because of blockers, rejected consent or private browsing on iOS 17.
3. Semalt’s own crawl — the rank-tracking engine cross-references your traffic, so every organic hit is tagged with the exact SERP position and features present at click time.

That interlock is what nothing else on the UK market does in the same form. GA4 tells you how many sessions arrived. Search Console tells you the average position of a keyword. Semalt tells you, for each individual session, which position the query held at that exact minute, which SERP feature stood above it (People Also Ask, video carousel, Google Business Profile pack), and how that affected real CTR by device and by day of week.

5 things you see in Semalt and never in GA4

1. Real organic traffic per URL, without sampling

GA4 starts sampling the moment you cross two dimensions and pass ten million events per month. For a mid-sized Scottish online shop — even one with modest traffic — that threshold is easy to trip once you count scroll, view_item and outbound-click events. Semalt applies no sampling. Every URL runs through a column-oriented index built on ClickHouse that resolves queries like “give me the five hundred landing pages with the most organic traffic in January, compared to last January, filtered to mobile only on EE and Vodafone UK” in under a second.

2. Keywords without (not provided)

The infamous (not provided) does not exist inside Semalt, because the sources are raw Search Console data plus the platform’s own crawl. For every URL you see the fifty keywords driving the most traffic with clicks, impressions, CTR and average position. More importantly, you see the keywords sitting in positions four to ten — the ones a content refresh can push into the top three and double the traffic. This view is called Striking Distance and it is the first thing we open when auditing a new Glasgow client. If you want to see it for yourself, sign in to the Semalt dashboard and connect Search Console.

3. Sessions GA4 loses to blockers

In the UK, desktop ad-blocker adoption sits at roughly 34% according to GlobalWebIndex Q2 2026 data, and for under-35s on EE or O2 UK the number climbs to 43%. Every one of those sessions is invisible to GA4. Semalt’s log-based tracker sees them because it does not depend on JavaScript: the second the server serves the page, the session is counted. Across our Glasgow client base we have measured the gap between 14% and 51% additional sessions, depending on vertical — higher in B2B SaaS, lower in traditional bricks-and-mortar retail such as Buchanan Galleries or Silverburn tenants.

4. Cross-device journey without Google Signals

GA4 promises cross-device sessions via Google Signals, but only for users signed in to Google on both devices and who have accepted personalised advertising. According to the IAB UK 2025 consent tracker, only 41% of British users click Accept on a standard TCF v2.2 banner. Semalt uses a technique called server-side fingerprint fusion that respects UK GDPR (no ad profiles, no cross-site behavioural graphs) and still shows that someone read your article on mobile on the Subway ride home and bought on desktop later that evening.

5. Organic revenue per keyword, in real GBP

The crown jewel: connect your CRM or shop (WooCommerce, Shopify, Magento 2, BigCommerce, HubSpot, Pipedrive) via webhook and Semalt links every order to the first organic keyword that brought the user. You can see that “chartered accountant West End Glasgow” produced £28,400 in organic revenue last month, and that a fatter head keyword generated £0. With that in hand, you stop chasing vanity metrics and prioritise content by actual GBP revenue.

Case study: Finnieston restaurant group, 18,000 sessions/month

A client running three Finnieston restaurants — the kind of small independent group with tables on Argyle Street and covers to fill on a Six Nations Saturday — came to us in January 2026 with this picture:

• GA4 reported 18,100 organic sessions and 62 online bookings for the month (0.34% CVR).
• Search Console showed 41,900 clicks in the same window.
• The gap — more than double — had no internal explanation. The team blamed GTM, Cloudflare’s bot fight mode, and the CookieYes banner in rotation.

We connected Semalt Analytics in fourteen minutes. First numbers landed the next morning:

Real organic sessions: 33,700 (86% more than GA4). Bookings correctly attributed to first organic touch: 148 (2.4×). Verified organic pipeline value based on average cover: £186,000 vs. the £48,000 the ownership had been estimating — a difference of £138,000 that was invisible in the monthly report.

The most valuable insight arrived when we cross-referenced keywords with pipeline value: six long-tail terms (each between 90 and 480 searches/month, all mentioning Finnieston or the specific cuisines) drove 63% of pipeline, while the head keyword “restaurants Glasgow” with 12,100 searches/month drove only 5% of bookings. Content strategy was re-prioritised inside a fortnight. By April, organic pipeline was up 71% and the marketing manager was quietly promoted.

UK GDPR, PECR and the ICO position on GA4

The reason many Glasgow and Edinburgh agencies switch to Semalt is legal defensibility. PECR regulation 6 requires prior consent for any storage of information on, or access to information from, a user’s device — so for cookies, localStorage, IndexedDB and similar. Server-log tracking accesses none of that. It uses only the information the browser sends anyway as part of the HTTP request (IP, user-agent, referrer). These are processed server-side under Article 6(1)(f) UK GDPR, with IP truncated within milliseconds (last octet removed) and never persisted.

This gives Glasgow marketers a rare advantage: Semalt Analytics counts users who reject the banner too. For a mid-sized Scottish shop with a 45% consent rate, that alone means a 122% more accurate reach measurement, without straying into ICO enforcement territory. Semalt provides a UK-law DPA that can be signed with one click per account, plus a TOM document aligned with ICO’s 2025 accountability framework and NCSC hardening guidance.

Setup in 12 minutes

Semalt Analytics vs. GA4 vs. Matomo vs. Search Console

More in this series: SEO changes in 3 minutes, not 6 weeks, Reading your Glasgow rivals' playbook, Rank Glasgow keywords by pounds, not volume.

FAQ

Does Semalt replace GA4 completely?

If your focus is purely SEO and content, yes. If you also run Google Ads and need to export audiences to Google, keep GA4 in parallel — Semalt does not replace the native Ads connector. For eight in ten Glasgow clients we keep GA4 as an Ads source and use Semalt as the SEO source of truth.

Is it compliant with UK GDPR and PECR?

Yes. Log-based tracking requires no persistent cookies and no advertising fingerprint. Server-side fusion works with pseudonymised data, and sessions anonymise after 26 months by default (configurable down to six). Semalt provides a UK-law DPA, a TOM document and a DPIA template aligned with ICO guidance.

Does it run on typical UK stacks?

Yes. The tag exists as a WordPress plugin, a Shopify app, an Umbraco package (still popular with Scottish councils and NHS boards), a Magento 2 module and SDKs for Node.js, PHP, Symfony, Laravel and .NET. For cloud-native setups it’s two lines in a Cloudflare Worker deployed from your Fasthosts or Krystal environment. Log in and pick your platform.

How fast do you see value?

Historical GSC data is visible in five minutes. Live tracking shows full data after 24 hours. The Striking Distance insight (keywords in positions four to ten) is actionable on day one.

Does it work for small websites?

Yes. A personal blog with 1,500 sessions/month uses Semalt the same way a B2B portal with two million does. For small sites the value is in seeing which article is about to reach page one and optimising it before Google cements the position.

Does it integrate with Semalt AutoSEO?

Yes — that’s the real synergy. Analytics identifies URLs with striking-distance keywords, and AutoSEO executes the fixes on those URLs without a developer in the loop. Details in the AutoSEO guide.