Every site on its own terms
Brief, audience, locale, keyword seeds, scoring thresholds, publishing schedule, image style and monthly budget are configured per site, versioned, and never shared by accident.
SEO articles, planned and published
Plan, write and publish SEO articles on every site you run.
Blogotter fills the editorial calendar a week ahead, checks each keyword against the pages you already rank for, writes the article the day before it is due, runs QA, publishes it, then verifies the live page and follows it in Search Console.
Seven days, 1 site, 3 complete articles. No card — verify your email and the workspace is created.
MonMigrating a phone systemPublished
TueWhat causes call jitterReady
WedChoosing a SIP trunk
ThuSoftphone vs desk phoneReview
FriNumber porting, end to endPlanned
Next article is generated 24 hours before it is due.
How it works
Six steps between a keyword and a published page.
Each one is a durable job. If a step fails it retries; if a worker dies mid-step another one picks the work back up.
Plan the week
The planner keeps seven days of calendar filled ahead of time. Candidate keywords are scored on search volume, difficulty, CPC, competition, intent and monthly, quarterly and yearly trend, against the brief, audience, locale and seeds you set per site.
Check it against what you already rank for
Before a keyword can take a slot it is compared with the titles of your live pages and with your Search Console queries. Past the warning threshold it lands in the topic cluster map; past the blocking threshold it cannot be scheduled until you decide whether to refresh the existing page or keep a new one. Both thresholds are per site.
Research 24 hours before it is due
The worker searches the SERP live, fetches the candidate sources, and checks each one is reachable and relevant. It will not write the article until at least two survive that check. No curated URL lists, no domain allowlists.
Write the draft, with images and links
The article is generated with internal links taken from your own published catalogue and images in the style configured for that site — felt stop-motion, claymotion, or a prompt you write yourself. Sources, verification and scores stay attached to the draft.
Run QA, then edit what you want
A QA pass runs over the draft, and the slot only becomes publishable once it passes. In the editor you can regenerate a single H2, or approve a proposed outline reorder. Every applied change creates an immutable version you can compare from the history.
Publish, verify, measure
At the scheduled time only the latest version that passed QA goes out. The platform then fetches the published page back and confirms it, and Search Console performance for it flows into the dashboard from the next sync onward.
What you get
Built for someone who runs more than one site.
Every site keeps its own brief, schedule, thresholds and budget, and the work of all of them lands in one calendar and one operations view.
A calendar you can actually steer
Weekly templates, several publishing times a day, blackout and holiday ranges, scoped quotas and manual slots that automation is not allowed to touch — with a 30-day capacity preview before you commit.
Section-level editing with real history
Select a heading and regenerate only its content. An outline proposal can reorder or rename existing H2s and nothing else, and needs your approval. If the draft moves while the model works, the result is marked stale instead of applied.
Sources you can audit
Each draft carries where its sources came from, whether they were reachable and relevant, and how they scored. Manual overrides exist, but they are recorded as the editorial exception they are.
An operations centre, not a log file
Queue depth, current delays, late starts, automatic recoveries in the last 24 hours and the failures that need a human — per site, with a single manual retry for jobs still worth retrying.
Provider spend, per site, per month
Every paid provider call is recorded against the site and job that made it, measured against the monthly budget you set, with an alert before the budget is gone.
Search Console, wired in
Activation backfills 90 days, then a daily sync refreshes the last seven consolidated days. The dashboard shows clicks, a 28-day comparison and refresh suggestions. It is an optional dependency: if it fails, the last good data stays and publishing carries on.
Publishes to WordPress, or to your own API
A WordPress connector using application passwords, a generic connector for any site that implements the documented list-and-publish contract, and export. Writes are idempotent by slug, so a retry never gives you the same article twice.
Access control that survives an audit
Owner, editor and viewer memberships resolved per site on every request, server-side revocable sessions, TOTP on privileged accounts, and an audit trail behind the decisions that changed something.
Plans
What each plan includes.
Article allowances, site limits and seats are enforced by the application itself. These are the numbers it enforces, not a summary of them.
Trial
Free for seven days
Seven days on one site, from an empty calendar to a published article.
- 3 articles in total
- 1 site
- 1 team member
- 3 section rewrites per article
- 2 image regenerations per article
- Keyword planning with live search data
- Cannibalisation review before anything is scheduled
- Full drafts with images, sources and QA
Starter
€29 / month
A steady publishing cadence on the site that matters most.
- 10 articles a month
- 1 site
- 2 team members
- 3 section rewrites per article
- 2 image regenerations per article
- Editorial calendar with versioned drafts
- Automatic publishing and post-publication verification
- Search Console performance and refresh suggestions
Growth
Most complete€79 / month
A portfolio of sites, each with its own brief, schedule and budget.
- 30 articles a month
- 3 sites
- 5 team members
- 3 section rewrites per article
- 2 image regenerations per article
- Everything in Starter, on every site
- Portfolio dashboard and shared operations centre
- Per-site monthly budget with cost alerts
Prices exclude VAT. The allowances above come straight from the plan catalogue the application enforces, so what a plan includes here is exactly what a workspace on it gets.
Questions
The things worth knowing before a site is connected.
Will it publish to my site before I have seen anything?
No. A new connection starts in dry run: the platform builds and validates the whole payload but does not call your publish endpoint. You run at least one full cycle that way, check the content, sources, images and payload, then turn dry run off and publish a single article by hand as a canary before leaving the daily automation on.
Do I need Google Search Console?
It is optional. Connecting it sharpens the cannibalisation analysis and gives you performance data and refresh suggestions. Without it the comparison against your live page titles still runs. A Search Console outage never blocks generation or publishing — the last valid data is kept and the pipeline continues.
What stops it writing the same article twice?
Every candidate keyword is scored against your existing pages before it is scheduled. Matches are grouped into one review per keyword, where you either point the keyword at the page you already have or explicitly keep a new one. Decisions are kept and can be reopened, and the automatic pool only counts keywords that are actually usable.
What happens when something fails at three in the morning?
Jobs are idempotent and retried with exponential backoff; a worker that dies mid-job leaves a lease that another worker recovers. Lanes are separate processes, so a slow generation cannot delay a publication that is due. Anything that ends up genuinely failed shows up in the operations centre and can send you a Telegram alert.
What is in the trial?
Seven days, 1 site, 3 complete articles, no card. You verify your email and the workspace is created with the trial credits already on it.
Start with one site and see a week of it.
Connect a site, let the planner fill the calendar, and read the drafts before anything goes anywhere near your publish endpoint.
Start a free trial3 articles · 1 site · no card