Implement
flowseo_content_calendar
Your SEO calendar writes along. You decide what goes live.
The calendar looks for topics, writes on a rolling basis 30 days ahead and hands you every post for review. Publishing happens on the scheduled date, via WordPress, webhook or email.
Example data: Lumivo Werkhaus GmbH (fictional)
Every date has a status
In the month grid you see where each post stands. If a date passes and nothing has been released, nothing goes out.
-
Finding a topic
From keywords, clusters and Search Console opportunities.
-
Researching
One SERP analysis per topic.
-
Writing
In the tone of your Brand DNA.
-
Review needed
You read, edit, release or discard the topic.
-
Published
On its date, through the target of your choice.
Every topic is checked against your existing texts
A topic is checked against your content, link targets and top 10 rankings. The calendar then compares the first ten results of the new analysis with your existing texts.
| Result | When | Consequence |
|---|---|---|
| Free | fewer than three pages in common, no page of yours in the top 10 | The text is written as planned |
| Similar | three to five pages in common, or a page of yours below position 3 | The text is written and differentiated in content |
| Same | six or more pages in common, or a page of yours at positions 1 to 3 | The topic is discarded and the date gets a new one |
The card shows how many topics were discarded and what a text is differentiated from.
What you see before release
A release check reads the text and reports what you should look at: claims without evidence, meta details, style. Only fact-check findings hold up the release, and only until you explicitly confirm them.
In the browser you edit the text and meta details yourself and use the AI actions in the editor, within your package.
Example data: Lumivo Werkhaus GmbH (fictional)
How release through an agent works
Your agent can schedule and release posts. We tell you exactly how far that is technically secured.
Switch off (default)
The agent is instructed to ask you first. It reports your yes itself with confirmed_by_user: true. That is its own self-report, and FlowSEO cannot verify it. So your approval is not technically enforced.
Switch on
The agent releases and publishes on its own. The browser then shows “Released by an AI agent”.
- The switch applies per domain. An agent cannot flip it itself, and you change it in the domain settings.
- Scheduled publications keep running even after the switch is turned off. There is currently no separate button to withdraw them. If you revise the post in the SEO calendar, its release is reset: it goes back to “Review needed” and does not go out until it has been released again. Your agent resets the release when it changes the post’s metadata.
What works in the browser and what through an agent
The calendar and the content workflow are open to you in the browser and through your agent.
| Capability | Browser | Agent |
|---|---|---|
| Set up the calendar, maintain topics and dates | Yes | Yes |
| Release and schedule a post | Yes | Depends on the switch |
| Connect WordPress or a webhook | Yes, for the calendar | No, existing targets only |
| Order content outside the calendar | Yes, limited | Yes, limited |
| Export as HTML, Markdown, Word or PDF | Yes | Yes |
Without a connected target, the post goes by email to your domain team on its date, with HTML, Markdown, Word, PDF, JSON-LD and an image ZIP attached.
Seven content types
The calendar writes blog articles and guides. The other types are created in the content workflow.
In the Brand DNA you store your brand, voice, products and locations. It feeds into every text.
- Blog article
- Guide
- Landing page
- Product page
- Category text
- Local page
- Comparison
How your agent asks for it
Your agent sees the same dates and reports what is waiting for you.
- Ordering content counts as a limited action.
- A confirmation from the release check has to be set by a person, your agent cannot confirm it.
- It cannot set up WordPress or a webhook, it can only use existing targets or email.