GTranslate sits in a different category from WPML, Polylang, and TranslatePress: the actual translations live on GTranslate's hosted infrastructure, not in the WordPress database. The free version injects a JavaScript widget; paid plans use a Translation Delivery Network that proxies the site through GTranslate's edge. The only WordPress-side state is plugin configuration — which languages are enabled, which mode each uses, what URL pattern serves them, and which one is the default.

That configuration is spread across the GTranslate settings screen as toggles, dropdowns, and free-text fields. SleekView pulls those settings into a sortable table where every configured language is one row with code, mode, URL pattern, default flag, and visibility status as columns.

The audit becomes mechanical: confirm that French is set to subdirectory mode at /fr/, German is active and not hidden, the Polish entry left over from a discontinued market is disabled, and no test languages slipped through to production. For agencies running GTranslate on multiple client sites, the same view loaded across sites makes the multilingual surface verifiable in minutes.

GTranslate handles the translation layer outside WordPress, which removes a class of database problems but introduces a different one: configuration drift on the WordPress side is invisible. A test Polish entry added during launch can sit hidden but enabled for a year before someone notices a stray /pl/ URL in the sitemap. A subdirectory-mode German that should have been switched to subdomain after a CDN migration silently keeps serving from the wrong path.

The plugin settings UI is built to set these values, not to audit them, and there's no built-in list view that makes drift obvious. Reading the GTranslate options into a sortable table closes that gap. An agency auditing a portfolio of multilingual sites can load the same view across each site and verify the matrix in minutes.

A maintainer doing pre-launch QA confirms that no test languages are still active in production. The translation work itself stays where it lives — on GTranslate's infrastructure — but the WordPress-side configuration becomes a list that can actually be reviewed.