Evergreen Content

Before the term existed, content teams were managed by publishing count. Someone counted how many pieces went out this month, and a rising count read as a healthy team. Then teams that doubled their output kept reporting the same visitor numbers as before.

The cause was usually what they had written. A launch announcement, an event recap, a release note — a piece about a moment gets read by 3,000 people in its first three days and by five people a day a month later. Stack up only those and this month's traffic has to be manufactured entirely by this month's posts, so publishing one piece fewer means that much less traffic.

Planning meetings kept circling the same spot. Ravi would say the team shipped eight pieces last month and traffic came in flat against the month before, and next month's plan would become ten pieces. Count was the only dial anyone could see.

Evergreen content renames that problem: it's about lifespan, not volume. The question stops being how much you published and becomes how long each piece keeps working.

You pick a question people will still be searching a year from now, publish the piece that answers it, and collect traffic for as long as that piece sits near the top of the results.

It starts with keyword research, the work of finding the phrases people actually type into a search box. What you choose there decides the lifespan. "How to write meeting notes" gets searched about as often this month as it did three years ago. "New document tool features in 2026" gets searched for one half of one year.

Three checks tell you whether a chosen question will last.

1. Does the question stay the same? Ask whether someone in the same situation will type the same words a year from now. As long as the way people work doesn't change, meeting notes stay a problem.
2. Does the answer stay the same? A piece that walks through one specific product's screens becomes wrong the day that product redesigns them.
3. Is it a question people search at all? Some things people wonder about they ask the person next to them instead of typing into a search box, and those bring no traffic.

Once the topic is set, search intent — the kind of result someone wants when they type a given query — decides the shape of the answer. Someone searching "how to write meeting notes" is waiting for an explanation of the method, not a product pitch. Publish something that misses the intent and visitors leave immediately, and that signal accumulates until the ranking drops.

Traffic accrues the way a savings deposit does. A timely piece spends what it earns in the month it goes out. An evergreen piece earns again this month for work done last month, and this month's piece stacks on top of it. A guide to meeting notes on the Pagedeck blog drew 200 readers in its first month; six months on, it draws 150 a day.

It isn't the plant-it-and-forget-it kind. Run a periodic content audit — lining up everything published and reviewing how each piece performs — to find posts that still draw traffic but have gone stale, and rewrite those.

The most common home is a blog post written to earn search traffic. Those usually take one of four forms.

1. How-to — a piece like "how to write meeting notes" that walks through the steps of doing something. Tools change; the question survives them.
2. Concept explainer — a piece that unpacks one term used at work. A fresh batch of people hears that term for the first time every year.
3. Comparison — two candidates side by side with the differences laid out. The people searching this are standing at a decision, which puts it closest to paid conversion.
4. Templates and checklists — material readers take and use as is. It attaches easily to a lead magnet, something given away in exchange for a contact address.

There are places outside the blog. Help center articles, in-product guidance, and frequently asked question lists all share the character. Long-lived topics also travel well through content repurposing, which moves one piece into a short video or an email by changing only the format.

In content strategy it gets handled as a ratio. Deciding who to write for and on what topics includes deciding the split between evergreen and timely pieces. Pagedeck runs four evergreen pieces and two announcements out of six a month. Search engine optimization (SEO) effort gets concentrated on the first group. SEO means shaping titles and structure so a page surfaces more readily in search results, and effort spent on a piece that will be around for years keeps paying back.

"This one's going to be evergreen, so let's take two more days and do it properly."

A piece that will work for years justifies more effort up front.

"There's nothing evergreen on the blog, so the month we stop publishing, traffic stops too."

A diagnosis: every visitor arriving right now comes from something written that same month.

"This post is evergreen but the screens changed, so it's wrong as written. I'll add it to the refresh list."

Filing it as something to rewrite rather than something to retire.

At Pagedeck's quarterly content review, Ravi lays out last quarter's pieces next to their traffic curves. The top five still bring people in daily three months after publication; the bottom seven flatlined after the first week. That doesn't make the bottom seven bad. A feature announcement was written to be read on the day it went out, and it did its job.

What the meeting actually decides is the split between the two kinds next quarter. Mia joins because she knows the product release dates: in a month heavy with launches, the announcement count goes up and an evergreen piece slides to the following month.

The most common misreading is that a piece, once written, needs no further attention. The name comes from a tree that stays green on its own, which makes that easy to assume. In practice new answers to the same question keep getting published, and when product screens change the instructions inside the piece turn into wrong information. Left alone, a post that ranked first two years ago drifts to fourth and loses two-thirds of its traffic, while the people who do arrive read a description that doesn't match what they see. A long-lived piece isn't one that never dies; it's one that takes less upkeep.

"Then just write evergreen" comes from the same place. The traffic numbers favor it, but news about what the product shipped only reaches existing customers and the wider industry if someone announces it. The two aren't competing — they serve different readers.