The governing idea
Three checks keep a translation useful
WPML records which source and target belong to a translation relationship. The localized item and its visitor-facing output determine whether that relationship works in practice.
01
Identity
The translation group identifies which source and target belong together, while language details identify how each item is registered.
02
Content
Localized URLs, taxonomies, text, and media make the mapped item useful to readers in its language.
03
Output
Target-language links and frontend assets must deliver the intended localized surface after the relationship is mapped.
Discovery
Find the exact language context before a change
Start with evidence that names the target, its language, and its existing relationship. That record prevents a repair from landing on a guessed item.
Evidence to establish
Active languages
See which languages WPML currently exposes before choosing a target language.
Language-scoped content
List pages and posts in the selected language so the target is an existing item, not a guess.
Language-scoped terms
List taxonomy terms in the selected language to keep term relationships in the same context.
Translation status
See which page translations exist and the status attached to each one.
Translation groups
Inspect the source and target members of a post or term translation group.
Element language details
Confirm the recorded language and translation identity for the item you may change.
Reusable candidates
Find an existing item that can be reused instead of creating a duplicate.
Decision point
Name the exact source or target and its language context from the evidence before a mutation.
Use the result to name the exact source or target and its language context before any mutation.
Mapping
Map the target to the relationship that owns it
Once the source and target are known, make the smallest relationship change that preserves WPML identity.
1
Create the missing shell
When the target is absent, create the appropriate page or post translation shell in the requested language.
2
Record language details
Set the target language and translation-group details against the confirmed source context.
3
Link an existing target
When a suitable target already exists, register it in the correct group instead of creating another copy.
4
Maintain localized context
Update the translated URL, categories, and primary category in the target language context.
5
Read back the relationship
Read the resulting group and target-language details to verify the mapping before treating it as complete.
Audits
Audit what a localized visitor will receive
Read translated content and its destinations together. A relationship can be present while the visitor-facing surface is still wrong.
Checks and repair boundaries
Untranslated fragments
Detect source-language fragments carried into translated content.
Targeted translated-link audit
Inspect translated links for one identified item, and enable a fix only when the audit names the intended change.
Batch translated-link audit
Run the same translated-link check across selected translated posts to expose repeated stale destinations.
Missing or stale coverage
Report translations that are missing or no longer match the expected coverage.
Translated content and URLs
Audit translated text and localized URLs for source-language carryover, stale links, or incorrect destinations.
Galleries and frontend assets
Audit translated gallery membership, media captions, and the gallery assets delivered to a localized visitor.
Audits stay read-only until an explicit repair input is enabled, and any repair must identify the affected item and language context.
Recovery
Recover a damaged WPML language switcher deliberately
Language-switcher recovery changes stored multilingual state and requires administrator permission. Record the current structure before authorizing a reset.
Build a recovery record
Current settings
Inspect the stored language-switcher settings.
Available slots
Inspect the registered language-switcher slots and their placement data.
Structural validation
Validate that the settings and slots have the expected structure.
Controlled reset
Reset the stored option only when the evidence justifies removing the damaged state.
WPML rebuild
Rebuild the language-switcher settings through WPML and validate the resulting structure.
Inspect and validate first. Reset only when the evidence justifies removing damaged state, then rebuild through WPML and validate the result.
Media maintenance
Keep the media behind a translation in sync
Media maintenance affects what a localized visitor sees. Separate inspection from repair, and make force and permission choices explicit.
Elementor language assets
Audit language-specific Elementor assets and identify the localized asset state needing attention.
Translated gallery audit
Inspect translated gallery media and expose mismatches without changing them by default.
Targeted gallery repair
Repair thumbnails and metadata only for the identified gallery. Run a dry run first when the proposed repair needs review, then enable repair explicitly.
Selected media text
Update selected media captions or other selected text fields in the intended language context.
Force and permission
Regenerate existing valid image sizes only when force is explicitly enabled. Media changes require upload permission, and changing a gallery page also requires permission to edit that page.
Optional integrations
Keep optional integrations outside WPML core
These operations apply only when the matching integration is present. WPML remains the multilingual state owner.
Targeted integrations
One exact Yoast Premium redirect
Remove the specific matching redirect when it blocks the intended localized route. This targeted action requires administrator permission.
One translated Contact Form 7 form
Update the selected translated form template and locale with the matching content-edit capability, leaving unrelated forms and WPML translation groups untouched.
They do not alter unrelated forms or WPML translation groups. Redirect removal requires administrator permission, while the form update follows the matching content-edit permission.
Honest boundary
WPML remains the multilingual authority
WPML owns the language, translation-group, translated URL, language-switcher, and multilingual content state used by every registered operation. SitePress gives an AI client focused WordPress operations for inspecting and maintaining the relationships, routes, assets, and integrity checks around that state.
Every operation requires an authenticated WordPress user. Translation reads and content operations require the relevant page, post, or item editing capability. Language-switcher recovery, translation linking, and removal of one exact Yoast Premium redirect require administrator permission. Media changes require upload permission, and changing a gallery page requires permission to edit that page.
Requirements
Install the native stack SitePress extends
Confirm these requirements before expecting the plugin to expose its WPML maintenance surface. Each dependency has a distinct runtime job.
6.9 or later
WordPress 6.9+Provides the native Abilities API and the WordPress content, taxonomy, media, and permission interfaces used by the plugin.
8.0 or later
PHP 8.0+Provides the minimum runtime required by the plugin.
Required
WordPress Abilities APIRegisters the SitePress operations as typed WordPress abilities.
Required
WordPress MCP AdapterTransports registered WordPress abilities to authenticated MCP clients.
Required
MCP Expose AbilitiesExposes the registered public abilities through the controlled Devenia MCP surface.
Installed and active
WPMLOwns the language, translation-group, translated URL, language-switcher, and multilingual content state used by every registered operation.
Next action
Give an AI client a focused WPML maintenance surface
Download MCP Abilities – SitePress when a WordPress AI client needs a focused surface for WPML translation relationships and localized integrity. The download gives you the plugin package that provides these operations.