The WP Spin Rewriter Integration and similar Smodin integrations plug a rewrite button into the WordPress post editor. One click sends the post content to Smodin or SpinRewriter, gets a rewritten version back, and stores it as a post revision or a draft. The catch is that the built-in screen is a thin settings page with a request counter. There is no way to chart how many rewrites each editor ran, which provider produced them, or how many rewrites actually shipped to publish.

SleekView Charts reads the rows the plugin already writes. Rewrite jobs land as wp_posts revisions and drafts, and the plugin stamps each one with postmeta keys like _rewriter_provider, _rewriter_mode, _rewriter_original_id, _rewriter_word_count, and _rewriter_run_id. Settings sit under the article_rewriter_settings option. SleekView pulls the posts joined to those postmeta keys directly into a chart builder.

You keep every guardrail the plugin gives you. The Smodin or SpinRewriter API key stays in the plugin, per-user limits stay enforced, and the rewrite history still lives in revisions where it always did. SleekView simply turns the existing rewrite log into a configurable dashboard editors, content leads, and finance can read without opening a post one revision at a time.

Article Rewriter integrations are popular because they sit one click away from the post editor, which is also why their usage is so easy to lose track of. The plugin records every rewrite as a post or revision with provider, mode, and word-count postmeta, but the built-in settings screen never groups it into anything readable. SleekView Charts treats those rewrites as a real dataset.

Editors get a daily rewrite area chart they can read in five seconds, content leads get a modes bar that shows whether the team trusts light, standard, or aggressive rewriting, and finance gets a clean monthly KPI that lines up with the Smodin or SpinRewriter invoice. The keys stay in the plugin, the revisions stay in WordPress, and the reporting finally lives where the writing happens.