Skip to content
Start a free audit

Content automation

Written overnight, verified at the URL

Plan a month of posts. Auto-write drafts each at midnight on its calendar date through the same researched pipeline you run by hand, and every publish is checked at the public URL.

Plan your calendarTry free: CMS detector

Autoblogging earned its reputation: thin posts on a timer, dumped into a CMS, with nobody checking whether anything went live.

The cadence is worth keeping. The blindness is not.

  • 9publishing platforms, plus a signed webhook for anything else
  • 36checks each overnight draft is revised against
  • 5verification fetches per publish, five minutes apart
  • 1credit per article, clicked or written overnight

The queue writes the next due item

Your calendar holds the planned items. At midnight on its date, Auto-write claims the item and advances it through a job queue, so closing the tab changes nothing.

Help centre: Content calendar
The content calendar as a month grid, with the Auto-write switch sitting off above it and the calendar, list and board views beside it.
The switch decides whether it drafts overnight, and until it is on, every card sits where it was planned and nothing generates.

  • A researched article, not a scheduled prompt

    Each item gets research, a draft written with the business context from setup, internal links, images and structured data, all on a background worker. A researched article does not fit in one request.

  • Revised against the same 36 checks

    Drafts are revised against the 36-check, six-category content score used everywhere else in the product. The engine is deterministic, so the number means the same as it does on an audited page.

  • Published means the public URL answered

    After each publish, the verifier fetches the public URL and records what came back. A CMS reporting saved while the page 404s never reaches Published.

  • A fresh 404 waits instead of failing

    Hosts deploy asynchronously, so a fresh 404 stays at Checking through a grace window. A server error never concludes the page is missing, and a git-hosted publish is never URL-verified.

  • Failed jobs reopen the card and email you

    A failed job marks the card Write failed with the reason, returns the item to To Do and sends an email. Pressing Write twice never queues a second paid generation.

How it works

The sequence, start to finish. Read it in order: each step assumes the one above it has already run.

  1. Load the calendar

    Add items with a target keyword and a publish date, a month at a time.

  2. Let the nights run

    The auto-writer queues the next due item and advances it one step every couple of minutes, revising against the content score.

  3. Publish, then verify

    Review the morning's drafts, publish through your connected platform, and the verifier fetches the public URL before the record reads Published.

The same queue for searchblueprint.io as a list: one row per date, carrying the type of page it produces, the title it will be written under and the keyword it targets.
The queue is the schedule. Every row states the day it is due, the kind of page it produces, the title it will be written under and the search it is written to win.

The other ways people do this

What each approach does, and what happens here instead. Mechanism only, never an outcome claim.

A scheduled-post pluginHow it worksIt publishes text you already wrote at a time you picked. Nothing writes it and nothing checks it afterwards.HereThe queue writes the next due item through the researched pipeline, then fetches the public URL before the record reads Published.
An RSS-to-blog autoposterHow it worksIt republishes someone else's feed under your domain, unedited, unscored and about their subject.HereEach item is written for your keyword with your business context, links drawn from your own crawl, and a score you can read.
A writer on a monthly quotaHow it worksDrafts arrive by email on the writer's schedule, and whoever has time reviews them.HereItems draft overnight from the calendar and wait as drafts. A failed job returns the card to To Do with the reason and emails you.
Pasting drafts in by handHow it worksYou paste into the CMS, see a success message, and take it as evidence the page is live.HereA platform reporting saved is recorded as Sent. Only a public URL that was fetched and found becomes Published.

Try the job, or learn the subject

The tool below runs here, on this page, without an account. The rest of the free tools and the lessons sit under it.

CMS detector

Detect the CMS and tech behind a site. It runs here, on this page, with no account.

CMS detector on its own page

More free tools, no signup

Content idea generator
Get content ideas around a topic.
AI content writer
Draft SEO content from a topic or keyword.

Lessons in the Academy

Days 31 to 60: the content engine5 min · Intermediate
Publish on a cadence, one cluster at a time, with every page mapped to a keyword and an intent.
Topic clusters: own a subject, not a keyword5 min · Intermediate
Group pages around one subject so Google and AI treat you as the authority on it.
Refreshing content that slipped5 min · Intermediate
Find pages that lost rankings, work out why, and bring them back without rewriting from scratch.

Questions people ask

The ones that decide whether this fits, answered with the verdict first.

Is the overnight article a cheaper draft?
No. Click-to-write and auto-write run the same researched pipeline, and the finished article lands with your per-website settings applied either way.
What does Published actually mean here?
That the public URL was fetched and the page was found. A CMS accepting the write is a different event, because a platform can report saved while the page 404s.
What happens when a publish 404s?
It waits. Hosts deploy asynchronously, so a fresh 404 stays at Checking through a grace window and re-verifies on its own.
What if a job fails overnight?
The card returns to To Do reading Write failed with the reason, and an email goes out, so an overnight failure is never a silent one.
What does a month of posts cost in credits?
One credit per article, whichever way it was written. Twenty posts is twenty credits, and a job that fails before finishing gives its credit back.
Which platforms can it publish to?
Nine, plus a signed webhook. WordPress directly or through the official plugin, Shopify, BigCommerce, Webflow, Wix, Ghost, GoHighLevel, Snapps, and GitHub for git-built sites.
Does it need access to my server?
No. Publishing goes through your platform's own connector with credentials you issue, and verification afterwards only fetches the public URL the way a visitor would.
What happens when a publish cannot be verified?
It is recorded as delivered but unverified, never as Published. Verification retries every five minutes up to five times, and a 401 or 403 counts as verified because access control is yours.

Where this fits

The jobs either side of this one, and the two pages that read it from your side of the desk.

  • AI article writer

    Give it a keyword. It researches, drafts with internal links and images, then scores the result on the same 36 checks that grade audited pages.

  • Integrations

    Connect WordPress, Shopify, BigCommerce, Webflow, Wix, Ghost, GoHighLevel, Snapps or a git repository. Every publish is verified by fetching the public URL.

  • AI SEO agent

    Paste a URL and it reads your business, researches keywords, grades the site, writes score-gated articles and tracks rankings. You approve the decisions that shape everything downstream.

Content automation

See it on your own site

A free audit grades your site A+ to F, then shows where this feature pays first. No card required.

Plan your calendarCompare the alternatives