Products
Solutions
Pricing
Compare
Resources
Developers
Support
Translation Operations WordPress multilingual translation

Translation Queue for WordPress.

Translate large WordPress sites through an asynchronous queue instead of blocking editors or overloading provider APIs. This page is written for real WordPress usage: admin screens, REST operations, translation tables, SEO outputs, frontend rendering and global growth workflows.

v1.5.7Current plugin version
WP 6.0+WordPress requirement
PHP 7.4+Runtime requirement
Translation Queuepending → running → review → approved → published
Translation Queue visualized
Page-specific SVG based on real Verto workflow.
Version OK
Product context

Built for practical multilingual WordPress operations.

Async jobs, live progress and controlled translation operations. The goal is not only to translate strings, but to keep localized URLs, SEO signals, provider cost, review quality and frontend performance aligned.

/products/verto/translation-queue/
01
Why a queue is necessary

Whole-site translation can involve thousands of strings across posts, meta, menus, terms, image alt text and LemonX Code blocks. Verto uses a job queue so translation work is controlled, retryable and observable.

02
Real-time admin progress

The admin panel can open a Server-Sent Events stream to /queue/stream for live queue updates, with a fallback to polling when streaming is disabled or unsupported.

03
Operator controls

Operators can run the queue now, scan for missing content, pause, resume or clear jobs from the Verto admin panel.

Key features

What this Verto page covers.

Every module is represented with content and a matching SVG card so the page reads like a product document rather than a plain marketing landing page.

Pending, running, done and error job states

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Queue pause and resume

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Run-now and scan-now REST actions

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Real-time SSE updates with fallback polling

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Batch size and time-budget controls

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Stale running job cleanup

Translation Queue helps teams handle this requirement in a WordPress-native multilingual workflow.

Recommended workflow

How teams should use this feature.

The workflow below matches how operators usually work inside WordPress: configure, scan, queue, review, publish, cache and report.

WordPress admin
01
Scan content for missing translationsDesigned for repeatable operations inside the LemonX Verto admin workflow.
02
Create jobs per object and target languageDesigned for repeatable operations inside the LemonX Verto admin workflow.
03
Run queue within time budgetDesigned for repeatable operations inside the LemonX Verto admin workflow.
04
Fallback provider keys when necessaryDesigned for repeatable operations inside the LemonX Verto admin workflow.
05
Store translated rowsDesigned for repeatable operations inside the LemonX Verto admin workflow.
06
Update admin progress liveDesigned for repeatable operations inside the LemonX Verto admin workflow.
Translation Queue data modelpending → running → review → approved → published
Plugin data model

Connected to real plugin structures.

This page is mapped to Verto’s real settings, REST endpoints, database tables, services or frontend rendering behavior. That makes the content suitable for Google SEO, AEO inclusion and developer trust.

SourceMeaning
REST endpoints/queue, /queue/stream, /queue/run-now, /queue/scan-now, /queue/clear, /queue/pause, /queue/resume.
Optionsqueue_batch_size, queue_tick_time_budget_seconds, queue_stale_running_seconds, realtime_sse.
Jobs tableTracks object, field, language, attempts, priority, status and errors.
RunnerLxt_Queue_Runner drains jobs and writes translations with cost/runtime accounting.
SEO & AEO readiness

Structured for search engines and answer engines.

The page includes a descriptive title, meta description, canonical URL, Open Graph metadata, FAQ structured data, SoftwareApplication structured data and BreadcrumbList structured data.

  • Clear definitions near the top of the page.
  • Question-style FAQ content for AI answer extraction.
  • Internal links to adjacent product features.
  • Plugin-version and WordPress-context signals for trust.
  • Original SVG scenes instead of generic small decorative icons.

Search-friendly content, answer-ready structure and product evidence in one page.

FAQ

Common questions about Translation Queue.

Does the queue run automatically?
Yes, cron and operator actions can drain jobs depending on settings and site activity.
Can I pause translations?
Yes. queue_paused stops the runner while still allowing new saves to enqueue.
What is SSE progress?
It is a real-time admin stream that sends queue state updates without waiting for periodic polling.
Can failed jobs retry?
Yes. The queue tracks attempts, max attempts and cooldown behavior.

Build multilingual WordPress growth with LemonX Verto.

Use Translation Queue as part of a complete multilingual workflow: languages, provider chain, translation queue, review, SEO, cache, search and LemonX ecosystem integration.

WhatsApp+44 7724 592551