Baidu Search Resource Platform vs Google Search Console: A Working Comparison

If you run search for a European or UK company, you already have a mental model of Google Search Console. You know what the Pages report tells you, roughly how long a sitemap takes to matter, and what "Discovered, currently not indexed" means when someone asks. The obvious question, when China comes up, is which tool does the same job on Baidu and how much of your existing model still holds.

The short answer: the tool is Baidu Search Resource Platform (百度搜索资源平台), at ziyuan.baidu.com. About two thirds of your model transfers. The remaining third will mislead you, and it is worth knowing which third before you start.

First, the name

You will see it called Baidu Webmaster Tools, or Baidu Zhanzhang (百度站长平台), in most English-language guides. That was the old name. Baidu renamed it to Search Resource Platform years ago, the URL did not change, and the two names refer to the same product. If a guide still says Zhanzhang, it is old enough that the screenshots will not match what you see.

The interface is Simplified Chinese only. There is no English toggle. Browser translation handles it well enough to click around, but keep the Chinese labels somewhere, because they are what you will need when you search for help on a specific report.

Getting in

Google Search Console needs a Google account and a verified property. Baidu needs the same two things, with a harder first step.

You need a Baidu account (百度账号), and registering one requires a mainland Chinese mobile number for SMS verification. International numbers are generally not accepted. Depending on what you do with the account, real-name verification (实名认证) may also come into it. This is the wall most foreign companies hit, and it is worth being clear that it is a real wall rather than a formality you can talk your way past.

Domain verification, once you are in, is familiar: an HTML file at the site root, a meta tag in the <head>, or a CNAME record. Same three options Google gives you, same reliability order, and the file method is still the one that breaks least often.

Feature by feature

| Job to be done | Google Search Console | Baidu Search Resource Platform | How close | | --- | --- | --- | --- | | Sitemap submission | Sitemaps report | 链接提交 (Link Submit), sitemap tab | Same idea. Baidu's sitemap slot has at times been gated by site level rather than open to every verified property, and that gating changes. | | Push one URL | URL Inspection, Request Indexing | 普通收录 manual submission, with a daily quota | Same idea, harder ceiling. The quota is visible and finite. | | Push URLs programmatically | Nothing general purpose. The Indexing API covers job postings and livestreams only | API push (推送接口) with a per-site token, plus a JavaScript auto-push snippet | Baidu is better here, and it is not close. | | Index coverage | Pages report, with a reason per excluded URL | 索引量 (index volume), a count over time | Baidu gives you the number. It does not tell you why a given URL is missing. | | Crawl statistics | Crawl stats report | 抓取频次 (crawl frequency), which you can also ask to raise or lower | Baidu lets you request a change. Google retired that control in January 2024. | | Crawl errors | Folded into the Pages report | 抓取异常 (crawl exceptions) | Comparable, Baidu's is more granular on network-level failures. | | Fetch as the crawler | URL Inspection live test | 抓取诊断 (crawl diagnosis) | Close, and for a foreign site this is the single most useful screen in the product. More below. | | Query and click data | Performance report, 16 months, queries, pages, countries, devices, export and API | 流量与关键词 (traffic and keywords) | Same concept, much thinner. Shorter window, coarser breakdowns, no reporting API worth building on. | | Mobile | Mobile usability report was retired in December 2023 | 移动适配 (mobile adaptation), for declaring PC to mobile URL pairs | Only relevant if you run a separate m. site. Most European sites do not. | | Page experience | Core Web Vitals from real Chrome user data | No field-data equivalent. Baidu publishes a rulebook instead, the 移动搜索落地页体验白皮书 | Google measures. Baidu specifies. Different kind of artefact. | | Structured data | Rich results test, open schema.org vocabulary, public docs | Application-based structured data programmes | schema.org is not the mechanism on Baidu, and the programmes have mostly been closed to foreign sites. | | Manual actions | Manual Actions and Security Issues | Site security notices, plus named public algorithm announcements | Baidu names its algorithms (清风, 惊雷, 细雨, 蓝天) and expects you to read the announcements. | | Removing URLs | Removals tool | 死链提交 (dead link submission), you upload a list | Different shape, same purpose. | | Backlinks | Links report | Baidu retired its external link analysis tool years ago | No backlink report at all. | | Site migration | Change of address, domain level only | 网站改版 (site revision), where you declare old-to-new URL rules | Baidu's is more capable. |

What Baidu has that Google does not

Real submission control. Baidu's product is built around getting URLs into the index, and it gives you three ways to do it plus a quota you can grow. Google's philosophy is that you submit a sitemap and wait. If you have ever wanted a supported way to push ten thousand URLs at Google, Baidu already has it.

Crawl frequency you can argue with. 抓取频次 shows what Baiduspider is doing and lets you request more or less of it. Google removed the equivalent setting.

A dead link pipeline. You hand Baidu a text file of URLs that are gone, and it processes them as a batch. Nothing in Search Console works that way.

A migration tool with rules. 网站改版 accepts URL patterns, not just a domain swap.

What Google has that Baidu does not

Query data you can actually work with. Sixteen months, exportable, with an API and a Looker Studio connector behind it. Baidu's keyword report is a screen you read, not a dataset you model.

Per-URL indexing diagnosis. The reason a page is not indexed is the most valuable thing Search Console tells you, and Baidu has no equivalent of it.

Field performance data. No Baidu CrUX.

hreflang that works. Baidu's handling of international annotations is weak enough that you should plan as if it does not read them. A Chinese-language site or subdirectory needs to stand on its own.

Ranking: what actually differs for a foreign site

This is where most English-language writing about Baidu turns into folklore, so it is worth separating the parts that hold up.

Hosting location and latency

This is real, and it is not mysterious. Baiduspider crawls from mainland China. Cross-border traffic to European origins is slow and lossy in a way that has nothing to do with anyone's algorithm. If your time to first byte from Shanghai is three or four seconds, you will be crawled less often and less deeply, and Chinese users will bounce before your page paints.

You can measure this rather than guess. 抓取诊断 fetches your URL as Baiduspider and reports the fetch time it observed. That number is the honest answer to "is our hosting a problem", and it takes a minute to get.

Serving from Hong Kong or Singapore is the pragmatic middle option: much faster than Frankfurt, and no ICP filing required.

ICP filing

To host on mainland Chinese servers you need an ICP filing (ICP备案), issued through the Ministry of Industry and Information Technology, and that requires a Chinese legal entity. Distinguish it from an ICP licence (ICP许可证), which is a separate, heavier permission for commercial online services.

Treat the filing as the gate on the fastest possible hosting rather than as a ranking factor you tick off. Whether Baidu applies a direct ranking bonus to filed sites is argued about and not well evidenced. What is not argued about is that filed, mainland-hosted sites are faster from inside China, and speed is a factor.

Simplified Chinese content

Baidu ranks Chinese-language pages for Chinese queries. An English page will occasionally surface for a brand or product name and almost never for anything else. Traditional Chinese is not a substitute: zh-TW and zh-HK content is written differently, uses different terminology, and does not read as native to a mainland audience.

Machine translation is obvious to a reader and performs accordingly. This is the largest single cost in any serious Baidu programme, and it is a content budget, not an SEO budget.

The weight Baidu gives its own properties

Baidu 百科, 知道, 贴吧 and 百家号 occupy a meaningful share of the first screen for informational Chinese queries. How large a share is contested, the measurements vary by query set and by year, and the proportion has come down since the criticism Baidu took around 2019. It is still higher than Google's own-property share.

The practical consequence is about target selection rather than despair. For broad informational head terms in Chinese, a foreign domain has a low ceiling. For commercial, product-specific and long-tail queries, the first page is ordinary web results and you can compete on the usual merits.

JavaScript

Baiduspider's rendering has improved and there is no public documentation of how far. Google publishes how its rendering works; Baidu does not. Server-side rendering removes the question entirely, which is why it is the standard recommendation. That is risk management, not a claim about a specific limitation.

Things that are repeated and are not true

"Meta keywords matter on Baidu." Baidu's own webmaster communications have said the tag is not used for ranking. The description can influence how your snippet reads, which is worth doing, but it is not a ranking lever.
"You need a .cn domain." You do not. A .com ranks fine.
"Baidu penalises HTTPS." Baidu has supported HTTPS since 2015.
"Baidu has 60% market share." Measured share differs by source, by device and by year, and it has been falling for a long time. Any single figure deserves suspicion. What is not in dispute is that Baidu is still the largest general web search engine in mainland China, and the one that gives a foreign website a documented way in.

What to realistically expect

Verification and submission is a short piece of work, and on its own it produces visibility, not traffic. For a European site hosted in Europe with no Chinese content, expect partial indexing over weeks rather than days, and expect some sections never to be picked up.

If the goal is presence, so that a Chinese partner, customer or regulator searching your brand name finds you rather than nothing, indexing alone usually does the job and is cheap.

If the goal is acquisition, Baidu is not a channel you switch on. The order that works is: get indexed, read what 流量与关键词 actually shows for your domain, then decide whether Simplified Chinese content and closer hosting are worth the investment. Deciding that before you have any data is how most China SEO budgets get spent badly.

If you want the submission handled

The account requirement is the part that stops most European companies, and there is no clever way around it. Our Baidu submission service takes your domain, runs the submission and reports back on what Baidu actually indexed, at a fixed price per domain. You need no Chinese phone number, no Chinese entity and no Baidu account of your own.

If you want the mechanics of submission rather than the comparison, our guide to submitting a website to Baidu covers the steps. If you are weighing up a wider China programme, book a call and we will scope it honestly.