Global service map
. Regenerated with each Chinaready Landscape publish.
Quick answer: WordPress is Limited for mainland China — the software itself is not blocked, but a default install reaches for third-party endpoints that mainland browsers cannot load reliably. Gravatar avatars are blocked outright, WordPress.com is inconsistently reachable, and mainland servers routinely get HTTP 429 responses from the wordpress.org update API, which breaks one-click core, plugin, and theme updates. The usual answer is to keep WordPress and decide hosting location first: onshore on Alibaba Cloud or Tencent Cloud with ICP filing, or Hong Kong / Singapore as a no-filing middle path. If the site is really a docs portal or a government / state-owned site cluster, evaluate Self-hosted WordPress on China cloud, PageAdmin, Baklib instead. Availability in China: Limited.
Availability in China: Limited
WordPress is Limited rather than Unavailable in mainland China. Nothing bans the software, and self-hosted WordPress runs fine on mainland cloud. What fails is the set of overseas services a stock WordPress install assumes: the hosted WordPress.com service, the avatar service, and the update endpoints the admin dashboard calls. Answer three questions in order — what breaks in the page, where the site will be hosted, and how the admin stays patchable.
Teams usually say WordPress is blocked in China when the truth is more specific. Separate the pieces before changing anything.
| Dependency | Status from mainland China | Practical impact |
|---|---|---|
| WordPress software (self-hosted) | Not blocked | Core PHP / MySQL stack installs and runs normally on Alibaba Cloud, Tencent Cloud, or any mainland host |
| WordPress.com (hosted service) | Inconsistently reachable | GreatFire measurement across roughly 1,500 tested WordPress.com URLs shows a mixed picture — a large share blocked or intermittently disrupted, the rest loading normally. Not a dependable China-facing host |
| wordpress.org and api.wordpress.org | Reachable but rate-limited | Mainland server IPs frequently receive HTTP 429 Too Many Requests, reported continuously since October 2019. Core, plugin, and theme update checks and one-click installs fail in the admin |
| Gravatar (secure.gravatar.com and related hosts) | Blocked | Every Gravatar host GreatFire can reach a verdict on is blocked. Comment threads and author boxes hang on avatar requests until the browser times out |
| Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | Unreliable | Measurement is mixed rather than uniformly blocked, but font CSS is render-blocking, so a stalled request delays first paint for every visitor. Widely reported as a leading cause of slow China page loads |
| Emoji assets from s.w.org | Third-party dependency you do not need | Core injects an inline emoji detection script plus a DNS prefetch to s.w.org on every page. Harmless overseas, avoidable weight in China |
The pattern is that the site resolves and the HTML arrives, then the page stalls on blocked or slow third-party sub-requests. Fix the in-page dependencies before blaming the host: serve avatars locally, self-host the font files you use, and strip the emoji script and its DNS prefetch. Those three changes are free and often the single largest improvement for a China audience.
Hosting location determines your compliance workload, not your company's location or your audience. The ICP filing requirement follows the physical location of the server that serves the public site.
| Hosting posture | ICP filing | Latency to mainland users | Best fit |
|---|---|---|---|
| Mainland China (Alibaba Cloud, Tencent Cloud, and similar) | Required before the site may go live; also required to use a CDN with mainland points of presence | Best available — traffic stays on domestic networks | China-committed teams with a mainland entity and a real China audience |
| Hong Kong or Singapore | Not required, and not available — you cannot file for an offshore server | Better than Europe or North America but crosses the border, so expect congestion at the domestic evening peak. Hong Kong is commonly cited around 20–40 ms versus roughly 180–250 ms from the United States | Market testing, fast launches, teams without a mainland entity |
| Existing overseas host plus China optimization | Not required | Weakest of the three, and no mainland CDN nodes are available without a filing | Small China traffic share where the work is mostly removing blocked third-party assets |
Two consequences are easy to miss. First, an offshore origin cannot be paired with mainland CDN nodes: Alibaba Cloud requires an MIIT filing number for its Chinese Mainland and Global acceleration regions, and only the region that excludes the mainland is filing-free. Second, offshore hosting removes the filing burden but keeps the cross-border path, which is exactly what causes inconsistent load times. Neither option is strictly better — pick the one that matches how committed the China audience is.
This is the path most teams end on when China traffic matters. Sequence it in this order, because each step gates the next.
A domain registered with an overseas registrar cannot be filed. Transfer it to a registrar approved by the Ministry of Industry and Information Technology (MIIT), complete domain real-name verification, and make sure the verified registrant details match the entity that will file. Tencent Cloud advises waiting a few days after real-name verification so the record syncs into the MIIT database before you apply, otherwise the provincial review can fail on stale data.
Filing is submitted through your access service provider, and the provider requires an eligible mainland instance on the account before it will accept an application. Note that Alibaba Cloud filing is only available through the China site (aliyun.com) with a verified account, and the filing workflow is Chinese-language only — plan for a Chinese-reading colleague or a local partner.
The provider does an initial check, then forwards the application to the provincial communications administration that has jurisdiction over your entity. That authority sets its own document list and verifies the domain registrant details against the filing entity. Published timelines vary widely by province and by whether the entity is filing for the first time, so treat any single number you read as indicative rather than a commitment.
Once approved, the ICP number goes in the site footer linked to the MIIT verification site; some provinces require additional notices. A separate public security bureau filing is commonly required after go-live (often cited as within 30 days) for mainland-hosted sites. Timelines and document lists vary by province and change over time — confirm the current requirements with your hosting provider and your own counsel before you commit to a launch date. Chinaready does not provide legal advice on filings.
With the filing in place, a mainland CDN is available for images, CSS, JavaScript, and media. This is where onshore hosting earns its keep, and it is unavailable to offshore origins.
The most common surprise after moving onshore is that the dashboard stops being able to install or update anything. This is the HTTP 429 rate limiting from the wordpress.org update API, not a firewall block, and it has been reported by mainland site owners since 2019. Do not respond by disabling updates — an unpatched core and plugin set is the larger risk. Practical mitigations, roughly in order of how much control they give you:
Switching CMS is the right call in a minority of cases — usually when the site is a documentation portal, or when a government or state-owned buyer imposes domestic-technology (Xinchuang / 信创) and security-grading requirements that a PHP plugin ecosystem cannot satisfy. None of these is a drop-in WordPress replacement; themes, plugins, and content models do not carry over.
| Option | What it actually is | Genuinely good for |
|---|---|---|
| Self-hosted WordPress on China cloud | The same WordPress, hosted on Alibaba Cloud, Tencent Cloud, or similar, with ICP filing and a China CDN | Keeping your existing content, editors, and theme while fixing performance. The default recommendation for most teams |
| PageAdmin (from Zhongshan Huatuo Information Technology, 中山市华拓信息技术有限公司) | Private-deployment .NET / .NET Core CMS with a free edition, published since 2008. Runs on domestic operating systems and domestic databases, and is marketed around site-cluster management and security-grading compliance | Government, education, and state-owned enterprise site clusters where domestic-stack and security-grading requirements are contractual |
| Baklib | China SaaS content platform combining a knowledge base, a template-driven CMS, and digital asset management, and able to run headless with content in the knowledge base and presentation in the site layer | Help centers, product documentation, and public service portals — teams who used WordPress mainly as a docs tool |
| Z-BlogPHP | Long-running lightweight China PHP blog and small-site system with its own domestic theme and plugin ecosystem | Small content sites where WordPress feels heavy and the maintainer prefers a domestic ecosystem |
| Halo | Modern China-origin open-source Java CMS with a plugin system and a clean API surface, self-hosted | Developer-maintained blogs and content sites where API-first structure matters more than a large plugin catalogue |
| WeChat Official Account (微信公众号) and Mini Programs (小程序) | A distribution channel inside WeChat, not a CMS — no page templates, themes, or site structure to own | Reaching a China audience where they already read, usually alongside a website rather than instead of one. Accounts and Mini Programs carry their own registration and review requirements; confirm the current rules with the platform |
One thing to avoid: DedeCMS (织梦) still appears in older Chinese build guides, but it now requires commercial licensing and has a long public vulnerability history, and current domestic selection write-ups advise against it for new projects. Treat legacy PHP CMS recommendations from a decade ago with suspicion.
A decoupled setup keeps WordPress overseas as the editing tool and content API, and serves mainland visitors from a China-hosted frontend that consumes it. It is attractive because editors keep the interface they know, the admin stays out of the mainland network path, and update management happens in a jurisdiction where the wordpress.org endpoints behave normally.
It does not avoid ICP filing. The requirement attaches to the server that serves the public site, so a frontend hosted in the mainland needs a filing even though the WordPress admin sits overseas — the same logic that makes mainland CDN nodes require a filing number. Going headless changes where the CMS lives, not whether you file. Confirm the specifics for your architecture with your hosting provider and counsel.
Two practical notes. The frontend still needs to fetch content across the border at build or request time, so prefer building or caching content onshore rather than calling the overseas API on every page view. And an internet-exposed WordPress admin and REST endpoint is a standing security liability — restrict admin and API access to known networks, and authenticate the API rather than leaving it open.
Options named on this page are alternatives-page orientation candidates only — Chinaready does not add PageAdmin, Baklib, Z-BlogPHP, Halo, or WeChat channels as Explore / Landscape product tiles. Availability and blocking behaviour change; re-test from a mainland network before you commit. Compare nearby pages for Altis, Pantheon, Google Fonts, Cloudflare CDN, and Amazon CloudFront when the stack also includes managed WordPress hosting or overseas CDN and font delivery.
Mapped Chinaready candidates
Self-hosted WordPress on Alibaba Cloud, Tencent Cloud, or similar mainland hosting with ICP filing is often the most direct path — WordPress software itself is not blocked, but overseas WordPress.com / plugin CDN paths are unreliable.
PageAdmin is a domestic CMS commonly used for government, education, and Xinchuang site clusters when WordPress plugin ecosystems and overseas updates are a liability.
Baklib is a China SaaS knowledge-base / help-center / content-portal path for teams that used WordPress mainly for docs portals rather than marketing sites.
Yes, with work. Chinaready labels WordPress as Limited for mainland China. The software is not blocked and self-hosted WordPress runs normally on mainland cloud, but a stock install depends on overseas services that mainland visitors cannot load reliably — Gravatar avatars are blocked, Google Fonts is unreliable, and the wordpress.org update API rate-limits mainland servers. Sites usually resolve and then stall on those sub-requests, which is why WordPress feels broken in China rather than simply unreachable.
They behave differently, and the distinction matters. WordPress.com, the hosted service, is inconsistently reachable — GreatFire measurement across roughly 1,500 tested WordPress.com URLs shows a large share blocked or intermittently disrupted and the rest loading normally, so it is not a dependable China-facing host. WordPress.org is not blocked, but mainland server IPs frequently receive HTTP 429 Too Many Requests from its update API, reported since October 2019, which is a rate-limiting problem rather than a firewall block. Gravatar, which core loads for avatars, is blocked across every host with a verdict.
If the site is hosted on a mainland China server, you need an ICP filing before it may go live, and you also need one to use a CDN with mainland points of presence. The requirement follows the physical location of the server, not your company's location or your audience. Hosting in Hong Kong, Singapore, or anywhere offshore needs no filing — and cannot obtain one. Filing requires a filing-eligible domain at an MIIT-approved registrar with real-name verification matching the filing entity, an eligible mainland server on the provider's account, and the ICP number published in the site footer. Provincial requirements, document lists, and timelines vary and change, so confirm the current rules with your hosting provider and your own counsel. This is not legal advice.
That is the HTTP 429 rate limiting from the wordpress.org update API hitting mainland IP ranges, which disables update checks and one-click installs across core, plugins, and themes. Options are to route update traffic through a domestic mirror plugin such as WP-China-Yes, proxy installs through overseas nodes with a plugin such as Kill 429, give the server a compliant outbound proxy for WordPress HTTP requests, manage the plugin set from an overseas staging environment and deploy as code, or upload plugin ZIP files manually as a stopgap. Review any third-party plugin that sits in your update path before trusting it in production, and do not simply switch updates off — an unpatched install is the bigger risk.
Hong Kong is a legitimate middle path when you do not have a mainland entity or want to launch quickly. It needs no ICP filing, and latency to mainland cities is commonly cited around 20–40 ms versus roughly 180–250 ms from the United States. The honest tradeoff is that traffic still crosses the border, so it shares congested cross-border links and degrades during the domestic evening peak, and you cannot pair an offshore origin with mainland CDN nodes because those require a filing number. If China is a primary market with sustained traffic, onshore hosting with a filing is still the performance ceiling.
Chinaready currently lists Self-hosted WordPress on China cloud, PageAdmin, Baklib on this page. For most teams the answer is not a different CMS: keep WordPress, move hosting onshore or to Hong Kong, and remove the blocked third-party assets. Switch CMS when the job has changed — PageAdmin for government, education, and state-owned site clusters with domestic-stack and security-grading requirements, Baklib for help centers and documentation portals, and Z-BlogPHP or Halo for lighter self-hosted content sites. None is a drop-in replacement, since themes, plugins, and content models do not carry over. These are alternatives-page orientation candidates only, not Chinaready Explore tiles.
