Measuring Shenma When Analytics Calls It Direct: Logs, UC Referrers and the Webmaster Curve

Shenma disappears in three different dashboards, and teams usually conclude it therefore does not matter. StatCounter often folds it into “other”. GA4 files a chunk of UC Browser traffic as direct, because the referrer is missing or useless. Baidu’s webmaster tools, obviously, do not report a rival engine. The result is a channel that exists in the browser and not in the QBR. You cannot optimise a zero you invented with the wrong report.

Public share figures are a weak substitute. Statista’s January 2025 pageview cut put Shenma near 2.8%. StatCounter’s China mobile series frequently refuses to name it while Baidu sits near three-fifths. Both can be “right” about their panels and wrong about your UC-heavy customers. We argued the strategic version in why the smaller engine still matters. This is the measurement version.

Three instruments, none of them GA4 alone

  • Server logs for YisouSpider. Count fetches, 200s versus 403s, and which hosts were hit. If the spider never appears, you have an access problem, not a ranking problem. The robots.txt trap is the usual cause.
  • Shenma Webmaster at zhanzhang.sm.cn. Index and sitemap status are first-party. Screenshot them monthly. They will not match GA4 sessions, and they are not supposed to.
  • A tagged UC entry point you control. Where you buy Shenma ads or place a UC campaign, use UTMs. For organic, sample referrers containing sm.cn or UC hosts, and accept that some visits will still land as direct. Report a range, not a false precision.

Do not import Baidu AI Traffic Analysis as a Shenma proxy. That dashboard is Baidu’s AI answers only, as Chinese webmasters keep pointing out. A healthy Baidu citation chart can sit next to a Shenma property that has never been verified.

What a sane monthly note looks like

One page is enough: YisouSpider hit count, percent of money URLs fetched, webmaster index trend, known sm.cn sessions, ad-tagged sessions, and a five-query spot check on a phone in UC. Add leads that mention mobile Chinese search if the CRM can bear it. Leave StatCounter off the page or footnote it as context, not as the KPI. If the spot check shows your model numbers and the log shows fetches, you are in the engine even when GA4 shrugs.

Opinion: the industry’s refusal to count Shenma is mostly a tooling habit. The panels undercount browser-bundled search, and then strategists treat the undercount as demand. Measure the crawler and the console you were given. If both are dead, say Shenma is not a channel for this site yet and fix verification. If both are alive and sales still come from Baidu and Tmall, say that too. Either sentence is better than “share is 3%, so we don’t track it”, which is how a mobile engine stays a rumour in the analytics stack and a fact on the factory floor.

One more trap: agency reports that “include Shenma” by dropping a StatCounter screenshot into the Baidu appendix. That is not measurement, and it trains the client to think the channel is a national share figure rather than a crawl and a referrer. If you cannot get logs, say you cannot get logs. A partial webmaster screenshot with a date stamp is still more honest than a blended “China search” line that adds Baidu clicks to a Statista percentage and calls the sum insight. Shenma is small enough that bad measurement hides it completely, and large enough inside UC that a sales team will notice the website failing on the phones their distributors actually use. Those two facts can be true in the same month. The report should be allowed to say both.

Dan Taylor is the founder and editor of International Search Insights (ISI), the publication behind ReadIsi, and a Partner and Head of Innovation (Search & AI) at SALT.agency. He has worked in search for more than a decade, in-house and agency-side, and is regarded as one of the West’s leading voices on search engines beyond Google, including Yandex, Baidu, Naver and Cốc Cốc. On ReadIsi, Dan covers the engines and AI answer platforms that English-language coverage tends to miss: Baidu and ERNIE, Yandex and Alice AI, Naver, Cốc Cốc, Shenma, Sogou, WeChat and Weibo search, plus DeepSeek and Alibaba’s Qwen. He also keeps dated records of documented changes, such as the Yandex, Baidu and Naver algorithm update histories and the DeepSeek, ERNIE and Qwen model update histories. His approach is to take learnings from global search engines and apply logic with a high evidence threshold. A claim needs a source, patterns seen in one market are treated as a hypothesis until they are checked in another, and where the evidence is thin he says so. For brands, that means advice built on what can be shown, with measurement that separates being cited from being chosen. Dan is credited with coining the term “edge SEO” and won the inaugural TechSEO Boost research competition in 2018 for his work on CDN and edge changes for SEO. In 2026 he was credited with coining “Infinite Tail” to describe how keyword research is changing with AI search. He is the author of AI Search Marketing For The Travel Sector, writes for Search Engine Journal, Search Engine Land and Travel Marketing Guy, and has advised technology, SaaS, travel and enterprise ecommerce brands, including Cloudflare, GitLab and Airbnb. He has given multiple talks and panels at the International Search Summit in Barcelona, and has also spoken at Optimization Moscow, brightonSEO, Google Search Central Live Deep Dive Asia in Bangkok, Athens SEO and the Asia SEO Virtual Summit 2026, where his talk looked at how Baidu, Naver, DeepSeek, Tencent, Cốc Cốc and Yandex built their own AI answers.