Content Engine

The Content Engine drafts production-ready content assets — meta, page copy, FAQs, schema, article briefs, AEO answers — with versioning and a review step before they're queued for implementation.

Some actions need content written before they can be implemented. The Content Engine is where that content is drafted, reviewed and approved — separately from the change that publishes it.

1
Create an asset
Choose a type (SEO meta, page copy, FAQ, schema, internal links, article brief, article draft, AEO answer, GEO entity), give it a title and a brief, and optionally link it to a work item and target URL / keywords.
2
Draft
RankOut drafts the asset from your brief and the project's brand context, returning only the fields that make sense for the type. Or paste your own content instead.
3
Version and edit
Add new versions while the asset is a draft. Each version keeps a change note.
4
Submit for review
Submitting locks editing. A reviewer approves or rejects.
5
Queue for implementation
An approved asset can be queued — RankOut drafts a change proposal that publishes it, which then goes through the normal Changes approval and validation.

A content asset with its versions, review status and queue-for-implementation action — Content is drafted, versioned and approved before it's queued to publish.

RankOut marks any factual claims that need checking in the asset's reviewer notes rather than asserting them. Review those before approving.