Linguise Pro stores most of its WordPress-side state in wp_options under keys like linguise_options, including configured languages, URL rules, content exclusion selectors, and per-domain settings. The Linguise dashboard handles the translation cache itself, but the WordPress operator still needs to audit which rules apply to which pages and which content has local overrides.

SleekView reads the relevant wp_options rows along with any locally saved overrides, then exposes each rule as a row with language, scope, selector, and last-updated columns. Saved views group rules by language, by post type, or by whether they have been edited since rollout, which the default settings UI cannot do.

Edits route through Linguise's own option API, so changes apply the same way they would through the plugin settings page. The grid is purely a more navigable surface on the same configuration; nothing about the front-end translation proxy changes.

Linguise's strength is that it removes content from the WordPress operator's plate: the proxy handles translation, caching, and serving without local edits. That works beautifully right until the rule set in wp_options grows past a couple of dozen exclusions, replacements, and per-language overrides. At that point the settings page becomes a list of strings that nobody can usefully audit, and questions like which rules are disabled but still in the database, or which exclusion selectors no longer match any element on the redesigned site, become research projects instead of one-screen lookups.

Treating the rule set as a table changes the cost of those audits. A localization manager can group rules by type and status, a developer can find unused selectors, and an SEO lead can confirm that alt-attribute translation is still active for every target language. Inline toggles still route through the same option API as the settings page, so nothing about the Linguise proxy behaviour changes; only the WordPress-side audit surface gains a grid.

For multi-language commerce sites running Linguise across dozens of locales, that grid is what keeps the rule set honest over months and years of edits.