A multilingual AI translation system needs observability. Verto includes activity, stats, coverage, runtime and provider health surfaces so operators can understand translation progress and provider behavior.
Activity & Runtime Stats for WordPress.
See what your translation system is doing: jobs, costs, tokens, provider health, queue state and multilingual coverage. This page is written for real WordPress usage: admin screens, REST operations, translation tables, SEO outputs, frontend rendering and global growth workflows.
Page-specific SVG based on real Verto workflow.
Built for practical multilingual WordPress operations.
Monitor translation activity, cost, health and runtime counters. The goal is not only to translate strings, but to keep localized URLs, SEO signals, provider cost, review quality and frontend performance aligned.
The runtime table tracks minute-bucket request counts, ok/error counts, tokens, cost and average latency by key, giving teams a practical way to monitor provider usage.
Stats endpoints can show translation coverage, review counts, queue state and persistent alerts such as encryption secret warnings or dismissed admin notices.
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.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual workflow.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual workflow.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual workflow.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual workflow.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual workflow.
Activity & Runtime Stats helps teams handle this requirement in a WordPress-native multilingual 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.
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.
| Source | Meaning |
|---|---|
| REST endpoints | /activity, /stats, /coverage, /stats/dismiss-alert. |
| Runtime table | lemonx_translation_runtime stores minute buckets with requests, ok, errors, tokens, cost and latency. |
| Key table | Provider keys store request_count_total, error_count_total and health_status. |
| Stats | Review counts, translation coverage and queue status support admin decisions. |
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.
Common questions about Activity & Runtime Stats.
Can Verto show translation coverage?
Can I monitor cost?
Are provider errors visible?
Can alerts be dismissed?
Build multilingual WordPress growth with LemonX Verto.
Use Activity & Runtime Stats as part of a complete multilingual workflow: languages, provider chain, translation queue, review, SEO, cache, search and LemonX ecosystem integration.