Content Operations SOP

This content operations SOP is a working procedure, not a description of content operations.

Copy it into your operating system, replace the bracketed fields, test it on one live commercial page and revise whatever your team cannot follow. The procedure is complete when a new owner can move an asset from approved need to verified release without relying on tribal knowledge.

If you need the operating model around roles, governance and bottlenecks before the procedure itself, start with content operations for lean marketing teams. If the wider portfolio has no clear page jobs, priorities or commercial parent, fix that in the content strategy system before you automate production.

SOP control block

Purpose

Move approved content from intake to verified release with:

• one page job;
• one accountable owner;
• sufficient evidence;
• clear editorial and risk decisions;
• correct search and publishing controls;
• source and rendered proof;
• a named measurement and maintenance owner.

This SOP is designed to prevent random publishing, unsupported claims, duplicated page intent, approval deadlocks, broken releases and pages that are never reviewed again.

Roles

One person may hold several roles. Do not leave the accountability blank.

Entry criteria

Do not start drafting until the record contains:

• intended client or user;
• problem or decision;
• business outcome;
• page type and intended URL;
• target query, discovery surface or non-search job;
• current page owner and overlap check;
• accountable asset owner;
• minimum source pack;
• known prohibited or unverified claims;
• required reviewers;
• primary CTA and measurement event;
• priority approved by the portfolio owner.

If the request fails these criteria, return it to intake. Do not let “urgent” mean “undefined”.

Procedure

1. Log and triage the request

The requester creates one queue item with the entry-criteria fields.

The portfolio owner assigns one disposition:

• accept now;
• hold pending a named dependency;
• merge with existing work;
• reject with a reason;
• escalate because the decision exceeds their authority.

Exit criteria: priority, page owner, asset owner and dependency are explicit.

2. Freeze the baseline

For an existing page, capture:

• current source or CMS revision;
• live URL and rendered desktop/mobile page;
• current metadata, canonical and indexability;
• relevant query and page data;
• current conversion path;
• known links, citations or commercial use that must be protected.

For a new page, record the current SERP, competitor and internal-coverage gap.

If you cannot yet assign safe page-level actions across the existing estate, run the SEO content audit framework before this SOP. The audit owns diagnosis and disposition; this procedure owns execution.

Exit criteria: another reviewer can compare the candidate with the actual starting state.

3. Build the brief

The brief must state:

• target client and sophistication;
• page job;
• dominant intent and page type;
• target market and device where relevant;
• live-result consensus;
• deliberate information gain;
• required questions, entities and sections;
• primary internal-link destination;
• CTA;
• cannibalisation risk;
• acceptance proof.

For important search-led pages, record the research date and evidence limitation. A free visible-result sample is not precise geo-pinned rank evidence.

Exit criteria: the portfolio owner and senior editor agree on what the page must achieve.

For the briefing stage in more depth, use the SEO content brief SOP rather than expanding this end-to-end procedure into a second briefing manual.

4. Build the source and claim pack

Classify every material claim:

List claims that must not appear. If evidence conflicts, name the winning source or stop for resolution.

Exit criteria: the writer knows what is true, what is uncertain and what is prohibited.

5. Draft

The writer:

• answers the page job directly;
• uses the approved voice and speaks to the client;
• makes the commercial mechanism concrete;
• uses sources at the point of claim;
• preserves limitations;
• adds internal links where they help the user;
• avoids unsupported superlatives, guarantees and fake timelines;
• keeps important information in accessible text;
• does not copy competitor expression.

AI assistance, if used, stays under human ownership. The writer verifies every factual statement and does not treat generated prose as evidence.

Exit criteria: the draft is complete enough for editorial judgement, not a skeleton awaiting reviewers to write it.

6. Senior editorial review

The editor compares the draft with the brief, current page and live evidence.

Check:

• the opening is the strongest useful answer;
• the page has a clear argument and point of view;
• the language sounds like the brand, not an SEO template;
• each section earns its place;
• repetition and generic filler are removed;
• proof is specific and bounded;
• the page speaks to the intended client;
• valuable current content has not been lost;
• CTA and next step make sense;
• the candidate is materially better than the baseline.

Assign accept, revise or reject. Comments must identify the problem and decision, not merely express taste.

Exit criteria: accepted by the senior editor.

7. Specialist review

Only required reviewers assess their named scope.

Examples:

• clinician: treatment, suitability, risks and patient claims;
• lawyer: legal interpretation and disclaimers;
• security owner: controls and certification claims;
• product owner: feature, integration and pricing facts;
• case-study owner: client permission and result boundaries.

Record approval, revision or unresolved exception. Silence is not approval.

Exit criteria: all required claim owners have approved or the final approver has accepted a documented exception within authority.

8. Search, AEO and technical review

Check:

• one intended page owns the query or job;
• title, H1 and opening align naturally;
• the page satisfies the dominant result type;
• answer blocks are useful outside their immediate paragraph;
• internal links point to and from the right owners;
• metadata is specific and accurate;
• URL and canonical are correct;
• indexability is intentional;
• structured data is supported, visible and valid;
• key information exists in rendered text;
• AI states are described accurately: access, fetch, mention, citation, link, visit and conversion are not collapsed.

Google says structured data must represent visible content and does not guarantee rich-result appearance.^[1] Google also says its AI features rely on the normal search foundations rather than special AI markup.^[2]

Exit criteria: all blocking search and technical issues are resolved or explicitly deferred by the owner.

9. Prepare and release

The publisher:

1. uses the approved source;
2. confirms the URL and redirect plan;
3. enters metadata and visible content;
4. applies images, captions and alt text where appropriate;
5. applies approved structured data;
6. checks headings, tables, lists and links;
7. checks mobile and desktop previews;
8. verifies analytics and CTA configuration;
9. runs the required build or CMS validation;
10. releases through the approved path.

Do not publish if an approval, secret, legal check or release authority is missing.

Exit criteria: the release completes without a blocking error.

10. Verify the live or review page

The release owner verifies:

• correct content and layout;
• desktop and mobile readability;
• working links, media and CTA;
• successful form or key event;
• expected status, canonical and robots state;
• structured data validation where used;
• navigation and internal links;
• no accidental staging, temporary copy or internal-language copy;
• release reference and screenshots recorded.

A successful deployment log is not rendered-page proof.

Exit criteria: source, release and rendered evidence are attached.

11. Measure and decide

The measurement owner records:

• release date and annotation;
• page and query baseline;
• relevant leading indicators;
• qualified actions;
• known attribution gaps;
• any AI mention, citation, link or referral state;
• the next review trigger.

The owner chooses:

• keep and monitor;
• improve;
• expand the pattern;
• consolidate;
• roll back or correct;
• investigate because the evidence is inconclusive.

Exit criteria: next action, owner and trigger are recorded.

12. Maintain or retire

Review when a trigger fires, not only when the calendar says so.

For a material update, repeat the relevant steps. For consolidation or retirement:

• preserve valuable content and evidence;
• choose the closest relevant owner;
• implement redirects where appropriate;
• update internal links and sitemaps;
• verify that no critical user or commercial job was lost.

Exception procedure

An exception record must state:

• rule being bypassed;
• reason;
• risk;
• authority approving it;
• expiry or review trigger;
• compensating control.

“We were in a hurry” is context, not a compensating control.

Definition of done

An asset is done only when:

• the current source is identifiable;
• required approvals are recorded;
• the release path passed;
• the rendered page passed desktop/mobile review;
• links, CTA, canonical and indexability are verified;
• measurement and maintenance ownership are assigned;
• any exception is documented.

FAQ

How detailed should a content operations SOP be?

Detailed enough for a competent new owner to execute without guessing. Keep strategic judgement in the brief and portfolio process; keep repeatable steps and controls in the SOP.

Should every content type use the same SOP?

Use one core procedure with narrower checklists for service pages, articles, locations, products, regulated content and other materially different assets.

Who owns the SOP?

The role with authority over the end-to-end process. Individual experts still own truth within their domains.

Can AI perform the editorial review?

It can assist with checks and alternatives. A responsible human must make the final editorial, factual and release decisions.

What happens when an expert misses a deadline?

Escalate to the named decision-maker. Do not silently publish without required approval and do not let the asset remain indefinitely unowned.

How often should this SOP be updated?

Whenever a material workflow, CMS, platform, policy or failure changes what the team must do. Scheduled reviews can catch slow drift.

What is the most important release check?

There is no single universal check. For web content, source accuracy, rendered correctness, working conversion paths and intentional indexability are all hard gates.

How do we know the SOP is too complex?

If low-risk assets wait at gates that cannot change the decision, or the team maintains duplicate systems of record, simplify it. Do not remove controls that protect material risk.

Put the SOP through a real page

Choose one commercially important asset and run this procedure exactly once. Any step the team cannot complete reveals a missing owner, source, authority or tool—not a reason to pretend the process worked.

Use the content strategy system when the test reveals a portfolio-level problem with page ownership, commercial priority or cluster architecture rather than a procedural defect.

Primary sources

• Google Search Essentials — Google Search Central.
• Creating helpful, reliable, people-first content — Google Search Central.
• Web Content Accessibility Guidelines — W3C Web Accessibility Initiative.