Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Writing desk

Evergreen SEO

I used to think evergreen content required zero maintenance, but now I refresh every page annually and choose topics with stable intent to avoid wasted effort.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

What I’d do first

  • Audit your existing content for topics with stable search demand and refresh them before creating new pages.
  • Choose a topic with a flat or gradually growing search volume trend, not a spike that will fade.
  • Build a content hub with a pillar page linked to supporting articles to pass authority and cover subtopics.
  • Set a quarterly reminder to review each evergreen page for outdated statistics, broken links, and shifting intent.
  • Write for the reader first: clear explanations, step-by-step logic, and useful examples beat keyword stuffing every time.

The path I'd take

I start with recurring problems, not with keyword volume. Customer support logs, forum threads, and the search queries that already drive traffic to your site are the richest veins. For a client selling car tyres, the question "how to change a tyre" appeared in support tickets three times a week. I ran it through Ahrefs: 2,200 monthly searches in the UK, a flat trend over three years, and a keyword difficulty of 18. That is a green light. I built a hub: a pillar page titled "How to Change a Tyre: Complete Guide" with step-by-step instructions, and cluster pages for jack placement, torque specifications, and safety checks. Within six months the pillar page ranked number one for the main query and drove 80% of the hub's organic traffic. The decision rule is simple: if the topic has a clear how-to or definition intent, search volume at least 200 per month, and a stable trend, I invest. I avoid topics where intent is mixed — "SEO tools" can be a listicle, a comparison, or a tutorial. I check Google Trends for the past five years; if the line is mostly flat or slowly rising, it passes. I also ensure the page is written for the reader by using clear headings, short paragraphs, and images with descriptive alt text. I always link the pillar page to a broader [seo-content-strategy](/seo-content-strategy/) so the hub supports the site's goals. If the topic is highly competitive but has a unique angle I can exploit, such as a data-backed example from my own work, I still go for it. For lower volume topics (under 100 searches per month) with no clear conversion path, I skip them unless they act as trust builders for a specific audience. The last step is setting a calendar reminder to review the page every six months for broken links or outdated references. That discipline turned one hub into a recurring lead generator.

Watch-outs

The first trap is trend-chasing. When ChatGPT launched in late 2022, dozens of sites published "best AI writing tools" lists. Those pages saw a spike in traffic, then a steep decline as the hype settled. By 2024 many of those keywords had lost half their volume. I would rather target "how to edit AI-generated text" which has a stable search curve and clear intent. If a spike exists, check if the underlying behaviour is a permanent shift — "remote work" surged in 2020 but stabilised into a new baseline, so it can become evergreen if you are willing to refresh it annually. The second trap is set-and-forget. I inherited a site with a guide on "social media marketing tips" from 2018. It still ranked, but mentioned MySpace and outdated Facebook features. After updating the stats, replacing broken links, and tightening the language, organic traffic increased by 40% in three months. Evergreen does not mean immortal; every year a good chunk of your content ages. Set a calendar. The third trap is over-optimising. A site I consulted for had an "on-page SEO" guide that stuffed every heading with exact-match keywords. After Google's helpful content update the page lost rankings because it read like a checklist, not a tutorial. I rewrote it with natural language, added examples, and used synonyms in headings. The rankings returned within two months. For [on-page-seo](/on-page-seo/) I now write paragraphs that answer the question first, then optimise the title and meta description. A decision rule: if a sentence contains more than one target keyword, rewrite it. Also watch for seasonal evergreen topics like "best Christmas gifts" — these are worth doing if you have the bandwidth to update them annually, but they are not truly passive. Finally, always verify that the search intent matches the format of your page. If the top results for "how to change a tyre" are all videos, your text guide needs a video embed to compete. Use the [meta-description](/meta-description/) to signal exactly what the reader will find.

What I got wrong

I used to think "evergreen" meant I could publish and walk away. My guide on "best SEO tools" ranked second for two years. Then MozBar changed its core features, a competitor launched a better comparison, and my page dropped to page three. I had no process to catch the decay. Now I set calendar reminders every six months to review each evergreen page, and I check the top ten results to see if competitors have updated theirs. The second mistake was choosing topics on high volume alone. I once picked "SEO tips" with 5,000 monthly searches because the number looked good. But the intent was for beginners wanting quick wins — listicles and simple checklists — while I wrote a technical deep dive with server logs and Python scripts. The page never converted and attracted the wrong type of traffic. Now I analyse intent by looking at the SERP features: if the top results are listicles, I write a listicle; if how-to guides, I write step-by-step. I also use the [internal-links-seo](/internal-links-seo/) technique to support evergreen pages: I link to them from new blog posts and update old posts with contextual links. After I added links from high-traffic blog posts to my updated "on-page SEO" guide, its rankings improved by an extra 30%. The third mistake was undervaluing authoritative sourcing. I used to cite random blogs; now I reference Google Search Central documentation or reputable industry studies. That small change improved click-through rates from the SERP because users trust a page that backs claims with solid sources. In hindsight, I should have started with a content audit of my existing pages before creating new ones. A full [content-audit](/content-audit/) would have revealed which topics had stable demand and which were losing traction. That is step one on every new project now.

Next step

Quick answers

How often should I update evergreen content?

I set a calendar reminder every six months for each evergreen page. If the topic shifts rapidly, for example legal guides or software reviews, I check quarterly. The update may be as small as fixing a broken link or as large as rewriting the entire page.

Can a news article become evergreen?

Rarely. News articles cover time-sensitive events. But if the underlying concept has lasting interest, such as a major policy change that becomes the new normal, you can convert it by stripping the date and reframing it as a resource. Most news is best left in archives.

What is the difference between evergreen and pillar content?

Evergreen content focuses on a topic with stable long-term demand. Pillar content is a specific format: a comprehensive page that covers a broad topic and links to cluster pages. A pillar page is almost always evergreen, but an evergreen page does not have to be a pillar.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

  • Google Search Central — Official guidance on helpful content, search intent, and quality signals that underpin evergreen content success.
  • Ahrefs Blog — Practical framework for identifying stable topics and evaluating long-term search demand with real examples.
  • Semrush Blog — Actionable workflow for topic selection, content structuring, and periodic maintenance of evergreen pages.
  • Search Engine Land — Industry commentary on algorithm updates and content strategies that affect evergreen page performance.

Notes from Callum Bennett.