WPGlobus does not split translations into separate posts. Every language for a post lives inline in the same row, wrapped in tags like [:en]Title in English[:][:de]Titel auf Deutsch[:] stored in wp_posts.post_title, wp_posts.post_content, and the excerpt. Configuration lands in wp_options under WPGlobusConfig with the enabled language codes, the default locale, and the URL strategy. SEO and image fields used by Yoast or RankMath get the same inline encoding inside wp_postmeta.

That structure is great for editors and terrible for reporting. The default Posts list shows one row per post in the admin language only. There is no built-in screen that answers "how many posts are still missing the German variant" or "which post type lags behind on French" without running a custom SQL query against the inline tags.

SleekView Charts reads wp_posts directly, parses the WPGlobus inline tags per language code from WPGlobusConfig, and renders four cards on top of that. A Number for posts missing any language. A Pie split by primary language coverage. A Bar of coverage per post_type. An Area of WPGlobus edits per week from post_modified. The plugin still owns the language switcher and the inline tag format. SleekView only reads what is already in the database.

WPGlobus stores every language inside the same post row, which is exactly what makes its editor experience smooth and its reporting experience hard. The Posts list shows one entry per post in the admin language, hiding which translations are present and which are missing. Localization managers cannot answer "how complete is German across the corpus" without exporting and grepping the inline tags.

SleekView Charts reads the same post_content column, parses the language tags using the codes from WPGlobusConfig, and renders four cards that answer those questions in one glance. The data is already correct because WPGlobus wrote it. Charts just gives the team a dashboard to look at it.

Missing translations cost the business search traffic in every market that lags behind, and a live coverage dashboard catches the gap the day a new post lands.