Edit, then approve for its date
Change the title, description, or body in place. Saving re-runs the checks. Approving early holds it for its slot, or send it now.
A blog for every product, on a calendar you run.
Plan topics onto dates. LopeBase drafts each article days ahead in your voice, checks it, and publishes it on time to your site. Review every post first, or let it run.
Set up per product. Uses the AI credits in your plan, or your own AI key.
The whole workflow, in six steps
Set it up once per product. After that, the calendar fills itself and you step in where you want to.
- 01
Pick where articles go. Your app through a signed webhook, a GitHub pull request, an EmDash blog, or copy and paste.
- 02
Describe the voice. LopeBase drafts it from your site and imports your existing posts so it never repeats them. You edit anything that is off.
- 03
Gather topics. From Search Console, search suggestions, and your own keywords. Plan any of them onto a date.
- 04
Set the schedule. How many posts a week, which days, what hour, your time zone, and how many days ahead to draft.
- 05
Review or let it run. Drafts wait for you, or publish on their own when every check passes.
- 06
Watch the results. Clicks, impressions, and rankings come back per article from Search Console.
Calendar
See the month. Plan the month.
Every product gets a calendar of what went out, what is scheduled, and the open slots ahead.
- Slots from your schedulePosts a week, on which days, at what hour, in your time zone. One slot a day at most.
- Drafts written aheadEach article is drafted up to 14 days before its date, so there is time to read it.
- Plan a topic for a datePut a topic idea on any open slot. Otherwise the best idea is used when the draft is due.
- Write a slot nowDraft any open slot straight away instead of waiting for its day.
- Move an articleShift it to another open slot, or clear its date so it goes out as soon as it is approved.
- Nothing runs awayOne draft at a time per product, and a slot that fails twice is skipped instead of retried forever.
Voice
It writes like your site, because it read your site.
LopeBase drafts the voice from your homepage and posts. Every setting stays yours to change.
- Audience and toneWho the articles are for and how they should sound.
- House rules and off-limits topicsRules every draft follows, and subjects it never touches.
- Length and FAQA word range, and an FAQ section at the end if you want one.
- Example posts and extra instructionsYour best posts to match, and anything else in your own words.
- Internal linksLinks to your existing posts, checked to be real pages.
- ImagesUp to three per article in the style you pick: photo, illustration, diagram, or screenshot ideas, with alt text.
- A relevant videoOne real YouTube video where it helps, found for the topic and checked.
- An editor passA short AI review: does it sound like your site, and does it answer the search.
Where topics come from
Ideas are scored and checked against everything already written, so two articles never chase the same search.
- Search ConsoleSearches your site already shows up for but rarely gets clicked on.
- Search suggestionsWhat people type around your keywords.
- Your keywordsThe terms you give it, drafted from your site to start.
- Your coding agentTopics and full drafts from an agent working in your product's repo.
The checks before anything goes out
On autopilot, only a draft that passes all of them publishes. Anything else waits for you.
The basics
- Length within your range
- Title 20 to 70 characters
- Meta description 70 to 160 characters
- Clean URL slug
- Not already published
Structure
- At least 4 sections
- No top-level heading in the body
- Has an FAQ section, when asked for
- Plain Markdown, no raw HTML
Honesty and style
- No filler phrasing
- Every statistic has a source link
- Not an off-limits topic
- No em or en dashes, when asked for
Links and fit
- Every link opens
- Links to your site go to real pages
- Links to at least one of your posts
- Videos are real ones found for the topic
- Sounds like your site, and answers the search well
Review and edit
Read it first. Fix it after.
Every draft opens as an editable preview, with its checks beside it. Publishing is not the end of editing.
Edit after it is live
Fix a published article in LopeBase and the change goes to your site. Its address stays the same, so links keep working.
Where it publishes, and how edits follow
Your appA signed webhook to an endpoint in your product. LopeBase gives your coding agent the prompt that builds it, for any stack.Edits arrive as article.update
GitHubA pull request adding the article as Markdown, for blogs kept in the repo. Merging publishes it.Edits open a pull request
EmDashStraight to a blog in your own Cloudflare account, with images as image blocks.Edit in EmDash for now
Copy and pasteApproved articles wait as Markdown, ready for any CMS.Copy again
What you see afterwards
- Faster indexingWhen your app takes articles by webhook and serves an IndexNow key, search engines hear about each new post as it goes live.
- Per articleClicks, impressions, and average rank from Search Console, refreshed daily once a post has been live a couple of days.
- Per productThe calendar and a library of everything written, with its status and where it went.
- Who signed offEach article keeps who approved it, when it went out, and where it lives.
Do I have to publish what it writes?
No. In review mode every draft waits for you. You can edit it, approve it, or reject it. Autopilot mode publishes drafts that pass every check on the schedule you set; anything that fails a check waits for you.
How far ahead does it write?
As far ahead as you choose, from the same day up to 14 days. A draft written three days early gives you three days to read it before its slot.
Can I choose the topic for a specific day?
Yes. On the calendar, plan any topic idea onto an open slot. When that slot's draft is due, it is written about that topic. Slots without a plan get the best idea at the time.
Can I edit an article after it is published?
Yes. Edit the title, description, or body and save. A webhook site receives the change as article.update with the same id and slug, and GitHub gets a pull request that edits the file. The address stays fixed so existing links keep working.
Where do the topics come from?
From Search Console queries your site already shows up for but gets few clicks on, from what people type into search around your keywords, and from the keywords you give it. Ideas that overlap an article you already have are dropped.
Which AI model writes the drafts?
By default, LopeBase's own AI access, paid for with the AI credits included in your plan. You can add your own OpenAI compatible key instead, and then drafts use no credits.
Can my own coding agent write the articles?
Yes. Through the LopeBase MCP server, an agent can read a product's content profile, ask for the next topic, and submit a draft, with a date if it should go on the calendar. The draft goes through the same checks and review.
Give every product a blog that keeps up.
Free for one product. No card.