Purpose of this setup

This procedure creates a clean, supportable connection between one WordPress website, one NextlerAI Translator licence and a customer-owned AI provider account. No translation should be started until every check below passes.

Pre-installation checks

• Confirm WordPress 6.0 or newer and a supported PHP version.
• Take a database and file backup.
• Confirm administrator access and outbound HTTPS access from the server.
• Choose and configure Polylang, WPML or TranslatePress before creating jobs.
• Download the official ZIP from the customer account; do not rename internal plugin files.

Install the plugin

1. Go to Plugins → Add New Plugin → Upload Plugin.
2. Upload the ZIP and select Install Now.
3. If replacing an earlier Translator version, use WordPress’s replace-current-version flow. Do not delete multilingual content.
4. Activate the plugin and open Translator → Dashboard.
5. Confirm there is no PHP critical error and that the Translator menu is visible.

Activate and manage the licence

1. Open Translator → License.
2. Enter the purchase email/key information supplied for this product.
3. Activate and confirm the status badge is Active.
4. Verify the masked local key and last-verified time.

Refresh licence checks the same activation and updates local status or grace information. Deactivate licence releases the site activation; existing target-language content remains, but new translation jobs are blocked. Requesting a licence sends purchase/customer information for verification and does not expose the AI API key.

Connect the AI provider

1. Open Translator → Settings.
2. Select the provider.
3. Paste the provider API key into the dedicated field.
4. Select a stable text model with strong multilingual instruction following, at least 32k context and enough output capacity for structured results.
5. Save Translator settings before running a test.

The provider key is encrypted using this website’s secret, masked in the interface and never added to the downloadable plugin ZIP. To replace it, save the new key. To remove it, use the explicit removal checkbox; leaving a masked field unchanged preserves the saved key.

Configure the professional profile

• Select Professional — recommended.
• Use creativity/variation 0.1 as the faithful baseline.
• Enable the independent AI quality-review pass.
• Keep ambiguous or risky content in the review workflow.
• Add glossary and brand rules before testing if terminology must remain fixed.

Run the qualification test

1. Select Test connection & translation quality.
2. Wait for the provider response; do not navigate away during the small test.
3. Confirm the score is at least 90/100 for Professional mode.
4. Review any failed category: target language, placeholders, brand terms, HTML, JSON or instruction following.

A successful network request alone is not enough. The test deliberately checks whether the model can return usable structured translation. If it fails, verify provider billing, model access, rate limits, key permissions, outbound HTTPS and model stability. A 401/403 error points to credentials or permissions; 429 normally means rate or account limits; timeouts point to the provider connection or hosting.

First safe content test

1. Set new translated content to Draft.
2. Set the small background run to one item.
3. Choose one short page with headings, links and a button.
4. Translate to one target language.
5. Open Jobs & Logs, preview the result and compare the source.

Setup acceptance criteria

• Licence remains active after a refresh.
• Dashboard detects the intended multilingual system.
• The provider test scores 90/100 or higher.
• The original language and target language are correct.
• The draft uses the source template and layout.
• No complete key appears in logs, screenshots or support messages.