WordPress CDN is GA for Mainland China

Chinaready WordPress CDN is generally available: a free Alibaba Cloud mirror of wp-includes and GPL plugin files for allowlisted Origins.

Chinaready WordPress CDN is now generally available as a free WordPress CDN China utility — a Mainland China–reachable Alibaba Cloud CDN snapshot of WordPress core wp-includes and selected GPL plugin and theme static files. It sits beside Google Fonts for China and Frontend CDN.

When WordPress static assets stall in China

WordPress sites serving China often load dozens of files from wp-includes and wp-content over a slow or unreliable cross-border path. Themes, page builders, and SEO plugins multiply those requests. When origin latency climbs, so does front-end wait time. The HTML page can return 200 while core, plugin, and theme CSS and JS still hang.

That is a WordPress plugin CDN / theme-host problem, not a yes/no “does WordPress work” SKU. Keep-CMS origin, ICP, Jetpack, Google Fonts, and replace-CMS forks live on WordPress in China. This post is the free static-file utility for matching GPL files.

Moving those static files onto a China-reachable hop removes one request chain. It does not, by itself, make the rest of a WordPress site ready for Mainland China. Uploads, HTML, commercial plugins, fonts, APIs, and tags still need to be tested as part of the actual stack.

What general availability includes

This product is a curated static snapshot, not a full-site CDN and not an on-demand proxy of wordpress.org. Files are published at wp-cdn.launchready.cn behind an Origin allowlist. The live inventory is manifest.json.

Included

  • WordPress core static files under versioned paths such as /wp/6.9.7/wp-includes/…
  • Curated GPL / wordpress.org-redistributable plugins and themes (Elementor Lite, Blocksy, Contact Form 7, Yoast SEO, WooCommerce, and more)
  • Versioned wp-content paths of the form slug@version

Not included

  • Site uploads and media libraries
  • Admin PHP and dynamic endpoints
  • Commercial plugins (for example Elementor Pro)
  • Optimizer-merged CSS/JS bundles with site-specific hashes

If you need Google Fonts, use Chinaready Google Fonts — covered in GFonts is GA for Mainland China. If you need npm or ajax.googleapis libraries, use Frontend CDN. If you need HTML and media for the whole site, pair this with a normal full-site CDN strategy — China CDN / edge.

How access works

Files are available only to approved Origins. Approving a domain for Google Fonts or Frontend CDN does not automatically approve it for WordPress CDN — each product has its own allowlist, CORS rules, and CDN Referer configuration.

To apply, use the Chinaready Contact form and list every production and staging Origin that should load assets.

Connect with the WordPress CDN plugin

After allowlisting, install the free GPL plugin Chinaready WordPress CDN. It rewrites URLs from wp_enqueue_script() and wp_enqueue_style() so matching core, plugin, and theme static assets load from the CDN when the installed version matches the published snapshot.

Get the plugin

Typical flow

  1. Apply for allowlist and list every Origin.
  2. Upload the ZIP under Plugins → Add New → Upload Plugin (or install from WordPress.org once the listing is live).
  3. Activate the plugin.
  4. Open Settings → Chinaready WP CDN to review version matches and rewrite scopes.

Assets that do not match the snapshot stay on your origin, so you avoid silent 404s from version drift.

Who this is for

Teams running WordPress for China-facing traffic — marketing sites, event sites, commerce fronts, and product blogs — where core and plugin static assets currently leave the country on every page view.

If a plugin, theme, or version you need is missing from the snapshot, request it through Contact. We expand the corpus based on real customer Origins and licenses we can redistribute.

A free utility, not a full readiness verdict

Chinaready WordPress CDN is operated by Chinaready as free China-launch infrastructure under launchready.cn. It addresses one concrete dependency class — overseas WordPress static assets — so matching GPL files can take a path that works inside Mainland China networks.

It is not a paid service SKU, and using it does not replace origin, ICP, or leftover-host work on WordPress in China. If static files are only one of several uncertain dependencies, the China Readiness Assessment maps the stack and recommends which route is worth considering.

Open WordPress CDN to review the live snapshot, plugin, and service boundaries — then apply for free use with every Origin that must load the files.

Get a route recommendation for your stack.

Map your dependencies, get a measured readiness verdict, and a concrete 30/60/90 route.