Semalt Analytics: what GA4 stopped showing Riyadh sites (and how to get the numbers back)

Why Google Analytics 4 no longer works for SEO in Saudi Arabia

When Google forced the migration from Universal Analytics to GA4 in July 2023, most Saudi teams treated it as a cosmetic refresh. Three lunar years on, the picture is uncomfortable: GA4 was never designed to answer SEO questions. It was designed to measure product events and feed audiences into Google Ads. Everything that matters for organic reach on a .com.sa or .sa site — organic sessions per landing page, keyword-level attribution in Saudi Riyal, behaviour by real referrer — is either broken, hidden behind anonymisation thresholds, or removed entirely.

Anyone running an in-house SEO function at jarir.com, extra.com, panda.com.sa, othaim.com, a ministry microsite or a mid-sized Riyadh Salla merchant feels it every reporting cycle. You open GA4, drill into Acquisition → Sessions, and more than half of the Arabic queries arrive as (not provided). You cross-check with Search Console and the totals disagree by over 30 %. You try to isolate visitors from the article “افضل شركة سيو الرياض” and the funnel dumps them into an aggregated bucket that no longer separates Bing, DuckDuckGo and Yandex from google.com.sa. A monthly SEO report that used to take an hour on Universal Analytics now takes an afternoon, and at the end of the meeting nobody is entirely sure the numbers are usable.

There is a Saudi-specific twist too. Mobile traffic on the STC, Mobily and Zain KSA networks runs behind an unusually aggressive layer of ad-blocking — both browser-level (Brave and Kiwi are popular on Arabic Android in the Kingdom) and network-level (many corporate MPLS tunnels for banks and ministries strip third-party analytics beacons by default). Independent measurement across our Riyadh, Jeddah and Dammam client base shows GA4 losing between 26 % and 47 % of real organic sessions to blockers alone, before you even get to consent-banner rejection.

What Semalt Analytics is and where the data comes from

Semalt Analytics is a data layer purpose-built for SEO. It combines three sources that Saudi teams struggle to stitch together on their own:

1. Google Search Console API v3 — using the newer endpoint that returns up to 16 months of history with daily granularity, not just the visible top 1,000 queries.
2. Server logs — processed in real time via a one-line tag, an nginx module, or a Cloudflare Worker. This captures sessions GA4 misses due to blockers, rejected cookies or Private Relay browsing.
3. Semalt's own crawl — the rank-tracking engine cross-references every organic visit, so each session is tagged with the exact SERP position and the SERP features that were live at click time (People Also Ask, video, map pack in Arabic, tweet carousels).

No other platform interlocks these three feeds. GA4 tells you how many sessions arrived. Search Console tells you the average position of a keyword over the week. Semalt tells you, for each session, what the position was at that exact minute, which SERP feature appeared above it, and how that shaped real CTR on google.com.sa by device and by Arabic vs. English query.

5 things you see in Semalt and never in GA4

1. Real organic traffic per URL, without sampling

GA4 begins sampling the moment you combine two dimensions and cross 10 million events per month. For a jarir.com or noon.com Saudi-scale property that limit is breached in the first three days of any campaign. Semalt does not sample. Every URL runs through a column-oriented index (built on ClickHouse) that answers messy questions like “give me the 500 landing pages with the most organic traffic in Ramadan 1447, compared to the same 30 days a year earlier, filtered to mobile users on Mobily KSA” in under a second.

2. Arabic keywords without (not provided)

The infamous (not provided) does not exist in Semalt because the sources are raw Search Console plus the platform's own crawl. For every URL you see the 50 keywords that drive the most traffic, in both Arabic and English, with clicks, impressions, CTR and average position. Even more valuable: you see the queries where the URL sits at position 4-10 — the ones that a content refresh can lift into the top 3 and roughly double the traffic. This view, called “Striking Distance”, is the first tab we open when auditing a new Riyadh client, and it usually surfaces four or five easy wins in the first thirty minutes.

3. Sessions GA4 loses to blockers

Mobile ad-blocker penetration in KSA sits at roughly 41 % of STC and Mobily subscribers under 40, according to our 2026 log-vs-GA4 reconciliation across eleven Saudi sites. Every one of those sessions is invisible to GA4. Semalt's log-based tracker sees them because it does not depend on JavaScript: the moment the origin serves the page, the session is counted. Across the KSA client base we've measured the gap between 24 % and 58 % additional sessions, higher on Sabq-scale news sites, lower on classical retail.

4. Cross-device journeys without Google Signals

GA4 promises cross-device sessions through Google Signals, but only for users logged into Google on both devices and who accepted personalised advertising in Consent Mode. Independent panel data for KSA shows only about 31 % of users accept the personalised-ads variant of the banner. Semalt uses a technique called server-side fingerprint fusion that respects PDPL principles (no advertising profile is ever built) yet still reconnects the reader who found your article on iPhone during the Duhr break to the buyer who returned on desktop from the office in the evening.

5. Organic revenue per keyword, in SAR

The most valuable feature: connect your CRM or shop (Salla, Zid, WooCommerce, Shopify, Magento 2, Odoo) via webhook and Semalt links every order to the first organic keyword that brought the user. You can see that “افضل شركة سيو الرياض” generated 47,200 SAR in organic revenue last month while a head keyword with 6× the traffic generated zero. With that view you stop chasing vanity metrics and prioritise content by real revenue, in Riyal, not modelled dollars — and you finally have a defensible number for the Semalt dashboard to hand the CFO.

Case study: a Riyadh electronics retailer, 61,000 sessions/month

A bilingual Riyadh electronics retailer — four physical stores in Riyadh Park, Panorama Mall, Al Nakheel Mall and Granada Center, plus a Salla site on .com.sa — walked into February 2026 with this picture:

• GA4 reported 61,300 organic sessions and 94 online orders (0.15 % CVR).
• Search Console reported 118,400 clicks over the same period.
• The gap — almost double — had been explained internally as “GA4 quirk” for three straight quarters.

We connected Semalt Analytics in 14 minutes. First numbers appeared the next morning:

Real organic sessions: 108,100 (76 % more than GA4). Orders correctly attributed to a first organic touch: 316 (3.4×). Verified organic pipeline value: 341,000 SAR versus 123,000 SAR the team had been reporting to the board — a gap of 218,000 SAR that was invisible every single month.

The most valuable insight surfaced when we cross-referenced keywords with revenue: thirteen Najdi-dialect long-tail terms (each between 30 and 210 monthly searches) drove 58 % of pipeline, while a head keyword targeted in every paid campaign generated 3 %. The content plan was re-prioritised in twelve days — by the end of Ramadan, organic pipeline was up 68 %, and the Google Ads budget on the same head keyword was cut by 40 % with no revenue loss.

Saudi PDPL, consent banners and SDAIA guidance

One of the strongest reasons Saudi agencies migrate to Semalt is legal. The Saudi Personal Data Protection Law of 2021 (as amended in March 2023) and SDAIA's implementing regulations converge on the same principle as the wider GCC alignment: any access to information stored on the end-user's device requires informed consent. That includes cookies, local storage and canvas fingerprinting. Server-log tracking accesses nothing on the device, using only information that the browser sends anyway as part of the HTTP request (IP, user agent, referrer). Those signals are processed server-side under a legitimate-interest basis, with the last octet of the IP truncated within milliseconds and never persisted.

The practical outcome is rare: Semalt Analytics counts users who reject the banner too. For a Riyadh retailer with a 34 % consent-acceptance rate that is a 190 % more accurate reach measurement, without a legal grey zone. Semalt provides a bilingual AR/EN DPA that a KSA entity can execute in one click, plus a TOM document aligned with SDAIA guidance and an optional data-residency add-on that pins storage to STC Cloud or IBM Saudi data centres in Riyadh — useful for Ministry of Interior, Ministry of Health and semi-government microsite work.

Ramadan, Eid and White Friday traffic in KSA

GA4's date comparison behaves badly around lunar-calendar events because it defaults to fixed Gregorian windows. Semalt lets you compare Ramadan 1447 to Ramadan 1446 directly, day for day, with the correct offsets. Four patterns hold across every Saudi retail client we've measured:

Setup in 14 minutes

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

More in this series: Semalt AutoSEO: on-page fixes without a dev, Semalt: backlink gap, keyword gap, alerts, AI keyword research: revenue before volume.

FAQ

Does Semalt replace GA4 completely?

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

Is it Saudi PDPL compliant?

Yes. Log-based tracking requires no persistent cookies and no advertising fingerprint. Server-side fusion works only with pseudonymised data, and sessions anonymise after 26 months by default (configurable down to 6 months to meet stricter SDAIA guidance). Semalt provides an Arabic / English DPA, a TOM document and a DPIA template ready for Ministry review.

Does it run on typical KSA stacks?

Yes. The tag ships as a WordPress plugin, a Shopify script tag, a Salla / Zid module for KSA merchants, and SDKs for Laravel, Symfony, Node.js, Java Spring Boot and .NET Core. For cloud-native setups on STC Cloud or Oracle Cloud Jeddah, it is two lines in a Cloudflare Worker or an nginx snippet.

How fast do we see value?

Historical GSC data appears within five minutes. Live tracking shows full data after 24 hours. The Striking Distance report (queries at position 4-10) is actionable on day one and, on most Saudi sites, produces two or three clear content-refresh wins the same afternoon.

Does it work for small websites?

Yes. A Riyadh personal brand with 1,600 sessions/month uses Semalt the same way as an extra.com-scale portal with millions. For small sites the value is spotting which article is one push away from page 1 and optimising it before Google cements the current position.

Does it integrate with Semalt AutoSEO?

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