Grow
Autoblogging you would put your name to.
Autoblogging has a bad name because most of it is spam. This is the other kind: posts written against a keyword plan, published to your own site, checked, indexed and rewritten when they stop earning.
The content log
Every post the agents published, its target keyword, and how it is performing in Search Console.
What autoblogging is
Autoblogging is software that writes and publishes blog posts without a person doing each step. Done badly, it floods a site with thin pages that search engines learn to ignore.
Done well, it is a writer that never misses a week, follows a plan, links posts together properly and goes back to fix the ones that are not working.
How the agents do it. Step by step, on a schedule.
Pick the next post from the plan
The publisher reads your keyword plan and chooses the next topic, respecting a weekly budget so quality does not slip.
Read before writing
It reads existing posts on your site first, so the new one matches your format, tone and components.
Write, check, commit
The draft is checked for AI tells, its frontmatter is validated, and it is committed and pushed to your repository.
Confirm it is live and log it
A chained job waits for the deploy, requests the page, and only then records it in the content log.
Measure and refresh
Search Console numbers are written back weekly. Posts that stop earning are refreshed or pruned.
What you get. Small things that add up.
Your format, your repo
Markdown or MDX in the directory your site already uses, deployed by your own pipeline.
Checked for AI tells
Posts are checked for the phrasing that makes writing read as machine-made before they ship.
Internal links both ways
Pillar and cluster posts link to each other as each is published.
A content log
Every post, its keyword, its URL and how it is performing, in one table.
Refresh, not just publish
A lifecycle agent revisits posts that decay and rewrites or retires them.
Weekly budget
You set how many posts a week. The plan decides which ones.
What it will not do. On purpose.
- It will not invent statistics, studies or customer quotes to pad a post.
- It does not publish to a platform you do not own. Posts live in your repository.
- A post is only logged once the live page returns successfully.
Questions
Will Google penalise AI-written posts?
Google’s guidance is about helpfulness, not authorship. The risk is thin, repetitive content, which is exactly what the plan, the budget and the refresh cycle are there to avoid.
Which site frameworks does it work with?
Any site whose posts live as files in a Git repository, such as Next.js, Astro, Hugo or Jekyll. It reads your existing posts to learn the format.
How many posts a week?
You choose. Most products start with one or two a week and raise it once the posts are earning.
Can I review each post first?
Yes. Have the publisher open a pull request, and merge when you are happy.
Keep reading
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.