Content Cull Marketing

A quarterly content cull removes posts that cost maintenance budget without generating pipeline. Most teams run it as a traffic exercise: sort by sessions, retire the bottom quartile, and repeat. According to the NinjaCat 2026 AI Maturity in Marketing Report, 81% of marketing teams have no content measurable movement framework, so most cull decisions have no attribution data behind them. A post with 200 monthly sessions that sourced two enterprise deals last quarter is worth keeping. A post with 4,000 sessions that has never touched an opportunity is the better retire candidate. The full per-post attribution framework lives at The 44% Gap: Per-Post Attribution. This spoke covers the quarterly cull decision: which posts to retire, which to consolidate, and which to keep regardless of their traffic rank.

Why do most content culls produce the wrong retirement list?

Traffic is not a proxy for business value. A post can rank well for a high-volume keyword that draws researchers, job seekers, and competitors who will never buy. Another post can rank for a narrow intent-specific term, pull 80 sessions a month, and introduce eight qualified accounts into the company's pipeline in that same period. Sessions count arrivals. They say nothing about what those arrivals did next.

A team that runs quarterly culls using only GA4 session data will systematically retire posts that underperform on vanity metrics and keep posts that outperform on them. If the attribution data shows the opposite correlation, the team is removing the wrong posts every quarter.

What traffic metrics measure and what they miss

Traffic measures reach. It does not tell you whether readers became contacts, entered a pipeline, or generated ARR. The gap between "someone read this" and "this post contributed to a deal" is where most content investment decisions fail. Harvard Business Review documented this directly: marketing teams systematically track campaign performance metrics while undertracking capability metrics, the indicators that reveal whether content processes are actually moving buyers.

The attribution-based alternative

Per-post pipeline attribution reads from the CRM opportunity record, not from analytics. It counts how many deals had the post as a first-touch source or an influenced asset, and it sums the ARR of those deals. That number is the post's actual return on investment, and it is the figure a content cull decision should start from, not session rank.

The two attribution questions before a retire decision

First: did this post ever source an opportunity (the account's first recorded marketing touch before a deal opened)? Second: did it ever influence one (appearing in the account's interaction history before close)? A post that answers "no" to both, across a full lookback window with a confirmed-intact UTM chain, is a retire candidate regardless of traffic. The mechanics of that wiring are in the pipeline attribution guide.

Which posts should land on the initial cull shortlist before you run attribution?

Not every post needs an attribution deep-dive. Some posts disqualify themselves from the keep column before you open the CRM. Build the shortlist first using data that is quick to pull, then run the attribution query only against that shortlist.

Posts that belong on the initial shortlist share at least one of three characteristics: organic traffic declined more than 25% year-over-year with no refresh scheduled, the topic targets an ICP the company no longer sells to, or the post addresses a problem the product no longer solves. These three signals are available in GA4 and a keyword tool without any CRM query.

Posts targeting buyers outside the current ICP

A company that shifted its ICP from SMB to mid-market may have dozens of posts targeting small business buyers. Those posts pull traffic from audiences who will not convert at the new deal size. They consume crawl budget and editorial maintenance. They belong on the retire shortlist regardless of traffic volume.

Posts with two or more consecutive quarters of traffic decline

Consistent traffic decline indicates keyword decay (the topic is losing search demand) or content decay (competitors published better answers and the post lost rank). Both are detectable without attribution data and both are grounds for closer review.

Building the shortlist in under an hour

Export GA4 data for all published posts: trailing-12-month organic sessions and year-over-year session change. Filter to posts where sessions declined by more than 25% and where the topic is outside the current ICP definition. That list, typically 15 to 25 posts for a team with 50 to 100 published articles, is the attribution plan queue. Every post on it gets the CRM query. Posts not on it do not need it this quarter.

How do you pull the per-post attribution data needed for the cull analysis?

The CRM report for a content cull has two components: sourced pipeline and influenced pipeline, grouped by post slug. Sourced pipeline is the ARR sum of opportunities where the post appears as the account's first-touch asset. Influenced pipeline is the ARR sum of opportunities where the post appeared anywhere in the account's history before the deal closed.

Both numbers come from a field on the Opportunity record. If that field is not yet wired, the per-post attribution wiring guide documents the setup: UTM tag on blog CTA links, form handler that writes the UTM to the CRM contact, and an automation that copies the contact field to the Opportunity on creation.

The CRM query structure

Filter Opportunities to Closed Won status. Set the close date to the lookback period (12 months is a sound quarterly cull default; shorter if your median sales cycle is under 60 days). Group by the first_touch_blog_post field on the Opportunity. Sum ARR per group. Export the results and join to your GA4 session data by post slug. You now have one row per post with sessions, year-over-year change, sourced pipeline, and influenced pipeline.

What to do when the attribution data looks empty

If the query returns zero pipeline for posts live 18 months or more, the most common cause is a missing contact-to-opportunity field copy. Revenue reports read the Opportunity; if no automation copies the Contact's attribution field to the Opportunity on creation, every opportunity starts with empty blog attribution regardless of UTM cleanliness. Run the three-step plan (UTM in the link, UTM written to Contact after a test form fill, Contact field copied to Opportunity) before treating zero as a confirmed retire signal. The first-touch vs last-touch guide also covers self-reported attribution, a fallback signal for posts where session-tracked UTM expired between a mobile read and a desktop conversion.

What signals confirm a retire decision?

A retire decision requires two confirmed signals, not one. Traffic decline alone is not grounds for retirement (the post may be pulling the right buyers in smaller numbers). Zero pipeline alone is not grounds for retirement (the attribution chain may be broken). Both conditions confirmed simultaneously, with a verified UTM chain, meet the retire threshold.

The retire test: organic traffic declined more than 25% year-over-year, the post has zero sourced and influenced pipeline across the full attribution window, and the three-step UTM plan confirms the zero is real and not a data gap.

Topic decay vs keyword decay

Topic decay means the business problem the post addresses is no longer a buyer priority. Keyword decay means the term is losing search volume industry-wide. Both produce traffic decline but call for different responses. Topic decay is grounds for retirement. Keyword decay may just require a refreshed H1 and updated statistics. Check Google Search Console: if impressions and clicks fell together, that is keyword or ranking decay. If impressions held and click-through rate fell, a meta description update is the intervention, not retirement.

When the topic is evergreen but the pipeline number is still zero

Forrester notes that sourcing metrics understate marketing contribution in complex B2B buying cycles. A post on a buying committee topic may influence deals through offline sharing that never appears in the CRM. If the topic is genuinely evergreen and the average deal size is large, survey recently closed accounts before retiring the post. Ask whether any team member read it during the evaluation process.

When to 301 redirect vs noindex

A 301 redirect retires the URL permanently and passes link equity to the destination. A noindex tag removes the post from search results while keeping the URL live for readers who have it bookmarked or linked externally. Use 301 redirect when consolidating two posts on the same topic into one canonical post. Use noindex for posts on topics you may refresh within 12 months (competitive comparisons, dated feature lists). Never delete a post URL without a 301 redirect in place first.

When does consolidate beat retire?

Consolidate applies when two posts compete for the same primary keyword, produce overlapping content, and would be stronger as one combined article than as two competing ones. The consolidate trigger: two posts targeting variants of the same keyword (for example, "B2B attribution models" and "marketing attribution models for SaaS"), with combined traffic below what one strong post should earn, and neither showing meaningful pipeline attribution.

Picking the canonical post

The canonical post is the one with stronger backlink authority and the cleaner URL structure. A backlink tool shows this directly. If both URLs are close in authority, prefer the post with the more durable slug (no year in the slug, no product name that might change). Redirect the weaker post to the canonical with a 301. For the attribution model implications of merging two posts, the multi-touch attribution guide covers how to handle URL transitions cleanly.

Preserving pipeline attribution through the merge

Before retiring the weaker URL, export its pipeline attribution record and document which deals it sourced or influenced. Add that credit to the cluster-level investment record before the redirect fires. A URL that disappears without this step makes those pipeline contributions unauditable in future reviews. Update every internal link pointing to the retiring URL before the 301 fires: letting a redirect carry internal equity adds crawl latency and costs ranking signal.

How do you execute the cull without an organic traffic penalty?

Execute the cull in batches of five to ten posts per week. A bulk retirement of 30 posts simultaneously, with no monitoring window between batches, can produce unexpected organic signal drops even when each individual decision is correct. Batching gives Google's crawlers time to process each wave and gives Search Console data time to reflect the change before the next batch fires.

301 redirect implementation order

For each retiring post: update all internal links first, implement the 301 in the route configuration, then submit the old URL in Google Search Console's URL Inspection tool to accelerate crawl. Monitor for 14 days before the next batch. In this codebase, retired post redirects belong in the BLOG_CULLED_REDIRECTS map in src/routes/pages/blog.ts.

Monitoring post-cull organic performance

Set a Search Console filter for the retired URL set. Monitor impressions and clicks for 30 days after each batch. A traffic drop on a 301'd URL that recovers on the canonical destination within 60 days is normal crawl processing. A sustained drop on both the retired URL and the canonical after consolidation points to a technical issue: redirect chain, canonical conflict, or a coverage error. When internal links from retiring posts previously pointed to other cluster spokes, update them to point to the cluster pillar at The 44% Gap: Per-Post Attribution. Centralizing internal equity at the pillar level compounds across the full editorial calendar in ways individual retirements obscure.

What should the quarterly content cull output look like?

The deliverable from a quarterly content cull marketing review is not a list of URLs to delete. It is a documented investment decision: content actions mapped to pipeline impact, in a format that holds up in a budget conversation.

A complete cull document has three sections. The plan data: post slug, trailing-12-month organic sessions, year-over-year session change, sourced pipeline, influenced pipeline, and decision (retire, consolidate, keep). The action log: what was retired, what was consolidated into what, and what was kept and why. The reinvestment brief: where the freed editorial capacity goes next.

The reinvestment brief

The reinvestment brief answers one question: which topic angles in the cluster deserve more editorial investment, based on what the attribution data showed about the posts you kept? If four of the top five pipeline-sourcing posts in the cluster share a specific question format or buyer stage, that format and stage deserve more spokes. The case study attribution guide is an example of a spoke built directly from attribution insight about which content format produces sourced pipeline.

Presenting the cull output to a CMO

According to 6sense's Science of B2B 2025, fewer than a quarter of marketing organizations report pipeline or revenue from priority accounts to their board. A cull document that maps retired posts to freed editorial capacity, and freed capacity to projected pipeline investment, speaks the language of a board conversation. That format is also the correct deliverable for an AI systems plan of a content program: where attribution data exists, decisions follow from it; where it does not, the plan identifies what infrastructure to wire first.

When the cull list exceeds 20 posts in a quarter

If the shortlist consistently exceeds 20 posts, the inventory growth rate has been too aggressive. The net-zero discipline (one post added for each one retired) is not in place. A quarterly cull that stays under ten retirements per pass signals the ICP gate, cannibalization check, and attribution gate are operating before each post ships, not just at quarter's end.

Methodology

This article describes the content cull marketing decision framework used in the Conversion System blog program, which applies per-post pipeline attribution data alongside traffic analytics to make quarterly retire, consolidate, and keep decisions. The framework assumes the attribution infrastructure described in the C4 cluster is in place: UTM tags on blog CTA links, a form handler that writes the first-touch UTM to the CRM contact, and an automation that copies the contact field to the Opportunity on creation.

The attribution queries described here read from the Opportunity record, not the Contact record, because revenue aggregates at the deal level in every CRM. The field schema and automation setup are documented in the per-post attribution pillar. The UTM capture implementation is the withUtm() helper in src/templates/shared.ts, verifiable directly in the repository.

Statistics cited: NinjaCat 2026 AI Maturity in Marketing Report (n=500+, 2026), 81% of marketing teams have no content measurable movement framework. Harvard Business Review, "Do Your Marketing Metrics Show You the Full Picture?" (April 2022), marketing teams systematically undertrack capability metrics. Forrester, "B2B Marketers: It's Time to Ditch Sourcing Metrics," sourcing metrics understate contribution in complex B2B buying. 6sense, "Science of B2B 2025," fewer than a quarter of marketing organizations report pipeline from priority accounts to their board.

The section budget formula: floor(2200/8) x 0.85 = 234 words per section cap across seven H2s plus Methodology. The content cull marketing process described here runs on any team with per-post attribution wired into their CRM and a quarterly editorial review.