✨ 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 Charts for WP Auto Content

SleekView Charts reads the posts WP Auto Content generates and the cron log it writes on every run, then renders volume, status mix, token spend and schedule adherence as Number, Pie, Bar and Area cards.

♾️ Lifetime License available

SleekView Charts dashboard for WP Auto Content

Auto-generation is easy. Auto-governance is the missing half.

WP Auto Content runs on a schedule, calls an OpenAI-style endpoint and drops the result into wp_posts as a draft or published article. The plugin's own admin shows a recent activity list and the last run status. That covers the operational question of whether the last cron tick worked. It does not cover the editorial question of how much the bot has actually shipped this quarter, how many of those posts ever reached publish, and what each of them cost in tokens.

SleekView Charts reads the same wp_posts rows the plugin writes, combined with the run log it stores in postmeta or its custom log table, and turns the auto-writer into a measurable channel. A Number card surfaces total posts generated this month. A Pie splits them across draft, pending and publish. A Bar groups output by configured topic or category. An Area trends generation volume per day so cron drift, throttling and quota issues become visible at a glance.

Because the dataset is the same posts and meta the table view uses, every filter carries across. Scope to a single category, a date range or an author and the entire dashboard narrows with it. Nothing is recomputed in a separate analytics product, and nothing leaves the site.

Workflow

Turn auto-generated posts and run logs into a dashboard

1

Read the generated posts

SleekView scans wp_posts for rows tagged with WP Auto Content's source meta and pulls the run log it writes per cron tick, including model, token count and topic.
2

Compose the chart cards

Pick Number, Pie, Bar, Area or Line cards. Group by category, post_status, configured topic or run date, and aggregate as Count, Sum, Average, Minimum or Maximum.
3

Save and scope the dashboard

Name it ("Auto content this quarter", "Token spend per topic") and gate it by WordPress capability so editors, ops and the site owner each see the slice they need.
4

Share or export

Send stakeholders a read-only URL or export the filtered set to CSV. The dashboard refreshes against live data, so monthly content reviews work off real numbers instead of a vague "the bot is running".

Sample dashboard

Charts you can build from WP Auto Content data

Each card reads from the posts and run log the plugin already writes. Mix them to build a dashboard for editorial leads, content ops or a monthly auto-content review.
Number · Default

Posts generated this month

Total wp_posts rows created by WP Auto Content in the current month. The headline number for any auto-content review.
Count
Pie · Donut text

Generated posts by status

Split across draft, pending, publish and trash. Surfaces how many auto-drafts editors actually approved versus how many sat untouched.
Count group by post_status
Bar · Horizontal

Output by configured topic

Posts grouped by the topic or keyword the plugin was configured to write about. Shows which configured prompts are doing the most work.
Count group by topic
Area · Gradient

Token spend per day

Daily total of tokens reported by the run log. Useful for spotting quota spikes, configuration changes or runaway prompts before the monthly bill arrives.
Sum(tokens_used) group by run_date

Comparison

Default WP Auto Content reporting vs SleekView Charts

Default WP Auto Content activity log

  • Activity log shows last few runs, not quarterly output volume
  • No visual split of generated posts across draft, pending and publish
  • Token usage hidden inside individual run rows, no aggregate
  • Cannot group output by configured topic or category visually
  • No way to share a read-only auto-content dashboard outside WP admin

SleekView Charts

  • KPI card for total auto-generated posts this month
  • Pie split across draft, pending and publish to track editor approval
  • Bar of output per configured topic for prompt-level accountability
  • Area trend of token spend to catch quota and config drift early
  • Filters carry between table view and chart view on the same dataset

Features

What SleekView Charts gives you for WP Auto Content

Dashboard, not an activity log

Render WP Auto Content output as Number, Pie, Bar and Area cards so editorial leads see the channel, not just the last cron tick that succeeded.

Filters span table and chart

Scope to a category, a topic or a date range in either view and the other stays in sync. Same dataset, same meta, two ways of reading it.

Token spend in plain sight

Sum tokens_used per day or per topic so quota spikes show up the day they happen, not the day the bill arrives.

Audience

Who builds WP Auto Content charts dashboards with SleekView

Editorial leads

Track how many auto-drafts editors actually approve, watch the pie split shift over time and treat the auto-writer like any other contributing channel.

Content ops

Sum token spend per topic and per day to catch a prompt that ballooned overnight, or a category configured a touch too aggressively for its real demand.

Site owners

See the auto-content channel as a single dashboard: total posts shipped this quarter, status mix, top topics and a clear daily trend instead of cron log scrolling.

The bigger picture

Why auto-generation needs editorial reporting, not just a run log

WP Auto Content makes shipping the next post almost free, and that very frictionlessness is what makes governance hard. A run log answers whether the last cron tick fired. It does not answer whether half of this month's auto-drafts ever cleared editorial, whether one configured topic is quietly consuming most of the token budget, or whether output has drifted up or down since a configuration change six weeks ago.

A KPI of posts generated this month makes volume visible. A pie of statuses shows whether the channel is actually shipping or quietly piling up drafts. A bar per configured topic exposes which prompts are doing the work and which are dead weight.

A token-per-day area makes quota and config drift visible before it shows up on a credit card statement. Same wp_posts rows, same run log, completely different operating posture.

Questions

Common questions about SleekView Charts for WP Auto Content

Standard wp_posts columns plus the run log WP Auto Content writes (as postmeta or in its custom log table), including configured topic, model and token count. No external service is required, the dashboard runs entirely on data already in the WordPress database.

 

Yes. Table view and chart view sit on the same dataset, so a filter for last month's posts or a single category applies to both. Editors can pivot between row-level review and chart-level summary without rebuilding filters.

 

Yes. Group by post_status with a Pie or Donut card and the split between draft, pending and publish is the answer. Pair it with a Number card for total generated this month and the approval rate becomes obvious.

 

Yes, if WP Auto Content's run log is configured to record token counts (most builds do). Group by run_date with an Area or Line card and aggregate tokens_used as Sum. Spikes correspond to prompt changes, schedule changes or model swaps.

 

No. SleekView queries are scoped to the dataset behind each chart and cache aggressively. The auto-content dashboard reads from indexed columns on wp_posts and the plugin's log, so a quarter of activity renders in milliseconds even on a large editorial site.

 

Yes. Any filtered set behind a chart card exports to CSV with the same columns the table view would show. Useful for quarterly auto-content reviews or for handing a sample over to a writer who reviews the bot's drafts.

 

Yes. Add a filter for the configured topic value and the KPI, pie, bar and trend cards all narrow to that topic. Editorial leads use this when one prompt is on probation and they want a dedicated cockpit for it.

 

No. WP Auto Content keeps generating posts on the schedule it is configured for. SleekView Charts only reads the resulting data and turns it into a dashboard. The plugin remains the source of truth for generation, model choice and scheduling.

 

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