Your editorial calendar says publish three posts this month. Two are product launches someone promised in a leadership meeting. The third is a topic a writer picked because it sounded interesting in January. Nobody checked whether your best traffic pages are slipping, or whether Search Console is showing queries you almost rank for but never wrote about.

That is how most marketing teams plan content. It works until it does not. Traffic plateaus. Refreshes get pushed to next quarter. New posts compete with old ones for the same keywords. An editorial calendar driven by decay and opportunity data fixes the blind spots by putting defense and offense on the same spreadsheet.

This guide shows how to build a content editorial calendar from Search Console, analytics, and gap signals: what to pull each month, how to score URLs, and how to balance refreshes with new topics without drowning your writers.

Why Opinion-Only Editorial Calendars Fail

Most calendars are built from three inputs: executive priorities, seasonal campaigns, and whatever the content team finds interesting. Those inputs matter. They are not enough on their own.

Opinion-driven planning misses what your site is already telling you:

• Pages losing clicks while impressions hold steady (often a title, snippet, or freshness problem)
• Pages losing impressions and position (classic decay signals)
• Queries with impressions but no dedicated URL (coverage gaps)
• High-CTR pages with low visibility (easy wins if you strengthen and interlink them)

When the calendar ignores those signals, teams default to net-new posts because writing something fresh feels more productive than fixing what already exists. That is how libraries bloat with overlapping articles while hub pages quietly lose ground.

A data-informed calendar does not replace strategy. It ranks the work so strategy shows up in the URLs that actually move traffic and pipeline.

Two Data Streams: Decay (Defense) and Opportunity (Offense)

Think of your calendar as two lanes that share the same capacity.

Decay lane: protect what you already have

Decay work is anything that stops existing URLs from losing visibility, engagement, or trust. Examples:

• Light refresh: update stats, examples, and meta titles
• Medium refresh: new sections, better internal links, stronger intent match
• Merge or redirect: two thin posts competing for the same query

Signals come from Search Console trends, engagement drops in GA4, and qualitative checks (outdated screenshots, broken tools, wrong product names). Our posts on content decay and how to fix it and improving old blog posts that stopped ranking go deeper on diagnosis and refresh depth.

Opportunity lane: capture demand you are missing

Opportunity work creates or expands coverage where demand exists but your site under-delivers. Examples:

• New spoke post for a query cluster your hub page ranks for but does not answer
• Depth pass on a page ranking positions 5 to 15 with rising impressions
• FAQ or section add targeting People Also Ask patterns you see in Search Console

Opportunity signals include rising impressions on existing URLs, query reports with high impressions and weak pages, competitor gaps you can cover honestly, and sales or support questions that repeat in calls.

Why both lanes belong on one calendar

If decay work lives in a separate backlog owned by nobody, it loses every time a launch deadline appears. If opportunity work only happens during annual planning, you miss queries that spike in Q2. One calendar forces tradeoffs in the open: three refreshes and one new spoke this month, not four net-new drafts while decay piles up.

Pull Decay Signals From Search Console and GA4

You do not need a custom dashboard on day one. You need a repeatable export.

Search Console: page performance (last 90 days vs prior 90)

Export or note pages where:

• Clicks down 20% or more with stable or rising impressions (snippet or relevance issue)
• Impressions down and average position worsening (decay or competition)
• Impressions up, clicks flat, position 8 to 20 (visibility without traffic; often worth a content upgrade, not just a title tweak)

Our breakdown of impressions vs clicks in Search Console explains how to read those patterns without misdiagnosing the problem.

GA4: engagement after the click

Search Console tells you what happened in the SERP. GA4 tells you whether the page still helps after someone lands.

Flag URLs where engaged sessions, average engagement time, or key events (demo requests, newsletter signups, resource downloads) trend down quarter over quarter. A page can hold rankings while failing readers; that is still decay for planning purposes.

Qualitative decay flags

Add manual checks to your monthly review:

• Publish date more than 18 months ago on fast-moving topics
• Product or platform references that changed or shut down
• Internal links pointing to redirected or removed pages
• Comments or sales feedback that the post feels old

Export decay candidates to a spreadsheet: URL, primary query, click trend, position trend, engagement trend, suggested action (light, medium, merge), owner, target month.

Find Opportunity Signals Without Keyword Tool Overload

Opportunity research does not start with a 500-row keyword list. Start with questions your site almost answers.

Search Console query report

Filter queries with meaningful impressions where your average position is 5 to 25. Group by topic cluster. Ask: do we have one strong page for this cluster, or none?

Queries with position under 5 but no matching H2 on your best URL are often section-add opportunities, not new post opportunities.

Pages with strong CTR, low impressions

These are under-fed assets. The result converts when people see it; you need more internal links, cluster support, and sometimes a depth pass. They belong on the opportunity lane even though the URL already exists.

Hub gaps

Map your hub pages to child posts. Clusters with one pillar and no spokes are calendar gaps. Clusters with three overlapping spokes are merge candidates. Both show up in the same planning doc.

Voice-of-customer inputs

Support tickets, sales call notes, and community questions validate search data. A query with 40 impressions might still be worth a post if every demo asks it. Tag those as opportunity rows with source noted so writers trust the brief.

Score and Prioritize: A Simple Framework

Without scoring, every row in the spreadsheet feels urgent. Use a lightweight model your team can explain in a standup.

Variables that matter

• Business value: pipeline influence, product tie-in, strategic priority (score 1 to 3)
• Traffic at risk or available: current clicks or impression trend (1 to 3)
• Effort: light refresh vs new post vs merge project (inverse score: 3 for light, 1 for heavy)
• Confidence: how sure you are the fix matches intent (1 to 3)

Multiply or sum into a priority score. Sort decay and opportunity rows separately, then merge into one ranked list. Adjust manually for hard deadlines, but do not skip the sort. The point is to make tradeoffs visible.

Action types to assign

Signal	Likely action	Calendar slot
Clicks down, position still top 5	Title, meta, stat refresh	Light decay (1 to 2 days)
Position sliding, engagement down	Medium refresh, new examples, internal links	Decay sprint (3 to 5 days)
Two URLs same intent, both weak	Merge and redirect	Decay project (1 to 2 weeks)
Query cluster, no URL	New spoke post	Opportunity (1 to 2 weeks)
High CTR, low impressions	Interlink, expand sections	Opportunity light (2 to 4 days)

Cap how many heavy projects run at once. Two medium refreshes and one new post per month beats five half-finished drafts.

Build the Calendar: Monthly Rhythm

A data-driven editorial calendar is a living doc tied to a monthly pull, not a PDF you print in January.

Week 1: Data pull and scoring

One owner exports Search Console and GA4, updates the decay and opportunity tabs, and publishes a ranked top 20 list. Marketing, SEO, and content leads review for 30 minutes. Decisions: what ships this month, what waits, what needs dev or design.

Week 2 to 3: Production

Writers work from briefs that include the data row: target query, trend screenshot, action type, internal links required, success metric. Editors verify the fix matches the signal (do not rewrite a whole post when the data called for a title test).

Week 4: Publish, index, note baseline

Ship changes, request indexing for material updates, record baseline clicks and engagement. Set a 4 to 8 week check date on each row.

Quarterly: Rebalance lanes

Review whether you overweighted new content. If decay rows keep rolling forward, shift next quarter to 60% defense, 40% offense unless leadership overrides with a launch. Living content teams treat this rebalance as normal, not a failure of creativity.

What the Calendar Doc Should Look Like

Keep one spreadsheet or Notion database with tabs or views:

1. Decay backlog (sortable by score)
2. Opportunity backlog (sortable by score)
3. This month (committed work with owners and dates)
4. Done (with before and after metrics filled in at check-in)

Columns worth keeping: URL, cluster or hub, action type, primary query, score, owner, status, baseline clicks, check date, outcome notes.

Link the doc from your content analytics metrics review so numbers and assignments stay in one conversation.

Balance New Content With Refreshes

Leadership often asks for net-new posts because they are easier to announce. Data-driven calendars make the tradeoff explicit.

A practical split for B2B marketing sites with a mature blog: roughly 50 to 70 percent of monthly capacity on decay and opportunity fixes, 30 to 50 percent on net-new posts. Adjust when you are building a new hub from scratch or when decay backlog is finally clear.

When someone requests a new post, ask which opportunity row it replaces or whether it outranks a decay URL on score. That single question prevents calendar creep.

Common Mistakes When Planning From Data

• Chasing impressions without intent. High impressions on irrelevant queries inflate the opportunity list. Filter for queries that match your offer.
• Treating every decline as decay. Seasonality and SERP feature changes move charts. Compare year over year when you can.
• Skipping merges because redirects feel scary. Two weak posts often hurt more than one consolidated URL.
• Only refreshing intros. Body content, stats, and internal links carry most of the decay signal.
• No success metrics on calendar rows. If you cannot name what should improve, the task is not ready for a writer.
• Resetting the calendar after every leadership fire drill. Protect at least 40% of capacity for decay and opportunity work tied to data.

Connect the Calendar to Living Content

An editorial calendar driven by decay and opportunity data is the operational layer of a living content strategy. You are not publishing once and hoping. You are measuring, choosing the next task from evidence, and closing the loop when metrics move.

Teams that adopt this rhythm spend less time debating what to write and more time shipping fixes that compound. New posts still matter, especially for gaps your library never covered. They matter more when they are not stealing capacity from URLs that already earn traffic.

Turn decay and opportunity data into a calendar your team will actually use

The goal is not a prettier spreadsheet. It is a short, ranked list each month that mixes refreshes and new topics based on what Search Console and analytics show, not what felt urgent in a meeting. If you want help building that queue for your site, we pull decay and gap signals from your data, score URLs against your hubs, and hand you a 90-day editorial plan your writers can execute.