WordPress in China. Yes, it works.

If it’s hosted on a server in mainland China, yes. The ICP filing (ICP备案) is made through the provider whose server hosts the site, and it has to clear before the site goes live. A site on a Hong Kong or overseas server has nothing to file, but every mainland visit then crosses the border. An ICP licence (ICP许可证) is a separate permit, needed by sites that charge users for information or online services, and we check in the audit whether yours does.

Yes. WordPress stays WordPress. The admin interface is the same, the content workflow is the same, and the editorial roles work the way they always have. The changes we make under the hood are mostly invisible to the editorial team.

No published benchmark compares the two in China, so we won’t quote a number. The difference is in how a page gets built. Astro ships finished HTML files. WordPress builds each page in PHP from a database unless a page cache answers first, and on a tuned mainland server it usually does. Most of the delay in China comes from the outside hosts the theme and plugins call, and clearing those is the same job on either stack.

Probably not, in its current state. But it can usually be made to work. We strip out the Google dependencies, swap the fonts, and reroute the integrations. Most Elementor and Divi sites we inherit are running cleanly inside the Firewall within a few weeks of getting started.

They often fail. WordPress.org rate-limits some Chinese networks, which get HTTP 429 errors back; its staff said so on the project’s Meta Trac on 21 March 2020. The dashboard doesn’t warn you. It simply stops offering updates. We route updates through a proxy or run scheduled manual update windows, so your team shouldn’t have to think about it day to day.

Yes. Polylang 3.8.7 makes no outside calls when it serves a page, so it behaves the same on a mainland server as anywhere else. WPML suits three or more languages and heavy translation work. For two or three, Polylang is the lighter install. The choice comes down to your editorial process.

WooCommerce itself works fine. The work is in the checkout layer. Chinese consumers expect to pay through Alipay, WeChat Pay, or UnionPay, almost always on mobile, almost always via QR code. We add those payment gateways through dedicated plugins, and we redesign the checkout flow for the way Chinese users actually buy. Out of the box WooCommerce assumes credit cards and PayPal, which don’t apply here.

Technically yes, with WordPress Multisite or a multilingual setup. In practice we usually recommend two separate WordPress installs, one outside China and one on a mainland Chinese server. The reason is performance: a single global install means Chinese users are pulling from servers outside the Firewall, which defeats the point. Two installs share editorial workflows where it makes sense and stay independent where they need to.

Standard WordPress hardening still applies. We disable file editing in the admin, lock down xmlrpc, enforce two-factor authentication, and run a Web Application Firewall configured for the Chinese cloud provider. The extra discipline in China is around plugin updates: when auto-updates fail, the site can sit on an outdated plugin version longer than a Western team is used to. We monitor and patch on a fixed schedule.

We use Aliyun, Tencent Cloud, and Huawei Cloud depending on the project. All three are mainland-licensed, all three perform well, and all three support the WordPress stack properly. Aliyun is usually the default for marketing sites, Tencent Cloud is strong for sites that integrate with WeChat, and Huawei Cloud comes up more often for clients who already use Huawei infrastructure elsewhere. We handle the hosting account, the ICP filing, and the day-to-day server work, so you never have to log into a Chinese hosting panel yourself.