The organic traffic Liverpool marketers can’t see in GA4 (and where it actually is)

Why GA4 stopped answering SEO questions on Merseyside

There is a running joke among the marketing crowd who drink in the Baltic on a Thursday: nobody has trusted a GA4 export since the Grand National weekend two years ago, and the ones pretending they do are billing for it. That is unkind, but not by much. GA4 was never designed to answer SEO questions in the first place. It was designed 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 gone. When the numbers stop lining up with the till roll, marketing directors from Liverpool ONE to Aigburth start reaching for something else.

Ask the in-house SEO at a Baltic Triangle SaaS, a Liverpool ONE fashion brand or an Anfield-adjacent hospitality group. Open GA4, drill into Acquisition → Sessions, and more than half of your organic queries turn up as the placeholder (not provided). Cross-check against Search Console and the totals refuse to reconcile. Try to see what the person who arrived on your article “best physio Anfield” actually did on the site — and GA4 hands you an aggregated funnel that will not separate the channels cleanly. A monthly SEO report that used to take forty-five minutes now eats a full working day, and by the time the client meeting starts nobody in the room is convinced the numbers hold up.

Then there is the legal angle, which the Liverpool market has been slower to internalise than either London or Manchester. The Information Commissioner’s Office has not gone as far as the French CNIL or the Austrian DPA in declaring GA4 unlawful outright, but its 2024 guidance on international transfers and its persistent PECR enforcement against sites that fire analytics before consent have made the “install GA4 and forget it” approach genuinely indefensible. For a Ropewalks agency renewing a Merseyside charity contract, the awkward question in the room is now: how many of your reported sessions would survive a two-hour audit?

What Semalt Analytics is and where the numbers come from

Semalt Analytics is a purpose-built data layer for SEO. It leans on three sources that reinforce each other rather than replace what you have:

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

That interlock is what nothing else on the UK market delivers in the same shape. GA4 tells you how many sessions arrived. Search Console tells you the average position of a keyword. Semalt tells you, for every individual session, the position the query held at that exact minute, which SERP feature stood above it (People Also Ask, video carousel, Business Profile pack), and how that affected real CTR by device and by day of week. For a Merseyside marketing lead about to defend an SEO budget to a finance director in Bootle, that specificity is the difference between an approval and a “let’s revisit next quarter”.

Five things you see in Semalt and never in GA4

1. Real organic traffic per URL, without sampling

GA4 begins sampling the moment you cross two dimensions and pass ten million events in a month. For a modestly successful Liverpool e-commerce site — the sort of catalogue that runs a Grand National promotion and a Christmas markets drop at the same time — that ceiling is straightforward to trip once you count scroll, view_item and outbound-click events. Semalt applies no sampling at all. Every URL passes through a column-oriented index built on ClickHouse that answers questions like “give me the five hundred landing pages with the most organic traffic in January, filtered to mobile only on EE and Vodafone UK” in under a second.

2. Keywords without (not provided)

The infamous (not provided) placeholder 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 usefully, you see the keywords sitting in positions four to ten — the ones a content refresh can push into the top three and roughly double the traffic on. That view is called Striking Distance, and it is the first screen we open when auditing a new Merseyside client. If you want to see it applied to your own domain, sign in to the Semalt dashboard and connect Search Console before you finish your coffee.

3. Sessions GA4 loses to ad-blockers

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 above 43%. Every one of those sessions is invisible to GA4. Semalt’s log-based tracker sees them because it never depends on JavaScript in the browser: the second the server serves the page, the session is counted. Across our Merseyside book we have measured the recovered gap at between 16% and 54% additional sessions, higher in B2B SaaS out of the Baltic Triangle and lower in traditional bricks-and-mortar retail on the Liverpool ONE estate.

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. IAB UK’s 2025 consent tracker puts UK acceptance of a standard TCF v2.2 banner at 41%. 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 the Wirral Line train 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 customer. You can see that “independent framing Bold Street” produced £18,900 in organic revenue last month, and that a fatter head keyword generated absolutely nothing. With that in hand, you stop chasing vanity metrics and start prioritising content by the pound.

Case study: a Bold Street homewares indie, 14,200 sessions/month

A client running a small homewares and framing business at the Central Station end of Bold Street — the kind of independent that lives on repeat customers, LFC European nights bringing tourists in, and a decent showing every Christmas markets weekend — came to us in February 2026 with this picture:

• GA4 reported 14,200 organic sessions and 41 online orders for the month (0.29% CVR).
• Search Console showed 32,600 clicks in the same window.
• The gap — more than double — had no internal explanation. The owner blamed the Cookiebot banner, Cloudflare’s bot fight mode, and the Squarespace-to-Shopify migration finished the previous autumn.

We wired in Semalt Analytics in eleven minutes. The first proper numbers landed the next morning:

Real organic sessions: 27,800 (96% more than GA4). Orders correctly attributed to first organic touch: 94 (2.3×). Verified organic pipeline value based on average basket and repeat rate: £142,000 vs. the £38,000 the owner had been quoting to her accountant — a difference of £104,000 that was invisible in the monthly export.

The most useful insight arrived when we cross-referenced keywords with pipeline value: eight long-tail terms (each between 90 and 720 searches/month, all mentioning specific product categories or Merseyside neighbourhoods) drove 68% of pipeline, while the head keyword “homewares Liverpool” with 9,900 searches/month drove less than 4% of orders. The content plan was re-prioritised inside a fortnight. By May, organic pipeline was up 63% and the owner had stopped answering emails about that Shopify migration.

UK GDPR, PECR and the ICO’s slowly hardening line

The reason serious Liverpool agencies are moving to Semalt is not novelty; it 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 cookies, localStorage, IndexedDB and anything similar. Server-log tracking touches none of that. It uses only the information the browser sends anyway as part of the HTTP request (IP, user-agent, referrer). Those are processed server-side under Article 6(1)(f) UK GDPR, with IP truncated within milliseconds (last octet removed) and never persisted.

That gives Merseyside marketers a rare advantage: Semalt Analytics counts the users who reject your cookie banner as well as the ones who accept. For a mid-sized Liverpool shop running at a 44% consent rate, that alone represents a 127% more accurate reach measurement, without straying into ICO enforcement territory. Semalt provides a UK-law DPA signable in one click, a TOM document aligned with the ICO’s 2025 accountability framework, and NCSC-aligned hardening guidance for the tag itself.

Setup in twelve minutes on a Liverpool stack

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

More in this series: Push SEO changes live in 3 minutes, Watching Liverpool rivals, properly, Optimise for customers, not for volume.

FAQ

Does Semalt replace GA4 completely?

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

Is it compliant with UK GDPR and PECR?

Yes. Log-based tracking needs neither persistent cookies nor an advertising fingerprint. Server-side fusion works on 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 Liverpool stacks?

Yes. The tag exists as a WordPress plugin, a Shopify app, an Umbraco package (still common with Liverpool City Council and the NHS estate), a Magento 2 module and SDKs for Node.js, PHP, Symfony, Laravel and .NET. For cloud-native setups it is two lines in a Cloudflare Worker deployed from your existing hosting. Log in and pick your platform.

How quickly do you see value?

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

Does it work for small websites?

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

Does it integrate with Semalt AutoSEO?

Yes — and that is the real synergy. Analytics identifies URLs with striking-distance keywords, and AutoSEO executes the on-page fixes without a developer in the loop. See the AutoSEO guide.