Install and activate POM Translate

Install POM Translate from its production ZIP, then confirm that activation prepared the current WordPress site for translation and localized routing. Language configuration comes after this installation check.

Protect the existing site

Before installation:

1. create a current database-and-files backup or a recoverable staging snapshot;
2. record the active WordPress site language and permalink structure;
3. inventory any plugin, theme code, redirects, or server rules that currently own multilingual routes;
4. preserve an export from an existing translation system before changing it;
5. choose whether the plugin will be active per site or network-active on multisite.

Do not activate two multilingual routers on the same public site merely to compare them. Their prefix detection, canonical filters, language selectors, and redirects can conflict before any content is migrated.

Install the release package

On a single-site installation:

1. open Plugins → Add Plugin;
2. select Upload Plugin;
3. upload the official POM Translate ZIP;
4. select Install Now;
5. select Activate Plugin.

On multisite:

1. open Network Admin → Plugins → Add Plugin;
2. upload and install the release ZIP;
3. return to Network Admin → Plugins;
4. choose Network Activate when POM Translate should be available throughout the network, or activate it only on the intended sites.

The normal plugin directory is:

wp-content/plugins/pom-translate/

If activation reports a missing Composer class or POM Framework dependency, the package is incomplete. Replace it with the official release ZIP instead of copying individual missing files.

What activation changes

Activation performs three setup actions:

• creates or updates the translation storage for the current site;
• refreshes WordPress rewrite rules so language-prefixed routes can be registered;
• adds POM Translate management capabilities to administrators and editors.

It does not add a target language, translate existing content, enable POM AI, choose a language selector, or validate the product license.

Deactivation deliberately leaves stored translations in place. Removing the plugin files is therefore not the same as removing its saved multilingual data.

Confirm the administration screens

Sign in as an administrator and verify:

1. Settings → POM Translate opens.
2. The settings navigation includes Languages setup, Content types, Advanced, Tools, and License.
3. The main administration menu includes Translations.
4. Translations opens without a storage or permission error.
5. Settings → Permalinks still shows the intended structure.

An editor should be able to open Translations but should not receive full settings-management access.

Establish the source language

POM Translate’s Main language follows the WordPress language selected under Settings → General → Site Language.

If that value is wrong:

1. change Site Language before translating content;
2. save Settings → General;
3. reopen Settings → POM Translate → Languages setup → Base setup;
4. confirm Main language displays the intended locale.

The main-language control in POM Translate is read-only. Its optional custom label changes selector text, not the underlying WordPress locale.

Leave public behavior controlled

For the first test:

• add only one additional language;
• leave Browser language detection disabled;
• do not enable the floating selector until its markup and location are reviewed;
• use one short representative post;
• test the origin before a page cache or CDN.

Next, activate the POM Translate license, then add the first additional language.