QueueLingo for WPML is a tool for...WPML usersManaged translation plugin: Automatically monitors the WPML translation queueXLIFF MissionAfter the translation is complete, it will automatically push the data back to WPML, freeing you from the repetitive process of "exporting/translating/importing/proofreading/returning".

What can you do with it?

1) Managed WPML translation queue (core capability)

• Automatic monitoring of WPML Translation Queue

• Automatic fetch/receive XLIFF task

• The translation will be automatically pushed back to WPML after completion (or you can download the translated XLIFF file).

2) Multi-engine translation: Machine translation + LLM neural translation

• Free users: Machine translation only (MT)

• Subscribers: LLM translation availableAnd supportComes with its own API Key (does not use the platform's credit limit).

3) Quality Enhancement: Prompt Template + Custom Website Material Prompt

When using an LLM translation website, you can choose the Prompt template:

• b2b / b2c / tech_doc / creative
  It can also be configuredCustom website prompt(Brand tone, target audience, product terminology, prohibited expressions, etc.) to make the translation more relevant to your business.

Terminology Glossary Function:Coming soon(Terminology consistency can be further stabilized after going live).

4) Cost advantage: Only translate the "nodes that need translation", saving tokens.

QueueLingo parses translation nodes in XLIFF; for HTML/rich text content, it automatically extracts translatable text for translation and replacement.
This means:While ensuring quality, actual token consumption is more economical.(Only send the necessary text to the LLM).

5) Traceable: Translation tasks + spending details

Backend provides:

• Translation task list(Status, progress, reasons for failure, etc.)

• Task Consumption Details(View consumption and charges by task)

Billing and Deduction Principles

• Machine translation (MT)Available to free users (specific restrictions are subject to your backend display).

• LLM Translation:according toActual input/output tokens + model unit priceBilling (usually priced in "$/1M tokens").

• Task failureFailure may be due to model limitations, reduced intelligence, timeout, or complex content.Based on the actual consumption of successfully processed data.(Final charges will be settled based on the actual usage recorded by the system).

• Comes with API KeyOnce enabled, it will not consume your platform credit limit; the cost will be charged to your own third-party account (or your own channel's bill).

Quick Start (Runs in 10 minutes)

Step 0: Preparing the Conditions

• WordPress has WPML installed and enabled (and can create translation tasks normally).

• Background downloadQueueLingo for WPML Install plugins from the WordPress plugin marketplace or by searching for them.

Step 1: Install and enable the plugin

1. Install and enable uploads in the WordPress admin panel.QueueLingo for WPMLPlugin

2. Confirm that WPML is enabled and that the site has set the default and target languages.

Step 2: Create/bind the site in the backend

In the top menu of the QueueLingo backend, you will see:
Homepage / Activation Code Management / Site Management / Translation Tasks / Subscription Packages / User Guide

1. Open"Site Management"Automatically added to the list after binding with activation code.

2. In WordPresss siteIn the plugin interface, enter the activation code to complete the binding.

3. After successful binding, the system will have the capability of "listening queue + managed tasks".

Step 3: Choose a translation method (free MT or LLM subscription)

1. If you just want to get the process running: use **machine translation (MT)**.

2. To use LLM:

   • Make sure you have a subscription to a plan that supports LLM (or your plan allows it).

   • Select the LLM model in the relevant settings.

   • Select the Prompt template (b2b/b2c/tech_doc/creative）

   • Optional: Fill inCustom website prompt(Recommended to improve consistency)

You can also fill inComes with API KeyAt this time, the platform's credit limit will not be used.

Step 4: Initiate your first translation task in WPML

1. Select an article/page in WPML to create a translation task.

2. Send the task to the WPML Translation Queue.

3. QueueLingo will automatically start processing tasks once it detects them in the queue.

Step 5: Check the status and results in "Translation Task".

Access the backendTranslation Task:

• You will see the task status (Waiting/In Progress/Completed/Failed)

• Once completed, the translation will be automatically pushed back to WPML (or you can download the translated XLIFF file).

If it fails:

• Check the reason for failure and retry suggestions.

• Recorded by the systemActual consumptionFor the final deduction basis

Step 6: Check the consumption details in "Task Consumption Details"

View the expense details page (usually found in the translation task section):

• Token consumption per task / Engine / Model

• Deduction records (platform credit limit or records with built-in key)