Search the help center

Searching needs JavaScript. Without it, every article is listed here by topic.

Getting started

• What ResilientLang is

  A website translator whose translated pages keep working when our servers are down. What it does, in plain words.

• Create your account

  Sign up with your email, confirm it, choose a password, and set up two-factor sign-in if you are an owner or admin.

• Add your first site

  Create a site in the dashboard, pick the source and target languages, and find your public site key.

• Publish your first translation

  The path from a new site to translated pages your visitors can see, and which step is done where.

• Words you will see

  Short definitions of the terms used in the dashboard and in these articles, such as site key, bundle, loader and allowance.

• Set up two-factor sign-in

  Turn on two-factor sign-in with an authenticator app, save your recovery codes, and replace them later. Required for owners and admins.

Install on your site

• Choose how to install

  WordPress, Shopify, a script tag, a framework kit or the API. Which one fits your site, and what each can do for search engines.

• Install on WordPress

  Install the plugin, enter your public keys, sync the translation files to your own site and place the language switcher.

• Install on Shopify

  Two ways translations reach a Shopify store, what each one covers, and what Shopify does not let any app translate.

• Install with the script tag

  One script tag for any website. Where to paste it, what the attributes mean, and how to test that it fails safely.

• Install on Next.js

  Translate a statically exported Next.js site at build time, with language addresses, hreflang and the loader.

• Install on Nuxt

  Add the Nuxt module and run nuxt generate to write translated pages with language addresses and hreflang.

• Install on Astro

  Add the Astro integration so your static build includes translated pages with hreflang and the loader tag.

• Install on a static site

  Translate a folder of built HTML files from the command line, with language folders, hreflang and an optional sitemap.

• Install on Wix

  Paste the script tag into Wix custom code. Wix names no plan for custom code, has blocked some older snippets, and has its own multilingual feature.

• Install on Squarespace

  Add the script tag in Code Injection. Checkout pages cannot run custom code, some plans do not offer Code Injection, and Squarespace has no built-in multilingual feature that we could confirm.

• Install on Webflow

  Add the script tag in the site-wide head code. Webflow's own help pages could not be opened by our checker, so these steps are still unconfirmed.

• Install on a single-page app

  Add the script tag once in your HTML shell, load it after hydration, and know what happens when you change routes.

• Other platforms and the script tag

  What each platform's own documentation says about adding the script tag, which plans and pages are excluded, and what has not been checked.

• Deploy translated pages on Netlify or Vercel

  Add a build step that writes translated copies of your static pages, and stops the deploy if anything fails a check.

• Translated pages at the edge (Cloudflare)

  Serve real translated pages at language addresses such as /fr/ from your own hostname for sites that cannot be built ahead of time. Not deployed.

Languages

• Choose your languages

  How to pick source and target languages, what each plan allows, and how language codes with regions are handled.

• The language switcher

  Let visitors choose a language. Where the switcher comes from on each platform, how it behaves, and how to style it.

• Right-to-left languages

  How Arabic, Hebrew, Persian and Urdu are handled, and what you may need to check in your own theme.

How translation works

• How translation works

  From the text on your page to a translated page in the visitor's browser, step by step, in plain words.

• Machine and reviewed translations

  The four translation states, what each one means, which ones a machine run can change, and why you should check important text.

• What is and is not translated

  Which text on a page is translated, which is left alone on purpose, and which text the product cannot reach.

• Tags and placeholders

  What the numbered tags and the special tokens in a translation mean, and the one rule for editing them safely.

Glossary and do-not-translate

• Glossary and do-not-translate list

  Keep brand names exactly as written and set your preferred translation for key terms, per language.

• Mark content that must not be translated

  Use translate="no" or the notranslate class to keep a part of a page in its original language.

Editing and publishing

• Edit translations in the dashboard

  Find a string, correct its translation, and see its state. Filters, search, keyboard shortcuts and what is saved.

• Edit on your live page (visual editor)

  Click a string on your own page and edit its translation in place. Off by default, and not yet complete.

• Bulk actions and re-translation

  Mark many strings as reviewed, send them back to untranslated, or re-translate in the background, up to 500 at a time.

• Publish changes

  What publishing does, where your files go, how long visitors take to see a change, and what to do when a publish fails.

• Quality flags

  What each automatic check on a translation means, which ones are errors, and how to clear them.

• Preview before you publish

  Open your own page with your draft translations applied, check the result, and know that nothing is published from the preview.

• Translate without a translation provider

  What works when no automatic translation provider is connected yet: typing translations, importing files, the demo text and how to connect a provider later.

Team and review

• Team roles

  What owners, admins, editors and viewers can do, how two-factor sign-in applies, and how support staff access works.

• Reviewers and translators

  How suggestions, approvals, comments and the review queue work, and who is allowed to publish.

• Invite teammates

  Invite people from the Team page, how long an invitation lasts, who can accept it, and what is still missing.

• Give a client access to their sites

  Invite a client as a viewer or reviewer for chosen sites only, what they can and cannot do, and how to take access away.

Search engines and SEO

• SEO for translated pages

  What search engines see on each install path, and what you must have for translated pages to be found.

• hreflang for translated pages

  What hreflang tags are, the rules they follow, what the plugin and kits write for you, and how to add them by hand.

• SEO and the script tag

  Why translating in the browser does not give search engines translated pages, and when the script tag is still the right tool.

• Thin pages and noindex

  Why pages with too little translated text are hidden from search engines, and how to change the threshold.

• Translated addresses at the edge

  How edge delivery handles hreflang, the sitemap hint, robots rules and noindex pages, so translated copies are not indexed by mistake.

Plans and billing

• Plans and the AI-word allowance

  The planned plans, what each includes, how AI words are counted, and what is never charged. Prices are not live yet.

• Pricing questions and how billing works

  Answers to the common pricing questions: how signing up and paying work, monthly or yearly, the free plan, running out of words, and what every plan includes.

• When your allowance is used up

  What stops, what keeps working, which emails you get, and your options when your AI words run out.

• Word packs and your own provider keys

  Two ways to translate more than your plan includes: a one-time pack of extra words, or your own key from a translation provider.

• Cancel, lapse and grace

  What happens to your site when you cancel, when a payment fails, or when a plan ends. Your published translations keep serving.

• Payment and invoices

  How payments are planned to work, who can see invoices, and what is not set up yet.

• What the limit messages mean

  The 402 messages and codes you may see when a plan limit, the AI-word allowance or a lapsed plan stops an action, and what to do about each.

• The billing page

  What the owner sees on the Billing page: plan, allowance, trial, word packs, plan chooser, Manage billing and invoices.

• The free trial

  How the 14-day trial works, which limits it has, what happens when it ends, and when a paid plan takes over.

• Read your usage

  What the Usage page shows: words used against your allowance, the period, strings found, and translation coverage per language.

Keys, CLI and automation

• Licence keys

  What a licence key is, how it ties a WordPress site to your plan, how to replace it, and what happens offline.

• API keys

  Site keys and secret keys, what each is for, scopes, rotation, and how to keep a secret key out of the wrong place.

• The command-line tool

  Use the rl command to push text, translate, publish, pull and export from a terminal or a build job.

• Webhooks and the audit log

  Get a signed message on your server when a site is published, a job fails or your allowance is reached, and review who did what.

• Webhook events reference

  Every event you can receive, when it fires, and what its data holds. Payloads never contain text or secrets.

• Run translations from CI

  Push new text, translate and publish from GitHub Actions, GitLab CI or Bitbucket Pipelines, with a safe dry run on pull requests.

• Catch untranslatable text before you commit

  A lint tool that warns about text the translator cannot reach, such as text built in code or words split by markup.

• Check your setup with rl doctor

  A read-only command that checks your key, address, site, plan and published files, and explains each failure in plain words.

If our servers are down

• What happens if our servers are down

  The promise in plain words. Your visitors keep getting translated pages while our dashboard and API are offline.

• The honest limits of the promise

  What the resilience promise does not cover: first-time visitors, new translations, unsupported browsers and the loader script itself.

• Keep your own copy

  Ways to hold a copy of your published translations on your own systems so you do not depend on us or on a CDN.

Privacy and security

• Privacy basics

  What data the product handles, who decides what, and what you must tell your own visitors. General information, not legal advice.

• What visitors' browsers store

  The language choice and cached files the loader keeps in a visitor's browser, and what it never does. For your privacy notice.

• What is sent to translation providers

  Which data leaves the product when text is machine translated, what never does, and what you can control.

• How your files are protected

  Signatures, checksums, keys, passwords and access rules, in plain words, and what has not been checked by outsiders yet.

Troubleshooting

• My page is not translating

  A step-by-step check when a page stays in the original language, from the dashboard to the browser's network tab.

• Test my install

  Run the install check on your live page. It finds why a page is not translating and tells you how to fix it, in plain words.

• The wrong language is shown

  How the loader chooses a language, why a visitor can land in an unexpected one, and how to reset it.

• Flash of untranslated text

  Why visitors can briefly see the original text before the translation appears on script-only sites, and what reduces it.

• Content security policy

  What to allow in a Content-Security-Policy so the loader and the translation files can load, and what to do when you cannot change it.

• Caching plugins and CDNs

  Settings in caching, minifying and optimising tools that can stop translations from loading, and what to exclude.

• Only some text is translated

  Why a page can be partly translated, and how to find and fix the missing parts.

• The language switcher is missing or broken

  Why the switcher may not appear, show only one language, or look wrong, and what to check on each platform.

• Sign-in and two-factor problems

  What to do when you cannot sign in, a link has expired, or you lost your authenticator app or recovery codes.

• A publish failed

  How to read a failed or partly finished publish, what the product retries by itself, and what to check.

• Your account is suspended

  What a suspension means, what keeps working for your visitors, and what to do next.

• My CI run failed

  What the errors 401, 403, 402 and 503 mean in an automated run, and what to change. A 402 is a plan limit, not a permission problem.

• Other translation plugins on the same page

  Why two translation tools on one page clash, which ones the install check can recognise, and how to switch one off safely.

Export and ownership

• Export your translations

  Download everything you have translated in standard formats, any time, including after a plan lapses.

• Import translations

  Bring in translations from files made by people, agencies or other tools, with a dry run and clear error reports.

• Ownership and leaving

  What is yours, what happens to your data and published files if you stop using the product, and which periods are still undecided.