From "connect your blog" to "published" — the whole pipeline, and exactly where you stay in control.
Most content tools do one step of this and leave you the rest. Draftcamp runs the entire maintenance loop — finding what needs fixing, diagnosing why, drafting the fix, and publishing it — with one hard rule threaded through all of it: nothing changes on your site without a person approving it. Here's the whole thing, step by step.
The pipeline, end to end
Draftcamp handles
GSC (read-only), a crawl of your library, and your ICP + brand profile — all yours.
Continuous, across four dimensions: performance, ICP fit, brand, and technical.
Every flagged article: touch-up, rewrite, or retire — each with the reasoning.
Your team decides
Researched from your page’s own data. You edit and approve it first.
A full rewrite in your voice, quality-checked. You edit and approve it.
Approval gate
A named person signs off. No auto-publish — this is the spine of the product.
Draftcamp handles
To Ghost or WordPress — same URL, rankings equity kept, every publish logged.
And it keeps running. After a refresh pass the audit stays on — catching the next articles as they slip, keeping your queue current. Back to Audit, on its own.
Draftcamp works from three things that are already yours: your Google Search Console performance data (connected read-only — it reads, it never writes), a crawl of your existing article library, and a definition of who you sell to and how you sound. You confirm your ICP during setup, and the system builds a first draft of your brand profile — tone, style, audience, intent — by analysing your published articles and any style guide you upload. You review and correct both before they're used to judge anything. Everything downstream is measured against the company you are now, defined by you — not a generic best-practice checklist. See the data it uses →
The audit is the engine. It checks every article in your library against four things at once — and only the first is something your existing tools already watch:
The audit runs continuously, triggered by data signals rather than by someone remembering to run it. When something changes that matters, it surfaces — you don't have to go looking. Go deep on the audit →
Performance
Position and click trends per page, drawn from your GSC history, with drop detection and page-boundary alerts. Not a snapshot; a trajectory.
ICP alignment
Whether the article still speaks to the buyer you sell to today, checked against your confirmed ICP. This is the one that catches articles still ranking but quietly wrong.
Brand standards
Whether it still sounds like you and makes your current case, measured against your brand profile.
Technical SEO
Titles, metas, heading structure, internal links, schema — judged per article, in the context of what that page actually ranks for.
The audit doesn't just flag; it classifies. Every article that needs attention is sorted into one of three verdicts — touch-up, full rewrite, or retire — each with the reasoning attached, and the queue is prioritised by opportunity rather than by age or alphabet. You can agree, dismiss, or reclassify any of it. The system recommends; you decide. Nothing is ever rewritten or removed automatically.
For each article you choose to move forward, Draftcamp researches and writes a specific brief: what changed, what's missing, what needs updating, the queries the page ranks for and is losing, the keyword and AI-visibility opportunities, and the technical fixes — all grounded in that page's own performance, not scraped from competitors' pages.
This is the first place you're in the loop, by design. The brief is fully editable. Cut sections, change the angle, add the context the data can't know. The draft is generated only after you approve your version of the brief — so the rewrite is built to your intent, not the system's guess. Go deep on briefs →
Once the brief is approved, the system writes a complete updated draft against it — in the brand voice learned from your library and style guide, keeping the article's existing URL so its accumulated authority carries. Before that draft ever reaches your queue, it passes content-quality and technical-SEO review; those findings surface as suggestions alongside the text, visible for your judgement rather than silently applied.
The draft lands in an editor made for reviewing, not just reading. Edit anywhere directly. Select any passage and describe what's wrong — the system proposes a revision for just that block, which you accept or reject, leaving the rest untouched. Every accepted change is snapshotted, so you can compare versions and restore any earlier point. Your changes are always the source of truth. Go deep on rewrites →
This is the line the whole product is built around. The system handles everything up to the moment of human judgement — the audit, the research, the brief, the draft, the checks — and then it stops. A named person on your team approves each piece before it can be published, and the approval is logged. There is no auto-publish setting, no "trust the AI" mode, no way to route around the human. Every content manager we talked to said the same thing unprompted: they will not publish unreviewed work. Neither will Draftcamp on their behalf.
Once you've approved a draft, Draftcamp publishes it directly to Ghost or WordPress — headings, structure, links, and metadata carried over exactly as approved. Refreshed articles update the existing post rather than creating a new one, so the URL and its rankings equity stay put, with a check against the CMS's current version so a simultaneous edit is never silently overwritten. Every publish is logged: what shipped, where, and when. And if you'd rather keep publishing in your own hands, the approved draft is yours to take wherever your workflow needs it. Go deep on publishing →
Content decay isn't a one-time event, so the audit isn't a one-time job. After you've refreshed a set of articles, the system keeps watching — catching the next articles as they slip, and keeping your queue current. The maintenance that used to depend on someone remembering now runs whether or not anyone made it a priority. That's the whole point: not a better refresh sprint, but a process that doesn't stop.
To be exact about the division of labour, because it's the thing that makes the rest trustworthy
The fastest way to understand the pipeline is to watch it work on your real content. Book a 30-minute demo — connect your GSC and we'll run a live audit, walk through a brief and a draft, and show you the approval flow end to end.
