Your content budget covers maybe two pieces this month. You could write two new posts, or you could fix two of the forty you already have. Most owners default to new, because new feels like progress. Sometimes it is. Sometimes the better move is sitting in your archive.
Here is a simple audit for deciding which.
Build a prioritized content plan
Book a call and we will walk through your existing posts and sort them into keep, update, merge, and new.
Let the Buzz BeginQuick answer: should you update old blog posts or write new ones? Update a post when it targets a question customers still ask and already shows some search activity but is outdated or incomplete. Merge posts that answer the same question. Keep posts that are accurate and doing their job. Write new when you have a real customer question that no existing page answers. Do not delete a page just because its traffic was low for a short stretch.
What should you look at before deciding?
For each post, gather three things:
- The question it answers. If you cannot name the customer question in one sentence, note that.
- Evidence from Search Console. Google’s Performance report shows the queries, clicks, impressions, and average position for each page. Impressions with few clicks can mean the page is visible but not compelling; no impressions at all can mean it answers nothing people search for.
- Accuracy. Prices, regulations, screenshots, and product details go stale. A post that was right two years ago may be wrong today.
Use a long date range, such as the last 12 months, so a slow season does not mislead you.
When should you keep, update, or merge?
Keep / update / merge decision sheet
| What you find | Decision | What to do |
|---|---|---|
| Accurate, answers a real question, getting impressions or clicks | Keep | Leave it; check it again next audit |
| Real question, some impressions, but outdated or thin | Update | Refresh facts, add what is missing, improve the answer at the top |
| Two or more posts answer the same question | Merge | Combine the best of each into one page and redirect the others to it |
| Real question, no impressions yet, recently published | Wait | Give it time before judging |
| No clear question and no search activity over a long period | Rewrite or retire | Rewrite around a real question, or merge it into a related page |
| A customer question no page answers | Write new | Add it to your content plan |
Government web teams use the same discipline. Digital.gov, the federal government’s resource for web teams, evaluates its pages on a regular schedule and removes outdated or redundant content, and Massachusetts’ content cleanup guide has agencies audit for anything redundant, outdated, or trivial, then update or remove it.
What does a good refresh look like?
A refresh is more than changing the date. Work through the post:
- Re-check every fact, link, and number against its source. Remove anything you cannot verify.
- Answer the question in the first few sentences.
- Add what is missing, often the follow-up questions customers ask.
- Fix internal links so the post points to your related service page and to newer articles.
- Update the visible “last updated” date only if you made meaningful changes, so the date stays honest.
Google’s guidance on helpful, reliable, people-first content is a useful checklist here: it asks whether content is written for people rather than to manipulate rankings, and warns against changing dates or adding small edits just to make pages seem fresh.
How do you merge two posts?
Pick the stronger URL, usually the one with more search activity or links. Move the best material from the weaker post into it, then set up a permanent (301) redirect from the old URL to the merged page so visitors and links arrive in the right place. Update any internal links that pointed to the old URL.
How do you measure the results?
Note the date of each change and compare the page’s Search Console numbers over the following months against the same period before. Look at impressions, clicks, and the queries the page shows up for, plus leads that came from the page. Changes take time to show up, so judge them over months, not days.
How often to publish new pieces is covered in our guide to how many blog posts it takes to rank. Where updates fit in the bigger plan is in our SEO content strategy guide, and how merged pages fit into a cluster is in our topic clusters guide. Related guides cover planning your internal links and whether you need llms.txt. Our SEO Content Creation service handles new posts and refreshes.
Frequently asked questions about updating old blog posts
When should I update instead of writing new?
When an existing post targets a question customers still ask but is outdated, thin, or buried. Improving it starts from a page that already exists.
When should two pages be merged?
When they answer the same question. Merging gives readers one complete answer instead of two partial ones.
What if I have very little data?
Judge by the question and the accuracy. If the post answers a real customer question and is correct, keep it and give it time.
Final thoughts on updating old blog posts
Before paying for another new post, check the ones you have. Keep what works, update what is close, merge what overlaps, and write new only for questions nothing answers yet. For help sorting your archive, book a call with one of our hive specialists today.