How often to blog, and when to refresh

How often to blog has a plain answer: start with five posts, then publish one a week, refresh every post within 12 months, and judge each one by the customers it brings. A blog compounds only when posts keep coming and the old ones stay true.

Cadence

  • Start with five posts, then publish one a week: 4 a month.
  • The quality gate decides, not the calendar. A post that fails chapter 12 doesn't ship to hit a number. There is no magic quota, and review capacity sets the real pace.
  • Recurring formats come on top: a customer story once a month, and a discovery story and a small how-to guide every 3 months (chapter 2).
  • Each month: new posts from the topical map, internal links from existing pages to them, and a check of how each cluster performs.
  • Twice a month, look at what brought calls, enquiries or orders, and improve the site to bring more.
  • Seasonal demand seeds the calendar: frost weeks, the start of the heating season, spring roofing, holidays, launches, the start of the financial year. A seasonal demand calendar is itself a heading your buyers value.

If someone else writes for you: a post that makes claims about your business needs your approval before it goes live.

Bar chart of a blog's first-year output: 50 weekly posts, 12 monthly customer stories, 4 discovery stories and 4 small how-to guides.
One post a week plus the recurring formats gives a small business 70 posts in its first year.
Embed this image
<a href="https://rend.ee/en/blog/seo-blog-guide/how-often-to-blog#fig-first-year"><img src="https://rend.ee/images/guides/seo-blog/en/first-year-blog-posting-plan.webp" alt="Bar chart of a blog's first-year output: 50 weekly posts, 12 monthly customer stories, 4 discovery stories and 4 small how-to guides." width="1600" height="938" style="max-width:100%;height:auto"></a>

Refresh

  • Improve useful existing material before replacing it. Keep the URLs and whatever already brings customers. Redirect only when a change makes it necessary.
  • Prune and merge thin, outdated or duplicate pages so two pages never compete for one search.
  • Change displayed dates only when the content really changes.
  • Review the statistics page every quarter with a dated change log, change its title year each January, and rerun price analyses each January.
  • Copy is never finished. Once traffic allows, test bold against safe: for example, split-test the H1.

The update window

  • Every post is refreshed between its 5th and 12th month. No post goes longer than 12 months without an update, and none is updated sooner than 4 months after it went out.
  • A refresh is a real update (new figures, new questions, sharper answers, new links), and the updated date on the page changes with it.
  • After each refresh the window starts again from the new updated date.
Timeline of a blog post's first year: published at month 0, no update before month 4, refreshed in the window between month 5 and month 12.
Every post is refreshed between its 5th and 12th month, and the window restarts after each refresh.
Embed this image
<a href="https://rend.ee/en/blog/seo-blog-guide/how-often-to-blog#fig-refresh-window"><img src="https://rend.ee/images/guides/seo-blog/en/blog-post-refresh-window-months.webp" alt="Timeline of a blog post's first year: published at month 0, no update before month 4, refreshed in the window between month 5 and month 12." width="1600" height="926" style="max-width:100%;height:auto"></a>

The monthly refresh

  • Refresh from Search Console every month. A query for which a page ranks just below position 1 (positions 2 to 5) goes into that page's H1, its first sentence and a heading.
  • Run a content gap check every month with more than one method, and fill the gaps that month. Start by comparing your sitemap with the sitemap of the competitor that ranks highest for your niche's highest-volume keyword in your market, and list the topics they cover that you don't. Then add the other methods: queries with impressions but no page that answers them, People Also Ask questions, and keyword gaps in a keyword tool.
  • Make small internal-link edits every month from Search Console and backlink data: a page that gained authority or impressions links to the pages that benefit, and new pages get links from strong related pages. Log each edit and its effect.
  • Analyse why winning posts won (intent match, format, angle, original material, links, title) and build the next posts on the parts that made them win.

What a year of posts looks like

After the first five posts, one post a week gives you 50 posts a year, each one checked, linked and refreshed inside its 5 to 12 month window. The monthly Search Console refresh and gap check decide the next topics, and the posts that bring customers show you what to write more of.

The work is steady rather than hard. It does take hours every week: research, writing, images, checks and refreshes, in every language you sell in.

When to stop, merge or retire a post

  • Merge two posts that answer one search into the stronger one, and give the other address a one-hop redirect to it.
  • Retire a post whose topic no longer exists, such as a discontinued product or a law that changed, and send its address to the closest live page.
  • Never delete a post that earned links without a redirect; the links are the value it built.
  • Stop a recurring format that brings no enquiries after 6 issues, and spend the hours on the format that does.

Measurement

  • Success is qualified enquiries, not page count or a tool score. Tell apart impressions, clicks, rankings, enquiries and bookings. Before you name a cause, check indexing, technical changes, seasonality and competition.
  • Measure cluster coverage in Search Console: how many queries per cluster rank, which pages gain impressions, and where gaps remain.
  • Re-run the AI question set every month and report mentions, citations, AI referrals and enquiries month by month (chapter 11).
  • Log every change and its effect (rankings, impressions, calls, enquiries, orders) to build your own evidence.
  • Audit on a rhythm: a light audit weekly, a full audit monthly, a deep audit quarterly and a re-audit yearly. Every finding becomes a task or a reasoned "won't fix".

What counts as success depends on the business.

  • For an online store: orders and revenue, measured as product-card clicks, add-to-carts and orders from sessions that included a post.
  • For a software or B2B company: trials, demo requests and the pipeline from sessions that included a post.
  • For a publisher: returning readers, newsletter sign-ups and subscriptions.

Also

  • Write down every lesson the day you learn it, so the next post starts from it.

A blogger's week

One post a week holds when every day has its own job, not when the post is written on the last evening.

  • Monday: the results note and the post's plan from the topical map.
  • Tuesday and Wednesday: the text, your own finding, figures with sources, and the images.
  • Thursday: the checklist, the check on the live page, and links in from existing pages.
  • Friday: refresh one older post from the update window, and log the changes.

When a week slips, the publishing date moves, not the bar: a post that goes out two days late and passes every check brings more than a weak one published on time.

  • Andres Lepik, co-founder and head of growth at REND, with a short beard, smiling in a black REND cap and T-shirt against a light grey backgroundEdited by Andres LepikCo-founder & Head of Growth
  • Siim Saar, head of SEO at REND, with stubble, in a black REND cap and T-shirt against a light grey backgroundFact-checked by Siim SaarHead of SEO
Rasmus Kivi, co-founder and CEO of REND, smiling in a black REND cap and T-shirt against a light grey background

Post by Rasmus Kivi

Co-founder & CEO

Co-founded REND and still reads every client's monthly report himself before it goes out.