You find an article that answers exactly your question. Halfway through, it tells you to click a button the software no longer has.

The question is still useful. The answer needs work.

That’s the catch with evergreen content. You’re writing about something people will keep needing, rather than this week’s announcement. You still have to look after it.

Choose a lasting question

How do you prepare for a branding project? What should a website brief contain? How do you compare two approaches to a familiar business problem?

Those subjects can remain useful even as the examples and tools change.

A product launch, a temporary offer and this month's platform interface have different lifespans. They can still be worth publishing. They simply require a different maintenance plan.

Do not force every subject into an evergreen label. Choose the role of the content first.

Write something substantial enough to keep

A lasting topic does not make a generic answer useful.

Explain the actual decisions, trade-offs and exceptions. Use examples that help someone apply the idea. Include the information you repeatedly find yourself explaining in conversations.

Google's helpful-content guidance asks publishers to consider whether material provides original analysis and substantial value. It also warns against changing dates merely to make unchanged content seem fresh.1

That is good editorial discipline regardless of which search engine sends the next visitor.

Decide what could go out of date

A technical tutorial may need checking when a platform changes. A pricing guide needs checking when the offer changes. A professional opinion may need context rather than a complete rewrite.

Record what could become outdated and where the underlying evidence comes from. Give someone responsibility for checking it. A simple editorial record can name the article's purpose, the change that should trigger a review and the person who will make it.

Check links, examples, screenshots, references and calls to action as well as the main body. When a service changes, review the articles that describe it then, rather than wait for the next publishing slot.

A reliable article about website planning can be undermined by a closing paragraph promising a service the business no longer sells.

Update, combine or retire deliberately

Keep the original publication history. Update substance when necessary and record a genuine modification when the approved revision is published.

When two articles answer the same question, review whether one stronger page would serve readers better. Check what people use, what other pages link to and whether important material would be lost before proposing consolidation.

Read it before deciding. A well-explained idea may need a new example or corrected link, not a completely different article. An old announcement may still be a useful historical record; it doesn't need to masquerade as current advice.

Changing the date without improving anything helps nobody.

Make the knowledge usable in more than one place

A good guide can support a sales conversation, answer a recurring enquiry or provide an introduction to a more detailed publication.

For businesses with research libraries, the same thinking applies to reports and whitepapers. Preserve the approved record, decide what can be updated, and choose the appropriate reading experience. Public previews can introduce a topic while full material remains available through the agreed access process.

Do not rewrite a dated research finding as though it was collected yesterday. Sometimes the most useful update explains what has changed since the original work.

Look through the articles you already have before adding ten more. Which questions still come up? Which explanations would you be comfortable sending to a client today? Start there, and fix the parts that would make you hesitate.