SleekView for WP Auto Content
SleekView reads the wp_posts rows WP Auto Content creates plus the run log it writes per cron tick, then exposes topic, model, status and tokens_used as sortable columns you can filter, edit inline and export.
♾️ Lifetime License available
A list of recent runs is not a workspace.
WP Auto Content runs on a schedule, calls an OpenAI-style endpoint and writes the result into wp_posts as a draft or publish article. The plugin's admin shows a recent activity feed and the last run status. That covers verification of the last cron tick. It does not cover the editorial workflow of reviewing a week of auto-drafts, comparing topics, or seeing which generated posts ever reached publish.
SleekView reads the same wp_posts rows and the run log metadata (topic, model, tokens_used, run_status) into a single sortable, filterable table. Editors get one screen that lists every generated post with the operational columns the plugin already records, plus inline status edits so approving a batch of drafts no longer means opening each one.
Save the column set per role: editorial leads see status, topic and publish date; ops sees model, tokens_used and run_status; the site owner sees a slimmed-down view scoped to this month. Same dataset, different lenses, none of it pulled into a separate analytics tool.
Workflow
How SleekView reads WP Auto Content data
Pick the source
Compose the column set
Save and scope the view
Edit inline and export
Sample columns
A typical WP Auto Content runs view
wp_posts + WP Auto Content run log (postmeta or custom log table)
| Post | Status | Topic | Model | Tokens | Run date |
|---|---|---|---|---|---|
| Best espresso grinders 2026 | Publish | coffee gear | gpt-4o-mini | 1,842 | May 14 |
| Mid-roast vs dark roast guide | Draft | coffee gear | gpt-4o-mini | 2,104 | May 14 |
| How to clean a burr grinder | Pending | maintenance | gpt-4o | 3,512 | May 13 |
| Latte art for beginners | Failed | barista | gpt-4o | — | May 13 |
| Cold brew ratios that work | Publish | recipes | gpt-4o-mini | 1,205 | May 12 |
Comparison
Default WP Auto Content admin vs SleekView
Default WP Auto Content admin
- Activity feed shows recent runs, not a sortable list of every generated post
- Fixed column set, no way to expose configured topic or model per row
- Token usage hidden inside individual run rows, no per-column sort
- Bulk status changes require leaving the activity log for the Posts screen
- No saved per-role view for editorial, ops and ownership
SleekView
- Read directly from wp_posts plus WP Auto Content's run log meta
- Surface configured topic, model and tokens_used as real, sortable columns
- Inline bulk-publish auto-drafts through the normal WordPress post hooks
- Save filtered views per role ("Pending drafts", "This month's runs", "Failed runs")
- Export the filtered table to CSV for monthly editorial review
Features
What SleekView gives you for WP Auto Content
Custom columns from the run log
Add configured topic, model name, tokens_used and run_status as first-class columns. Editors finally see why a draft was generated, not just that it exists.
Inline status edits with WP hooks intact
Move auto-drafts to publish in bulk and the normal transition_post_status, save_post and email hooks fire. Approving a batch no longer means thirty post-edit screens.
Filters editorial actually uses
Combine post_status, topic, model, run_status and date. Save the result as a named view ("This week's pending drafts") so the team reuses it every shift.
Audience
Who uses SleekView for WP Auto Content
Editorial leads
Triage a week of auto-drafts in one screen, group by topic, bulk-approve the publishable ones and keep the failed runs visible until they are diagnosed.
Content ops
Sort by tokens_used to spot prompts that ballooned. Filter by model after a config change to confirm runs landed on the intended endpoint.
Site owners
One scoped view of monthly output: post_title, status, topic and date in a sortable list. The auto-writer becomes a measurable channel instead of a black box.
The bigger picture
Why auto-generation needs a real editorial table, not an activity feed
WP Auto Content's value is throughput, and throughput is exactly what an activity feed is bad at presenting. A feed answers whether the last cron tick worked. It does not let editorial sort fifty drafts by topic, bulk-approve the publishable ones, or surface that a recent prompt change pushed average tokens per post up by sixty percent.
A real table on wp_posts joined to the plugin's run log fixes that, because the columns editors actually need (topic, model, tokens, status) become first-class fields. Inline status edits flow through the standard WordPress hooks so nothing about email triggers, scheduling or stock plugins changes. Same posts, same log, completely different operating posture toward the auto-writer.
Questions
Common questions about SleekView 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 table runs entirely on data already in the WordPress database.
Yes. SleekView writes through wp_update_post so transition_post_status, save_post, scheduled-publish and email-related hooks all fire as expected. Bulk operations iterate through the same path so the side effects are identical to manual edits.
Yes. The agent UI scans the install for keys actually written by WP Auto Content (topic, model, tokens_used, run_status, prompt_hash and similar) and lists them so you pick from a real list instead of guessing names.
Yes for any data the plugin writes to wp_posts and postmeta. Pro builds typically record richer metadata (token counts, model attribution) which simply gives more columns to filter on when present.
No. Queries hit indexed columns on wp_posts (post_status, post_date, post_type) and the run log key/value pairs SleekView surfaces. Even on installs with thousands of generated posts the table paginates without scanning the world.
Yes. Any filtered set exports to CSV with the columns currently shown. Useful for handing a monthly review to an editor or for sharing a sample of failed runs with the prompt engineer.
Yes. Filter by the configured topic value and save the result as a named view. Editorial leads use this when one prompt is on probation and they want a dedicated working surface for it.
No. WP Auto Content keeps generating posts on the schedule it is configured for. SleekView only reads the resulting data and turns it into a workable table. 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout