A team writes 10 articles in a month; three months later, 8 of them bring 47 organic visits combined, while the other 2 bring 3,000. Same writing cost, 60x difference in output. If content budget is allocated by article count, you’re using an average cost to hide the extreme performance of individual articles. Data-driven content budgeting is fundamentally about estimating each article’s expected output, then deciding what to write, how many, and when to stop.
Here’s the bottom line: content budget allocation goes in three steps. Split topics into three buckets — new keyword coverage, existing page expansion, and old page maintenance. Score every topic with three data points: estimated search volume, competition difficulty, and existing page performance. Then do a quarterly review, stopping or merging the worst-performing content and moving the freed resources to high-potential topics. The unit of budget is expected traffic and conversions, not article count.
“Budget” here isn’t just money — it’s writing time and editing effort, which are the real bottlenecks for most indie-site teams. The goal of the method is making every writing session correspond to a data-backed decision, rather than “this topic feels good” intuition. The method works regardless of team size — one-person sites and ten-person sites both apply it; the only difference is how many fields the scoring sheet has.
Allocating by article count assumes every article has equal value
Content SEO output is heavily skewed: a small number of head articles contribute the vast majority of traffic, while long-tail articles lie at single digits forever. Scheduling by article count feeds resources evenly to all topics, and a batch is doomed not to take off. The skewed distribution isn’t accidental — it’s a property of search demand itself: in an industry, 20% of head keywords eat 80% of search volume. If your topic list isn’t sorted by this rule, you can’t write high-output content no matter how hard you try. Budget allocation must be designed along this property.
Three investment scenarios, different priorities
Drop candidate topics into the three buckets below, then decide resource order.
| Investment scenario | Goal | Data basis |
|---|---|---|
| New keyword coverage | Enter new search demand | Related uncovered keywords in the query report |
| Existing page expansion | Push pages ranked 10-20 into top 3 | Existing pages’ impressions and clicks |
| Old page maintenance | Stop traffic decline | Page traffic trends and content aging |
The priority of the three scenarios isn’t fixed. In the new-site phase, new keyword coverage has top priority because the index has no content yet. Once the site matures, existing page expansion often has higher ROI — the page already has historical authority, so a revised version can raise rankings at far lower cost than writing a new page from scratch. For actual scheduling, allocate writing resources at roughly a 5:3:2 ratio, then fine-tune by site phase — don’t give each bucket a third.
Score every topic on three dimensions
Score each candidate topic with three numbers: search volume (cross-validate with GSC query report and keyword tools), competition difficulty (check what level of sites fill the homepage), and existing support (is there a page that can catch the traffic). After scoring, sort by total and take the top 20% into next month’s schedule. A concrete example: the candidate pool has keywords A and B. A has 2,000 search volume but the homepage is all industry giants; B has 800 volume but weak sites on the homepage. For an indie site, B’s actual ROI is higher, because the difficulty of grabbing the top 3 isn’t on the same level at all. The “low-CTR keyword” list compiled in the GSC query CTR analysis is a ready-made candidate pool — one keyword is one potential topic. For how to compute each article’s real revenue after writing, the content ROI article explains it fully; at the allocation stage, just use the expected values in reverse for sorting.
Quarterly review: decide to stop or scale up
At the end of each quarter, do a full content review: summarize traffic, rankings, and conversions by URL. Content with zero traffic for two straight quarters and no upward ranking trend gets stopped or merged into neighboring pages. The freed resources flow to the highest-scoring new topics, and the budget enters a self-correcting loop. To hand the boss a quarterly expected output, borrow the organic traffic forecasting method to make investment and output reconcile. The biggest value of the review isn’t cutting content — it’s that the next scheduling has a historical reference, and judgments get more accurate over time. Fix the review point at the last week of each quarter, avoiding the month-end data settlement peak.
Turn the budget table into a trackable dashboard
The content budget ultimately lands in a table: topic, scenario, estimated score, planned word count, owner, review result. No complex system needed — one Google Sheet suffices, but someone must update it monthly. For field selection, the principles in the SEO KPI dashboard article apply directly: keep only fields that truly affect decisions and don’t record the rest, so the dashboard doesn’t become a data warehouse. Once the table is built, open it directly in monthly meetings to review topics — budget allocation shifts from personal judgment to team consensus.
Before you start, run through this round’s checklist: sort the last 6 months of published articles by organic visits and verify the skew between head and bottom content; export keywords with modest impressions but strong relevance from the GSC query report to build a new topic candidate pool; score each pool topic on search volume, difficulty, and support, taking the top 20% into next month’s schedule; set up a quarterly review table, updating traffic data at each quarter end to decide stop or merge; connect the content budget table with the KPI dashboard so budget allocation and result reporting use the same data.
