Install on WordPress
On this page
The plugin copies your published translation files to your own WordPress site. Visitors' browsers load them from your domain first. If our servers or the CDNs cannot be reached, your copy keeps working.
Before you start#
- WordPress 5.9 or newer and PHP 7.4 or newer.
- Self-hosted WordPress, or a WordPress.com paid plan. WordPress.com says plugins can be installed on its Personal, Premium, Business and Commerce plans, and that free sites must upgrade first (checked 2026-10-29). Accounts from before a plan change may differ: verify.
- A theme that calls
wp_head(). Plugins print their head output through it, and a theme without it will not load the script tag. - Your site key, your public signing key and the address where your translation files are published. All three are public values. The dashboard shows them on the site's Install page.
In the dashboard's install page, the WordPress guide is marked "coming soon" and shows a short notice instead of steps, because the plugin is not distributed yet.
Steps#
- Upload the plugin folder to
/wp-content/plugins/, or install it from the Plugins screen once it is distributed. Activate it. - Open Settings > ResilientLang.
- Enter the site key, the public key and the files address. Tick the permission box that allows downloads from that address.
- Press Sync now. The plugin downloads the manifest and checks its signature against your public key. Then it downloads each language file and checks its checksum.
- Place the language switcher: a widget, the block, the shortcode
[resilientlang_switcher], or a menu item. It is plain links and needs no JavaScript. - Choose how often to sync: hourly, twice a day or daily. A failed download never removes the copy you already have.
Language addresses and hreflang#
The plugin includes a part for language addresses (/fr/), hreflang tags, canonical tags and a sitemap of translated pages. It has its own tests. It has not yet been run inside a real WordPress together with the core part: OPEN. See hreflang.
What is sent where#
Syncing is an ordinary secure request for public files. The file host sees your server's address and the plugin's name. It does not receive your content, your visitors' data or any secret key.
Licence key#
The WordPress.org directory rules#
WordPress.org's plugin guidelines allow a service the plugin exists for, if the readme documents it, links its terms and privacy policy, and the user opts in. They do not allow outside scripts unrelated to a service, or third-party CDNs other than for fonts (summary of the guidelines; wording to be checked by a person: verify). Whether a loader served from our delivery address fits is OPEN. Bundling the loader in the plugin is the safest route.
The licensed build of the plugin asks for a licence key on the same settings area. See Licence keys. Whether the free build is accepted by the WordPress.org directory is OPEN.
Uninstall#
Deleting the plugin keeps the downloaded files unless you tick "delete on uninstall". The script that applies them is no longer added to your pages. Your pages show the original language until you add the script tag.
Something wrong? See Troubleshooting.