Home / Features
Every part of the line, in detail
AutoBlogForge is one pipeline with twelve stations. This page walks through what each one does, what you control, and where a human still has to make the call.
Set up once
Connect a site, upload a few sample posts for the voice profile, and choose a cadence. Most workspaces are running inside an hour.
Run in batches
Feed the line a keyword list whenever your research is done. Batches run unattended and land in the queue.
Keep the gate
Review what matters, automate what does not. The gate is a per-format setting, not an all-or-nothing switch.
The twelve stations
Listed in the order a topic travels through them.
Bulk topic intake
Paste up to 500 keywords, upload a CSV from Ahrefs, Semrush or a spreadsheet, or add topics one at a time. Each row carries its own target keyword, format, word count and publishing date, so a batch can mix a buying guide with three product descriptions.
Brand voice profiles
Upload three to five existing posts and the profile captures vocabulary, sentence length, formatting habits and the things you never say. Agencies keep one profile per client; publishers keep one per site.
Outline approval
Every draft starts as an outline you can approve, edit or reject in bulk. Lock a heading structure for a format and every future article in that pipeline follows it.
Long-form drafting
Drafts run from 400 to 4,000 words with consistent section depth, a working introduction and a closing section that carries your call to action rather than a generic sign-off.
Automatic SEO checks
Title length, meta description, single H1, heading depth, keyword placement, keyword density range, image alt text, readability grade and internal link count. Failures are listed with the specific fix.
Internal link planner
Point the planner at your sitemap once. It maps your existing pages, then proposes links in both directions for every new draft so clusters build themselves instead of being retrofitted.
Image placeholders and alt text
Each draft ships with figure placeholders, suggested alt text and a caption, so the editor is not writing accessibility copy at the last minute.
Publishing calendar
Set a cadence per site — three a week, one a day, weekdays only — and the queue drains at that rate. Holidays and blackout dates are respected.
CMS delivery
WordPress and Ghost through their official APIs, Webflow through the CMS API, and a signed webhook for everything else. Category, tags, author and featured image are mapped per pipeline.
Review gates and roles
Editors approve, writers draft, viewers read. Turn the gate off per format once you trust the output, and keep it on for anything commercial or regulated.
Reports and exports
Monthly output, word counts, publish rate and per-client summaries. Export any draft as Markdown, HTML or plain text at any point.
API and webhooks
Create jobs, read drafts and receive status callbacks from your own systems on the Agency plan. Rate limits and payload shapes are documented in the app.
What AutoBlogForge does not do
Software that claims no limits is selling something. These are the places where you still need a person.
It does not check facts
Drafts should be verified before publication, particularly anything with prices, statistics, medical or legal content. The review gate exists for this reason.
It does not do keyword research
You bring the keywords, or import them from your research tool. The pipeline turns a list into published pages; it does not decide what is worth ranking for.
It does not promise rankings
Nobody can. Well-structured content published consistently gives you a better chance, and that is what a pipeline provides.
Where drafts go
Do not see your platform? A signed webhook delivers the draft as JSON or Markdown and you handle the last step.
See it run on your own topics
The browser generator forges a full draft from your brief with nothing to install. It uses the same structure as the live pipeline.