SleekView for WPML: translations and content as customizable tables
WPML uses 20+ custom database tables to manage multilingual content. SleekView reads icl_translations and string tables directly so missing translations, stale jobs, and per-language gaps surface as one filterable workspace in WP admin.
♾️ Lifetime License available
Find translation gaps in seconds
WPML splits translation state across icl_translations, icl_strings, icl_string_translations, plus job, package, and rate tables. The default Translation Management screen aggregates this into a heavy React app that stalls on sites with tens of thousands of rows. SleekView reads those WPML tables directly and renders results server-paginated, so a localization manager looking at 40,000 posts across five languages gets a usable list instead of a spinner.
Each configured WPML language becomes its own status column with badges for translated, in-progress, needs-update, and missing. Saved views remember which combination of source language, post type, translator, and date window you care about — useful when you run weekly sprint planning and always start from the same filter.
The result is concrete: instead of clicking through Translation Management tabs to count gaps, you see at a glance that 312 products are missing French, 47 pages need a German update, and the About page is fully covered. CSV export builds translator handoffs scoped to exactly that work.
Workflow
How SleekView reads WPML in practice
Connect WPML tables
Pivot per-language status
Save sprint views
Export translator briefs
Sample columns
A typical WPML translation status view
WPML custom tables (icl_translations, icl_strings, icl_string_translations, plus 15+ supporting tables)
| Title | Source language | EN | DE | FR | Last updated |
|---|---|---|---|---|---|
| Spring 2026 campaign | EN | Translated | In progress | Missing | Apr 24, 2026 |
| About us | EN | Translated | Translated | Translated | Apr 22, 2026 |
| Pricing | EN | Translated | Needs update | Needs update | Apr 19, 2026 |
| Old launch post | EN | Translated | Missing | Missing | Mar 12, 2026 |
Comparison
Default WPML admin vs SleekView
Default WPML admin
- Translation Management screen is heavy and slow on large sites
- Filters reset between visits
- Per-language status columns are limited
- Bulk reassign across languages takes many clicks
- Cross-post-type audits are difficult
SleekView
- Per-language status columns at a glance
- Saved views for missing, in-progress, or stale translations
- Filter by post type, source language, or translator
- Inline edit status flags and notes
- CSV export for translator handoffs
Features
What SleekView gives you for WPML
All languages, one table
Each configured WPML language gets its own column with translated, in-progress, needs-update, and missing badges sourced from icl_translations directly.
Find what's missing
Save a view for missing-in-French or stale-since-Q1 and reload that exact filter combination next sprint without rebuilding it from defaults.
Inline notes for translators
Leave handoff notes per row that travel with the CSV export, so context reaches the translator without separate spreadsheets or email threads.
Audience
Who uses SleekView for WPML
Localization managers
Plan sprints by language and post type with concrete missing-translation counts pulled from icl_translations rather than estimated from sampling.
Translation agencies
Hand off scoped CSVs of exactly the rows that need work — title, source URL, notes — instead of dumping the whole site catalog onto translators.
Site owners
Spot stale translations where the source has changed since the target was approved, before the gap surfaces in customer-facing support tickets.
The bigger picture
Why WPML visibility beats one more dashboard
WPML is powerful but its scale assumptions show on busy editorial sites. The built-in Translation Management UI loads in chunks and resets filters between page loads, so anyone running a real localization program ends up exporting to spreadsheets and tracking state outside the plugin. That works until someone forgets to update the spreadsheet.
Then a German product page launches without French and Spanish, the missing translations surface in support tickets, and the team rebuilds an audit by hand. Reading icl_translations directly closes that loop. A saved view that says missing-in-French-for-product-pages-updated-since-March is the same view tomorrow, regardless of who is at the keyboard.
Translators get scoped CSVs instead of full exports, agencies hand off work with no ambiguity, and site owners can see the localization debt clearly enough to budget for it. The plugin still runs the actual translation work — SleekView just makes the state legible across a 40,000-row site without changing any WPML configuration.
Questions
Common questions about SleekView for WPML
WPML uses around twenty custom tables. The core ones are icl_translations for content language relationships, icl_strings and icl_string_translations for theme and plugin strings, plus supporting tables for translation jobs, packages, language pair rates, and queues. SleekView reads the relevant ones at query time.
 No. The actual translation work still happens inside WPML, whether through the Translation Editor, a connected service, or manual translators. SleekView focuses on visibility and status management — finding gaps, scoping work, and surfacing handoff CSVs.
 Yes. Source language, target language, post type, translation status, and translator can all be combined and saved as a view. The combination loads with one click rather than rebuilding filters each visit.
 Yes. SleekView ships a separate string-translation view that reads icl_strings and icl_string_translations, so theme and plugin string coverage is auditable in the same way as post and page content.
 Yes. Filter to missing in a target language, optionally narrow by post type or update date, and export to CSV. The export contains only the columns visible in the view, which keeps translator briefs lean instead of dumping entire site exports.
 No. SleekView paginates server-side and reads WPML tables only when an admin loads a view. There is no front-end query overhead, and the translation logic that runs on every public request is untouched.
 Yes. Translation jobs from the WPML Translation Management workflow live in their own tables and surface as a dedicated view, with translator, deadline, status, and word count columns alongside the source post.
 Yes. Sites with eight or more configured languages get a wide table with one column per language. Hidden columns can be toggled per saved view, so a French-and-German-only sprint doesn't have to scroll past Japanese and Korean every time.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout