How to Decide Whether to Update, Merge or Retire an Old Article

Older articles tend to accumulate quietly. A product guide describes a discontinued model, two posts compete to answer the same question, or a once-useful explainer attracts visits but no longer helps readers make a decision. The obvious response is often to refresh everything. That can waste editorial time, and it can leave outdated or overlapping pages in place under a newer publication date.

Deciding whether to update, merge or delete old website content is really a decision about the page’s current purpose. Does it still serve a reader and a business need? Can it do so with a focused revision? Is another page now the better home for the information? Or is there no good reason to keep it available?

This guide sets out a practical way to make that call. It covers what to inspect before editing, how to distinguish a refresh from a merger, when retirement makes sense, and how to manage redirects and measurement without treating every change as a ranking fix.

Start with the page’s job, not its age

Publication date is a weak decision rule. A six-year-old reference page may still be accurate and useful; an article published last quarter may already be obsolete. Start by describing the page’s intended job in one sentence: who is it for, what question does it answer, and what should a reader be able to do afterwards?

Then compare that intended job with what the page does now. Has the subject changed? Has the business changed? Does the page answer a question that matters to your audience, or is it present only because it once brought in traffic? Those distinctions help prevent two common mistakes: refreshing a page that should be retired, and deleting a page whose useful information only needs a better structure.

Build a shortlist rather than auditing everything at once

For a large site, begin with pages that show a reason for review: declining organic visits, outdated claims, overlapping topics, broken conversion paths, no meaningful links or internal references, or a product and service that no longer exists. A content inventory can combine URL, page type, topic, last reviewed date, organic landing-page data, conversions, links and a brief editorial assessment.

Use a consistent time period and compare like with like. A seasonal guide should not be judged by comparing its peak month with an off-season month. A recent redesign, tracking change or change in search demand can also affect the numbers. Analytics helps identify candidates; it does not make the editorial decision for you.

If the site is large, check whether a page is genuinely disconnected before concluding that it has no role. Our guide to finding and fixing orphan pages explains how to investigate pages with no internal links.

What to check before choosing an action

Search intent and the current results

Look at the searches the page is visible for and the kind of results appearing for its main topic. Are searchers looking for a definition, a step-by-step answer, a comparison, current pricing or a local provider? A page built for one need may struggle if the query now implies another. Search results are not a perfect statement of intent, but they are useful evidence about what people can currently find.

Also check whether the page is attracting the right audience. A high-traffic article can be a poor business asset if it answers an unrelated question and sends visitors nowhere useful. Conversely, a low-volume technical page may support sales conversations or help existing customers, even if it is not a major organic landing page.

When a revision requires a new structure, a content brief connecting intent to page structure can help define what the page should cover before anyone starts rewriting.

Accuracy, completeness and distinctiveness

Mark information that is wrong, no longer verifiable, or dependent on a product, law, interface or process that has changed. Separate facts that can be checked from advice that needs a subject-matter expert. If the article relies on an old screenshot or an expired offer, for example, changing the date alone does not make it current.

Next, compare it with your own relevant pages. Do they serve different stages or audiences, or are they near-duplicates with different headings? Similar wording does not automatically mean two pages should be merged. The important question is whether each has a distinct purpose and useful information that a reader would miss if it disappeared.

Performance and business value

Review organic landing-page visits, queries, engagement and conversions over a suitable period, alongside referrals, email use or other known routes to the page. Look for trends rather than a single week. Check whether the page has external links worth preserving and whether other pages on your site link to it.

Performance is evidence, not a verdict. A page can have little search traffic and still be useful to customers, sales teams or support staff. A page with visits may still be a poor candidate to retain if it is misleading, irrelevant or attracting the wrong audience. Record the reason for the decision so future reviewers understand the context.

When to update an article

Update the article when its underlying purpose remains sound, its topic still matters, and the gaps can be fixed without changing the page into something fundamentally different. This is usually the cleanest choice when the existing URL has a useful history, the page already matches the intended audience, and the work is mostly about improving accuracy, coverage or clarity.

What a meaningful update involves

• Correct the substance: replace outdated facts, instructions, examples and screenshots. Verify claims with appropriate sources or a qualified reviewer.
• Close real gaps: answer questions the article currently leaves unresolved, rather than adding sections just to make the page longer.
• Improve the route through the page: make the answer easier to find, clarify headings and remove repetition.
• Review the next step: make sure calls to action, product references and links still lead somewhere relevant.
• Check the surrounding site: update internal links and any related pages that repeat information now covered here.

For example, a small accountancy firm might have an article explaining how to prepare records for a self-assessment appointment. The process is still relevant, but the checklist refers to an old client portal and omits a newly common source of income. If the article continues to answer the same practical question, revise those details, check the instructions with the team and keep the page’s purpose intact.

Do not change the publication date just to make a page look fresh. If you make a substantial revision, show the original publication date and a clear updated date where appropriate, and describe what changed if that helps readers. A cosmetic date change does not repair stale advice.

When to merge two or more articles

Merge pages when they substantially overlap and a single, stronger page can serve the shared audience and intent better than separate pages. A merger is not a way to remove a page merely because it has fewer visits. First establish that the pages are genuinely competing or fragmenting useful information, and decide which URL will become the main destination.

Signs that a merger may make sense

• Several articles answer nearly the same question for the same audience.
• The pages repeat sections, examples or advice, with no clear reason for the separation.
• Search queries and landing-page patterns suggest that users are being sent to inconsistent versions of the same answer.
• One page has a stronger history or clearer fit, while another contains a useful detail that can be incorporated.

Imagine a software company has separate posts on choosing project-management software for a small team and comparing tools for a small business. If both target the same buyer, repeat the same criteria and offer no distinct perspective, a comprehensive comparison guide may be more useful than two thin articles. Keep the genuinely different advice, remove duplication and make the chosen page easy to navigate.

Before merging, map each source page’s useful sections, queries, links and internal references. Select the destination based on topic fit and reader usefulness, not just which URL has the most traffic. Rewrite the combined page so it reads as one coherent resource; pasting two articles together usually creates repetition and awkward transitions.

Once the destination is ready, redirect retired source URLs to the closest relevant replacement. Update internal links to point directly to the destination, rather than relying on redirects. Avoid sending every old article to a broad category page or the homepage: a redirect should make sense to someone following the link.

When to retire an article

Retire a page when it no longer serves a useful purpose and there is no appropriate replacement. This could be an announcement for a completed event, an obsolete offer, an outdated product page with no successor, or a thin article whose subject no longer belongs on the site.

Ask three questions before removing it:

1. Would a reader reasonably expect this information to remain available? Consider customer support, legal, historical or reference needs, not just search traffic.
2. Is there a close replacement? If yes, a redirect may preserve a useful route. If not, do not invent a replacement just to avoid a missing page.
3. Does the page have links or traffic that still matter? Review external links, internal links and referral activity, and decide whether those routes need a relevant destination.

If the content is genuinely gone and no substitute exists, return an appropriate not-found response rather than redirecting visitors to an unrelated page. Search engines need a clear signal that a removed URL no longer has content. Google’s documentation on HTTP status codes and network errors explains how responses such as 404 and 410 are handled; these signals do not guarantee instant removal from search results.

There are cases where a page should remain available but not appear in search, such as a useful account or internal utility page. That is a different decision from deleting an article, and it needs an appropriate access or indexing approach. Do not use a redirect, canonical or noindex directive as interchangeable tools. For duplicate URL situations, see our guide to choosing between canonical tags and redirects.

A practical decision framework

Use this sequence for each candidate page. The outcome should follow the evidence, not a blanket rule for all old content.

1. Is the page accurate and still useful? If yes, keep it and schedule a review if needed. If no, continue.
2. Does its original purpose still matter? If yes, decide whether a focused revision can restore usefulness. If not, assess whether another page can serve the need.
3. Does a closely overlapping page serve the same audience and intent? If yes, consider a merger. If the pages have distinct jobs, improve their differentiation instead.
4. Is there a relevant destination for readers of this URL? If yes, prepare a redirect after the replacement is ready. If no, retire the content and return an appropriate not-found response.
5. What needs to change elsewhere? Update internal links, navigation, related content and any references in email or support materials.
6. How will you assess the result? Record the reason, actions and date, then review relevant traffic, conversions, indexing and user paths after enough time has passed.

Keep a simple decision log with the URL, action, rationale, destination if applicable, owner and review date. That record is especially useful when content changes hands or when a later performance review raises questions about a missing page.

How to measure the decision after publication

Set a baseline before making a substantial change. Depending on the page’s role, this might include organic landing visits, query coverage, leads, assisted conversions, referral visits, internal clicks or support usage. For a merger, review the destination page and the retired URLs together, while remembering that seasonality, demand and other site changes can affect results.

Check that the technical implementation matches the plan: the destination returns the intended status, redirects resolve in one step where possible, internal links use the final URL, and the replacement can be crawled and indexed. A migration or wider redesign may involve additional checks; our SEO release checklist for migrations and redesigns covers those broader risks.

Do not judge success only by whether the replacement receives more organic visits. A well-judged retirement may reduce irrelevant visits; an update may improve usefulness without a dramatic traffic change. The question is whether the page now does its job more reliably, with fewer confusing or outdated routes for readers.

FAQ

Should I delete an article that gets no organic traffic?

Not automatically. Check whether it helps customers, supports another channel, has useful links, or serves a topic that matters to the business. Low search traffic is one signal. If the page has no distinct purpose and no useful replacement, retirement may be reasonable.

Should I change the URL when I update an old article?

Usually not if the existing URL still describes the page and is usable. Changing a URL adds migration work and can break links. If a URL change is genuinely necessary, redirect the old address to the closest relevant replacement and update internal links.

When should I redirect a retired article?

Redirect when a genuinely relevant replacement exists and would satisfy the needs of someone arriving at the old URL. If there is no suitable destination, return a not-found response rather than sending visitors to an unrelated page.

Can I merge articles that target different keywords?

Possibly, but keyword differences alone do not settle the question. Check whether the pages answer the same underlying need for the same audience. If they serve distinct intents, keep them separate and make their purpose and internal linking clearer.

How often should I review old content?

Use a schedule that reflects how quickly the subject changes and the risk of outdated advice. Review regulated, technical or fast-changing topics more often than stable reference material. Also review pages when performance, products or business priorities change.