A second wave of fabricated Singapore traffic is showing up in Google Analytics 4, and part of it is now built to look like real visitors instead of obvious bots. Search Engine Watch recorded 365 of 419 active users reporting as Singapore-based in a GA4 Realtime snapshot on September 18, with desktop devices making up more than 85 percent of that traffic. Any site owner reading a geography report without checking engagement first could mistake the spike for a genuine new market.
The pattern was not isolated to one property. Developer Ken Imoto documented a separate case on September 2, finding Singapore sessions had jumped ninefold in a single day. That traffic carried the classic markers of automation: a 0 percent engagement rate, an average session of 0.5 seconds, and 99 percent of visits arriving as Chrome on Windows desktop, nearly all reporting the same screen resolution.
Shopify merchants describe the same problem at a larger scale. One merchant reported as many as 80,000 Singapore visitors in a single day in early September. A separate August report said the traffic had inflated normal volume by 20 to 30 times in earlier bot waves, a scale large enough to distort conversion-rate reporting for any store that does not segment by geography.
The most recent incident suggests the traffic is evolving rather than fading. One Shopify merchant reported on September 17 that the platform tagged roughly 74 percent of a large Singapore spike as bots, while the remaining share still appeared engineered to resemble human browsing. Google’s own Analytics community has logged repeated complaints about suspicious Singapore and China traffic, including new reports this summer.
The distinction from earlier waves is what makes this one worth tracking. Prior Singapore spikes left an unmistakable footprint: 0 percent engagement and sub-second sessions that any analyst would flag on sight. This month’s traffic, by Shopify’s own detection, includes sessions designed to avoid that signature, which means the duration and bounce-rate filters teams have relied on to auto-exclude bot sessions may no longer catch the full volume.
Neither Search Engine Watch nor the merchants cited have identified the source or motive behind the traffic, and no platform involved, Google or Shopify, has published a technical explanation for why Singapore keeps recurring as the origin point. That gap leaves open whether this is ad fraud, scraping infrastructure, or something else routed through Singapore-based servers.
For a search or ecommerce team, the fix is not waiting for GA4 to solve the problem. Cross-check any unexplained regional or device spike against engagement rate, session duration, and conversion data before it feeds into a forecast, budget decision, or client report; a Singapore desktop surge with no matching revenue is very likely still inflated, regardless of whether GA4’s own bot filtering flags it.
Teams running paid campaigns or affiliate programs with Singapore in their footprint should audit traffic-source rules and consider IP or behavior-based exclusions now, before a future wave that mimics human sessions even more closely makes manual review the only reliable filter left.
Search Engine Watch (Radu Tyrsina) reported this pattern on September 18, 2026, building on findings from a September 2 investigation by developer Ken Imoto and Shopify merchant reports from August and September 2026.
