What should I use for evergreen pages, a blog or a knowledge base?

For evergreen pages, I’d usually recommend a knowledge base if your goal is:

• clear, stable information
• easy navigation by topic
• support/docs/how-to content
• long-term searchability
• frequent small updates without “post” framing

Use a blog if your goal is:

• commentary or opinion
• news, updates, announcements
• content tied to a date or event
• storytelling or thought leadership

Simple rule

• Evergreen reference content → Knowledge base
• Time-sensitive or editorial content → Blog

Why a knowledge base is often better for evergreen content

Evergreen pages tend to perform better when they feel like a living resource rather than a dated article. A knowledge base supports:

• category-based organization
• article revisions without preserving publish-date emphasis
• user self-service
• internal linking across related topics

A good hybrid approach

Many sites do both:

• Knowledge base for core evergreen guides, FAQs, and product info
• Blog for updates, announcements, trends, and driving traffic

If you want, I can also help you decide based on your specific site type, like SaaS, ecommerce, agency, or personal brand.