Other translation plugins on the same page
On this page
Only one tool should translate a given page. When two do, they change the same text, add two switchers, and often add two sets of language links. The result can be mixed languages, flicker, and search engines that cannot tell which version to show.
Two kinds of conflict#
- A tool that changes the page in the browser or through a proxy, like ours. Two of these fight over the same text. The install check reports this as a Fix.
- A WordPress plugin that builds language URLs on the server. It can work next to our script only if you choose which tool owns the switcher, the language URLs and the hreflang links. The check reports this as Review.
How the check finds them#
It looks for markup these tools are known to leave on a page: script addresses, class names and meta tags. It never reads your visible text, so an article that only mentions a plugin is not flagged. It can miss a tool, or flag one that is switched off but left files behind. Treat the result as a pointer and verify on your page.
What to do#
- Decide which tool translates which pages. Do not run both on the same page.
- Before you switch the old one off, export its translations if it lets you. You can import many formats into ResilientLang. See Import translations.
- Switch off the old tool's switcher and its hreflang output, or the page ends up with two of each.
- Clear your page cache and your CDN cache.
- Run the check again.
If you keep a WordPress plugin for language URLs#
Keep its URLs, and let ResilientLang translate the text on them. Make sure only one tool writes the hreflang and canonical links. See hreflang and Install on WordPress.