WordPress in China — when hosting and deps stall
WordPress China is Limited when the site depends on WordPress.com or overseas plugin CDNs. Keep the CMS: remap hosting, dependencies, and ICP filing — replace the CMS only when the job is not keep WordPress.
WordPress China is Limited when the site still depends on WordPress.com or overseas plugin and theme CDNs. The CMS itself is not categorically blocked. Keep WordPress when a China-reachable origin, clean dependencies, and ICP filing (if you terminate in Mainland China) line up. Replace the CMS only when the job is not keep WordPress. This is an origin + deps fork — not a yes/no SKU.
What a WordPress China stack actually is
Hard names your stack decision will use:
- WordPress software vs WordPress.com — Self-hosted WordPress (WordPress.org) can sit on an origin you choose. WordPress.com is hosted SaaS plus plugin, theme, and API hosts. Landscape labels WordPress Limited for that typical WordPress.com / overseas plugin-CDN setup — not a categorical block. “Does it work?” is not a yes/no SKU.
- Failure class — WordPress.com; overseas plugin and theme CDNs; Google Fonts; Gravatar; Jetpack / WordPress.com APIs; GTM/GA; YouTube embeds; reCAPTCHA. The HTML host can return 200 while those assets stall. Inventory hosts. Do not assume the theme is local.
- Usual keep path — Self-host on a China-reachable origin (Alibaba Cloud / Tencent Cloud class — Landscape maps Self-hosted WordPress on China cloud), file ICP when you terminate in Mainland China, and put clean deps on a China CDN. Depth: host in Mainland China, ICP filing — domain DNS, website accessible in China, China CDN / edge. Overseas-only WordPress is a different architecture with known limits — filing is a go-live stall, not “cannot use WordPress.”
- Replace only when the job is not keep WordPress — PageAdmin for government / education / Xinchuang-class sites where the plugin ecosystem is a liability; Baklib when WordPress was mainly a docs / help-center portal. Landscape holds that shortlist.
- Shopify contrast — A Shopify in China storefront is usually SaaS you do not own. WordPress can remain Plan A after origin, deps, and ICP line up.
Vocabulary first. Next: what must be true before WordPress stays the CMS at all.
What must be true before WordPress stays the CMS
Missing a clear origin + deps job stops your product team before a “keep WordPress, add China” sprint is real work.
| Precondition | Why your process stalls |
|---|---|
| Job locked — keep WordPress vs replace the CMS (government / education / Xinchuang, or a docs portal) | A PageAdmin / Baklib sprint is staffed while the keep-CMS path was the job — or the reverse |
| Origin named — WordPress.com / overseas host vs China-reachable self-host | Acceleration is bought for a US VPS or WordPress.com while Mainland China users still wait on those hosts |
| Honest dep inventory — fonts, Gravatar, Jetpack, WordPress.com APIs, GTM/GA, YouTube embeds, reCAPTCHA; do not assume the theme is local | “We self-hosted” still loads overseas plugin CDNs on every page |
| ICP filing scoped when Mainland China termination is the publish plan — not claimed as a ban on overseas-only WordPress | Filing starts too late, or teams treat overseas-only WordPress as illegal |
| Mainland China vantage proof on origin and dep hosts — broadband + mobile; HQ laptop is not proof | Overseas QA “passes” while China users see a broken theme — same class as website not working in China |
| Hong Kong ≠ Mainland China | Regional hosting is reported as WordPress hosting China |
Product teams usually cannot treat “ship the same WordPress.com site globally” as the Mainland China plan. Origin, deps, and ICP are the floor. SKU orientation lives on WordPress alternatives.
WordPress hosting China — origin before a CDN hope
| Stage | Decision / outcome |
|---|---|
| 1. Name the job | Keep WordPress, or replace because the job is government / education / Xinchuang or a docs portal? |
| 2. If keep WordPress | Rule WordPress.com / overseas plugin-CDN as Plan A. Place self-hosted WordPress on a China-reachable origin (Alibaba Cloud / Tencent Cloud class) |
| 3. Inventory deps | Fonts, Gravatar, Jetpack, WordPress.com APIs, GTM/GA, YouTube embeds, reCAPTCHA — list hosts, then self-host, drop, or remap each |
| 4. If Mainland China termination | Treat ICP filing as a go-live stall; bind host + domain DNS — see ICP filing — domain DNS |
| 5. If overseas-only WordPress remains | Keep it as a capped architecture with known limits — not “WordPress China launched” |
| 6. Prove from Mainland China | Broadband + mobile on origin and dep hosts (or China Network Diagnostics) — not only the HQ laptop |
| 7. Cut over, then re-test | China-reachable origin + clean deps on the China journey. A later plugin can restore an overseas CDN |
Hard gate — keep CMS vs replace
Necessity: confusing these two jobs wastes the quarter — either you underfund origin / ICP / dep cleanup, or you replace WordPress when the CMS could have stayed.
| Job | WordPress role | What must already be true |
|---|---|---|
| Keep WordPress for a marketing / product site | Plan A after gates | China-reachable origin; dep hosts inventoried; ICP filing in motion if you terminate in Mainland China |
| Government / education / Xinchuang-class site | Often replace — plugin ecosystem is the liability | PageAdmin (or equivalent domestic CMS) named; Landscape shortlist, not a dump |
| Docs / help-center portal | Replace when that was the only job | Baklib as the portal path |
| “CDN the WordPress.com site” | Myth as Mainland China plan | Origin reachability from the user network — not an HTML cache |
Hard gate — WordPress hosting China
WordPress hosting China is onshore / China-reachable origin versus accelerating WordPress.com or a US VPS. Hong Kong ≠ Mainland China — see host in Mainland China. A China CDN helps after origin and filing line up; it does not turn WordPress.com into an in-country CMS.
Why origin, deps, and ICP stall each other
Engineering constraints you must design around:
| Constraint | What breaks | What to do |
|---|---|---|
| WordPress.com / overseas origin | The CMS admin may work from HQ while Mainland China users wait on WordPress.com or a US VPS. Landscape labels typical WordPress.com / overseas plugin-CDN setups Limited. | Move self-hosted WordPress to a China-reachable origin. Do not treat “try WordPress.com, then a China host on timeout” as Plan A. |
| Plugin / theme CDNs | “We self-hosted PHP” still loads fonts, sliders, and builder assets from overseas CDNs. | Inventory every link / script / srcset host. Allowlist what must stay; self-host or drop the rest. |
| Font and third-party CSS hosts | Many themes pull Google Fonts. Failure looks like fallback type and layout shift. Stack Break Lab keeps a live Google Fonts demo — verdicts flip by carrier; do not freeze one Beijing run as forever-blocked. | Self-host WOFF2 or use a China-reachable font path. Accessibility design: website accessible in China. |
| Gravatar, Jetpack, WordPress.com APIs | Avatar, stats, related-posts, and backup plugins call WordPress.com-class hosts (Jetpack, Gravatar). | Turn off or replace those plugins on the China journey. Do not assume Jetpack is “just a plugin on our server.” |
| Analytics tags and embeds | GTM/GA, YouTube iframes, and similar tags stall the same way as other Google hosts. Stack Break Lab demos: gtm.html, ga4.html, youtube-embed.html. Leftover YouTube on-page VOD is a YouTube alternatives fork. | Inventory tags. Remap measurement and embeds; do not leave them on the critical path. |
| Captcha / forms | Contact Form plugins often load reCAPTCHA. The page returns 200; submit never completes. | Follow captcha forms in China. |
| ICP filing vs overseas-only | Filing is required when public DNS terminates in Mainland China. Overseas-only WordPress does not automatically create that duty — and does not become a China launch. | If you terminate in-country, file before honest public publish (ICP filing — domain DNS). Do not claim WordPress is illegal without filing on an overseas-only architecture. |
Self-hosted PHP ≠ China-reachable deps. An origin in Mainland China with Jetpack, Google Fonts, and a US plugin CDN is still a stalled WordPress in China journey.
HQ laptop QA → false confidence. Testers outside Mainland China never see the broken theme, so the ticket never opens.
Hong Kong / Taiwan reported as WordPress hosting China → wrong stack. Outside-Mainland China performance is not ordinary Mainland China users at scale.
CDN without rewrite → partial win. Faster HTML does not restore blocked plugin hosts. Fix origin and deps, then tune delivery.
What blocks teams that keep WordPress.com as Plan A
- Yes/no SKU thinking — Product treats “Does WordPress work?” as a geo toggle before origin and deps are named.
- WordPress.com as the keep path — Hosted SaaS is confused with self-hosted software you can place on a China-reachable origin.
- Theme assumed local — Builder, slider, and font CDNs stay on every template after “we moved hosting.”
- ICP treated as a WordPress ban — Filing is skipped on a real in-country origin, or demanded on an overseas-only architecture that was never going to file.
- Shopify playbook pasted on WordPress — Teams rebuild commerce rails when the job was keep the CMS. Shopify is usually SaaS you do not own; WordPress can stay. See Shopify in China.
- HQ laptop QA — Green screenshots from outside Mainland China close the ticket.
- Hong Kong conflated with Mainland China — Regional hosting is reported as WordPress hosting China.
- Plugin defaults that re-inject overseas hosts — A “must-have” SEO, backup, or form plugin restores WordPress.com APIs, Gravatar, or reCAPTCHA.
- No owner for the allowlist — The keep path stalls because nobody owns plugin inventory, only “pick a China host SKU.”
- No Mandarin / entity owner — Host bind, ICP filing, and vantage proof sit on rails most global teams lack.
What “fixed” means: Mainland China users can complete the journeys you claim on a China-reachable WordPress origin; overseas plugin / theme / font / Jetpack / tag hosts are gone from that client path; ICP filing is done when termination is in Mainland China; residual overseas-only WordPress is named and capped; replace (PageAdmin / Baklib) is used only when the job is not keep WordPress. WordPress.com with a China marketing claim is not fixed.
China landing partner when hosting and deps stall
Most product teams exploring Mainland China entry need a China landing partner once they stop treating WordPress.com as Plan A — to open a China-reachable host, bind ICP filing when termination is in Mainland China, keep a plugin allowlist, run Mandarin consoles, and prove the journey from Mainland China broadband and mobile. Your team still owns whether WordPress stays the CMS, which templates ship, and which residual overseas line to keep; the partner path makes that keep-CMS stack executable when those rails are not already in-house. Keeping a capped overseas WordPress line for outside-Mainland China viewers does not remove the need for that China landing partner on the primary China path.
What we can offer?
WordPress China work for Mainland China is an origin + dependencies + ICP decision before any “keep the same WordPress.com site” sprint. Chinaready helps your product team keep the CMS on rails that can actually load — or replace it only when the job is not keep WordPress:
- China Readiness Assessment — Decide whether WordPress stays Plan A, which origin and dep hosts sit on the critical path, and whether ICP filing is a go-live stall before a keep-CMS date.
- China Access Acceleration — Keep China-facing pages reachable and fast from Mainland China vantage so a remapped WordPress origin does not die on leftover overseas plugin CDNs.
- China Product Hosting — Place self-hosted WordPress where ICP adjacency, entity consistency, and a China-reachable origin stay coherent after WordPress.com leaves the journey.
- Mobile App Distribution — Align any China app that still wraps a WordPress content API with the same origin and dep gates — not mistake a global WordPress.com feed for a China content plan.
Contact us when you need a WordPress China keep-CMS path before you staff another WordPress.com or overseas-plugin sprint.
Frequently asked questions
Does WordPress in China work if we keep WordPress.com?
Usually not as Plan A for ordinary Mainland China users. WordPress software is not categorically blocked, but WordPress.com and overseas plugin or theme CDNs are the usual stall. Chinaready Landscape labels WordPress Limited for that typical setup. Keep the CMS on a China-reachable origin and clean the deps instead of treating “does it work?” as a yes/no SKU.
What does WordPress hosting China actually mean?
A China-reachable self-hosted origin — Alibaba Cloud / Tencent Cloud class, which Landscape maps as Self-hosted WordPress on China cloud — not accelerating WordPress.com or a US VPS. Hong Kong is not Mainland China hosting. Depth lives in the host in Mainland China Guide. A CDN in front of an overseas WordPress origin is a different architecture with known limits.
When is WordPress China ICP filing required?
ICP filing is a go-live stall when public publish terminates in Mainland China — not a claim that WordPress is illegal on an overseas-only architecture. If DNS and origin stay outside Mainland China, you accept reach and dep limits instead of that filing duty. The ICP filing — domain DNS Guide is the path once termination is in-country.
Which WordPress dependencies usually stall in Mainland China?
Inventory hosts. Do not assume the theme is local. Typical failure class is Google Fonts, Gravatar, Jetpack and WordPress.com APIs, GTM/GA tags, YouTube embeds, and reCAPTCHA on forms. The HTML page can return 200 while those assets hang. Prove each host from Mainland China broadband and mobile — an HQ laptop is not proof.
When should we replace WordPress instead of keeping it?
Replace the CMS only when the job is not keep WordPress. PageAdmin fits government, education, or Xinchuang-class sites where the plugin ecosystem is a liability. Baklib fits when WordPress was mainly a docs or help-center portal. Landscape holds that shortlist; this Guide is the keep-CMS versus origin/deps fork.
Can product teams finish a WordPress China keep path without Mainland China ops?
Usually no. Mandarin host consoles, ICP host bind, plugin allowlists, and Mainland China vantage proof sit on rails most global teams lack. That is when a China landing partner becomes the realistic path.
