SleekView Charts for GTranslate
GTranslate stores translations on its hosted infrastructure, but the WordPress side holds configured languages, URL modes, and visibility flags. SleekView Charts pivots that into mode mix, status share, default-language KPIs, and configured-locale trends on chart cards.
♾️ Lifetime License available
Audit GTranslate language configuration at the dashboard level
GTranslate is a JavaScript and proxy translation service, so translations themselves do not live in WordPress. What does live in WordPress is configuration: which languages are enabled, which URL mode each uses (subdirectory, subdomain, alias, parameter), which is the default, which are hidden but still configured. The default GTranslate admin presents that data as toggles and dropdowns rather than as a dashboard.
SleekView Charts pivots the configuration into chart cards. URL-mode mix as a donut. Status share (active, hidden, disabled) as a bar. Configured locales over time as a line. A single-number KPI for the default language guarantees something is set, and another counts hidden-but-still-configured languages that should be reviewed.
The dashboard is read-only. Translation work itself stays on GTranslate's infrastructure, including any manual overrides through their editor. SleekView Charts surfaces the WordPress-side configuration so agency portfolio reviews and pre-launch audits run from a chart instead of a settings click-through.
Workflow
How charts plug into GTranslate configuration
Read GTranslate options
Aggregate into cards
Filter and gate
Export for portfolio review
Sample dashboard
Charts you can build from GTranslate data
Languages by URL mode
Count
group by mode
Languages by status
Count
group by status
Configured languages over time
Count
group by configured_at
Hidden but configured
Count
Comparison
Default GTranslate admin vs SleekView Charts
Default GTranslate admin
- Mode mix not exposed as a chart, only as per-language toggles
- Status share requires reading each language row by hand
- No timeline of when locales were added
- Hidden-but-configured languages are not flagged in a dashboard
- Portfolio audits across client sites have no shareable chart
SleekView Charts
- Donut of languages by URL mode
- Bar of status share with active, hidden, and disabled
- Timeline of configured locales over time
- KPI cards for default and hidden-but-configured languages
- Same source as the SleekView GTranslate table
Features
What SleekView Charts gives you for GTranslate
Mode mix at a glance
A donut of languages by URL mode reveals whether the site sits cleanly on subdirectory mode or whether legacy subdomain entries linger from an old CDN setup.
Hidden-language KPI
One number card counts languages configured but hidden. Often legacy market entries; sometimes test locales left active from staging. Either way, visible.
Locale growth timeline
A line chart of configured languages over time gives marketing a visible record of multilingual expansion across campaigns and product launches.
Audience
Who builds GTranslate charts dashboards with SleekView
Agencies
One audit dashboard per client site. Mode mix and hidden-language KPI surface configuration drift across portfolios without clicking into each install.
International marketers
Confirm at the chart level which locales are live, which are hidden, and which were promised but never activated. Campaign launches verify against the dashboard.
Pre-launch QA
Before a go-live, confirm that test languages are not still active and that URL modes match the planned hreflang plan, with the audit reduced to one chart.
The bigger picture
Why GTranslate configuration deserves a chart dashboard
Proxy translation 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. The SleekView table surfaces the matrix; the chart dashboard turns it into a one-glance audit. Mode mix, status share, locale growth, and the hidden-but-configured count all become visible.
Translation work itself stays on GTranslate's infrastructure where it belongs, but the WordPress-side configuration becomes a chart anyone can read in three seconds.
Questions
Common questions about SleekView Charts for GTranslate
No. Translation work lives on GTranslate's infrastructure, including the JavaScript widget overlay and the Translation Delivery Network proxy. SleekView Charts reads the WordPress-side configuration only: language list, modes, URL patterns, default flag, status.
The donut groups configured languages by mode (subdirectory, subdomain, alias, parameter). Useful for spotting legacy entries left over from an older CDN or proxy configuration, especially across multiple client sites.
Yes. Plugin options live in WordPress regardless of plan, so the dashboard surfaces them either way. Paid-plan-specific configuration like TDN subdomains or alias mode appears when those values are present.
Yes. Filters compose at the dashboard level, so the whole board can be scoped to subdirectory-mode languages or to active-only entries with a single saved view.
When URL Translation is enabled, slug pairs are written to plugin options. SleekView Charts can render slug-pair counts and per-language coverage alongside the main language matrix, depending on which cards you compose.
No. SleekView Charts is admin-side only. Front-end translation delivery, whether the JavaScript widget or the TDN proxy, is unaffected. There is no extra query or script on the public site.
Yes. Each card exports its computed series as CSV or JSON. Agencies use the export to share portfolio audits across teams or to track configuration drift between staging and production.
Yes. The hreflang-related settings GTranslate writes appear alongside the language matrix on the dashboard. Confirm that automatic hreflang is configured as expected and that the default URL matches the planned canonical.
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