Building Evergreen Content

I first learned of the term “Evergreen Content” a few years ago while reading Graywolf’s SEO Blog.  In case you are unaware, Evergreen Content refers to content on a website that never becomes outdated.  For example, historical facts such as Ronald Reagan was the 40th President of the United States will never change.  If your website is centered around history most if not all of your website would be considered Evergreen Content.

Why is it important and what are the benefits of having Evergreen Content on your website?  First, once evergreen content is written it will not have to be edited or changed even five years down the road because it never changes.  Second,  Evergreen content can be part of your overall core quality content.  Google and the other search engines will be searching your site for quality content and Evergreen Content can be part of it.

What are some pitfalls or things you should watch out for when planning your Evergreen Content?  First of all, plan your keyword research carefully.  Make sure your page titles contain the keywords you researched.  Second, carefully plan your content as even some Evergreen content has a limited “shelf life”.  For example, if your page is centered around customizing the WordPress theme Thesis 1.8 what happens when Thesis 2.0 comes out?  It is okay to write content about customizing Thesis 1.8 but keep try to plan ahead for future versions of the theme.  One way to organize this page would be to create a main title called “Modifying The Thesis Theme” with links to separate pages for versions 1.8, 2.0 and future versions as they come out.

Again, Evergreen Content is something that every website can and should utilize.  There are many additional things to consider when building Evergreen Content and that will be the focus of a future post.  Can someone please share what Evergreen Content techniques they have used on their website?

Thank you for sharing,

David Landen

{ 1 comment… add one }

Leave a Comment

CommentLuv badge

Next Post:

Previous Post: