MultilingualPress takes a different architectural path from inline-tag plugins: every language lives on its own WordPress multisite subsite. A post on the English subsite is linked to its German counterpart on the German subsite through rows in mlp_content_relations with content_id, site_id, and a shared relationship_id. The site list and language assignments live in mlp_site_relations and the related mlp_languages table maintained by the plugin.

That architecture is clean per subsite and brutal for cross-subsite reporting. The default WP Network admin shows a list of sites with a language label, the editor sidebar shows a link to a sibling translation, but neither answers "how many English posts have no German equivalent" or "which post type is most undertranslated network-wide" without a custom SQL roll-up across every subsite.

SleekView Charts reads mlp_content_relations joined to each subsite's wp_posts and renders four cards on top of that join. A Number for English posts without any linked translation. A Pie of relationships split by target language. A Bar of linked-translation coverage per post_type. An Area of new relationships per week. MultilingualPress keeps owning the editor, the relations API, and the synced features. SleekView only reads the rows the plugin has already written.

MultilingualPress already does the hard part: every language lives on its own subsite with a clean join table that links sibling posts. What the plugin does not do is roll those links up into a dashboard. Network managers can confirm that a single post has a German equivalent, but cannot answer corpus-wide coverage questions without a custom SQL pass across every subsite.

SleekView Charts reads the same mlp_content_relations and mlp_site_relations rows, joins them to each subsite's wp_posts, and renders four cards that answer those questions in one glance. The data is already correct because MultilingualPress wrote it. Charts just gives the team a dashboard to look at it.

A linked translation that nobody noticed is missing costs traffic on every search result page in that locale, and a live coverage dashboard catches the gap before it ships.