Loco Translate Pro reads and writes PO and MO files in plugin, theme, and custom language directories, with project metadata stored in wp_options under keys like loco_settings and per-project bundles inside WP_LANG_DIR. The default UI lists projects one at a time and opens a translation editor per locale, which is exactly the workflow when you fix one string. Across a site with thirty plugins and five locales, that is one hundred and fifty editor sessions to answer the question of which files are still fuzzy.

SleekView builds an index over those PO files at view-load time, with project, locale, total strings, translated count, fuzzy count, and last-modified as sortable columns. Filters like fuzzy > 0, or locale = fr_FR, or modified-since-March, become saved views that reload with one click.

Edits still happen in the Loco editor, but SleekView links each row directly to the right Loco screen, so the audit grid becomes a navigation layer over the same Pro editor experience.

Loco Translate Pro is an excellent file editor for PO and MO content, but the underlying truth of a multilingual WordPress site is that there are dozens of those files scattered across plugins, themes, and custom bundles. Auditing them one by one is feasible during the initial localization rollout, when somebody is doing the work full time. It stops being feasible six months later when the team has rotated, three plugins have updated their POT, and the developer who set everything up has moved on.

A queryable index of every PO file on the site, with fuzzy counts and last-modified dates as columns, changes that situation in a useful way. A weekly thirty-minute session sorts by fuzzy count, picks the worst project, and clears it in the same Loco Pro editor that has always been the right tool for the per-string work. Site owners get a reportable coverage number per locale, agencies can compare client sites on a single dashboard, and developers can confirm that their custom POT files are still being picked up by Loco.

None of that requires a new editor or a parallel translation memory; the index is read-only audit infrastructure on top of the editor that already works.