Content velocity measures how much content a team ships over time. It includes new pieces and, in mature programs, meaningful updates to existing ones. Velocity matters because topical coverage and compounding traffic take a body of work, but it is only useful alongside quality. Publishing more pages that nobody needs does not help, and AI drafting tools have made raw volume easy to inflate.
What limits velocity
Writing time is often not the main constraint. Briefing, expert input, reviews and approvals tend to create the longest delays, and they are where process improvements pay off.
- Unclear briefs that lead to rewrites
- Slow subject matter expert availability
- Too many approvers or unclear sign-off
- Design and asset bottlenecks
- Manual publishing steps in the CMS
Velocity and quality
Google's spam policies describe scaled content abuse: producing many pages primarily to manipulate rankings, with little value for users, regardless of whether humans or AI wrote them. A high publishing rate is not a problem in itself; the issue is pages that do not help anyone. Track velocity together with measures of quality and impact, such as indexing rate, engagement and conversions per page.
Example
Speeding up reviews, not writing
Hypothetical company Nettlecourt publishes about four articles a month and wants to double that. Mapping its workflow shows drafts wait about two weeks for product review. The team introduces a weekly 30-minute review slot with a product manager and a short checklist of what reviewers must check. Output rises without adding writers.
Common mistakes
Velocity as the goal
Targets based only on number of posts encourage thin content. Set targets for outcomes as well as output.
Ignoring updates
Counting only new posts undervalues refreshes, which are often the best use of time on an established site.
Questions
There is no correct universal rate. Publish as often as you can maintain quality and keep existing content accurate.
