Set up and audit a Weglot translation with AI — languages, hreflang, translated slugs, the switcher, exclusions, page rules, plan usage, a readiness audit and a step-by-step plan.
Weglot translates in its cloud, so the work is configuration — and the mistakes make no noise. A missing hreflang tag costs rankings. An unexcluded code block becomes nonsense someone pastes and runs. A language added without checking multiplies the bill.
Blockers, warnings and notes, each with what to do about it — not a list of problems to interpret.
Exclusions before languages, because a word translated once is billed whatever you do afterwards.
Code, brand names, SKUs and addresses kept out of the translator — correct output and lower usage at once.
hreflang and translated slugs, the two settings that decide whether translated pages rank at all.
Plan and word usage are read before anything that increases them, and adding a language asks first.
Weglot keeps settings locally and in your workspace. Changes are written to both, and drift can be compared.
Ask to translate the site and the Weglot integration reads what is already configured, then returns only the steps that still apply — in the order that does not waste quota.
Exclusions, languages, hreflang, slugs and switcher — in the order that does not waste words.
Find the hreflang nobody switched on and the private mode nobody switched off.
Exclude syntax highlighting, SKUs and brand names across a technical site in one pass.
See usage before adding a language, not after the allowance runs out.
The NibWP Weglot integration exposes a Weglot setup to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Languages, SEO settings, the switcher, exclusions, page rules and plan usage become typed tool calls.
Weglot translates in its own cloud rather than in WordPress, so there are no translated strings sitting in the database to edit. The work — and the risk — is configuration. A missing hreflang tag means search engines cannot tell the language versions apart. An unexcluded code block gets translated into something that no longer runs. A language added without checking the plan multiplies the word count across every page on the site.
Findings are ranked as blockers, warnings and notes, and each carries its fix. A report that names a problem without its remedy leaves you exactly where you started.
Exclusions are planned before languages are added, because a word translated once is billed whatever happens afterwards. Excluding code and brand names first saves both the quota and the nonsense.
| Tool | Type | What it does |
|---|---|---|
| nibwp/weglot-info | read | Key, languages, engine, and whether it is actually translating. |
| nibwp/weglot-languages | write | Configured and available languages, and adding one. |
| nibwp/weglot-settings | write | Every option, including hreflang and translated slugs. |
| nibwp/weglot-exclusions | write | URLs and CSS selectors to leave untranslated. |
| nibwp/weglot-switcher | write | The language switcher and its styling. |
| nibwp/weglot-slugs | read | Translated URL slugs. |
| nibwp/weglot-pages | write | Which pages stay untranslated in which languages. |
| nibwp/weglot-media | write | Media, PDF and email translation. |
| nibwp/weglot-plan | read | Plan, word allowance and usage. |
| nibwp/weglot-audit | read | What is misconfigured, ranked, each with its fix. |
| nibwp/weglot-workflow | read | The ordered plan for this particular site. |
| nibwp/weglot-sync | write | Compare, pull or push the workspace configuration. |
Yes, with an API key. Once Weglot is active and connected, NibWP detects it and its abilities go live — no configuration needed.
Weglot does the translating, in its own cloud. There are no translated strings stored in WordPress to edit. What this controls is the configuration — which is where translation projects actually go wrong.
No. Adding a language asks for confirmation first, and the plan and word usage are read before anything that increases them is suggested.
Because a word translated once has already been billed. Excluding code and brand names after the first pass fixes the output but does not refund the words.
Yes. hreflang is handled by Weglot itself, and the audit tells you if it has been switched off — which is the most common reason a translated site fails to rank.
Activate the integration and it's live on your MCP endpoint instantly.