Requirements and compatibility

Review the platform, routing, permissions, and optional integrations before installing POM Translate. A successful activation proves that WordPress loaded the plugin; it does not prove that localized URLs, every content type, or an external integration is ready.

Supported baseline

Use the official production ZIP. It includes POM Framework, the HTML parser, and the other Composer runtime files loaded during plugin startup. A repository source archive without installed production dependencies is not a supported release package.

Activation and upgrades need permission to create or update the current site’s translation storage. Normal settings saves also need the filesystem and WordPress environment required by POM Framework settings.

Administration permissions

POM Translate adds separate capabilities when the plugin is activated:

• administrators can manage translation settings, translations, and localized slugs;
• editors can manage translations and localized slugs;
• other roles receive no POM Translate management capability by default.

The Settings → POM Translate menu therefore belongs to administrators. The Translations menu is available to users with translation-management permission. A custom role needs an intentional capability assignment before it can use these screens.

URL and rewrite compatibility

Additional languages use a path prefix. WordPress and the web server must already resolve normal pretty permalinks correctly before POM Translate can resolve their localized equivalents.

Before launch:

• save Settings → Permalinks after the final route configuration when rewrite rules need refreshing;
• confirm nested pages and enabled custom post types resolve in the source language;
• test the prefixed target route without a CDN;
• review any redirect, security, cache, or SEO plugin that also changes request paths or canonical URLs.

Do not run two multilingual routing systems over the same public paths. Plan the migration and redirect ownership before activating POM Translate on an existing multilingual production site.

Optional integrations

POM Translate does not require these products for its core post and page workflow:

• POM AI is required only for assisted machine translation. It uses its own license and credits.
• WooCommerce is required only for product, cart, checkout, account, order-language, and transactional-email features.
• Rank Math or Yoast SEO can supply the site’s SEO output while POM Translate localizes supported canonical and sitemap values.
• POM Cache can coordinate translation-aware progressive JSON invalidation when both products and the relevant cache mode are configured.

The absence of an optional product should remove or bypass its integration, not prevent manual post translation.

Content compatibility

Posts and pages are enabled by default. Pages and navigation menu items are always included in the current translation parsing policy. Categories and tags are always enabled taxonomies. Other public post types and taxonomies appear under Settings → POM Translate → Content types and remain opt-in unless another supported integration changes the default.

For each custom type, verify:

• title, content, excerpt, and meta choices;
• the actual editor or builder storage used by the type;
• public single and archive routes;
• hierarchical parents where applicable;
• custom fields registered as translatable by the theme or plugin.

A visible custom field is not automatically safe to translate. Technical IDs, serialized configuration, prices, tokens, and relationship values should not be treated as prose.

Multisite planning

Translation data and settings are scoped to the current site. Network activation can make the plugin available across the network, but each site still needs its own language, content, route, and editorial review.

Private updates use the main/network POM Translate license. Optional POM AI requests from a subsite require that subsite’s explicitly saved POM AI license; they do not inherit the network service key.

Proceed with Install and activate POM Translate when the baseline, route ownership, activation scope, and rollback are clear.