Evergreen does not mean permanent. It means the topic stays relevant while the details go stale, which is a maintenance problem rather than a writing one.
Most guides on this cover how to pick evergreen topics and stop there. That is the easy half. The half that decides whether a large archive keeps earning is what you do with 200 pages that were accurate when published.
What actually makes a topic evergreen
| Evergreen | Decays fast |
|---|---|
| How something works | What is new this year |
| A process someone follows | A tool's current feature set |
| A decision framework | Pricing |
| Definitions and comparisons of concepts | Rankings and statistics |
| Problems tied to human behaviour | Anything tied to a platform's UI |
The test: will someone search this exact question in three years? If yes, the topic is evergreen and the details inside it are not.
The six things that kill an evergreen page
Prices change. Every tool you named has repriced since you published. A page quoting 2024 pricing in 2026 reads as abandoned.
Products die or get acquired. Named tools that no longer exist are the fastest way to lose a reader's trust, and the most common defect in any archive over a year old.
Screenshots go stale. An interface that no longer looks like that tells the reader the page is old before they read a word.
The SERP format shifts. A query that wanted a guide in 2024 wants a listicle now. The content is fine and the format lost.
Competitors publish better versions. Your page did not change. The bar did.
Internal links rot. Pages get merged, redirected or deleted, and the survivors point at nothing.
Only the first three are usually noticed. The last three cost more.
The refresh system
Tier 1, your top 20 pages by clicks. Review quarterly. These carry most of the traffic and a decay here costs more than any new page returns.
Tier 2, pages at position 8 to 20 with impressions. Review quarterly as well, but the work is different: these need a format and title decision, not a details update.
Tier 3, everything else with traffic. Annually, checking facts, prices and dead links.
Tier 4, pages with no impressions after twelve months. Do not refresh. Merge or delete. Refreshing a page nobody finds is the most common way content teams look busy.
What a refresh actually consists of
Not a rewrite. A rewrite loses the accumulated signals and takes four times as long.
- Verify every named product still exists, by loading it
- Update every price and statistic against the primary source
- Replace screenshots older than about a year
- Check the SERP still wants this format and this entry count
- Add anything genuinely new since publication
- Fix internal links to pages that moved, and add links to pages published since
- Update the visible date only when the content actually changed
That last one matters. Changing the date without changing the content is a pattern readers and search engines both recognise, and it is not worth the ten seconds it saves.
Building for refreshability from the start
The cheapest maintenance is the kind you designed out of the page.
Isolate the perishable parts. Put prices in one table rather than scattered through the prose, so updating them is a two-minute job rather than a re-read.
Avoid dates in the URL. A slug with 2025 in it needs a redirect every January or it dies on schedule.
Write the year into the title, not into the body. Titles are cheap to update. Twenty references to "this year" throughout the text are not.
Name fewer tools, describe them better. Every product named is a maintenance liability. Eight verified entries beat twenty half-checked ones on both quality and upkeep.
Link by topic, not by article title. Anchor text describing the topic survives the target being retitled.
What to automate, and what it cannot do
Automate the detection. Broken links, dead domains, pages with declining clicks, pages that lost position, and pages that have not been touched in a year. This is a scheduled job and it removes the hardest part of maintenance, which is knowing where to look.
Automate the linking. Adding links from new pages into old ones, and from old ones into new, is the maintenance task most reliably skipped and the one machines do best.
Automate the reporting. A monthly list of pages needing attention, ranked by traffic at risk.
Do not automate the verification. Whether a product still exists, whether a price is current and whether a claim is still true is a check against a primary source. A model asked to confirm its own earlier output will confirm it.
Do not automate the decision to delete. Merging and pruning changes what the site is about. It is a judgement call with consequences, and it should be made by someone who understands the business.
A workable annual rhythm
Every month: run the detection job, fix broken links, refresh the top five pages by traffic at risk.
Every quarter: review tier 1 and tier 2 properly. Re-check the SERP format for your ten most valuable queries.
Every year: audit the full archive, decide what to merge or delete, and re-verify every named product across the site. This is the entity check that catches the products that quietly stopped existing.
The ratio to aim for past 50 published pages is one refresh for every new post, rising to two per new post past 150. Most sites run zero, which is why archives that once worked stop working. Holding that ratio month after month is a scheduling problem, and our guide to blog content calendar automation covers how to run it.
Where a platform helps
Distribb publishes new content and keeps the internal links current as the archive grows, which handles the linking half of maintenance continuously rather than in an annual panic. The publishing side of that is our auto content writer, which takes the keyword and puts the finished article in your CMS.
Honest limitation: it does not audit your existing archive for stale facts, and it will not tell you that a tool you recommended two years ago has shut down. That check is manual, and on our own site it caught four products being recommended across live pages that either no longer existed or never had. Nobody should sell you an automated version of it.
See how the content platform handles publishing and internal linking together.
Related reading
For auditing an archive that has already drifted, see our guide to auditing automated content for SEO. For frequency, read how often you should blog for SEO, and for structure, topic cluster strategy.
FAQ
How often should evergreen content be updated? Top pages quarterly, everything else with traffic annually. Pages with no impressions after a year should be merged or deleted rather than refreshed.
Does updating old content help more than publishing new? Past about 50 published pages, usually yes. A page already at position 8 to 20 has relevance, links and history that a new page has to earn from scratch.
Should I change the publish date when I update? Only when the content materially changed. Date changes without content changes are recognisable and gain nothing.
How do I find what needs updating? Search Console, filtered to pages whose clicks fell against the previous 90 days, cross-checked against pages you have not touched in twelve months. That list is your queue, in order.