Recover the trafficyour posts quietly lost.
Four Claude Skills read your published library, score which posts are worth refreshing, draft the refresh in your voice, and assemble a publish-ready package you can ship in one review. It draws the line between the posts worth refreshing and the ones that need rebuilding — and won't fast-track inaccurate or worthless content to republish, however well it ranks. It reads, drafts, and stages a draft; you publish.
Your best posts are decaying — and refreshing all of them is a trap.
Posts that ranked two years ago slide down the results every month as competitors update and yours sits untouched. Decay is the default — nobody publishes once and keeps the traffic.
Some posts are worth refreshing, some need a full rewrite, and some should be pruned. Refresh them all and you pour hours into content that was never going to recover.
Which of your hundreds of posts deserves the next refresh? Without a score it's gut feel — and the highest-traffic fast win sits buried while you tinker with a post nobody reads.
Score a post — and see why a top ranker still can't republish.
This is the scoring core, live. Tune the post at the top and watch its verdict, your priority-refresh traffic, and the REFRESH-READY/CONTENT DEBT call move with it. The publish gate is the honest part: a post full of now-wrong stats is REWRITE OR RETIRE — raise its accuracy and watch it flip to REFRESH NOW.
Content audit · live demo
Tune the post at the top. It ranks well — but raise its accuracy to see why it can’t republish yet.
Priority refresh traffic
4,200/mo
of 12,300/mo audited
Library: CONTENT DEBT
5,000/mo locked in rewrites (41% of traffic)
Refresh this first: 2023 Pricing Guide (4,200/mo, REFRESH NOW) — the biggest fast traffic win you can ship.
SEO Statistics 2021 · 3,500/mo
REWRITE OR RETIRE · score 80
The publish gate is the point: a post that’s inaccurate, unsalvageable, or worthless is REWRITE OR RETIRE however well it ranks — it can’t be fast-tracked to republish. Same math as the engine and workbook. It reads, drafts, and stages a draft — you publish.
One audit, four Skills, from decaying to published.
The scout reads your published posts via your WordPress MCP and scores each, returning REFRESH NOW / WORTH A REFRESH / LOW PRIORITY / REWRITE OR RETIRE, the priority-refresh traffic you can recover, the REFRESH-READY or CONTENT DEBT roll-up, and the post to refresh first.
The drafter rewrites the flagged posts in your voice, grounded in the original — updated facts (each flagged to source), a sharper intro and sections, a new title and meta, internal links — with the URL preserved. It never invents a statistic.
The architect assembles the publish-ready package — the refreshed draft, a change summary, SEO metadata, a redirect note if needed, and a pre-publish QA checklist — and can stage it as an unshared draft in your own site.
Between sprints the tracker re-scores the library and flags what newly decayed, what recovered after a refresh, and where claims have drifted out of date — so the effort compounds instead of resetting.
Plus a runnable Python scoring engine with a worked sample, a spreadsheet that reproduces the same math and publish gate, the publish-ready package template, and two playbooks — the end-to-end content-refresh workflow and a WordPress MCP setup & safe-publishing guide.
Three rules the engine holds to.
Scoring runs on your actual published posts through the MCP, and the drafter never invents a statistic — every updated fact is flagged to source. It stops rather than guessing if the connection is missing.
It reads, drafts, and may stage a refresh as an unshared draft in your own site. It never publishes, overwrites the live post, changes the live URL, or deletes. Clicking publish is yours.
A post that's inaccurate, unsalvageable, or has no business value is REWRITE OR RETIRE — it can't be fast-tracked to republish, however well it ranks. Refusing to republish junk for a ranking is the point.
An orchestration layer on top of your CMS — honest about its limits.
- A repeatable audit that scores every post and gives you the priority-refresh traffic you can actually recover.
- The orchestration layer — Skills, scoring, a template, and playbooks — on top of your WordPress site + Claude.
- Built to keep you honest: it won't fast-track inaccurate, unsalvageable, or worthless content to republish.
- Not a CMS — you bring your own WordPress site and MCP connection.
- Not an auto-publisher: it reads, drafts, and stages an unshared draft, and never publishes, overwrites the live post, or changes the live URL on its own.
- Not a guarantee of rankings, and it never invents a stat — better, accurate content earns the traffic, and you verify every updated claim.
Built for a library that used to pull traffic.
- A founder, marketer, or content team sitting on a library of posts that used to bring traffic.
- Tired of guessing which posts to refresh — and of pouring effort into content that was never going to recover.
- Willing to connect your WordPress MCP and stay the one who verifies claims and clicks publish.
- Want a bot that rewrites and publishes posts on its own, with no review.
- Won't connect a CMS, or verify updated claims before publishing.
- Are starting a blog from zero — this refreshes an existing library, it isn't an origination engine.
Distribute it, measure it, sound like you.
Refresh the cornerstone here, then atomize it into AEO-ready posts across every channel.
See how AI answer engines cite the refreshed page — and tune it to get cited more.
Codify your voice so the refreshed drafts sound like you — not generic AI.
The honest answers, before you buy.
A WordPress MCP — a WordPress.com site, or a self-hosted WordPress connected via Jetpack — that exposes reading your posts and creating drafts. Optionally Google Drive, to stage the publish-ready package or the audit as an unshared doc. You bring your own site and connect it to Claude via MCP; the engine is the orchestration layer on top — it never includes or resells your CMS. Where a signal isn't in the CMS (current rank, a traffic trend), the audit asks you for it rather than guessing.
It scores each published post on six signals — traffic decay, search opportunity, update value, business value, fix feasibility, and accuracy & safety — each weighted, summing to 100, for a 0–100 score and one verdict: REFRESH NOW (≥ 78, gates pass), WORTH A REFRESH (55–77), LOW PRIORITY (< 55), or REWRITE OR RETIRE. The honest part is the publish gate: three of those signals are publish-blockers (business value, fix feasibility, accuracy & safety), and if any is at or below 1, the post is REWRITE OR RETIRE no matter how high the score — inaccurate, unsalvageable, or worthless content can't be fast-tracked to republish, however well it ranks. In the worked example an SEO-statistics post that ranks well but is full of now-wrong 2021 figures is REWRITE OR RETIRE, not a quick refresh.
No — and that's the point of the name's boundary. It reads your content and drafts the refresh, a publish-ready package, and the plan, and it may stage a refresh as an unshared draft (status = draft) in your own site. It never publishes, never overwrites or edits the live post, never changes the live URL, and never deletes. It prepares the publish; you verify the QA checklist and click publish.
The AEO-Aware Content Repurposing System atomizes one asset into many channel posts; the Anti-Slop Content System keeps new writing from reading like AI; the AEO Citation Audit & Optimizer Kit checks how AI engines cite a page. This refreshes your existing, decaying posts in place — same URL — and grades the whole library so you know which posts to refresh, which to rewrite or retire, and which one to start with. It pairs naturally with all three: refresh the cornerstone here, repurpose it, keep it human, and measure its AI visibility.
Four Claude Skills (content-audit scout, refresh drafter, publish-prep architect, content-decay tracker), a runnable Python scoring engine with the worked sample, the same scorer as an Excel workbook, a publish-ready package template, and two playbooks — the content-refresh workflow and a WordPress MCP setup-and-safe-publishing guide. You supply the WordPress site.
No on both. It tells you which posts are worth refreshing and helps you refresh them well, but rankings depend on many factors and outcomes are never guaranteed — better, accurate content earns the traffic. And the refresh drafter never invents a statistic: every updated fact is flagged [confirm: needs a current source] for you to verify before you publish.
Stop letting good posts decay.
Bring them back to life.
One purchase, lifetime access, 12 months of updates. $129, once. Bring your own WordPress MCP.
Sold by RedHub AI LLC · Secured by Stripe · redhub.ai