The Automatic Translate Addon for Polylang adds a one-click and bulk auto-translation flow on top of standard Polylang. 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 posts are still raw machine output and which already went through a human pass.

SleekView reads the Polylang taxonomy and the addon's per-post review meta together and renders every translated post as a real table. Title, post type, language, origin (machine or human), review status, batch date, and last-modified become first-class columns with sort, filter, and inline edit. A reviewer can scope the view to one language and unreviewed machine output, and a localization lead can pull every batch from the last sprint to confirm throughput before launch.

The addon keeps doing the batching and Polylang keeps owning the taxonomy. The table view owns the QA queue, so raw machine output stops shipping to the front end because nobody had a list to work from.

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 because nobody had a clear list of what was left to check. Job logs say a batch ran, but they do not say which posts inside that batch still need a reviewer or which targets carry the deepest backlog.

Reading the Polylang taxonomy and the addon's per-post review meta together turns the QA queue into a real table. Title, language, origin, and review status become first-class columns. Filters compose so a German reviewer narrows to unreviewed machine rows in a click.

Saved views split the audit by role so QA reviewers, editorial leads, and stakeholders each get their own surface. The addon stays in charge of running the translations, the table view stays in charge of the queue.