What this playbook covers and when to run it
The playbook covers the recurring work of producing and maintaining content that is meant to be found through organic search: choosing what to write each month, briefing it, writing and reviewing it, publishing and linking it, and refreshing or retiring pages as they age. It also covers the monthly reporting that closes the loop. It does not cover how to do keyword research, how to write a brief or how to demonstrate experience and expertise; the keyword mapping guide and the content briefs guide own those methods.
Run it once the site has a content strategy and a keyword map, even a rough one. Without a map the monthly planning step turns into a debate about topics every time. Run it continuously; SEOImproving visibility in unpaid search results. rewards consistency, and a programme that publishes in fits and starts tends to leave half-finished topic clusters that never earn authority.
It is one of the operating guides in the playbooks library, and it relies on the publishing procedure for the exact steps of putting a page live.
Roles and responsibilities
- SEO lead. Owns the keyword map, the monthly topic selection and the refresh list. Checks each brief targets the intended query and reviews performance each month.
- Content editor. Owns the production line and the quality bar. Assigns briefs, edits drafts, chases reviews and makes the final publish decision.
- Writer. Owns the draft. Works from the brief, raises gaps early and revises after review.
- Subject-matter reviewer. Owns accuracy. Checks claims, adds the first-hand detail that makes a page credible, and can block a page on factual grounds.
- Web publisher. Owns the publishing step: formatting, metadata, internal links, images and the final checks before the page goes live.
The subject-matter reviewer is the role most often left vague, and it is the one that makes the difference to E-E-A-TExperience, Expertise, Authoritativeness, Trust. in practice. Name a specific person per topic area and agree a turnaround time. A review that waits for a busy expert's free afternoon will hold up the whole line.
Cadence, inputs and outputs
| Cadence | Owner | Inputs | Outputs |
|---|---|---|---|
| Monthly planning | SEO lead, content editor | Keyword map, performance report, refresh candidates, capacity | The month's backlog of new pages and refreshes, each with an owner and date |
| Weekly production | Content editor | Backlog, briefs, drafts in progress | Briefs issued, drafts reviewed, pages published and linked |
| Monthly reporting | SEO lead | Search Console data, analytics, the publishing log | Report on rankings, clicks and organic conversions, plus the next refresh candidates |
| Quarterly maintenance | SEO lead, content editor | Page-level performance over a longer window, overlap between pages | Decisions to refresh, merge, redirect or retire pages |
The playbook in phases
Plan the month
At the start of each month the SEO lead and the content editor build the backlog. Start with capacity: how many briefs can be written, how many drafts can be reviewed, how much publishing time exists. Then fill that capacity from two sources. New pages come from the keyword map, prioritised by how well each topic fills a gap in an existing cluster and how valuable the audience is. Refreshes come from the monthly report and the quarterly maintenance list. Give every item an owner, a target query, the page it supports in the cluster and a publish date. Use the SEO traffic estimator for rough sizing when two topics compete for one slot.
Brief
Every page, new or refreshed, gets a brief before a writer starts. The SEO lead or editor writes it using the method in the content briefs guide: the target query and intent, what the current SERPThe page of results a search engine shows. rewards, the questions the page must answer, the internal pages it should link to and from, and who will review it. For a refresh, the brief also says what is wrong with the current page: outdated facts, missing sections, a mismatch with intent, or competition that answers the question better. Briefs should be issued at least a week before the writing slot so writers can raise questions. A page without a brief tends to drift away from the query it was meant for.
Write and review
The writer drafts against the brief and flags anything the brief did not anticipate. The content editor edits for structure, clarity and house style, then sends the draft to the subject-matter reviewer with a specific request: check these claims, add first-hand detail here, confirm this recommendation. Reviews come back within the agreed turnaround, or the editor escalates. Keep review rounds few and specific; open-ended "any thoughts?" requests produce slow, unfocused feedback. The editor resolves conflicts between reviewer and writer and makes the publish decision. The output of this phase is an approved draft with its metadata, internal link targets and images listed.
Publish and link
The web publisher puts the page live following the publishing procedure, which owns the exact steps: formatting, title and description, headings, image alt text, canonical tags and the final checks. Then comes the step most teams skip: internal linking. Add links from the cluster's hub page and from related existing pages to the new page, using descriptive anchors, and confirm the new page links back into the cluster. For a refresh, check that existing links still point to the right sections. Record the page in the publishing log with the date, target query and the pages that now link to it, and request indexing through GSCGoogle's search performance and indexing tool. if the platform documentation suggests it helps.
Refresh and report
At the end of the month the SEO lead reports on organic performance using the approach in the SEO KPIs and reporting guide: clicks, impressions, average position for target queries, and organic conversions where analytics can attribute them. Report new pages and refreshes separately, with a note on how long pages typically take to settle. Then build next month's refresh list: pages that have lost clicks over a sustained period, pages whose information has gone out of date, and pages that rank just below the top results for valuable queries. Each quarter, extend this into maintenance: decide which weak or overlapping pages to merge, redirect or retire.
The content backlog and refresh queue
The backlog is a single list of everything the content team might work on, with new pages and refreshes side by side. Keeping them in one list forces an honest trade-off each month: is the next hour better spent on a new page for a marginal topic or on rescuing a page that used to bring in a large share of organic traffic? Separate lists almost always starve refreshes.
Each backlog item needs the same fields: the target query, the cluster it belongs to, whether it is new or a refresh, the reason it is on the list, the estimated effort and the owner. Items chosen for the month move onto the content calendar template, which gives them dates, a distribution plan and a measure. The refresh queue is simply the refresh items sorted by priority. Feed it from three triggers: sustained decline in clicks, information that is out of date (prices, regulations, product names, screenshots), and pages that sit just below the top positions and could move with improvement.
The quarterly maintenance pass deals with pages that a refresh will not save. Two pages competing for the same query should usually be merged, with a redirect from the weaker one. Pages that serve no query and no internal purpose may be retired. The content governance guide covers who may make those decisions and how to record them; the playbook simply makes sure they are made on schedule. For a site that exists to win enquiries, the guide to organic search for lead generation explains why money pages for service, pricing and comparison queries should lead the backlog.
A B2B software blog rebalancing new and refreshed work
A project-management software company publishes 12 new blog posts a month with a team of three writers and one editor. Organic clicks have been flat for two quarters despite the output. The SEO lead adds refresh candidates to the same backlog and finds 40 posts that lost more than half their clicks over the past year. The team cuts new posts to 8 a month and refreshes 4 of the most valuable decliners instead, merging 6 overlapping posts at the quarterly pass. After two quarters, organic clicks are up 18% on the starting point, and the refreshed posts account for most of the gain.
Measuring the playbook
Measure the line, not just the output. Operating signals include the share of pages that had a brief before writing started, the median time from brief to publish, how long drafts wait for subject-matter review, the share of new pages that received internal links from at least the hub and a related page within the publishing week, and whether the refresh queue is being worked or growing without limit.
For outcomes, use the reporting approach the SEO KPIs guide sets out and keep it consistent month to month. Watch for a growing gap between pages published and pages that earn impressions; it usually means topics are being chosen without enough reference to the keyword map, or that pages are not being linked into their cluster. The SEO Starter Guide from Google Search Central is a sensible reference for what the publishing checks should cover, and it is worth rereading when the process is reviewed each year.
When the team debates whether linking work deserves a place in the monthly cycle, the internal linking experiment measures its effect on target pages before it is scaled.
Common mistakes
- Publishing without internal links. A new page that nothing links to is hard for search engines and readers to find. Linking is part of publishing, not a later task.
- Separate backlogs for new and refreshed pages. Refreshes always lose. Put them in one list and trade them off honestly.
- Vague review requests. Asking a busy expert for "any feedback" produces slow, generic comments. Ask for specific checks.
- Planning beyond capacity. A backlog the team cannot finish rolls over each month and erodes trust in the plan. Start from capacity.
- Reporting only on new content. Most organic traffic usually comes from pages published long ago. Report the whole site, with new pages as one slice.
- Never retiring anything. Overlapping and obsolete pages compete with each other. Use the quarterly pass to merge or retire them.
