Plan and publish with the content autopilot
Set up voice and schedule once, let LopeBase draft, check, and publish articles, and review what is waiting on the calendar.
Content writes articles for a property on a schedule, in its own voice, and checks each one before it goes out. You stay in control: nothing publishes until you approve it, unless you turn autopilot on.
No property set up yet? Open Content and pick a property to see both setup paths.
Set up a property
Open GrowContent, pick the property, and choose where its articles go first: hosted by LopeBase, an EmDash blog, a webhook to your own endpoint, a GitHub pull request, a CMS (WordPress, Ghost, Webflow, Shopify, Contentful, Sanity, Strapi, or Hashnode), or copy and paste. Then pick how to finish setup:
-
Set it all up with AI (recommended)
Reads the site and its existing posts, fills in the voice, audience, and house rules, picks keywords and topics, sets a schedule that matches the blog's pace, and writes a first article, fixing it against the checks until it passes. You end on a summary with that article ready to review.
-
Set it up yourself
Go through Voice, Topics, and Schedule one step at a time. Each step can still fill itself in with AI (for example, "Fill in from yoursite.com" on Voice) if you want the help without the full run.
Voice, rules, and checks
Voice has five tabs, all saved together:
| Tab | Covers |
|---|---|
| Voice | Who it is for, its tone, and one plain sentence on what the product does. |
| Rules | House rules, one per line, every draft follows them; topics to never write about; an optional no em or en dash rule. |
| Each article | Word count range, whether it ends with an FAQ, whether it links to your own posts, cites other sites, or suggests a YouTube video, and anything else the writer should know. |
| Images | Style (none, photo, illustration, diagram, or screenshot), how many per article, and shape. Images never carry text or logos and use AI credits unless you supply your own key. |
| Checks | Whether an editor check runs before publishing, and how many rounds of automatic fixing a failing draft gets. |
Every article, with or without the editor check, is checked for: length inside your range, a title 20 to 70 characters, a meta description 70 to 160 characters, a clean URL slug that is not already published, at least 4 sections, no top-level heading in the body, clean Markdown with no broken links or unclosed code fences, no filler phrasing, a source link on every statistic, and nothing from your avoid list. Turning on the editor check adds whether it sounds like the site, reads like a person wrote it, makes no invented claims, and answers the search it targets, using a few AI credits. A draft that fails a check is fixed automatically up to the rounds you set, then goes to review either way if it still fails.
Schedule and review mode
Set how many articles a week and on which days, the hour and time zone to publish, and how many days ahead to write the draft so there is time to review it. Pick one of two modes:
- You review each one. Drafts wait on the Content page; nothing goes out until you approve it.
- Autopilot. Articles that pass every check publish on their own. Anything that fails waits for you.
Turn on email alerts for a draft ready for review, an article published, or something that failed, sent to every admin by default or to addresses you choose.
The calendar
Each property's calendar shows the month with its scheduled slots, drafted articles, and open slots still needing a topic. Open Content, pick the property, then Calendar.
- An open slot can be planned with a topic idea, written right away with Write now, or left for its scheduled day.
- A scheduled or drafted article can move to another open slot, or be cleared to publish as soon as it is approved instead of on a fixed date.
Review and publish
Articles waiting on you show under Needs your review on the Content page, with how many of their checks pass. Open one to read it, see each check, and approve, reject, or ask for a rewrite. An approved article publishes to the destination you set up: a hosted LopeBase blog with its own RSS, JSON feed, and sitemap; an EmDash blog post, with an IndexNow ping to tell search engines right away; a signed webhook call to your own endpoint; a GitHub pull request; or your CMS of choice. A published article's clicks, impressions, and position from Search Console show on the Content page once it has been live a few days, and you can read every post across your sites on Posts on your sites.
The library
Posts on your sites (under Content) lists what is on the blog for every connected content destination, whatever its status: draft, in review, scheduled, or published, with word count, reading time, and author where the connector reports them.
Where to go next
- Use the SEO toolkit turns a search opportunity straight into a topic here.
- Connect the LopeBase Adapter if you chose the webhook destination and need the receiving endpoint.
- Automate multi-step work covers running content tasks as part of a larger pipeline.
If something goes wrong
Something else? Contact us.
Why is my draft stuck in review when autopilot is on?
Autopilot only publishes an article once every check passes. If one still fails after the fixing rounds you allowed, it waits for you instead, so nothing broken goes out on its own.
Why can't I turn on "Set it all up with AI"?
AI setup reads the property's site, so it needs the site's address added on the property's page first. Add it there, then come back to Content.
Why does writing an article need an AI key or credits?
Drafting, the editor check, and images all use AI. Connect your own OpenAI key or a Cloudflare AI Gateway to use that, or spend LopeBase AI credits; either way, the credit estimate shows before you write.
Why did my article fail the "statistic needs a source" check?
Any percentage, multiplier (like "3x"), or "N times more/less" phrase needs a link to its source in the same paragraph. Add the link, or remove the figure if you cannot source it.
Why didn't my article publish to EmDash or my CMS?
Use Test connection on the destination step after saving its settings. A common cause is a credential that changed on the other end, like an expired CMS token or a GitHub app no longer installed on that repository.
Can I write about a specific topic right now instead of waiting for the schedule?
Yes. Use Write now on the Content page or from an open slot on the calendar, with or without a topic in mind.