Baiduspider

What Baiduspider is — Baidu's crawler variants and user-agents, robots.txt compliance (and the cpro/ads exception), reverse-DNS verification, weak JS rendering, and crawl control in Ziyuan.

First published: Jul 3, 2026 · Last updated: Jul 13, 2026 · Advanced
demand #16 in Crawling#41 in How Search Works#193 in Technical SEO#267 on the site
1 evidence signal on this page

Baiduspider is Baidu's web crawler — the Chinese-market equivalent of Googlebot, and the bot that discovers, fetches, and indexes pages for Baidu Search inside mainland China. It runs named variants sharing one Baiduspider token family (image, video, news, favo, cpro, ads), plus a Baiduspider-render JavaScript variant that Baidu documents only in Chinese. Verify it with bidirectional DNS to *.baidu.com or *.baidu.jp (the user-agent is spoofable), because Baidu's own FAQ warns about impersonators. Baidu's FAQ claims it strictly complies with robots.txt — with a named exception: Baiduspider-cpro and Baiduspider-ads run under commercial agreements and ignore it. Its biggest practical limitation vs. Googlebot is weak JavaScript rendering, so server-rendered HTML is the safe default. Control its crawl rate through Baidu Search Resource Platform (Ziyuan).

TL;DR — BaiduspiderBaiduspider is the web crawler operated by Baidu, China's dominant search engine — the Chinese-market equivalent of Googlebot. It discovers, crawls, and indexes pages for Baidu Search, and you manage its access via robots.txt and Baidu's own console, Baidu Search Resource Platform (Ziyuan). is Baidu’s crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. — the Chinese-market GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer.. It runs named variants sharing the Baiduspider tokenA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. family (general PC/mobile, plus -image, -video, -news, -favo, -cpro, -ads), and a Baiduspider-render JavaScript variant that Baidu documents only in Chinese. Verify it by bidirectional DNS to *.baidu.com/*.baidu.jp — Baidu’s own FAQ warns about impersonators. Baidu claims it “strictly complies with robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. protocol,” with a named exception: Baiduspider-cpro and Baiduspider-ads run under commercial agreements and may follow different access rules; it also doesn’t document the non-standard crawl-delay as a reliable control. Because renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. behavior can change, server-rendered HTML is the conservative default for critical content. Verify current controls in Baidu Search Resource PlatformBaidu Webmaster Tools — officially the Baidu Search Resource Platform (百度搜索资源平台) at ziyuan.baidu.com — is Baidu's free webmaster console: verify a site, submit URLs and sitemaps (including the fast API push), and monitor indexing and crawl diagnostics. Since May 2022 registration needs a Chinese mobile number. (Ziyuan).

Evidence for this claim Baiduspider is Baidu Search's crawler and Baidu's Search Resource Platform is the authoritative place to verify current crawler guidance. Scope: Current official Baidu webmaster platform; user-agent text alone is not authentication. Confidence: medium · Verified: Baidu Search Resource Platform Evidence for this claim Crawler access directives use the standardized robots.txt protocol, but engine-specific support and verification should be checked against Baidu's current documentation. Scope: Robots Exclusion Protocol baseline, distinct from undocumented Baidu-specific behavior. Confidence: high · Verified: IETF RFC 9309: Robots Exclusion Protocol

What Baiduspider actually is

Baiduspider (百度蜘蛛) is the crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. operated by Baidu, the search engine that dominates inside mainland China, where Google is largely inaccessible behind the Great Firewall. Its job is the standard crawl → indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. → serve pipeline: discover URLs, fetch pages, and build the index Baidu Search draws from. Baidu’s official English FAQ, “FAQs of Baiduspider” on help.baidu.com, is the rare piece of primary English-language documentation here, and it’s the source for most of the direct quotes below.

The asymmetry that frames everything: Baidu matters domestically, not globally. StatCounter’s June 2026 China snapshot put Baidu at 47.44%, Bing at 23.24%, Haosou at 14.02%, Sogou at 2.62%, and Google at just 2.28% (StatCounter, Search Engine Market Share China). Treat that as a snapshot, not a constant — StatCounter’s China numbers swing meaningfully month to month depending on device mix and methodology (Baidu has been reported anywhere from roughly 40% to 65% across different 2025–2026 snapshots), so re-check the live figure rather than quoting one month forever. The takeaway holds regardless: Baidu leads inside China while Google leads the rest of the world, which is why Baiduspider optimization is treated as its own international-SEO specialty rather than a GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. afterthought. Our market-specific SEO hub covers where Baidu fits alongside Yandex, Naver, and the other regional engines.

User-agent strings and crawler variants

Baidu’s English FAQ names the crawler variants directly. Reproduced verbatim (and yes, Baidu’s own copy repeats “Baiduspider” for both PC and mobile rather than giving distinct strings):

Name of Products | User-agentA user agent is the HTTP request header a client (browser, crawler, or bot) sends to identify itself. For crawlers, a short user-agent token — a substring of that string — is what robots.txt rules actually target. PC search | Baiduspider Mobile search | Baiduspider Image search | Baiduspider-image Video search | Baiduspider-video News search | Baiduspider-news Baidu bookmark | Baiduspider-favo Union baidu | Baiduspider-cpro Business search | Baiduspider-ads other search | Baiduspider

So the officially named variants in the English FAQ are Baiduspider-image, -video, -news, -favo (bookmark), -cpro (the “union”/ad-network crawler), and -ads (business search) — all sharing the Baiduspider family token. The literal general PC user-agent string, given on Baidu’s own site, is:

Mozilla/5.0 (compatible; Baiduspider/2.0; +http://www.baidu.com/search/spider.html)

The mobile UA embeds Baiduspider/2.0 inside an Android WebKit string. Every declared variant points to the same http://www.baidu.com/search/spider.html reference URL — the Baidu equivalent of Googlebot’s google.com/bot.html.

Baiduspider-render — the JS variant Baidu only documents in Chinese

Here’s a subtlety worth getting right, because a lot of write-ups get it wrong: the English FAQ table above does not list a “Baiduspider-render” variant, which has led some guides to call it merely third-party folklore. It isn’t. Baidu documents Baiduspider-render officially — just on its Chinese-language Ziyuan Academy page, “【官方说法】只需两步,正确识别百度蜘蛛(User-Agent)” (“[Official statement] Two steps to correctly identify Baiduspider”). That page splits UAs into three channels — 移动 (mobile), PC, and 小程序 (mini-program) — and lists an alternate render UA alongside the plain one:

Mozilla/5.0 (compatible; Baiduspider-render/2.0; +http://www.baidu.com/search/spider.html)

with a matching mobile string and a mini-program variant (Baiduspider-render/2.0;Smartapp). So Baiduspider-render is officially documented — just Chinese-only, absent from the English FAQ. What Baidu does not publish is a spec for what “-render” actually does differently; unlike Google, Baidu doesn’t document its JavaScript renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. capabilities. That gap is where the JS-rendering caveat below comes from.

How to verify Baiduspider (and not a spoofed bot)

The user-agent string is trivially spoofed — anyone can send a request that says Baiduspider. Baidu’s own FAQ warns about exactly this, describing “spammers or other trouble makers who pretend to be Baiduspider,” and its guidance is to verify with DNS, not the string. From the FAQ, verbatim:

We recommend using reverse DNS lookup to verify Baiduspider. Verification methods are different under linux/windows/os environments.

It gives per-OS commands — host on Linux, nslookup on Windows, dig -x on macOS — with worked examples, and the rule that matters:

The hostname of Baiduspider is *.baidu.com or *.baidu.jp. Others are fake hostnames.

The two *.baidu.com and *.baidu.jp domains are the quirk to remember — Baidu crawls from both a .com and a .jp reverse-DNS namespace, so a legitimate Baiduspider hostname can end in either. (One of Baidu’s own worked examples even resolves to BaiduMobaider-119-63-195-254.crawl.baidu.jp — note “BaiduMobaider,” not “Baiduspider,” in that hostname; that’s a real quirk in Baidu’s documentation, not a typo to silently correct.)

Baidu’s English FAQ spells out only the reverse-lookup half in its prose, but its Chinese Ziyuan Academy page is more explicit: it names the whole process “双向DNS解析认证” (bidirectional DNS resolution authentication) and breaks it into “第一步:DNS反查IP” (Step 1: reverse-lookup the IP) and “第二步:对域名运行正向DNS查找” (Step 2: run a forward DNS lookup on the hostname). That’s the complete, correct method — reverse-lookup the IP to confirm a *.baidu.com/*.baidu.jp hostname, then forward-lookup that hostname and confirm it resolves back to the same IP. It’s the same two-step approach you’d use to verify GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. or BingbotBingbot is Microsoft Bing's primary web crawler — the bot that discovers, fetches, and renders pages to build the Bing index. That index also powers Yahoo, DuckDuckGo, Ecosia, and Microsoft Copilot, so Bingbot's reach is far wider than Bing's own search-market share. — the commands are in the Scripts tab.

Baiduspider and robots.txt

Baidu makes an unusually strong, quotable compliance claim in its own FAQ:

Baidu strictly complies with robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. protocol.

And it supports the standard controls you’d expect. Per Baidu’s Ziyuan Academy material, Baiduspider supports wildcard matching with * and $ in robots.txt paths (parity with Google and Bing), and does exact, case-sensitive path matching. You can set per-user-agent rules — Baidu’s FAQ gives worked examples, including this one that blocks everything for general Baiduspider but allows the image crawler into /image/:

User-agent: Baiduspider
Disallow: /
User-agent: Baiduspider-image
Allow: /image/

(Baidu also notes that Baiduspider-video doesn’t currently support these rules.)

The named exception to “strict compliance”

The interesting tension: Baidu claims strict compliance but documents a named, official exception. Baiduspider-cpro (the ad-network crawler) and Baiduspider-ads (business search) operate under separate commercial agreements and ignore robots.txt by design. Verbatim from the FAQ: “Baiduspider-cpro will not work on the records set by robots.txt” and the same for -ads. So the honest framing isn’t the vague “Baidu doesn’t always respect robots.txt” you’ll see on aggregator sites — it’s that Baidu’s standard crawlers comply, with two contractually exempt ad crawlers as the one concrete, documented carve-out.

A separate, narrower point that’s easy to conflate: Baiduspider does not honor the non-standard crawl-delay directive. Search Engine Journal’s Abby Hamilton documented this in The Modern Guide To Robots.txt (Nov 2024) — her crawler comparison table lists “Baidu | Baiduspider | No” for crawl-delay support (Yandex’s YandexBotYandexBot is the main web crawler operated by Yandex, Russia's dominant search engine. It discovers and fetches pages for Yandex Search, is one of a family of Yandex robots, and supports a Yandex-only robots.txt directive (Clean-param) that Google and Bing don't have., by contrast, is a “Yes”). That’s a different claim from standard Allow/Disallow compliance, and worth keeping straight so you don’t accidentally contradict Baidu’s own robots.txt claim.

A real example: baidu.com’s own robots.txt

Baidu practices robots.txt segmentation on its own domain. Its live robots.txt gives its own Baiduspider a shorter disallow list than it gives Googlebot, MSNBot, Sogou, and Youdao (which additionally get /shifen/, /homepage/, and /cpro blocked), and blocks everything (Disallow: /) for any unnamed user-agent by default:

User-agent: Baiduspider
Disallow: /baidu
Disallow: /s?
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

One operational detail from the FAQ worth knowing when you’re editing rules: if you tighten robots.txt after Baidu has already indexed a site, “it usually takes 48 hours for the updated robots.txt to take effect.”

Does Baiduspider render JavaScript?

This is Baiduspider’s biggest practical limitation relative to Googlebot, and it’s worth being precise about what’s official and what isn’t. Baidu’s English FAQ doesn’t address JavaScript rendering at all — there’s no capability spec the way Google publishes one for Googlebot. What we have instead is consistent industry testing. Dan Taylor put it bluntly in Search Engine Journal’s Google vs Baidu comparison (Mar 2021): “Baidu is notoriously bad when it comes to crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. JavaScript, so make sure that all your important content and links are served in plain HTML on both the mobile and desktop versions of your website.”

That aligns with the position this site already takes. Our contentful SEOContentful SEO is the practice of making content delivered through the Contentful headless CMS crawlable, indexable, and rankable. Because Contentful serves content over APIs and renders no HTML itself, every SEO outcome is decided by the frontend that consumes it. coverage notes that Bing, Yandex, and Baidu “may not index [client-side-rendered JS] at all,” and that dynamic rendering is deprecated as a general Google technique. Put the three big crawlers on a spectrum: Googlebot does full evergreen-Chromium rendering, BingbotBingbot is Microsoft Bing's primary web crawler — the bot that discovers, fetches, and renders pages to build the Bing index. That index also powers Yahoo, DuckDuckGo, Ecosia, and Microsoft Copilot, so Bingbot's reach is far wider than Bing's own search-market share. does solid Chromium/Edge rendering, and Baiduspider is the weakest of the three at JavaScript — with plain, server-rendered HTML being the universally safe fallback across all of them.

Practical guidance for a China-facing site: default to server-side rendering or static HTML so critical content, links, and metadata exist in the initial response before any JavaScript runs. Treat client-side-only content as an indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. risk for Baidu specifically, independent of whether it ranks fine in Google. Frame SSR as an industry-consensus best practice here — not as an official Baidu recommendation, because no primary Baidu statement on JS rendering exists to cite.

Controlling Baiduspider’s crawl frequency

Baidu presents crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. as algorithmically self-adjusted, not something you set directly. From the FAQ, verbatim:

In order to ensure the search results cover most of your pages, Baiduspider must keep the crawling at a certain level. We have been trying our best to avoid increasing the loading to your servers, and to adjust the frequency based on combined factors, such as your server’s capability, your site’s quality and the update frequency of your site.

That’s the same server-capability-plus-demand logic Google and Bing describe. The FAQ names a feedback form (webmaster.baidu.com/feedback/index) as the official lever for reporting over-crawling — “If you find any unreasonable access from Baiduspider, please inform us.”

At the product level, Baidu Search Resource Platform (百度搜索资源平台, at ziyuan.baidu.com — the console historically called “Baidu Webmaster Tools”) is Baidu’s equivalent of Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility.. Its manual index confirms a “抓取频次” (Crawl Frequency) product area where site owners can view and cap Baiduspider’s crawl rateCrawl rate is how fast a search engine crawler fetches pages from your site — the number of simultaneous requests it makes and the delay between them. Google sets it automatically based on your server's health; it's the supply side of crawl budget, not a ranking factor. directly, alongside robots and crawl-diagnostics tools. Treat the feedback form as the official escalation path in Baidu’s English docs and the Ziyuan Crawl Frequency dashboard as the practical, UI-level control. (The exact in-product menu path sits behind a logged-in Ziyuan account, so confirm the current UI there before quoting specific steps.)

hreflang and other Google-standard signals

Signals that are standard for Google don’t all carry over to Baidu — and this is an industry/practitioner finding, not something either company documents. Google’s own localized-versions documentation is scoped entirely to Google Search and makes no claim about whether Baidu, Bing, or Yandex honor hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.. On this site, our hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. guide states it plainly: Baidu doesn’t support hreflang at all — the fallback is to set an accurate content-language and <html lang> so Baidu can at least read the page’s language. That’s additive to my own Google-scoped hreflang work (the Ahrefs hreflang tags guide and the study of 374,756 domains, both of which discuss Google’s implementation only) rather than a contradiction of it.

No English rep culture — why the FAQ is unusually valuable

One thing that genuinely sets the Baidu ecosystem apart: unlike Google (Gary Illyes, John Mueller), Bing (Fabrice Canel), or Yandex, Baidu maintains no visible English-language public-rep Q&A culture. There’s no named spokesperson doing SEO community back-and-forth. Baidu’s clearest official English voice is the unsigned, institutional help.baidu.com FAQ. That’s why that FAQ — and the Chinese-language Ziyuan Academy pages behind it — are so valuable: most operational knowledge about Baiduspider in the English-speaking SEO world comes from practitioner testing (server-log analysis, DNS-verification exercises, robots.txt trial and error) rather than official rep commentary. Michael Bonfils summarized the broader lesson in Search Engine Land’s Baidu vs. Google: “SEO strategies that work for Google may not always translate directly to success on Baidu, China’s dominant search engine.”

For where Baiduspider sits in the bigger picture — the crawler family, Googlebot and Bingbot as peers, the user-agent concept, and robots.txt — the crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. hub ties it together, and international SEO is the home for the China-market context.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.