Content Engine
Owns the editorial calendar end to end — research, brief, draft, schema, publish, refresh — and reports organic performance weekly against a named KPI.
What it watches
Your editorial calendar slots and each published page's decaying performance
What it does
Researches the topic, drafts against a brief, adds schema, and refreshes pages that are losing rank — all held for your approval before anything YMYL publishes
When it asks a human first
Any YMYL topic or any claim needing a source holds for your review before publish — no draft ships on a health, money, legal, or safety claim without your sign-off.
How it works
- 1Researches the slot
Pulls search intent, competitor coverage, and internal-link opportunities for the calendar slot before a single sentence is drafted.
- 2Drafts against a brief
Writes to a structured brief — not a loose prompt — so every draft matches your voice and covers the angle the research surfaced.
- 3Adds schema and links
Attaches the right structured data and wires internal links into the existing content graph automatically, not as an afterthought.
- 4Holds YMYL for you
Any topic touching health, money, safety, or legal — or any claim needing a source — is held for your review before publish, no exception.
- 5Refreshes what's decaying
A monthly sweep flags pages losing rank and drafts the refresh, so the calendar isn't only forward-looking.
What triggers it
- · An editorial calendar slot comes due
- · A published page's ranking or traffic decays past your threshold
- · A YMYL topic or a claim needing a source enters the calendar
- · A refresh candidate is flagged by the monthly performance sweep
What you get
- · A published or refresh-ready draft with schema attached
- · A brief with sources for anything YMYL or claim-bearing, held for your review
- · A weekly editorial report — published, refreshed, in review
- · Internal links added into the existing content graph on publish
Not the right fit if
Not for businesses without any editorial cadence at all yet — a single one-off article is better served by the lighter content-ops workflow.
The math
At ~8 articles/mo × 240 min, that is roughly 32 h/mo — an estimate, not a guarantee.
Frequently asked
Routine, non-YMYL updates can auto-publish once you approve the pattern; anything YMYL or claim-bearing always holds for your review.
Content-ops refreshes meta and schema on a schedule. This owns the whole editorial calendar — research, drafting, publishing, and refresh — as one function.
It can run either or both, each written natively for its market rather than translated from the other.
You do — the agent drafts and sources, but subject-matter approval on anything YMYL stays with a qualified human.
Ready to put content engine to work?
Tell us about your setup and we'll confirm it fits within 48 hours.