What an editorial workflow actually is
An editorial workflow is the documented sequence of stages, roles and handoffs that takes an SEO brief from "this page should exist" to "this page is live and being tracked". It is the operations layer of a content programme. Without it, every page is a heroic effort; with it, every page is a repeatable unit of work.
The workflow we use has seven stages and four roles. The stages are: brief, draft, SEO review, edit, fact-check, publish, track. The roles are: SEO, writer, editor, publisher. A fifth role (the credentialled subject-matter reviewer) joins the workflow for YMYL topics. Each stage has a named owner, a clear input from the previous stage, and a clear output that triggers the next.
The workflow is not a Gantt chart or a project plan. It is a steady-state operating procedure. The team should be able to run it on autopilot once a few cycles have been completed, with the only variable being the topic of the page in flight.
Why workflow beats heroics
Most content programmes are run on heroics. One person (usually the marketer or the agency lead) carries the strategy in their head, briefs the writer informally, edits the draft themselves, publishes it, and then forgets to track it. The system works as long as that person stays involved and never gets sick or busy. The moment they step away, the programme stalls.
Three concrete reasons workflow outperforms heroics.
- Workflow makes the programme survivable. If the SEO leaves, the workflow stays. The new SEO picks up the brief template, the review checklist and the tracking log, and runs the same workflow from week one. Heroics-driven programmes collapse when the hero leaves.
- Workflow surfaces problems early. The SEO review stage catches missing entities and wrong intent before the editor sees the draft. The fact-check stage catches technical errors before the publish stage. Each stage filters problems forward to the next, so problems get caught at the cheapest point to fix them.
- Workflow produces measurable output. With every page tracked through the same loop, the team can see which briefs produced strong rankings, which writers produced strong drafts, and which stages are bottlenecks. Heroics-driven programmes have no comparable diagnostic.
Workflow is not glamorous. It is also the single biggest improvement we make for clients whose previous content programme was running on heroics. The first month of a workflow-driven retainer often produces more shippable pages than the previous six months of heroics, and the pages rank better because they were briefed and reviewed properly.
The four roles
Each role owns specific decisions and specific outputs. The role boundaries are what stop the workflow from collapsing into one person doing everything.
The SEO
Owns the brief, the content map, the SEO review, the post-publication tracking, and any ranking-relevant call during the workflow. The SEO knows the cluster strategy, the topical authority plan, and the search intent for every page. See how to write a content brief for the input artefact, and topical authority explained for the wider context.
The writer
Owns the draft. Reads the brief, writes the page, self-checks against the brief before submitting. The writer should not be making strategic decisions during writing; the brief should have already made them. If the brief has gaps, the writer raises them before drafting, not after.
The editor
Owns voice, clarity and flow. Light line-edits inline; structural rewrites get sent back to the writer with notes. The editor is not the SEO; the editor reads for the reader's experience, not for ranking signals.
The publisher
Owns the technical ship. Schema injection, byline injection, dateModified, voice and originality lints, CMS publish, post-publish smoke-test (page loads, links work, schema validates). The publisher is the last line of defence before the page goes live.
The subject-matter reviewer (YMYL only)
Owns the technical accuracy of any claim in a YMYL topic. Credentialled (registered practitioner, admitted lawyer, qualified accountant) and named in the byline. See E-E-A-T explained for why the named credentialled reviewer matters for YMYL content.
On small teams these roles get combined. One person can hold two or three roles, but the role boundaries should still be enforced in process. The SEO writing their own draft is fine; the SEO writing the draft and then "SEO-reviewing" it themselves is not, because the review check loses its independence.
The seven stages
Each stage has an owner, an input, an output and an estimated duration.
Stage 1: Brief (SEO, 45-60 minutes)
Input: the next URL from the content map. Output: a completed brief document in the eleven-section template. See how to write a content brief for the template.
Stage 2: Draft (writer, 4-6 hours)
Input: the brief. Output: a first draft that hits the H2 outline, the must-cover entities, the FAQ list, the internal-link targets, the schema spec, and the word-count range. The writer self-checks against the brief before submitting.
Stage 3: SEO review (SEO, 30-60 minutes)
Input: the draft and the brief. Output: either approved-for-edit or sent-back-to-writer with specific notes. The review is structural, not stylistic. The checklist: did the page hit the must-cover entities, did the H2 outline match, did the internal links go in, is the schema spec implementable, did the FAQ block get written, is the CTA aligned?
Stage 4: Edit (editor, 30-60 minutes)
Input: the SEO-approved draft. Output: an edited draft that reads in the house voice, is free of jargon and bloat, and uses Australian English throughout. The editor catches the voice-lint violations before the publish stage runs them.
Stage 5: Fact-check (variable, 15-90 minutes)
Input: the edited draft. Output: a fact-checked draft with citations verified, statistics confirmed, named people and places double-checked. For YMYL topics, the credentialled reviewer signs off here. For non-YMYL topics, the SEO or editor handles the fact-check.
Stage 6: Publish (publisher, 30 minutes)
Input: the fact-checked draft. Output: a live, indexable URL with the correct schema, byline, dateModified, internal links, and lint-passing copy. The publisher runs the voice lint, the originality lint and a basic schema validator before flipping the page live.
Stage 7: Track (SEO, 5 minutes per check-in)
Input: the live URL. Output: rows in the tracking log at publication date, four weeks post-publish, and twelve weeks post-publish. Pulls the rank, impressions, clicks and conversions from GSC and GA4. Pages that have not moved by twelve weeks become refresh candidates per content refresh strategy.
The handoffs that matter most
Three handoffs cause more workflow problems than the rest combined.
Brief to draft
The writer should be able to start drafting immediately on receiving the brief. If the writer has to come back with clarifying questions, the brief is incomplete. Brief revisions should happen before the writer starts, not during. The fix: a brief acceptance step where the writer reads the brief, raises any clarifying questions, and confirms they are ready to draft.
Draft to SEO review
The most common failure mode here is the writer submitting a draft that did not self-check against the brief. The fix is a self-check column on the brief itself: must-cover entities (tick each as it goes in), H2 outline (tick each section as written), internal links (tick each link as inserted). The writer ticks their own self-check before submitting; the SEO reviews the ticks first.
Fact-check to publish
YMYL topics get stuck here when the credentialled reviewer cannot find time. The fix is to schedule the fact-check window before the writer starts drafting, not after. If the reviewer cannot fact-check this week, the page does not enter the workflow this week.
The tracking loop
Every published page goes into a tracking log. The log is a Google Sheet or an Airtable, with one row per URL.
- Publication date. When the page went live.
- Primary keyword. The head term the page is targeting.
- Baseline (zero). Recorded at publication for the avoidance of doubt.
- Four-week check-in. Rank, impressions, clicks from GSC. Sessions and conversions from GA4. Logged on the row.
- Twelve-week check-in. Same metrics as four-week, plus a decision: is the page on a trajectory worth keeping, or does it need a refresh? See content refresh strategy for the refresh path.
- Refresh date. The next scheduled refresh, usually 12 months from publication.
The tracking log is the feedback loop. After 30 to 50 pages have been through the workflow, patterns become visible: certain writers consistently produce strong rankings, certain brief structures consistently produce conversion-grade pages, certain topic types consistently underperform. The log is what surfaces the patterns; without it, the team is flying blind.
Common mistakes
- Enforcing role boundaries even when the same person holds two roles.
- Self-check ticks on the brief so the writer confirms the brief was followed before submitting.
- SEO review that is structural, not stylistic. Stylistic notes belong with the editor.
- Scheduling the credentialled reviewer's time before the page enters the workflow.
- Tracking every page at four and twelve weeks, no exceptions.
- Using the tracking log to surface patterns about writers, briefs and topic types.
- Collapsing the SEO review and the edit into one stage. They check different things.
- Letting one person do every role with no independent checkpoints.
- Skipping the fact-check on YMYL topics because the reviewer is busy.
- Publishing without running the voice and originality lints.
- Forgetting to track pages after publication. Without tracking the workflow has no feedback loop.
- Letting briefs sit waiting for clarifying questions instead of fixing the brief upfront.
Perth and WA context
Three patterns from running editorial workflows for Perth and WA clients.
Trade businesses benefit most from a tight publisher role. Small Perth tradies businesses often have one marketing person who has to be the SEO, the writer and the publisher all at once. The workflow still works on a one-person team, but the publisher stage needs to be enforced as a discrete checkpoint, otherwise pages ship without schema or with a half-finished internal-link graph. See trades SEO and SEO Fremantle for the local context.
Mining and resources programmes need explicit subject-matter reviewer scheduling. A WA mining services client whose technical reviewer is offshore on a FIFO swing cannot fact-check pages every week. The workflow accommodates this by scheduling the fact-check window in advance and batching the fact-check reviews into the reviewer's onshore time. See mining SEO and SEO Karratha for the regional context.
Healthcare and legal workflows always include the credentialled reviewer stage. No exceptions. The named reviewer for medical content is a registered practitioner; for legal it is an admitted lawyer. The fact-check stage is the compliance gate as well as the editorial gate. See healthcare SEO, legal SEO and E-E-A-T explained for the framework.
For the wider strategic frame, see the Content Strategy pillar. For the brief template that starts the workflow, see how to write a content brief. For the keyword research that feeds the brief, see how to do keyword research. For the refresh workflow that picks up where the post-publish tracking leaves off, see content refresh strategy.