Content operations: how to run content as a system, from plan to retirement

What is content operations?

Content operations is the set of people, processes and tools an organisation uses to plan, produce, publish, maintain and retire content, and the rules that connect them. It is the difference between a team that publishes when someone has time and a system that turns a strategy into a steady flow of pages that meet a standard and stay accurate.

Most published definitions agree on the parts. Contentful describes it as the coordination of people, processes and tools across content creation and distribution, and the Content Marketing Institute’s framework runs from the purpose of content through governance to the technology stack. The rest of this guide is about how those parts fit together in practice.

Why content operations matters for search

For a team that relies on organic search, weak operations show up as specific problems: two pages written for the same search months apart, guides that cite figures from three years ago, pages nobody owns, and a backlog of drafts that never ships. Each of those has a cost in rankings or wasted work, and none is fixed by writing better.

Google’s helpful content guidance asks whether content is produced well or appears sloppy or hastily produced, and whether you are producing lots of content on many different topics in the hope some of it performs. An operation with a keyword map, briefs, review standards and maintenance is how a team answers those questions consistently across hundreds of pages, not one at a time.

Maturity is low across the industry, which is an opportunity. Content Science reports that in its most recent State of Content Operations study, 38% of participants placed their organisations at the second of five maturity levels, piloting content operations in some areas, and 2% at the highest, thriving. The study’s sample is its own participants, so treat the figures as indicative.

The content lifecycle, stage by stage

The core of content operations is a lifecycle that every piece moves through, with an owner and a standard at each stage. Writing it down is the first step; most teams discover they have no owner for at least two stages.

Stage	What happens	Owner	Standard
Plan	Decide which topics and pages to build or update, from the keyword map and business goals	Content or SEO lead	Every item has a target query no other page owns
Brief	Record the decisions the writer cannot make alone	Content lead	Approved brief with acceptance criteria
Produce	Write, design and source the piece	Writer	Draft that passes the brief’s acceptance criteria
Review	Check facts, standards and quality	Editor, subject expert	Facts sourced, standards met, two review rounds or fewer
Publish	Put it live with links, metadata and checks	Editor or publisher	Automated pre-publish checks pass
Distribute	Link it from related pages, share it in the right channels	Content lead	Linked from its pillar and siblings on publish day
Maintain	Review on a schedule, update facts, fix decay	Page owner	Reviewed within its review cycle
Retire	Merge, redirect or remove pages that no longer earn their place	Content or SEO lead	Redirect to the best equivalent; links updated

Each stage has a guide on this site. The planning cadence is in the editorial calendar guide; the brief and its acceptance criteria are in the content brief guide; and the maintain and retire decisions are in the content audit guide. Where the operation produces page families from templates, the guide to programmatic SEO without thin content sets the rules.

Roles and ownership

Content operations needs clear roles more than it needs a large team. In a small company one person may hold several roles; what matters is that each is held by someone, by name.

Role	Owns	In a small team
Content lead or managing editor	The plan, the calendar, priorities and the overall standard	Often the head of marketing
SEO lead	The keyword map, target queries, internal link rules and technical checks	Often the same person as the content lead
Writers	Drafts that meet the brief	In-house, freelance or both
Editor	Acceptance against the brief, then style and accuracy	Can be the content lead, but not the writer of the same piece
Subject experts	Facts, examples and first-hand knowledge	Product, sales, support or founders, with time agreed in advance
Content operations owner	The process, tools, templates and metrics themselves	Usually the content lead, until the team is large enough for a dedicated role

Subject experts are the role most often left implicit, and the one that most affects quality. Agree a small, fixed amount of their time each month, such as a review slot or an interview per piece, rather than asking ad hoc. First-hand knowledge is what distinguishes a page from the ones already ranking.

Governance: standards that hold without a meeting

Governance is the set of rules that keeps content consistent without everyone checking with one person. It works when the rules are written down, short, and checked automatically wherever possible.

• A style guide. Spelling, terms, tone, formatting and words to avoid, short enough that writers read it.
• Evidence rules. Every factual claim sourced, every figure dated, no invented quotes, ratings or results.
• A keyword map. One URL per search intent, checked before any brief is written.
• Internal link rules. What each content type links to, written into the brief template.
• Templates. Brief templates, page templates and review checklists, versioned in one place.
• Decision rights. Who can approve publishing, who can change the standard, and who decides when two teams disagree.

The rules that never need judgement belong in automated checks that run before anything is published: metadata lengths, internal link rules, broken links, schema validity and banned words. That leaves editors’ time for what does need judgement. Which checks to automate, and how to keep them reliable, is covered in the guide to SEO automation; the recurring SEO rhythm and the procedures for technical releases and migrations are in the guide to SEO workflows.

Maintenance: the work most operations forget

Every page published adds to the library that has to be kept accurate. Facts date, products change, competitors publish better pages and links break. A team that plans only new content finds, after a year or two, that maintenance is eating its capacity unplanned, or that the library is quietly decaying.

Plan maintenance explicitly: give every page a review cycle, by type, and budget the hours. A pricing comparison might need review every quarter; a definition page might need it once a year. When a page is reviewed, update it substantially or leave the date alone: Google’s John Mueller has said Google would not rank pages differently just because the date changed, as Search Engine Journal reported.

Hypothetical defaults. Set the review cycle by page type; a weighted average works for planning.

Pages live todayNew pages published a monthAverage review cycle per pagemonthsHours per review, including any updatehoursHours per new pagehours

Reviews due a month today

10.0

Maintenance hours a month today

20.0

Production hours a month

84.0

Maintenance share of content hours today

19.2%

Maintenance hours a month in two years

44.0

Maintenance share in two years, at the same output

34.4%

This is the share that grows if output stays the same

The calculator assumes every page stays live. Retiring pages that no longer earn their place, through a content audit, is what keeps the maintenance load in check.

The second big number is the point. At steady output, maintenance becomes a larger share of the work every month, so a plan that holds today will be short of hours in two years unless it budgets for upkeep, raises capacity or retires pages. Retirement is part of the operation, not a failure: a page merged into a better one, with a redirect, reduces the load and usually strengthens the page that remains.

Content velocity, measured properly

Content velocity is usually reported as pieces published per month. On its own that number rewards publishing more, faster, whatever the quality. A useful measure of velocity has two parts: throughput, how many pieces finish in a period, and lead time, how long each takes from start to publish.

The two are connected by Little’s law, a result from queueing theory proved by John Little in 1961: the average number of items in a system equals the rate they arrive multiplied by the time each spends in it. For a content team in a steady state, average lead time equals the work in progress divided by throughput. Ten drafts open and five finished a month means each takes about two months, however hard people work. Halving the drafts open, at the same throughput, halves the lead time.

Lever	Effect	Cost or risk
Limit work in progress	Shorter lead time at the same throughput	Requires saying no to starting new pieces
Better briefs	Fewer revision rounds, so each piece takes fewer hours	More time up front for the content lead
Automated pre-publish checks	Less editor time on mechanical problems	Build and maintenance time
Clearing the bottleneck stage	Throughput rises to the next constraint	Usually editing or expert review; needs their time protected
More writers	More drafts	Often just longer queues at editing if the bottleneck is review
Generating drafts with AI	Faster first drafts	Review load rises; Google’s spam policies treat many pages without added value as scaled content abuse

Find the stage with the longest queue before choosing a lever. In many teams it is review rather than writing, and in that case adding writers or AI drafts without adding review capacity lengthens the queue rather than shortening it.

A worked example: a four-person team

Take a hypothetical B2B software company with a content lead, two writers and a part-time editor, publishing about eight pieces a month and with 150 pages live. Every month some pieces slip, two pages recently started competing for the same search, and nobody can say when the integration guides were last checked. The figures are invented; the diagnosis is the point.

Mapping the lifecycle shows the gaps quickly. Nobody owns pages after publishing, so maintain has no owner. Briefs are a title and a keyword, so drafts average three revision rounds. Eleven drafts are open, against six or seven finished a month, so by Little’s law each piece takes well over a month from start to publish. And the editor, at two days a week, is the stage where drafts wait.

The changes follow from that. Each page gets an owner and a review cycle by type, with integration guides every quarter. Briefs gain an angle, sources and acceptance criteria, which in the next quarter brings revision rounds down. Drafts in progress are capped at six, so writers help clear review or improve briefs instead of starting new pieces. Two of the eight monthly slots become updates. And a keyword map check is added before every brief, which stops the duplicate problem at its source.

Throughput barely changes, but plan reliability, lead time and review coverage all improve, and the team stops discovering problems on the live site. That is what good content operations usually looks like from the inside: not more output, but fewer surprises.

Tools for content operations

The tools matter less than the rules they encode. A spreadsheet and a shared folder can run a good operation; an expensive platform cannot rescue one without owners and standards. The Content Marketing Institute’s framework makes the same point when it notes that a spreadsheet can be an acceptable starting point.

Need	Minimum	When to invest more
Keyword map	A spreadsheet with one row per intent and one URL	When more than one person plans content
Calendar and workflow	A board with the lifecycle stages as columns and one owner per card	When work in progress needs limits enforced
Briefs and templates	Shared documents with a fixed template	When briefs are written by several people
Content management	A CMS that keeps revision history	When content is reused across channels or languages
Pre-publish checks	A checklist	When the library passes a few hundred pages
Measurement	Search Console and analytics, reviewed monthly	When decisions depend on comparing many pages

Two of the free tools on this site cover early parts of the cycle: the Topical Map Generator builds a keyword map from a keyword list and flags duplicates, and the content gap checker compares a draft with the pages that rank, which is useful during review.

How to measure content operations

Measure the operation separately from the content’s results. Results take months; operational numbers show problems the week they start.

Metric	What it is	What a problem looks like
Throughput	Pieces published per month, new and updates separately	Falling while the team is busy: work is stuck somewhere
Lead time	Days from brief to publish	Rising: too much work in progress
Plan reliability	Published divided by planned, per month	Below about 70%: the plan is not being used to decide
Revision rounds	Rounds per piece, by brief author and content type	Above two: briefs or standards are unclear
Review coverage	Share of pages reviewed within their cycle	Falling: maintenance is being squeezed out
Duplicate intent incidents	New pages competing with existing ones for a query	Any: the keyword map check is being skipped

Review these monthly with the team, and the content results quarterly. When an operational number moves, fix the process rather than the people: a rising lead time is almost always a work-in-progress problem, and rising revision rounds almost always trace back to briefs. How to report results to the rest of the business is covered in the guide to creating an SEO report.

Setting up content operations, step by step

Most teams can set up the core of a content operation in a few weeks, using tools they already have. The order matters: map what exists before changing it.

1. 1MapWrite down how content is made today, stage by stage, and who does each step.
2. 2OwnGive every stage one owner, by name, including maintain and retire.
3. 3StandardiseWrite the style guide, evidence rules, brief template and review checklist.
4. 4Map keywordsBuild the keyword map: one URL per intent, existing pages included.
5. 5Plan capacitySet the calendar’s cadence from real hours, with a share for maintenance.
6. 6Automate checksMove rules that never need judgement into pre-publish checks.
7. 7MeasureStart tracking throughput, lead time, plan reliability, revision rounds and review coverage.

Do not change everything at once. The Content Marketing Institute’s framework advises documenting current processes before standardising them, and leaving room for ad hoc requests. Start with ownership and the brief, which fix the most problems for the least effort, and add the rest over a quarter.

Common content operations mistakes

Each mistake below is common, and each has the check that catches it.

• Operating only the middle of the lifecycle. Check: are maintain and retire owned and planned?
• Shared ownership. Check: does every stage, and every piece, have one named owner?
• No maintenance budget. Check: what share of hours goes to reviewing existing pages, and is it planned?
• Velocity as posts per month. Check: are throughput and lead time tracked together?
• Adding writers to fix a review bottleneck. Check: which stage has the longest queue?
• Tools before rules. Check: are the standards written down before the platform is chosen?
• Subject experts asked ad hoc. Check: is their time agreed in advance?

Structure

Lifecycle written down from plan to retire One named owner for every stage Subject experts’ time agreed in advance

Standards

Style guide and evidence rules written down Keyword map with one URL per intent Brief template and review checklist in one place Mechanical rules checked automatically before publishing

Capacity

Calendar cadence set from real hours Review cycle set for every page type, with hours budgeted Retirement decisions made through a regular content audit

Measurement

Throughput, lead time and plan reliability reviewed monthly Revision rounds and review coverage tracked

Ticks are saved in your browser.

Designing content operations, from keyword map to maintenance, so a team can run them without constant supervision, is the work of a content systems engagement.