✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Charts for Automatic Translate Addon for Polylang

The Automatic Translate Addon for Polylang batches machine translations against the Polylang taxonomy. SleekView Charts reads the same taxonomy and surfaces machine-translated vs human-edited coverage as Number, Pie, Bar, and Area cards.

♾️ Lifetime License available

SleekView Charts dashboard for Automatic Translate Addon for Polylang

Track what the machine translated and what still needs review

The Automatic Translate Addon for Polylang adds a one-click and bulk auto-translation flow on top of standard Polylang. The translated posts land in the same Polylang taxonomy as human-edited ones, which is great for the front end and tricky for review. Once a few thousand posts have been auto-translated, the team needs to know which ones a human has reviewed and which are still in raw machine state.

SleekView Charts reads the Polylang taxonomy and the addon's per-post review meta together. A Number card shows the share of auto-translated posts that are still unreviewed. A Pie splits the catalog into linked-human, linked-machine, and missing. A Bar ranks the unreviewed queue by language. An Area trends review throughput per week so a QA sprint has measurable progress.

The addon keeps doing the batching; SleekView Charts surfaces what the batches actually produced and what is left to check before the front end goes live with raw machine output.

Workflow

Turn the auto-translation queue into a dashboard

1

Read the taxonomy and review meta

SleekView walks the Polylang translation taxonomy and joins the addon's per-post review meta so every translated row resolves to a source, language, machine-or-human origin, and review status.
2

Compose the chart cards

Pick Number, Pie, Bar, Area, or Radial cards. Group by language, review_status, post_type, or batch_date, and aggregate as Count, Sum, Average, Minimum, or Maximum.
3

Save and scope the dashboard

Name the dashboard ("Auto-translation QA cockpit", "Unreviewed machine output") and gate by capability so QA reviewers, editors, and ops see the slice that fits.
4

Share or export

Send a read-only dashboard URL or export the unreviewed queue to CSV. Reviewers receive a scoped list of slugs rather than a full taxonomy dump.

Sample dashboard

Charts you can build from Automatic Translate Addon data

Each card below reads from the Polylang taxonomy and the addon's per-post review meta. Mix them to build a QA cockpit for a launch or a quarterly review of machine output.
Number · Default

Unreviewed machine posts

Single KPI for translated posts whose origin is machine and whose review_status is still unreviewed. The anchor number a QA sprint commits to clearing.
Count
Pie · Donut text

Origin split across the catalog

Donut split across human, machine reviewed, machine unreviewed, and missing. Surfaces how much of the catalog already went through a human pass and how much has not.
Count group by translation_origin
Bar · Horizontal

Unreviewed by language

Per-language ranking of unreviewed machine posts. Surfaces which target language carries the deepest QA backlog so reviewer time goes where it matters first.
Count group by language_code
Area · Gradient

Review throughput per week

Time series of posts moved from unreviewed to reviewed per week. Confirms that a QA sprint actually moved the trend rather than just cleared the screen once.
Count group by reviewed_week

Comparison

Default addon UI vs SleekView Charts

Default addon UI

  • Auto-translation runs are summarised as job logs, not as catalog state
  • Unreviewed machine output is not surfaced as a single KPI
  • No breakdown of machine vs human origin across the catalog
  • No per-language ranking of QA backlog
  • No time series of review throughput across the team

SleekView Charts

  • KPI for unreviewed machine-translated posts across the site
  • Donut split of human, machine reviewed, machine unreviewed, missing
  • Per-language bar of QA backlog for sprint planning
  • Area trend of review throughput per week
  • Filters carry between the unreviewed queue view and the chart view

Features

What SleekView Charts gives you for Automatic Translate Addon for Polylang

Machine vs human origin

Resolve every translated post to a clean origin label so QA reviewers can scope work to raw machine output rather than touching posts that already went through a human pass.

Per-language QA backlog

Per-language bars expose where machine output piled up, so a German reviewer and a French reviewer each get a scoped queue instead of one mixed list.

Share read-only snapshots

Send a project lead a dashboard URL or export the unreviewed queue to CSV. Reviewers receive a scoped brief rather than a guess about what is left to check.

Audience

Who builds Automatic Translate Addon charts dashboards with SleekView

QA reviewers

Open the dashboard, see the unreviewed KPI per language, and clear the queue from a scoped CSV instead of scrolling the standard post list.

Localization managers

Plan QA sprints against a concrete number of unreviewed machine posts per language instead of estimating based on the most recent run.

Site owners

Track review throughput over time so the decision to expand auto-translation rests on the QA capacity to keep up rather than the budget alone.

The bigger picture

Why machine translations need a QA cockpit, not just a job log

The Automatic Translate Addon for Polylang makes a fast translation pass cheap enough to apply across thousands of posts at once. The risk is that the front end goes live with raw machine output that nobody reviewed because the team never had a clear view of what was left to check. Job logs say a batch ran.

They do not say how many posts inside that batch still need a human reviewer. A KPI of unreviewed machine posts gives the QA team a target. A donut of origin labels surfaces what the catalog actually looks like across human, reviewed-machine, and unreviewed-machine.

A per-language bar ranks the QA queue so reviewer time lands where the backlog is deepest. An area trend of throughput confirms that the team can keep up with the addon's pace, or surfaces the gap when it cannot. The addon stays in charge of running the translations; SleekView Charts stays in charge of what the QA program is actually doing.

Questions

Common questions about SleekView Charts for Automatic Translate Addon for Polylang

Only the Polylang translation taxonomy and the per-post review meta the addon writes when it batches a translation. There is no separate database, and the addon's job logs continue to record run-level detail in their own place.

 

No. The Automatic Translate Addon for Polylang still runs the machine translation step. SleekView Charts only surfaces QA backlog, origin splits, and throughput so reviewers know exactly what needs human attention.

 

Yes. Apply a filter for language_code and every chart card narrows to that target. A reviewer responsible for German sees a clean cockpit for German with no other languages in the way.

 

Yes. The translation_origin and review_status columns make that split explicit, and a donut or stacked bar can carry it cleanly. Reviewed-machine posts count as done so the KPI tracks the queue that actually needs a human.

 

Yes. Polylang controls which post types are translatable, and the addon respects that. SleekView Charts mirrors the same scope so a site that translates products, case studies, and standard posts can group QA backlog by post_type as a column.

 

No. SleekView only reads the taxonomy and meta in WP admin when a dashboard loads, paginates server-side, and caches resolved rows. Front-end Polylang behaviour stays untouched.

 

Yes. Filter the chart cards to translation_origin equal to machine and review_status equal to unreviewed, then export the rows behind them to CSV with title, source URL, and language for the reviewer brief.

 

No. The addon works with Polylang and Polylang Pro, and SleekView Charts reads the same taxonomy in either case. Sites that move from free Polylang to Pro keep the dashboards intact.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView