Key Takeaways
- Update an existing post when its purpose is still right but its information, examples or structure need work.
- Publish a new article when it answers a genuinely different customer question.
- Consider a merge when pages substantially overlap, but check their purpose and useful evidence before removing anything.
- Leave accurate, useful content alone when there is no clear improvement to make.
- Record what changed and evaluate the result without assuming that a new date or more words will improve rankings.
Update an old blog post when you can make the existing answer more useful. Publish a new one when the reader needs a different answer. That distinction is more reliable than a rule about posting frequency or the age of a URL.
For the broader editorial principles, see content that ranks: topical authority and E-E-A-T; this guide helps choose which page needs the work.
A content calendar can make every idea look like a new article. Before you commission the next piece, search your own website. You may already have a page with useful links, relevant search visibility and a half-finished answer to the same question.
Equally, an old article should not absorb every loosely related topic. If somebody needs a separate decision, forcing it into an existing guide can make both questions harder to answer.
Start with the Reader's Job
Write the proposed topic as a task. “Understand the difference between two platforms” is different from “plan the move from one platform to another”. They may mention the same products but require different information.
Then read the closest existing articles in full. A title search is not enough. Look at the opening answer, major sections, examples and next step.
Ask whether a reader would reasonably need both pages. If the answer is yes, explain the distinction in one sentence. If you cannot, there may be overlap worth resolving before writing.
For an illustrative agency blog, a general guide to choosing a CRM and a diagnostic guide to duplicate CRM emails can both be useful. Two broad “best CRM” articles with the same audience and recommendations are much harder to justify.
Review Evidence Before Assigning Work
Make a short record for the existing page: purpose, current accuracy, relevant queries, useful links, customer questions answered and commercial next step.
Use completed reporting periods and consistent filters when checking Search Console. Its performance-report guidance explains the page and query views. Inspect the searches associated with the page rather than relying on its total impressions alone.
Investigate Search Console impressions with no clicks before assigning a rewrite, as query relevance and position affect what those figures mean.
Also look beyond search traffic. Sales staff may use the article to answer prospects. Support staff may send it to customers. Those are useful roles even if the article brings few new visitors.
Where your reporting supports it, review enquiry quality. Our guide to tracking blog posts and qualified leads in HubSpot explains how to keep content touches separate from claims that one article caused a sale.
If you have non-branded impressions growing but enquiries flat, check which customer needs those searches represent before commissioning more articles.
Avoid treating missing data as poor performance. A new article, an untracked enquiry path or a seasonal topic may require a different review window.
Choose One of Four Actions
Use the diagnosis to choose the work. You do not need to fill every row of the publishing calendar with a new URL.
| Action | A good reason | What success looks like |
|---|---|---|
| Update | Same useful purpose, but information or explanation needs repair | A more accurate and complete answer |
| Publish new | A distinct customer task is not covered | A useful answer with a clear place in the site |
| Combine | Existing pages substantially repeat the same answer | One coherent destination preserving useful material |
| Retain | The page is accurate, useful and serves its purpose | Continued availability without unnecessary churn |
These choices can coexist in the same month. You might improve two service-supporting guides, publish one new diagnostic article and leave several dependable reference pages unchanged.
Our content marketing service uses the business need to shape the work. The correct mix depends on your inventory and evidence, not on a fixed ratio that applies to every site.
When an Update Is the Better Job
Refresh the existing URL when the underlying question remains the same. Typical reasons include outdated platform instructions, broken links, missing limitations, weak examples or an answer buried below a long introduction.
Start with factual repairs. Check product names, current documentation, dates and any figures. Remove claims that you cannot support. If an old article presents an invented result or an overconfident recommendation, adding a new paragraph at the bottom will not repair the main problem.
Next, improve the explanation. Put the direct answer where readers can find it. Add a useful decision table or a worked example only if it solves a real difficulty. Delete sections that repeat the same point without helping the task.
Finally, check the next step. If the related service has changed, the article's commercial link may need updating. Readers should not reach an old offer that the business no longer provides.
Google's people-first content guidance cautions against changing dates without substantial changes and against adding content merely to make a site appear fresh. Record a revised date when the work justifies it, and explain meaningful updates where that helps the reader.
When a New Article Earns Its Own URL
Create a new article when it has a distinct purpose, enough useful substance and an audience your business can help. The distinction should be visible in its opening answer and structure.
A platform comparison may help a buyer choose. A migration plan helps an owner move safely. An incident guide helps an operator diagnose a fault. Those are separate jobs even when the same brand name appears in all three titles.
Before writing, name the existing page that the new article will support and the related posts it should link to. This prevents the new URL becoming an isolated piece of content with no clear place in the site.
Choosing a service page or blog post for AI search is a related intent decision; the reader's task should guide the format.
Do not chase a phrase merely because a keyword tool shows a large number. Check the actual question and the likely reader. A popular query about a free personal tool may be a poor fit for a business selling a specialist service.
Write a short exclusion note in the brief: what this article will deliberately not cover because another page already does. That small decision helps the writer keep the angle distinct.
When Two Posts Should Be Combined
A merge is worth considering when two pages repeatedly answer the same question for the same reader and neither has a useful independent purpose.
Read both pages carefully before deciding which material survives. One may contain a better explanation; the other may have useful examples or important inbound links. Keep genuinely helpful content rather than selecting a winner solely by age.
Decide which destination best matches the combined purpose. Update internal links and plan the old URL's handling. Google's redirect documentation explains the use of permanent redirects when a page has moved. A redirect should lead to a relevant replacement, not an unrelated page chosen for convenience.
Keep a record of the old URLs, destination and release date. Check that the redirect works and that the destination answers the old page's useful questions.
Do not merge everything that shares a keyword. Overlap in vocabulary is normal. The problem is duplicated purpose without a useful distinction.
When Leaving the Article Alone Is Sensible
An accurate reference page may need no immediate edit. Age alone is not a defect. A guide explaining a stable concept does not become wrong because its publication date is old.
Check links and time-sensitive details during routine reviews, but avoid rewriting strong content to satisfy a schedule. Every edit creates a chance of losing a clear explanation or introducing an error.
Retain an article when it serves a current audience, its claims remain supportable and you cannot identify a worthwhile improvement. Put the review date in your internal tracker rather than manufacturing a public update.
If the page is no longer relevant to the business, decide its future deliberately. Low traffic on its own is not enough evidence to delete it, particularly if customers or other pages still depend on it.
Write a Brief That Matches the Decision
For a refresh, list the exact problems and the sections that should stay. For a new post, state the separate task and the overlap boundary. For a merge, include the source pages and URL plan.
Name the evidence required. A process article may need an interview with the person who does the work. A product article may need current documentation. A case study needs permission and verified facts.
Check what content marketing services include when assigning research, writing, review and implementation responsibilities.
Agree what the writer must not invent: client stories, performance figures, first-hand tests and claims about features they have not checked. A clear example labelled as illustrative can explain a decision without pretending it happened to a real client.
If you are buying the work, the retainer-versus-project guide helps separate the delivery model from this editorial decision. A retainer can contain refreshes, and a one-off project can contain new articles. Neither model dictates the right action for a particular page.
Review the Finished Work Against Its Purpose
Read the page without looking at the brief first. Can a suitable reader get the answer and decide what to do next? Then compare it with the requirements and source evidence.
Check links, headings, images, metadata and the actual published version. For a merge, test the old URL as well as the new destination. For a refresh, compare important factual claims with the previous version so you can see whether the intended repair happened.
An SEO content review should examine usefulness and site context alongside technical checks. Passing a word-count target does not establish that the article deserves publication.
Keep the Next Decision Small
Choose a handful of articles connected to an important service. Classify each as update, new opportunity, combine or retain, and write the reason beside the decision.
Complete one defined change before expanding the review across the whole archive. After publication, record the work and examine relevant evidence over a suitable period. Avoid crediting one edit for every later movement in the site's overall traffic.
If you need help choosing between a refresh and a new piece, send us the existing URLs and proposed question. We can start by checking what the reader already gets and what is still missing.
Frequently Asked Questions
Is updating old blog content better for SEO than publishing new posts?
Neither is automatically better. Update when the existing page serves the right purpose but needs improvement. Publish a new article when it answers a distinct question your audience needs help with. Choose the action from the page evidence and customer task.
Should I change the publication date when I refresh an article?
Use dates honestly. A substantial review or revision may justify a visible updated date, but changing a date without meaningful work does not improve the answer. Keep the original publication history and explain important changes where useful.
How do I know whether two blog posts overlap too much?
Compare their intended reader, opening answer, main sections and next step. If both solve the same task with little independent value, review whether they should be clarified or combined. Shared keywords alone do not prove harmful overlap.
Should I delete articles that receive no search traffic?
Not automatically. Check their accuracy, customer usefulness, existing links, age and reporting limitations first. A page may support sales or customers without attracting many new search visitors. Make removal or replacement decisions with a clear purpose.
What should I measure after a blog refresh?
Check the published page and links immediately, then review relevant page and query evidence over comparable periods. Where reliable tracking exists, consider suitable enquiries and customer use too. Record other changes that may affect the result and avoid assuming causation from a simple before-and-after chart.
