✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Weglot Pro: translation cache and visited URLs as tables

Weglot Pro stores cached translations and visited URL records locally and on Weglot's hosted translation memory. SleekView reads the local cache and option records directly so per-language coverage and visited-URL audits live in WP admin as one filterable workspace.

♾️ Lifetime License available

SleekView table view for Weglot Pro

Local Weglot data without leaving WP Admin

Weglot's main translation memory lives on the Weglot hosted service, but the WordPress plugin caches translation responses and tracks visited URLs locally in wp_options and per-language transients. The Weglot dashboard is the place to manage hosted translation memory, but the local plugin state is the source of truth for what is actually being served from the WordPress install.

SleekView reads the Weglot plugin's option records and cached translation entries directly and surfaces visited URLs, per-language cache status, and configured language pairs as one filterable workspace. Saved views remember combinations like uncached-in-Spanish or visited-this-week, scoped to a target language.

Edits to plugin configuration route through Weglot's settings save path. SleekView does not write to the Weglot hosted translation memory directly: that work still happens through Weglot's dashboard or its API. SleekView focuses on local cache visibility and configuration audit, not on replacing Weglot's hosted editor.

Workflow

How SleekView reads Weglot Pro in practice

1

Pick the local source

Point SleekView at the Weglot plugin's wp_options records and per-language local cache or visited-URL storage. Configured languages are detected from the plugin settings.
2

Compose columns

Add one column per language showing cache status, plus URL type, last-visited time, and exclusion-rule indicators alongside the URL itself.
3

Save audit views

Filter to uncached-in-target or excluded-but-visited URLs and save the combination so recurring audits load with one click.
4

Edit configuration through Weglot

Configuration changes route through Weglot's settings save path. Hosted translation memory edits still happen in the Weglot dashboard or via the Weglot API.

Sample columns

A typical Weglot Pro local view

Visited URLs with per-language cache status pulled from the Weglot plugin's local storage.
Source: wp_options (weglot_options) + per-language translation cache + visited URL records
URL Type DE FR ES Last visited
/products/cotton-tee Product Cached Pending Uncached Apr 24
/about Page Cached Cached Cached Apr 22
/blog/spring-2026 Post Cached Pending Pending Apr 18
/cart Page Cached Uncached Uncached Mar 30

Comparison

Default Weglot Pro admin vs SleekView

Default Weglot Pro admin

  • Most translation management lives in the Weglot hosted dashboard, not inside WP Admin
  • Local cache state is visible only as a top-line option, not per URL
  • Visited-URL audits across languages need direct database queries
  • Per-language cache priming status is not surfaced as a queryable filter
  • Filters across the local plugin state are not preserved between visits

SleekView

  • Visited URLs as a real table with per-language cache status
  • Saved views for uncached-in-target or visited-this-week
  • Filter by URL type, language, or last-visited window
  • Local cache state inside WP Admin, alongside content
  • CSV export scoped to URLs needing translation memory priming

Features

What SleekView gives you for Weglot Pro

URLs as a pivot

Visited URLs become rows with per-language cache columns sourced from the Weglot plugin's local storage, so cache priming and visited audits live in one screen.

Find uncached or pending URLs

Save a view for URLs uncached in a target language and load it again next sprint to coordinate cache priming with translation memory updates.

Configuration audit

View Weglot Pro language pair settings, excluded URLs, and override rules as filterable rows alongside the URL cache so configuration drift is visible.

Audience

Who uses SleekView for Weglot Pro

Localization managers

Audit local Weglot cache coverage alongside the hosted dashboard so the team has a WP-side source of truth for what's actually serving.

Site developers

Review excluded URLs, language overrides, and Weglot Pro configuration in one filterable view rather than scrolling settings screens.

Performance leads

Spot URLs that haven't been visited in a target language recently and may need cache priming before the next campaign launch.

The bigger picture

Why local Weglot visibility matters alongside the hosted dashboard

Weglot's hosted translation memory is one of the cleanest ways to ship a multilingual site without managing a translation database in WordPress. The trade-off is that the source of truth for translations lives off-platform, while the local WordPress plugin maintains cache state and configuration that affects what's actually served. Teams running Weglot at scale eventually want a WP-side view of what the plugin currently knows: which URLs are cached, which language pairs are active, which exclusions exist, and which URLs were visited but never primed.

The Weglot dashboard answers most of the translation questions, but the WordPress side is where deployments, caching layers, and request handling actually happen. Reading the plugin's local options and cache records directly gives operators a WP-native audit surface alongside the hosted dashboard. Configuration drift between staging and production becomes obvious.

Cache priming worklists become real CSV exports. The Weglot hosted service still owns the translation memory and the editor. SleekView just makes the local plugin state legible inside WP Admin, so multilingual operations don't have to live entirely off-platform.

Questions

Common questions about SleekView for Weglot Pro

No. Weglot's hosted translation memory and editor remain in the Weglot dashboard. SleekView focuses on the local plugin state inside WordPress, which complements the dashboard rather than replacing it.

 

The Weglot plugin's wp_options records (configuration, language pairs, exclusions) and the per-language local cache or visited-URL records that the plugin maintains on the WordPress side.

 

No. Translation memory lives on Weglot's hosted service and is edited through the Weglot dashboard or API. SleekView surfaces local cache state and configuration but does not write to Weglot's hosted memory directly.

 

Yes. URL exclusion rules from the Weglot plugin configuration surface as filterable rows so configuration drift between staging and production is auditable.

 

No. SleekView reads only the local plugin storage. Any Weglot API call still goes through the Weglot plugin itself, and SleekView does not add new network calls.

 

No. SleekView queries run only when an admin loads a view. The front-end Weglot translation path is untouched and the public site continues to use Weglot's normal serving logic.

 

Yes. CSV exports honor the current filter and column visibility, so an audit of uncached-in-French URLs is a one-click action against the local plugin storage.

 

Yes. Each multisite blog's Weglot configuration lives in its own wp_options rows, and SleekView's multisite-aware queries surface them per blog.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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