What this guide helps you achieve

This is the complete operating guide for NextlerAI Translator. Follow it in order to install the plugin, connect the correct multilingual system, qualify an AI model, create a small controlled test, translate larger queues safely, review the result and publish without damaging the source content or the layout.

Translator does not replace Polylang, WPML or TranslatePress. Those plugins continue to own language URLs, language relationships, hreflang and language switching. Translator discovers the content, separates readable text from technical structure, translates and reviews the readable text, validates the returned structure and saves it through the adapter for the active multilingual plugin.

1. Prepare WordPress before installing

1. Create a database and file backup. For a first production deployment, use a staging copy.
2. Update WordPress, WooCommerce, the active multilingual plugin and the page builder to stable versions.
3. Choose one multilingual system. Do not run a Polylang, WPML and TranslatePress migration during the same test.
4. Configure the source language, all target languages and the site’s language URL format in that multilingual plugin.
5. Choose three representative test items: one normal page, one post and, if WooCommerce is active, one variable product.

A representative page should contain headings, paragraphs, buttons, links, images, columns, responsive settings and at least one dynamic component such as tabs, an accordion or a form. This reveals integration problems before a large queue is started.

2. Install and activate the licence

1. Open Plugins → Add New Plugin → Upload Plugin.
2. Select the official NextlerAI Translator ZIP, install it and choose Activate.
3. Open Translator → License.
4. Enter the licence assigned to this website and activate it.
5. Confirm that the status is Active and the masked key belongs to the correct product.

Refresh licence rechecks the existing activation. It does not translate anything. Deactivate licence releases the website activation and blocks new AI jobs; translations already stored in WordPress remain in place. Never place a licence key or an AI provider key inside a distributable plugin ZIP.

3. Configure and qualify the AI provider

1. Open Translator → Settings.
2. Choose the supported provider, enter the API key and select a stable multilingual text model.
3. Use Professional — recommended for production work.
4. Keep creativity/variation low; 0.1 is a suitable baseline for faithful localization.
5. Enable the independent AI quality-review pass.
6. Keep ambiguous or risky content in the review workflow.
7. Save the settings, then run Test connection & translation quality.

The qualification test checks instruction following, target-language output, glossary and brand-term protection, placeholders, HTML and JSON structure. Professional unattended publishing is allowed only when the selected model reaches the required score. If the score is below 90/100, do not compensate by increasing creativity. Select a stronger model, correct the provider account or reduce conflicting instructions.

4. Confirm automatic system detection

Open Translator → Dashboard. Confirm the licence, multilingual plugin, source language, target languages, WooCommerce state, editor/builder integrations and custom-field integrations. Detection is read-only: rebuilding the inventory does not alter content.

If a system says Not detected, verify that the related plugin is active and that the content actually uses it. Do not enable an integration merely because it appears in the list. A site using Gutenberg does not need Elementor metadata translated, and a site using Polylang must not be written through the WPML adapter.

5. Choose the translation workflow

In Translator → Settings, set new translated content to Draft for the first production run. Enable only the public content types you intend to localize. Posts, pages, products and selected public custom post types can be included independently.

• Translate URL slugs: creates a target-language slug while preserving the source URL.
• Translate SEO metadata: includes supported Rank Math, Yoast, SEOPress and AIOSEO fields.
• Translate ALT text: localizes meaningful ALT text when the media relationship supports a language-specific value.
• Automatically queue changed source content: useful after the initial rollout; leave it off during first testing.
• Maximum items per small background run: start with one item on unknown hosting and increase only after stable jobs.

6. Select content without creating translation loops

1. Open Translator → Translate.
2. Filter by content type, original language and missing or outdated translation.
3. Select the required target languages.
4. Choose Only selected rows for the first test.
5. Select one representative row and start the translation.

The original language is detected from the multilingual system and skipped automatically. Existing target-language copies are not reused as new source items. Selections can be retained across result pages; always review the selected-item summary before starting a large queue.

7. Understand what is translated and what is protected

Translator can localize titles, excerpts, editor text, visible taxonomies, product names and descriptions, supported custom tabs, SEO text, slugs, media ALT text, public custom post content, compatible custom fields and human-readable strings inside structured builder data.

It preserves or synchronizes HTML structure, block comments, shortcodes, placeholders, URLs, IDs, CSS, JavaScript, serialized controls, hashes, product variation identities, prices, sale prices, stock, SKU, dimensions and download configuration. A valid translation changes language—not the design system or the commerce model.

8. Monitor background work correctly

The browser screen is not the worker. After a job is queued, WordPress background processing continues in server-safe batches. You may close the page. The status panel reports tasks, text sections, retries and final failures. A temporary provider limit or connection error normally schedules a controlled retry and keeps completed checkpoints.

Do not start duplicate jobs because the percentage appears unchanged for a short time. Open Translator → Jobs & Logs and check the current item, last update and retry message. Cancellation prevents future batches, but cannot undo a provider response or database transaction that finished immediately before the cancellation request.

9. Review every result before publishing

1. Open the result card in Jobs & Logs.
2. Use Preview translation while the target remains a draft.
3. Compare the source and target at desktop, tablet and mobile widths.
4. Open accordions, tabs, sliders, menus, forms and popups.
5. For products, test variations, price display, Add to cart, cart and checkout.
6. Review title, description, canonical, hreflang, slug, Open Graph and image ALT text.
7. Check menus, the translated homepage assignment and language-switcher links in the multilingual plugin.
8. Edit flagged wording in the target-language item, then publish deliberately.

10. Interpret completion and failure

Completed means the target result passed the structural and language checks and was saved through the active adapter. It does not replace visual or legal review. Retry scheduled means the job is still active. Failed means the job stopped without marking the translation complete; the result card explains the reason and the source content is not overwritten.

If validation reports a small number of missing rendered strings, open the technical details and identify the exact missing strings. Dynamic strings may only appear after a variation, tab, popup or form state is opened. Correct the specific content or use the multilingual plugin’s string workflow; do not repeatedly overwrite an otherwise correct page.

11. Scale from one page to a complete site

1. Approve the page, post and product tests.
2. Translate a small batch from each enabled content type.
3. Confirm hosting cron reliability and provider limits.
4. Increase the queue gradually.
5. Use missing/outdated filters and translation memory to avoid unnecessary rework.
6. Keep target status as Draft until the review process is proven.

After source content changes, Translator identifies outdated segments. Incremental retranslation processes changed text while reusing reviewed unchanged segments. Always perform a complete visual check when a builder structure, product configuration or template assignment changed.

Production sign-off checklist

• The correct multilingual adapter is active and only the intended target language was written.
• Source content, IDs and technical data remain unchanged.
• The target uses the same template, builder structure and responsive layout.
• Menus, homepage, forms, dynamic widgets and WooCommerce flows work in the target language.
• SEO, canonical, hreflang, slugs and media text are correct.
• Ambiguous claims and terminology have received human review.
• Caches are purged only after the correct saved version has been verified.