Weglot

Weglot is one of the plugins NIBWP turns into a set of typed, agent-callable tools. Once Weglot is active and connected to your account, an agent can configure and audit the whole translation setup over the same secure MCP endpoint as everything else.

Weglot translates in its own cloud rather than in WordPress, so there are no translated strings sitting in your database to edit. The work — and the risk — is configuration. That is what these tools cover, and it is where translation projects actually go wrong.

Translation fails quietly

Every common Weglot problem is silent. Nothing errors; the site simply underperforms:

• Missing hreflang — Search engines cannot tell your language versions apart, so translated pages compete with each other instead of ranking. The audit catches it.
• Untranslated slugs — A French page on an English URL ranks worse than one on a French URL.
• Nothing excluded — Code samples, brand names, SKUs and addresses get translated along with the prose — wrong output, and billed for.
• Private mode left on — Fine while building, invisible to the public if anyone forgets.
• Languages added blind — Weglot bills by translated words across every language, so each one multiplies usage against the plan.
• Two places, one truth — Weglot keeps settings locally and in your workspace. Changes are written to both, and drift can be compared.

The tools

Twelve abilities. The last two are the ones worth reaching for first:

The order that saves money

This ordering is not arbitrary. A word translated once is billed whatever you do afterwards, so excluding code and brand names after the first pass fixes the output without refunding the words:

1. Check the plan — weglot-plan before anything that increases usage. Going over stops translation rather than charging quietly.
2. Set exclusions first — weglot-exclusions. Code and pre blocks, syntax highlighting, brand names, SKUs, addresses.
3. Add the languages — weglot-languages. Adding one asks for confirmation, because it costs.
4. Switch hreflang on — The single most important SEO setting for a translated site.
5. Translate the slugs — Then review them in the Weglot dashboard.
6. Place the switcher — A translated site nobody can switch is a translated site nobody reads.
7. Re-audit — weglot-audit before telling anyone the site is translated.

Worth knowing

Weglot does the translating; NIBWP configures it. There are no translated strings in WordPress to edit here, and individual translations are edited in the Weglot dashboard. Adding a language and syncing the workspace are both confirm-gated because they cost money or overwrite configuration.

FAQ