Overview
Production-line SEO content. Where the content marketing workflow starts from a topic, this one starts from a keyword row in a spreadsheet and runs on a schedule — which is what you need once you are publishing at volume.
Every run produces an article plus the SERP analysis showing why it is structured the way it is, so an editor can challenge the reasoning rather than just the prose.
Business value
Makes content output predictable and forecastable: a keyword calendar becomes a publishing schedule with a known cost per article.
Expected outcome
A queued, optimised draft per calendar row, each with its SERP analysis attached for the editor.
Problems it solves
- Keyword research and content production live in separate tools and separate heads
- No audit trail for why an article was structured a given way
- Volume publishing degrades quality without a fixed process
- Refresh decisions are made on gut feel
Who it is for
- In-house SEO teams publishing weekly or more
- Content agencies with keyword-led retainers
- Publishers running topical clusters
Benefits
- Runs on a schedule — output becomes a forecast, not a hope
- Every article carries the SERP reasoning behind its structure
- Cost per article is known before you commit
- Refresh candidates surface automatically
Limitations
- Needs a paid SEO data source to be worth running
- Quality still gated by human review — this increases throughput, not autonomy
- Works poorly where the SERP rewards original research
- A core update can invalidate the structural assumptions overnight
Success metrics
- Articles published per week
- Median position at 90 days
- Cost per article including tool spend
- Percentage of drafts accepted without restructuring
Flow diagram
Every step in order, colour-coded by how much of it runs without a human.
Scroll to pan · use the controls to zoom, expand or export.
Steps
8 steps from trigger to result.
SERP analysis
- If the top ten are dominated by a format you cannot produce, stop and reassign the keyword
Entity and gap extraction
From these top-ranking pages for "{{keyword}}", extract:
1. Entities mentioned by ALL of them (mandatory coverage)
2. Entities mentioned by SOME (differentiation opportunities)
3. Entities mentioned by NONE that a domain expert would expect
Pages:
{{page_contents}}
Return three lists. Be concrete — name the entity, not the theme.
Structured outline
Draft and optimise
Editorial review
- Every factual claim needs a source check before publication
Queue for publication
Performance review at 90 days
AI tools
Each tool records the role it plays and whether it is required.
Integrations
Services this workflow connects to, and how each authenticates.
Prompt library
Every prompt in the workflow, in chain order. Swap the highlighted placeholders for your own values.
From these top-ranking pages for "{{keyword}}", extract:
1. Entities mentioned by ALL of them (mandatory coverage)
2. Entities mentioned by SOME (differentiation opportunities)
3. Entities mentioned by NONE that a domain expert would expect
Pages:
{{page_contents}}
Return three lists. Be concrete — name the entity, not the theme.
Prerequisites
Have these ready before you start.
Use cases
Topical cluster build-out
Publish a 20-article cluster on a schedule with consistent internal linking.
Cluster live in a quarterRetainer delivery
Hit a contracted article count per month with predictable cost.
Retainer met without overtimeProgrammatic category pages
Generate and optimise category descriptions at catalogue scale.
Thin pages replacedMetrics
Author estimates — treat them as a starting point and measure your own runs.
Accepts
Produces
FAQ
How is this different from the Content Marketing workflow?
What happens when Google ships a core update?
Can this run fully unattended?
Reviews
No reviews yet — be the first to share how this worked for you.