A content pipeline that publishes only what a person has approved
The pipeline reads a site's search performance, turns it into a ranked queue of page-level wording changes, and holds every change for a named person's review. Publication requires approval, and changes are limited to the agreed content.
- FieldContent operations
- EngagementKoca Ventures build on open-source foundations
- StatusComplete and gated, live publishing switched off
Proposals for review, publication by approval
The pipeline reads a site's own search performance and turns it into a ranked queue of specific, page-level wording changes: body copy, page titles, descriptions and headings. It does not touch code, layout or configuration, and it does not write new articles.
Site owners receive proposed wording changes for review. After approval, the change is published through whichever channel the site uses, or handed in writing to the client's technical staff when their platform accepts no automated write.
Content changes that could not be checked or contained
Organisations that publish at scale meet the same two failures: wording decisions made without evidence, and automation granted more access than its governance allows.
Decisions made without evidence
Which page to change, and what to change on it, was decided in meetings. The site's own performance data already existed, but nothing turned it into a prioritised queue of work.
Automation with more access than governance allows
The site owner needs to control what may change and who approves it. Automation granted broad access to a live site is not a control.
Approvals with nothing independent to approve
Reviewers need to see exactly what will change before approving it. When the description and the change can differ, approval becomes a formality.
Controls first, then automation
Five things the site owner can rely on.
The site owner controls what may change
Proposals are limited to the agreed content, and nothing is published without a named person's approval.
- The agent reads current text and records a proposal
- Changes limited to the agreed content
- Publication only by approval
Only wording ever changes
Every change stays within the wording approved by the site owner.
- Every change confined to content text; code, layout and configuration are out of scope
- Every proposal checked before it can be published
- Translated sites keep their structure while the wording changes
Reviewers approve the real change
Reviewers see the exact proposed wording beside the current wording, with the reason for the change.
- Current and proposed wording shown together
- The reason for the change beside the wording
- Each proposal carries the search evidence that raised it
One approval, and only one
The first approval decides, and a repeated approval changes nothing.
- The first approval decides; a repeat changes nothing
- Approval required for every proposed change
- Reviewers respond through the approval interface
Publishing that switches itself off
An approval starts a write, and the write is the step that can damage a live site, so it is the most controlled part of the pipeline. Publishing starts switched off and stays off until it is deliberately enabled with a measurement window in place. A measurable fall in organic search traffic or a rise in crawl errors switches it off again without anyone watching.
- Every publish captures a way back first, checks the live page afterwards, and reverts on its own when that check fails
- The page's search settings are verified before and after every write
- Publishing suspends itself on a traffic or crawl-error signal
What changes in operation
Site owners review proposed wording with the search evidence beside it.
Checkable
Every proposal
A reviewer reads the exact before and after, with the search evidence that raised it beside the text. Approval becomes an informed decision.
Reversible
Every publish
Nothing is written without a way back captured first, and a live page that fails its check is restored without anyone being called.
Gated
Current status
Publishing stays behind the approval gate at every step, and live publishing is switched on only deliberately, with a measurement window in place.
Talk to us about governed automation
If a system is going to change something you own, the first question is what stops it. We design the controls first, then the automation.
Discuss your project