Evergreen Content vs Timely Content: Choose by Decision Half-Life

Evergreen content is material whose central answer remains useful and accurate long after publication. Choose it when a reader could make the same sound decision months or years from now. Choose timely content when the correct answer depends on a current event, release, date, or fast-changing condition. The useful test is the decision’s half-life: how long the recommendation survives before material change makes it misleading.

Ahrefs defines evergreen content as content that remains relevant beyond its original publication date and sits on a topic with consistent, lasting demand. Semrush’s definition adds an operational condition: the page should need relatively few updates to keep providing value. Together, those definitions make evergreen a property of both demand and accuracy. A stable question is not enough if the answer keeps changing.

There is no accepted formula, minimum number of months, universal refresh interval, or correct evergreen-to-timely portfolio ratio. Decision Half-Life is a qualitative editorial heuristic introduced in this article, not a standard SEO metric. It means the expected time until enough of a recommendation’s assumptions change that a responsible editor would materially revise the answer. It is not the time until traffic falls by half, and it should not be converted into a decay equation without longitudinal data and a defined model.

That boundary matters because a numerical-looking label can create false precision. If a team has no evidence about how often prices, policies, interfaces, buyer needs, or accepted practices change, it does not know that a decision has a six-month half-life. It knows only which dependencies could invalidate the answer. Start there.

Evergreen, timely, trending, and seasonal are different contracts#

These labels describe how usefulness behaves over time. They do not describe a channel or format.

Semrush separates seasonal, trending, and evergreen patterns: seasonal interest rises and falls around recurring periods, trending attention spikes and fades, and evergreen demand persists over time. Seasonal content is therefore not strictly evergreen. It may be reusable every year, but a reader arriving outside the relevant window—or after dates, offers, and conditions have changed—does not receive a continuously current answer.

Format does not settle the classification either. A glossary definition can be timely if a regulator has just changed the term. A how-to guide can decay quickly if it documents a frequently redesigned interface. A dated case study can remain useful as evidence of a method, but its results do not become a current benchmark. A buyer guide may look like a durable reference while prices, features, and availability give its recommendation a short decision half-life.

The Decision Half-Life test#

Choose the content contract by testing the answer the reader needs—not by asking how long the team hopes the page will attract traffic.

1. Write the reader’s decision as one sentence#

Replace the topic noun with an action. “Customer onboarding” is a subject. “Choose the first three onboarding steps for a self-serve product” is a decision. “Reporting regulation” is a subject. “Determine which reporting requirement applies this quarter” is a decision.

This step exposes whether time is part of the answer. If the sentence needs words such as “today,” “this year,” “after the release,” “under the current policy,” or “before the event,” assume timely until evidence shows otherwise.

2. Separate the stable core from volatile dependencies#

List what must remain true for the recommendation to be sound. Common dependencies include:

• laws, policies, standards, and official guidance;
• product features, interfaces, integrations, prices, and availability;
• current research, benchmark data, and market conditions;
• event dates, deadlines, seasons, and campaign windows;
• audience knowledge, organizational constraints, and the next action available to the reader.

Then mark the stable core. A principle can survive while its examples decay. A method can remain useful while the recommended tool changes. A recurring question can persist while the correct answer is different every month. This separation is what makes a hybrid treatment possible.

3. Name the event that would force a rewrite#

“Review annually” is a calendar reminder. “Review when the cited standard changes” is an invalidation trigger. The second is tied to correctness.

Useful trigger questions include:

• What new fact would reverse or materially narrow this recommendation?
• Which source is authoritative enough to force a change?
• Could a reader be harmed, delayed, or sent to the wrong action if this page stayed unchanged?
• Would a small factual update restore accuracy, or would the conclusion need to be rewritten?

The last question distinguishes maintenance from expiration. If a link, example, or screenshot can be replaced while the central answer survives, the page can remain evergreen. If the event changes what the reader should decide, publish a timely update or revise the page’s core claim.

4. Choose the treatment before drafting#

Google offers a clean real-world contrast in its explanation of freshness-sensitive search results. A query about current tax brackets calls for recent information because the applicable figures change. An explanation of why the sky looks red at sunset rests on a much more stable answer, so the newest page is not automatically the most useful. The surface format could be identical; the decision half-life is not.

5. Assign the maintenance contract#

Record six fields with the brief:

This is the practical payoff of the framework. The classification becomes a promise about stewardship rather than a hopeful label in a content calendar.

A worked classification without a fake formula#

Consider four proposed assets. These are illustrative editorial cases, not performance forecasts or real company data.

The second row is where teams often misclassify content. Search demand for “best” or “compare” queries may persist for years, but persistent demand does not make an individual recommendation evergreen. If the decision inputs change every month, the page has an expensive maintenance contract even when its URL is durable.

The reverse mistake also happens. A page can contain a publication date and still preserve a useful core. A research report may remain valuable as historical evidence if the page states its period and does not present old findings as today’s norm. The date reduces ambiguity; it does not automatically destroy usefulness.

When to build a hybrid instead of choosing one side#

Many B2B topics contain a stable question and unstable evidence. Forcing the whole subject into one bucket either makes the evergreen page brittle or makes the timely stream repetitive.

Use a layered structure:

1. Evergreen core: Define the concept, explain the stable method, state durable decision criteria, and document the evidence boundary.
2. Volatile modules: Isolate current prices, interfaces, regulations, benchmarks, availability, and dated examples so they can be reviewed without rewriting the whole page.
3. Timely updates: Publish event-specific analysis when a material development changes what a reader should do now.
4. Explicit links: Connect the update to the durable explanation and revise the core only when the development changes its central answer.

This structure avoids two bad outcomes. The first is a permanent guide filled with decayed facts. The second is a series of news reactions that repeatedly explain the same fundamentals before reaching the actual change.

Do not silently replace a dated analysis with a different conclusion and pretend the historical article always said it. Preserve the original event context where it matters, publish a correction or revision record, and point readers to the current governing answer. Evergreen maintenance is not permission to erase provenance.

How to create evergreen content that deserves maintenance#

Evergreen content begins with a recurring need, not an evergreen-looking format.

Verify the demand pattern#

Use customer questions, support evidence, sales conversations, site search, and search research to confirm that the need recurs. Google Trends can add temporal context: its comparison tools show current interest against preceding periods and historical lines, which can help distinguish a sustained pattern from an unusual spike or a recurring seasonal cycle.

Interpret the chart carefully. Google explains that Trends uses a sampled dataset and normalizes interest from 0 to 100 within the selected time and location. It is relative interest, not absolute search volume, a scientific poll, or an evergreen score. A flat line does not prove the answer is stable, and a spike does not explain why people searched.

Answer the recurring question before adding scope#

An evergreen page must still be a good answer now. Open with the definition, decision, or method the reader came for. Then add the evidence, constraints, examples, and next action needed to use it. Longevity cannot rescue a vague answer.

Google’s people-first content guidance offers the right quality boundary: the intended audience should leave feeling that it learned enough to achieve its goal. The same guidance warns against changing page dates when the substance has not changed. A current timestamp cannot make an inadequate page useful.

Design volatile facts for replacement#

Place dated statistics, screenshots, product behavior, policy language, and market examples in clearly bounded passages. Cite the governing source near the claim. Record when the source was accessed and what it supports. If a volatile fact is not necessary to the central explanation, omit it rather than creating a maintenance burden for decorative specificity.

Good evergreen candidates commonly include stable how-to guides, tutorials, definitions, foundational explainers, and tools built on durable methods. Those are candidates, not guarantees. A tutorial tied to a changing interface and a calculator tied to changing policy can both have short decision half-lives.

Set a review trigger before publication#

The owner should know what to watch and what action follows. A trigger might be a cited source revision, product release, legal or policy change, broken destination, superseded dataset, changed audience question, or evidence that the page now leads readers toward the wrong next step.

Without an owner and trigger, “evergreen” often means the maintenance cost has been hidden rather than removed.

Why evergreen content matters—and what it cannot promise#

A useful evergreen asset can answer the same recurring question for successive readers, require fewer updates than fast-changing work, and spread its production cost over a longer useful life. Semrush identifies lower maintenance and extended traffic as potential benefits. The careful word is potential: durable accuracy does not guarantee discovery, ranking, links, conversion, or revenue.

HubSpot provides a bounded example of the traffic pattern marketers often hope for. It defines a compounding post as one whose ongoing organic traffic eventually exceeds its initial publication traffic and reported that 14% of its own posts met that condition after twelve months. That result describes one publisher, one archive, and HubSpot’s own definition. It is evidence that compounding can occur, not a benchmark for another company or a reason to classify every slow-growing page as evergreen.

The distinction between durability and performance prevents two false conclusions:

• An evergreen page with no meaningful audience can remain accurate and still produce little value.
• A timely page can be highly valuable within a short decision window even though its traffic later falls.

Evaluate each against its contract. A timely analysis should reach the right audience while action is possible and preserve a clear cutoff afterward. An evergreen asset should remain accurate, useful, discoverable, and connected to a real reader journey over a longer horizon. Comparing only first-week traffic rewards urgency; comparing only lifetime traffic penalizes work designed for a deadline.

How often should evergreen content be updated?#

Review as often as the answer’s dependencies can materially change; update when the substance requires it. There is no universal cadence.

Ahrefs’ maintenance guidance makes the volatility difference explicit: foundational concepts may need changes only when examples or statistics age, while software comparisons, financial products, and other fast-moving subjects require much more frequent attention. This is a reason to estimate maintenance before commissioning the page, not a fixed schedule to copy.

At each review, choose one action:

• Keep: The central answer, evidence, links, and next action remain sound.
• Update: The central answer survives, but a source, fact, example, link, or module has aged.
• Revise: A material change alters the recommendation or its boundaries.
• Split: The stable core remains evergreen, but a development deserves a dated update of its own.
• Retire or redirect: The need, answer, or next action no longer exists, and preserving the page would mislead readers.

Record what changed. Google Search Central specifically cautions against changing dates merely to make pages appear fresh. A meaningful refresh corrects or improves the substance; a timestamp-only edit obscures the page’s real evidence age.

Traffic decline can trigger investigation, but it is not proof that the facts expired. Check whether demand changed, intent shifted, competitors supplied a better answer, distribution weakened, the page became technically inaccessible, or the recommendation itself aged. Maintenance should restore usefulness, not perform freshness theater.

Choose the portfolio by decisions, not a universal ratio#

There is no evidence-based percentage of evergreen and timely content that every team should publish. The right mix follows the decisions the audience repeatedly makes, the dated developments it must respond to, and the team’s ability to maintain both.

Start with the smallest coherent system:

• create a durable answer for a recurring, strategically relevant question;
• publish timely work when a real development changes what the audience should know or do;
• use seasonal editions when relevance returns in a predictable window;
• connect timely updates to the stable core instead of duplicating it;
• reserve maintenance capacity for the dependencies each asset introduces.

If the audience’s important decisions change weekly, a mostly evergreen calendar may look efficient while failing to be current. If the audience repeatedly needs the same foundational explanation, a stream of timely posts may create attention without a durable place to learn. Classification should reduce that mismatch.

The final call is plain: choose evergreen content when the central decision should survive the calendar; choose timely content when the date, event, or current condition is part of the answer. When the core is stable but the evidence moves, build a maintained evergreen core with bounded timely updates.