A content engine that publishes every week without you
Topics planned against real search demand, drafted in your voice, reviewed by a human, published on schedule. Every week, including the busy ones.
The problem
How it works by hand
Most small businesses do content the same way: someone pastes a prompt into ChatGPT when they remember, publishes three posts in a fortnight, then goes quiet for two months. Search engines and buyers both notice the gaps. The work that would compound never gets the chance to, because consistency depends on the one person who is always busy.
A worked example
What a working version looks like
The engine starts with a topic plan built from real search data, the questions your buyers type, not the ones you assume they type. Each topic gets drafted by a model trained on examples of your actual writing, so the output sounds like you rather than like everyone else using the same tool. Drafts land in a review queue where a human reads, edits and approves; nothing ships without that step. Approved pieces publish on a fixed schedule through your CMS, with internal links, metadata and the sitemap handled automatically. The plan refills itself as topics get used up.
The exact tools change per business. The shape does not.
What it needs
Honest inputs, nothing exotic
- 01A website with a CMS we can publish to (or we rebuild it so there is one)
- 02Examples of your writing, so the voice profile is yours and not generic
- 03Google Search Console access (free, and enough search data to start)
- 04One person willing to review drafts roughly an hour a week
The payoff
What you get back
Content goes out every week whether you had a good week or a chaotic one. The library compounds instead of stalling, and the only human time spent is the review, which is the part humans are actually good at.
Do it yourself
How you would build this yourself
No course, no upsell. This is the order we would build it in, with the tools named, and a prompt to start from.
- 1
Open Google Search Console and export your queries report. The questions people already type are your topic plan; do not brainstorm topics from a blank page.
- 2
Paste five pieces of your own writing into a Claude project and ask it to describe your voice. Save that description; it becomes the style instruction for every draft.
- 3
Draft one article at a time, with the voice profile plus a real query as the brief. Batch-drafting twenty in one go feels productive and produces twenty versions of the same article.
- 4
Read every draft before it ships. The honest version of this system has a human in it; cut the review and your blog turns into slop within a month.
- 5
Publish through your CMS (WordPress, Webflow, whatever you have) on a fixed day each week. Consistency beats volume.
- 6
The fiddly bit is internal links, metadata and the sitemap. Script it against your CMS API with Claude Code rather than doing it by hand every week.
I want a weekly content pipeline for my business website. My CMS is [WordPress/Webflow/other] and Google Search Console is set up. Help me: 1) turn my GSC query export into a 12-topic plan based on what people actually search, 2) build a voice profile from the three writing samples I will paste in, 3) set up a workflow where each article is drafted from a real query, I review it, and a script publishes it with metadata and internal links handled. Start by asking me for the GSC export and the writing samples.
Copy it into Claude Code, fill the brackets, and it will plan the build with you before writing a line of code.
We would rather show you how than bill you. The whole ladder of free help, answers, guides and the weekly build-along, is on the do-it-yourself page.