SleekView for Weglot Translate
Weglot Translate stores active languages and per-post translation references in WordPress while its hosted service handles the actual translation. SleekView reads those references and renders every post-and-language combination as a column-perfect audit grid with sort, filter, and inline edit.
♾️ Lifetime License available
Weglot writes the references, the table gives you the audit surface
Weglot Translate makes a multilingual site possible in an afternoon by routing translation through its hosted service and exposing destination URLs on the front end. The WordPress side carries the active-language option, the original URL list, and the per-post translation references that confirm what is actually translated. None of that is surfaced in the default posts and pages screens, so a localization manager who needs to know which posts in German are still missing ends up exporting to a spreadsheet or sampling the front end by hand.
SleekView reads the same options and postmeta keys Weglot already writes and renders every post and active-language combination as a real table. Title, post type, language, translation status, source URL, and last-modified date become first-class columns with sort, filter, and inline edit on the WordPress-side fields. A localization manager can scope the view to one language, one post type, or every row still showing as missing in a single click.
Weglot keeps owning the front-end URL swap and the hosted translation service. The table view owns the audit surface, so untranslated posts and stale references stop hiding behind a word-count summary on the dashboard.
Workflow
How SleekView surfaces Weglot Translate data
Point at the Weglot records
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical Weglot Translate audit view
wp_postmeta
| Title | Type | Language | Status | Source URL | Modified |
|---|---|---|---|---|---|
| Pricing | page | de | Translated | /pricing/ | 2026-04-22 |
| Pricing | page | fr | Stale | /pricing/ | 2025-11-18 |
| Spring launch announcement | post | de | Missing | /blog/spring-launch/ | 2026-05-02 |
| Help: refunds | page | es | Translated | /help/refunds/ | 2026-03-09 |
| Help: refunds | page | it | Missing | /help/refunds/ | — |
Comparison
Default Weglot admin vs SleekView
Default Weglot admin
- The Weglot dashboard summarises word counts but never surfaces per-post coverage as a column
- Per-post translation status is not visible in the standard posts list
- There is no per-language view of which posts still need work
- Stale translation references are not flagged anywhere in WP admin
- Sorting and filtering posts by Weglot meta requires a custom column callback
SleekView
- Language, status, and source URL rendered directly from Weglot postmeta
- Filter to one language, one post type, or one status value in a click
- Inline edit on WordPress-side fields without opening the post
- Saved views per role: localization audit, editor checklist, owner overview
- Same dataset the chart dashboard reads, so table and charts stay in sync
Features
What SleekView gives you for Weglot Translate
Weglot references as real columns
Language, translation status, and source URL become first-class table columns instead of values hidden inside the Weglot dashboard and the hosted side.
Composable filters across languages
Stack filters on language, status, post type, and modified date to pull untranslated launch pages or stale references in one query, instead of one front-end sample at a time.
Inline edits route through WordPress
Update WordPress-side fields like status flags or modified timestamps inline, with the standard save path. The Weglot front-end flow stays exactly as configured.
Audience
Who uses SleekView for Weglot Translate
Localization managers
Open one saved view per active language and triage the queue of missing or stale posts before the front end ships gaps to customers.
Editorial leads
Scope the audit table to recently published posts and confirm every new article carries a translation owner across active languages before the next release.
Site owners
Pull a saved owner view scoped to top-level pages and active languages, so housekeeping debt around translations is visible in WP admin instead of guessed at.
The bigger picture
Why Weglot sites need a per-post audit table
Weglot Translate solves the translation step by handing it to a hosted service, which is also why the WordPress side stays thin. Word-count totals on the Weglot dashboard tell a buyer that work is happening, but they never tell a localization manager which German posts shipped untranslated last week or which French references have gone stale since the source was rewritten. Reading the active-language option and the per-post translation references already in WordPress turns those questions into a real table.
Language, status, and source URL become first-class columns. Filters compose, so an editor can pull every missing row for one language in a click. Saved views split the audit by role so localization managers, editors, and stakeholders each land on their own slice.
Weglot keeps doing the translation, the table view keeps the WordPress-side state honest.
Questions
Common questions about SleekView for Weglot Translate
Directly from wp_options for the active-language list and from wp_postmeta for the per-post translation references Weglot writes against translated posts. No additional service credentials are required, and the hosted translation flow is untouched.
Yes. Language becomes a dropdown filter with one entry per Weglot active language, plus the source-language fallback for posts that have no translation reference yet. Filters compose with post_type, post_status, and modified date in the same query.
Yes. Each post resolves to one row per active language with a status column derived from the translation reference, so a single view exposes translated, missing, and stale rows without a custom report.
Inline edits in SleekView only touch WordPress-side fields and route through the standard update path. The Weglot front-end runtime that swaps URLs and serves translated pages keeps reading the same configuration.
Queries hit indexed columns on wp_posts (post_type, post_status, post_modified) and indexed meta keys on wp_postmeta. SleekView paginates server-side and caches the resolved per-language rows, so a site with ten languages and tens of thousands of posts renders in seconds.
Yes. Each saved view is gated by WordPress capability, so localization managers, editorial leads, and read-only stakeholders each see the slice that matches their role without exposing the full editor.
Yes. Any filtered view exports to CSV with the visible columns. Translator briefs and renewal reports ship as a scoped list of slugs with language, status, and source URL rather than a full-catalog dump.
No. Weglot keeps owning the hosted translation service, the front-end URL swap, and the word-count side dashboard. SleekView adds a per-post audit table on top of the references Weglot already writes, so the plugin keeps doing translation and the table view handles the WordPress-side reporting.
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