Keep visitors on the right page when the language changes
A French hotel page should lead to the same hotel and the right booking destination. MCP Abilities – SitePress helps an AI assistant find missing WPML translations, reuse existing drafts and repair links that lead back to the source language.
Two language versions. One place to stay.
Imagine a small hotel with English and French pages. The French page already exists, but WPML has not linked it to the English original. Creating another translation would leave two competing French pages. Linking by a similar title could select the wrong property.
Ask the assistant to inspect the existing translation group and search for candidates. Compare the hotel, post IDs, language records and URLs. Then link the correct page, or create a draft shell if no suitable page exists. The shell still needs a reviewed translation.
The illustration shows two separate checks: the pages represent the same hotel, and each page has the right onward booking link. A translation link alone does not establish both.
Turn one page check into a repair queue
Once the relationship is clear, use the other abilities to find work worth doing. Start with a defined group of pages and review the proposed changes.
Find the versions still waiting
List pages without a linked target language and compare modification dates. Search existing drafts before creating new shells. A date difference is a reason to review the translation, not proof that its wording is wrong.
Keep the next click in French
A translated room description can still link to an English contact page. Inspect internal links, confirm the matching French destination, then apply the repair to one page or a selected batch. Check external booking links separately with the booking provider.
Check photos as well as paragraphs
Inspect Elementor template references, gallery images and missing thumbnail files. Look for known source-language words in captions, then update the selected media text. The correct photo can still have the wrong caption.
29 actions for an existing WPML site
The add-on covers language and term lists, translation groups, coverage, link repair, text comparison and language-switcher inspection. Optional actions maintain Elementor assets, translated Contact Form 7 templates, exact Yoast Premium redirects and Permalink Manager URLs. A native shortcode can also display a WPML language flag. These tools maintain the site’s existing content and relationships; writing and reviewing the translation remains a separate job.
Connect, inspect, then choose the change
Install on the WPML site
Use WordPress 6.9 or later with its Abilities API, PHP 8.0 or later, and an active, configured WPML installation. Choose a maintained PHP release supported by your site. Optional integration actions need the corresponding plugin.
Connect the assistant
Use an authenticated WordPress ability connection such as MCP Expose Abilities. The WordPress user needs access to the affected posts; translation linking and language-switcher recovery require administrative permission.
Start with one translation group
Ask for the source page’s linked languages and existing target candidates. Inspect the result before requesting a link, a draft shell or a repair. After a change, read back the group, open the target page and follow its main action.
Content comparisons help locate material to review; they do not certify translation quality. Inspect language-switcher settings before resetting them: a reset removes custom configuration and needs a check on the rendered site.
Find the next useful translation fix
Install MCP Abilities – SitePress and start with one source page. Ask the assistant to show its linked language versions and identify the first missing page, wrong link or media issue worth correcting.