How to Measure Content Decay (GSC + GA4 Signals)

You do not need a new dashboard to know a post is aging. You need a repeatable way to read Search Console and GA4 together, compare the same URL over time, and decide whether a drop is decay, seasonality, or something else. That is what how to measure content decay comes down to: a short export workflow, a handful of thresholds, and a review cadence your team can actually keep. We will walk through a concrete 30-minute GSC pass first, then layer GA4 signals so you are not refreshing pages based on clicks alone.

This guide is the measurement spoke in our content decay cluster. If you want symptom checklists, read our post on signs of content decay in blog articles. If you need help deciding whether a metric points to decay or growth, use the framework in content metrics decay vs growth. Here we focus on the numbers, the export steps, and when to flag a URL for review.

What measuring content decay actually means

Content decay is not a single metric. It is a pattern: a URL that used to earn meaningful search visibility and onsite engagement is losing ground relative to its own history and to competing pages on the same topic. Measuring decay means tracking that pattern with enough consistency that you can separate a real slide from a quiet week or a seasonal dip.

Teams often jump straight to rewriting when traffic falls. That wastes time when the issue is a tracking change, a redirect, or a query that was never yours. Measurement gives you a defensible reason to refresh, pause, or leave a page alone. It also creates a shared language between SEO, content, and leadership: this URL missed three thresholds across two quarters, so it enters the refresh queue.

Decay is different from a page that never worked. A post that peaked at 40 clicks a month and drifts to 12 is decay. A post that never left page three is a prioritization question, not a refresh emergency. Your measurement system should compare each URL to itself over time, not to site-wide averages that hide individual stories.

Think of measurement as the front door to your content decay monitoring workflow. The workflow tells you what to do after you flag a page. This post tells you how to flag it in the first place.

Set baselines before you measure decay

You cannot measure decay without a “before.” For each URL you care about, capture a baseline row: publish date, last substantive update, primary query cluster, and a 90-day GSC snapshot (impressions, clicks, CTR, position). Store baselines in the same spreadsheet as your monthly exports so new reviewers inherit context.

Baselines also stop you from overreacting to young pages. A six-month-old article with soft month two is still finding its level. A three-year-old pillar with six soft months in a row is a different conversation. Age alone does not equal decay, but age plus declining slopes on the same query set usually does.

If you have never done this before, spend the first month building baselines only. No refreshes. Just exports, notes, and thresholds. Month two is when flags start to mean something.

Why GSC and GA4 together (not either alone)

Search Console tells you how Google shows your pages and whether people click. GA4 tells you what happens after the click. Decay can show up in one channel before the other, and that timing matters.

A page can hold impressions while CTR and clicks fall. That often means the SERP or your snippet is the problem, not the body copy. A page can keep clicks while engagement rate and average session duration slide. That can mean the content still ranks but no longer satisfies intent. You only see the full picture when you line up GSC trends for the URL with GA4 landing-page behavior for the same path.

We are not asking you to build a warehouse. For most B2B blogs, a monthly spreadsheet with 90-day GSC exports and matching GA4 landing-page rows is enough to start. The goal is comparability week over week, not perfect attribution.

Your 30-minute GSC export workflow

Start here every month. Block 30 minutes, pull the same report shape each time, and you will spot decay faster than any tool that promises automation without context.

Step 1: Set the date range and comparison

In Google Search Console, open Performance → Search results. Set the primary range to the last 90 days. Turn on the comparison period (previous period or year over year, depending on how seasonal your topics are). Ninety days smooths weekly noise; comparison keeps you from misreading a holiday dip as decay.

Step 2: Export by page

Switch the dimension to Pages. Export the table. You want every URL with meaningful impressions, not just top ten. In the spreadsheet, keep impressions, clicks, CTR, and average position. Add a column for URL path so you can join to GA4 later.

Step 3: Export by query for flagged URLs

Sort the page export by largest negative change in clicks or impressions. For the top 20 movers, go back to GSC, filter to each URL, switch dimension to Queries, and note whether the drop is broad (many queries down) or concentrated (one head term lost). Broad drops often point to content or competitive decay. Single-query drops may be SERP feature or intent shifts.

Step 4: Record position alongside CTR

Before you label anything decay, read position. A URL that lost clicks but gained position on fewer impressions is not the same as a URL that lost clicks because it slid from position 4 to 11. Our guide on impressions vs clicks in GSC walks through that distinction in detail. Measurement depends on it.

Step 5: Save the file with a date stamp

Name the export so you can stack months: gsc-pages-90d-2026-07.csv. Next month, you compare against this file, not against memory. Decay is a slope, not a snapshot.

Step 6: Highlight URLs that share a template

If you run programmatic hubs or repeated page types, group URLs by template before scoring. A decay pattern across five city pages points to a structural refresh. A single outlier may be local competition or a bad merge. Grouping saves you from treating systemic decay as five unrelated one-offs.

GSC metrics that signal decay

Search Console gives you four numbers that matter for decay measurement. Use them as a set.

• Impressions: Falling impressions on queries you care about usually mean Google is showing you less often. That can be competition, freshness, or relevance drift.
• Clicks: The traffic you actually received. Clicks down with impressions flat often pairs with CTR or position problems.
• CTR: Clicks divided by impressions. Compare CTR to position bands, not site averages.
• Average position: Context for the other three. Position worsening over 90 days while impressions hold is a classic early decay signal.

In practice, we flag a URL when two or more of these move the wrong way for two consecutive monthly reviews, and the query set matches the page intent. One bad week is noise. Two months of sliding position on your target cluster is worth a row in your refresh backlog.

GA4 metrics that confirm onsite decay

After GSC flags a URL, open GA4 → Reports → Engagement → Landing page (or Explorations if you prefer a custom table). Filter to organic search and match the path from your GSC export.

• Sessions from organic search: Should trend with GSC clicks. Large gaps may mean tracking or URL variants.
• Engagement rate: Are people scrolling and staying, or bouncing fast? Engagement falling while rankings hold suggests the page no longer matches what searchers want.
• Average engagement time: Shortening time on page for the same query set is a soft decay signal, especially on educational posts meant to be read.
• Key events: If the post feeds demos or newsletter signups, decay often shows up in event rate before raw traffic collapses.

GA4 will not diagnose decay by itself. It confirms whether search losses reflect real dissatisfaction or a snippet problem sending the wrong visitors.

Aligning date ranges between GSC and GA4

Use the same 90-day window in both tools when you compare. GSC and GA4 process dates differently near time zones and property boundaries, so match on calendar weeks rather than obsessing over single-day deltas. Export GA4 landing-page data with session source/medium filtered to google / organic.

When GA4 disagrees with GSC

If GSC clicks are down but GA4 organic sessions are flat, check for query drift (you lost low-intent impressions but kept high-intent clicks), tracking filters, or URL canonical issues. If GSC is flat but GA4 engagement collapses, your rankings may still look fine while the content fails readers who arrive from other channels. Both patterns deserve investigation, but they lead to different fixes.

Worked example: one URL across two quarters

Imagine a B2B analytics post that peaked last year at 180 monthly clicks from organic search. In Q1 this year, your 90-day GSC export shows impressions flat, position sliding from 5.2 to 8.4 on its main query cluster, and CTR down from 3.1% to 2.0%. Clicks fell about 25%. That is two GSC flags: position and CTR/clicks.

You open GA4 for the same path. Organic engagement rate dropped from 58% to 41% quarter over quarter, and average engagement time fell from roughly two minutes to under 90 seconds. That confirms onsite decay, not just a SERP blip.

You check year-over-year GSC for the same quarter. Last year’s numbers were stronger, so seasonality is unlikely. You check the signs of decay checklist: outdated examples, thinner SERP competition, and a newer competitor guide align with what the data shows. The URL earns a high decay score and enters the refresh queue with a note: update examples, expand measurement section, revisit title for CTR.

That story took about 35 minutes with saved exports. Without measurement, the team might have debated whether the post “still looked fine” because impressions held.

Metric thresholds and review cadence (reference table)

Use this table as a starting point. Tune thresholds to your site size and volatility. Small blogs can use tighter bands; large sites may need percentile ranks instead of fixed percentages.

Metric	Source	Example threshold	Review cadence
Impressions (target queries)	GSC	Down 15%+ vs prior 90 days	Monthly
Average position (target queries)	GSC	Worse by 3+ positions vs prior 90 days	Monthly
CTR at stable position	GSC	Down 20%+ relative with position within 1 spot	Monthly
Clicks	GSC	Down 20%+ vs prior 90 days on URLs with 100+ prior clicks	Monthly
Engagement rate (organic)	GA4	Down 10+ percentage points vs prior quarter	Quarterly
Avg engagement time (organic)	GA4	Down 25%+ vs prior quarter on key landers	Quarterly
Portfolio impression share	GSC	Top 50 URLs: count how many missed any monthly threshold	Quarterly

Weekly reviews are for active campaigns or pages you are already refreshing. Monthly is the right default for decay measurement on most B2B blogs. Quarterly zoom-outs keep you from chasing noise and help you report trends to leadership.

How to tell decay apart from seasonality

Seasonality repeats. Decay drifts. The easiest test is year-over-year comparison in GSC for the same 90-day window. If July 2026 looks like July 2025, you likely have seasonality. If this July is materially below last July on the same query set, treat it as decay until proven otherwise.

Also check whether the drop is site-wide or URL-specific. A site-wide organic slide may be a technical issue, a Google update, or brand demand. A single URL sliding while siblings hold steady is classic content decay or cannibalization.

Finally, read the query list. If you lost one informational variant but kept commercial queries, the page may need a section added, not a full rewrite. Measurement should capture query-level detail, not just URL totals.

Build a simple decay score per URL

Once exports are routine, give each priority URL a lightweight score so refreshes sort themselves.

1. Traffic weight: Prioritize URLs that historically drove clicks and conversions, not long-tail pages with ten impressions.
2. GSC flag count: How many thresholds did it miss this month? Impressions down, position worse, CTR soft at stable rank = three flags.
3. GA4 confirmation: Add a point if engagement or time on page fell quarter over quarter.
4. Business value: Boost score for pages tied to pipeline, product education, or hub links.
5. Age and last refresh: Pages untouched for 18+ months with two bad months rank higher than recently updated posts.

Sort by score descending. That list is your refresh queue input. The decision matrix for whether a metric means decay or growth lives in our decay vs growth post; do not duplicate that table here. Use it when a flagged URL could still be a growth opportunity on a adjacent query.

What to do after you measure (without skipping diagnosis)

Measurement should end in one of three outcomes: refresh, monitor, or no action. Refresh when GSC and GA4 agree something is wrong and the page matters. Monitor when GSC flickers but GA4 is stable, or vice versa. No action when year-over-year is flat and engagement holds.

Document the decision. A one-line note in your spreadsheet (“July: position 4→7 on ‘content decay metrics’, engagement stable, monitor”) beats a debate next month about whether the page was already flagged.

When you are ready to operationalize, pair this post with our monitoring workflow for cadence, owners, and handoffs into editorial calendar updates.

Who should own decay measurement

Decay measurement fails when it is “SEO’s spreadsheet” that content never sees. Assign one owner to pull exports (often SEO or analytics), one to interpret flags against editorial priorities (content lead), and a monthly 30-minute review on the shared queue.

SEO owns GSC accuracy, filters, and query notes. Content owns whether a flagged URL still supports the strategy. Leadership cares about how many high-value URLs are decaying quarter over quarter, not about every long-tail post.

Document the ritual in your monitoring workflow so vacations do not reset the habit. The measurement is only as good as the calendar invite.

Common measurement mistakes

These catch experienced teams:

• Refreshing on one metric. Clicks down alone might be CTR or seasonality. Require a pattern.
• Ignoring position. Decay measurement without position context creates false alarms.
• Comparing unlike URLs. Benchmark hubs against hubs, spokes against spokes.
• Using 7-day windows. Too noisy for B2B. Default to 90 days with comparison.
• Skipping GA4. Search losses from snippet issues should not trigger full rewrites.
• Never closing the loop. After refresh, re-run the same export to see if thresholds recover.

Turn decay measurement into a refresh plan

Measuring content decay is how you stop guessing which old posts deserve budget. The 30-minute GSC export, GA4 confirmation, threshold table, and monthly cadence give you a defensible queue. Signs tell you what decay feels like in the wild; this framework tells you when the data agrees.

If you want help running the exports, scoring your library, and turning flags into a prioritized refresh plan, we do that as part of content analytics engagements. The next section links to request a content refresh audit so you can see where decay is costing traffic you already earned.