SleekView for Spin Rewriter: spun posts and run history as tables
SleekView reads the posts Spin Rewriter has rewritten and the connector log it keeps in WordPress, then renders source URL, confidence band and last-spin timestamp as real columns. The Spin Rewriter cloud still owns the model; WordPress owns the artifact.
♾️ Lifetime License available
Spin Rewriter rewrites in the cloud. WordPress records the artifact.
Spin Rewriter for WordPress is a thin connector to the Spin Rewriter cloud: the model call and the synonyms live in their service, the result lands in WordPress as an updated post body and a small amount of meta on the post (commonly _spinrewriter_source_url, _spinrewriter_run_id and a confidence value). For long-tail tracking the connector may also keep a lightweight log in wp_options or a dedicated table such as wp_spinrewriter_runs, depending on the version installed.
That artifact is what an editorial team needs a real list for. SleekView reads wp_posts with the Spin Rewriter meta keys, joins back to any connector log it finds and surfaces source URL, confidence, last-spin date and author as real columns. Sort by confidence ascending to find the weakest rewrites first, filter to one source URL for an audit, or scope to drafts only.
Inline edits run through standard WordPress CRUD, so post-save hooks still fire and any third-party listener stays consistent. The connector log, where present, is read-mostly: SleekView treats it as a queryable list rather than a static spin counter.
Workflow
How SleekView reads Spin Rewriter data
Pick the source
post. SleekView lists every standard wp_posts column plus the Spin Rewriter meta keys it finds.
Compose the column set
Save and scope the view
Edit inline or export
Sample columns
A typical Spin Rewriter posts table
wp_posts with the Spin Rewriter postmeta and any connector log it finds, so source URL and confidence sit as real columns.
wp_posts + wp_postmeta (_spinrewriter_source_url, _spinrewriter_run_id) + wp_options or wp_spinrewriter_runs
| Title | Status | Source URL | Confidence | Author | Last spin |
|---|---|---|---|---|---|
| Espresso machine roundup | Published | wirecutter.com/coffee | High | alex@studio.co | May 12 |
| Walking pad guide | Draft | consumerreports.org/fitness | Medium | ria@design.io | May 11 |
| Indoor herbs starter | Pending | gardenista.com/herbs | High | tom@hello.dev | May 10 |
| Cold brew at home | Trash | seriouseats.com/coffee | Low | mia@brew.coop | May 8 |
Comparison
Default Spin Rewriter admin vs SleekView
Default Spin Rewriter connector
- Connector UI focuses on the single-post rewrite flow, not an audit list
-
_spinrewriter_run_idand source URL are invisible on the Posts screen - No filter by confidence band across the WordPress archive
- No saved per-role view for editorial, SEO and governance
- Bulk-editing status across spun posts requires per-row clicks
SleekView
-
Read directly from
wp_postsjoined with the Spin Rewriter postmeta - Source URL, confidence band and last-spin timestamp as sortable columns
- Inline-edit status across many spun posts in one pass
- Save filtered views per role ("Low-confidence spins", "Source-URL audit")
- Export the filtered set to CSV without a custom report
Features
What SleekView gives you for Spin Rewriter for WordPress
Spin meta as real columns
Surface _spinrewriter_source_url and the connector's confidence value next to title and status. Triage moves from buried meta to a column set.
Inline edits through CRUD
Bulk-flip status, switch authors or correct categories in the row. Edits go through wp_update_post so post-save triggers still fire.
Compose precise filters
Combine status, confidence band and source URL into a saved filter. A monthly spin audit becomes a single named view, not a daily rebuild.
Audience
Who uses SleekView for Spin Rewriter
SEO leads
Sort posts by confidence ascending to find the weakest rewrites and prioritise them for a human rewrite sprint.
Editorial leads
Watch source URL and confidence next to status so low-confidence spins never quietly ship without a review pass.
Governance
Filter to spun posts only for a disclosure audit, then export the filtered set as evidence for a content review.
The bigger picture
Why Spin Rewriter output needs a row-level audit table
Spin Rewriter is a fast way to produce variant content, which means volume grows quickly and quality varies across the run. The default Posts screen turns that volume into a wall of titles with no way to see source URL or confidence. SleekView reads the same wp_posts rows and the same connector meta and renders them as a queryable list with source URL, confidence and last-spin timestamp as real columns.
SEO leads surface the weakest rewrites first. Editorial catches low-confidence spins before they ship. Governance produces a disclosure audit without a custom query.
Same posts, same plugin, very different operating posture.
Questions
Common questions about SleekView for Spin Rewriter for WordPress
Standard wp_posts rows for spun posts, the Spin Rewriter postmeta keys (commonly _spinrewriter_source_url and _spinrewriter_run_id) and any connector log the installed version writes to wp_options or a dedicated table.
No. SleekView never calls Spin Rewriter or any model vendor. It reads what the connector has already written to your WordPress database when a rewrite completed.
Yes, where the connector writes a confidence value to wp_postmeta. SleekView exposes it as a sortable, filterable column so the weakest rewrites surface first.
Yes. The connector typically stamps the source URL on each rewritten post. Add a filter for that meta key and the table narrows to posts spun from that URL, useful for cannibalisation and origin audits.
Yes. Select rows, pick a new status and SleekView writes through wp_update_post, so post-status hooks and any listening plugins still fire as expected.
No, that is the honest behaviour. If the connector did not write its meta keys for a post, the table cannot tell it apart from any other post. The view shows only what is actually in the database.
Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for an SEO consultant briefing or for archiving a snapshot before a content cleanup.
Yes. The connector can be pointed at any writeable post type, and SleekView mirrors that. Build separate tables for posts, products and case studies, or one combined table scoped by post type.
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 checkoutBrowse more
- Gooten Print On Demand
- Checkoutwc
- Stripe For Woocommerce
- Woocommerce Quick View
- Woocommerce Pdf Invoice Pro
- Woocommerce Product Question
- Yith Subscriptions
- Wholesale Suite
- Gumroad Wp
- Cartflows
- Woocommerce Wholesale Prices
- Woocommerce Follow Up Emails
- Customer Reviews For Woocommerce
- Product Vendors Marketplace
- Woocommerce Quaderno