Choosing between WPML, Polylang and TranslatePress for a WordPress site in China comes down to one test: what does the plugin call out to while it builds a page for a visitor? Polylang passes outright: it makes no outside call when it serves a page. TranslatePress, with automatic translation switched on, can stop a page mid-render to ask Google or its own AI service for the strings it has not stored yet. WPML’s code goes only to paying customers, so we could not read what it does when it serves a page, though its automatic translation runs in the editor, through WPML.org. For a Chinese site on a mainland server, Polylang is the pick with nothing to go wrong on the network, and TranslatePress works if every translation is in place before the site goes live.
| Plugin | Outside call while serving a page | Default Chinese URL | Hreflang, Simplified-only site | Translation service |
|---|---|---|---|---|
| Polylang 3.9.2 | None found in the code | /zh/ | zh | None in the free plugin |
| TranslatePress 3.3.9 | Yes, when automatic translation is on and a string is new | /zh-cn/ | zh-CN and zh | Google Translate or TranslatePress AI, off by default |
| WPML | Not inspected (closed code) | /zh-hans/ | zh-Hans on WPML’s own site | WPML’s cloud editor, used from the admin |
The Shanghai team read the Polylang and TranslatePress code from WordPress.org on 14 November 2026, in the versions named in the table. The plugin choice is one part of the build that our page on WordPress in China covers end to end.
Judge a multilingual plugin by what it calls at runtime
The usual comparison runs on features, such as the translation editor and WooCommerce support. On a server in Shanghai or Beijing the network behaviour matters more, because a call to a host outside the mainland, made while a page is being built, has to cross the border and come back before the visitor sees anything.
Plugins make two kinds of call. Admin calls fire when an editor saves a setting or checks for updates, and a slow one leaves that editor staring at a spinner.
The other kind fires while the page is being built for a visitor. That one costs the visitor, and every visitor after them who lands on a page with something new on it.
You can run the test on any plugin from WordPress.org. Download the zip, search
the code for wp_remote_get, wp_remote_post and curl_init, and follow each
hit back to the moment it fires.
Polylang: no outside call when a page is served
Polylang keeps each translation as an ordinary WordPress post or term, linked to its siblings. A visitor asks for the Chinese page and WordPress loads the Chinese post from your own database. Nothing leaves the server.
Polylang 3.9.2, updated 9 November 2026, contains five remote requests, all on the admin side: a flag image check when a language is saved, a ping of each language domain when separate domains are saved, the translation-pack update check, and the licence and updater code used by paid add-ons. None runs while a page is served. Source: ChinaWebFoundry reading of the plugin code from WordPress.org, 14 November 2026. https://wordpress.org/plugins/polylang/
The same five call sites were in version 3.8.7 on 18 October and in 3.9.1 on
31 October (we looked twice for a licence check on page loads, because it would have been
a fair guess, and there isn’t one). Polylang’s free version has no machine
translation engine at all, so there’s nothing to switch off and no API key to
store. Its default URL for Simplified Chinese is /zh/, and the slug is an
editable field on the language settings screen, so a site that wants /cn/ can
have it.
On a mainland server, that’s all Polylang does on the network.
TranslatePress: automatic translation inside the request
TranslatePress is built another way. It lets WordPress build the page in the original language, catches the finished HTML in an output buffer, and swaps each string for the translation stored in its own tables. That part is local.
The outside call comes from automatic translation. Turn it on and
TranslatePress sends any string it has not stored yet to a translation engine,
waits for the answer, saves it, and only then hands the page over. The default
engine is TranslatePress AI at mtapi.translatepress.com, which needs a
licence key the plugin offers free. The other engine in the free plugin is
Google Translate at translation.googleapis.com, with your own Google API key.
TranslatePress 3.3.9 ships with automatic translation off. When it is on, each engine call allows a 45-second timeout, and a request-wide budget of 10 seconds stops further batches once it has passed. Visitors whose browser identifies as a crawler, Baidu and Google included, never trigger a call. Source: ChinaWebFoundry reading of the plugin code from WordPress.org, 14 November 2026. https://wordpress.org/plugins/translatepress-multilingual/
The budget is checked before each batch, so it cannot cut short a call already waiting. A visitor who lands on a page with new strings waits for the first batch, up to 45 seconds.
And the engine hosts? Barely tested from the mainland.
GreatFire read
translation.googleapis.comas reachable from mainland China at its last test, on 8 May 2026. It has not testedmtapi.translatepress.com. Source: GreatFire, read 14 November 2026. https://en.greatfire.org/https/translation.googleapis.com
The Google result is six months old, and the TranslatePress AI host has never been tested. Either way, the page waits on a host no recent test covers. Baiduspider can’t fill the gaps for you either: crawlers are barred from triggering translations, so it sees only what is already stored.
The fix is to translate before launch. Run each page through the translation editor, or let automatic translation fill the tables on a staging copy outside China, then move the database with the site and switch automatic translation off on the mainland server. With it off, the engine calls never fire.
WPML in China: the zh-hans default and a cloud editor
WPML’s code isn’t on WordPress.org, so this section rests on what WPML documents and what its own site prints.
Its default code for Simplified Chinese is zh-hans. WPML’s site, which runs
on WPML, serves its Chinese pages at wpml.org/zh-hans/ and marks them
hreflang="zh-Hans" (page head read on 14 November 2026).
WPML comes with 65 pre-configured languages, added from a search list. The code, locale and hreflang fields appear in the form for a custom language. Source: WPML, How to Add Languages in WPML, updated 16 May 2024. https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/
WPML’s automatic translation runs in its Advanced Translation Editor, a service on WPML’s side. You review the result before you publish.
“You will see the translations before publishing, exactly as they will appear to visitors.” Source: WPML, Advanced Translation Editor documentation, updated 31 October 2025. https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/
WPML attributes editor connection failures and stuck translation jobs to “problems connecting with WPML.org”. Source: WPML errata, published 14 November 2022, updated 14 September 2026. https://wpml.org/errata/cant-connect-to-the-translation-editor-or-stuck-translation-jobs/
That puts the dependency in the editor’s session, during translation work. The three WPML pages we read name no host for it beyond WPML.org. If you run WPML on a mainland server, test the editor from that server before the translation work is scheduled.
GreatFire’s one recent conclusive test of
wpml.orgfrom mainland China connected normally (0 of 1 disrupted), on 16 August 2026. Source: GreatFire, read 14 November 2026. https://en.greatfire.org/https/wpml.org
zh, zh-CN or zh-Hans: what each plugin prints
This section is the one to forward to whoever owns your SEO tags.
All three codes are valid. Google reads the first part as the language and the optional second part as a region or a script.
Hreflang takes an ISO 639-1 language code and an optional ISO 3166-1 region. For a region such as
zh-TW, Google derives the script (Traditional). You can also name the script with ISO 15924:zh-Hantfor Traditional,zh-Hansfor Simplified. Values are case-insensitive. Source: Google Search Central, Tell Google about localized versions of your page, last updated 21 September 2026. https://developers.google.com/search/docs/specialty/international/localized-versions
So all three are correct. Your plugin decides which one gets printed, and when it switches.
| Site languages | Polylang 3.9.2 | TranslatePress 3.3.9, default | WPML |
|---|---|---|---|
| English and Simplified Chinese | en, zh | en-US, zh-CN, plus en, zh | zh-Hans on WPML’s own site |
| Add Traditional Chinese (Taiwan) | zh-CN, zh-TW | zh-CN, zh-TW, plus one zh for the first Chinese language | Not observed |
<html lang> on the Chinese page | zh-CN | zh-CN (default format) | Not inspected |
Polylang’s rule is exact, and it means the page and its hreflang carry
different codes by design. Polylang builds a W3C code from the WordPress
locale, so zh_CN becomes zh-CN, and puts that in the <html lang>
attribute. For hreflang it drops the region, unless two languages on the site
share the same first part. A Simplified-only site prints hreflang="zh". Add
Traditional Chinese and both Chinese tags switch to zh-CN and zh-TW. It
never prints zh-Hans. Developers who want script codes can change the list
with the pll_rel_hreflang_attributes filter.
TranslatePress prints both the region code and the bare language by default
(“Show Both” in its advanced settings). With two Chinese variants it prints one
bare zh, pointing at whichever Chinese language comes first in your language
list.
Open view-source on a live page after you install and read the tags it actually prints.
Simplified, Traditional, and when a site needs both
A site for mainland readers is written in Simplified characters. Mainland law makes them the national standard.
The national common language and script are Putonghua and standardised Chinese characters (规范汉字). Traditional characters (繁体字) are kept or used only in listed cases, such as heritage sites, calligraphy and publishing or research that needs them. Source: Standard Spoken and Written Chinese Language Law (国家通用语言文字法), Articles 2 and 19, revised 27 December 2025, in force 1 January 2026. https://policy.mofcom.gov.cn/claw/clawContent.shtml?id=104475
You need Traditional as well when you also sell to readers in Hong Kong or Taiwan. That is a second language in every plugin, with its own pages and its own review, because the wording differs as well as the characters. WordPress itself ships three Chinese locales, and they are not kept up equally.
WordPress core translation packs for 7.1:
zh_CN(简体中文) updated for 7.1 on 19 August 2026,zh_TW(繁體中文) last packaged for 7.0.8 on 7 November 2026,zh_HK(香港中文) last packaged for 6.2.15 on 15 July 2022. Source: WordPress.org translations API, read 14 November 2026. https://api.wordpress.org/translations/core/1.0/?version=7.1
WordPress falls back to English for any string a pack does not have, so a Hong Kong admin screen can mix the two.
Then there’s the font. A theme that loads its Chinese typeface from Google Fonts adds a host whose answer depends on where you stand.
From an Alibaba Cloud instance in Zhangjiakou on 28 August 2026, fonts.googleapis.com completed 72 of 72 requests at a median 111ms time to first byte. From a Beijing China Mobile residential line on 30 August 2026 it answered 0 of 54. Source: 21YunBox, A Chinese Cloud Probe Is Not a Chinese Visitor: The Same Hosts, Opposite Answers, 28 to 30 August 2026. https://www.21cloudbox.com/a-day-of-third-party-requests-from-inside-china.html
Self-host the Chinese font files, or use the system fonts phones already carry. The wider work of writing for mainland readers sits in our guide to website localisation for China, and the search side of a Chinese WordPress site is in our guide to Baidu SEO for a WordPress site.
Frequently asked
Does WPML work in China?
We have no dated test that answers it either way. WPML’s own site, wpml.org,
connected normally in GreatFire’s one recent test, on 16 August 2026, and
WPML’s automatic translation runs from the admin, before publishing. WPML’s
code is not public, so we cannot say what it calls when it serves a page. Test
it on your own mainland server before you commit.
Can I change Polylang’s zh slug or its hreflang?
Yes. The slug is an editable field when you add or edit the language in
Polylang’s settings, so /zh/ can become /cn/ or /zh-hans/. The hreflang
tag is built in code. To print zh-Hans instead of zh, a developer adds a
short function to the pll_rel_hreflang_attributes filter. Change the slug
before launch, not after search engines have indexed it.
Is TranslatePress safe on a mainland server?
With automatic translation off, it never contacts an engine, and pages are served from its own tables. The risk comes with automatic translation on, because a visitor can wait on a foreign engine while a page renders. Fill the translations first, on staging or through the editor, then switch automatic translation off on the mainland copy.
Should a Simplified-only site use zh, zh-CN or zh-Hans?
Google accepts all three. Use zh-CN or zh-Hans if you might add Traditional
Chinese later, so the tag on indexed pages does not change when the second
variant arrives. Whatever you choose, make the hreflang and the <html lang>
value agree with the content, and keep them the same on every page.
Need help with this?
ChinaWebFoundry handles WordPress projects in China end to end. If any of this feels like more than you want to tackle alone, get in touch.
Talk to Us