AllMeans · Insights

Should your SME delete old blog posts or update them?

Published · Updated

Assess each old article against a current customer question before deciding whether to keep, update, combine or retire it. Check its usefulness, factual support and maintenance owner. Start with pages containing consequential errors or obsolete service instructions, and record a specific reason for each change rather than applying an age cutoff.

Should your SME delete old blog posts or update them?

1. Judge the answer, not the publication year

Do not begin your content audit with an instruction to delete everything older than a chosen year. Begin with a question: what decision should this article help a prospective customer make today? Write that decision beside the page URL. If you cannot describe it without saying “bring in traffic”, put the article aside for a closer editorial assessment.

Google explicitly rejects adding or removing lots of content primarily to make a website seem fresh as a way to improve rankings overall. It also cautions against changing publication dates when the content has not substantially changed. These are statements about freshness tactics, rather than an instruction to preserve every old page. Source: Google Search Central, helpful content.

For a Singapore SME, use a simple worksheet with five columns: URL, customer question, current answer, supporting evidence and proposed action. Read the complete page before filling in the last column. Check examples, downloadable instructions and the final contact instruction as well as the opening paragraphs.

Hypothetical example: a signage workshop has an older article explaining which artwork details to prepare before requesting an assessment. If the workshop confirms that the instructions remain accurate, recommend keeping it. If the article names a discontinued submission method, recommend correcting that instruction. The publication year alone should not decide either outcome.

2. Give each page a keep, update, combine or retire decision

Use four editorial outcomes, with a written reason for each. Keep an article when its question remains relevant, its answer is supported and the business can stand behind its instructions. Update it when the purpose remains useful but particular facts, explanations or next steps need correction. Combine articles when your review finds that they answer the same decision and a single complete treatment would serve the reader better. Consider retirement when the page has no remaining customer purpose and no useful material worth carrying forward.

This is a recommended decision framework, not a Google classification system. Google’s own assessment questions emphasise originality, completeness, substantial additional value and whether readers learn enough to achieve their goal. Use those questions to challenge your proposed action. Source: Google Search Central, helpful content.

Hypothetical example: an equipment supplier has separate posts about preparing photographs, measurements and access details for the same assessment. Recommend reviewing them together. A consolidated preparation guide could be the editorial choice if each existing article is incomplete on its own. Preserve useful distinctions rather than simply pasting three introductions together.

Before approving any retirement, identify who owns the page and ask your web maintainer to document how its existing address and incoming navigation will be handled. Treat that implementation as a separate task. An editorial decision to retire content is not, by itself, a complete technical change plan.

3. Make an update substantial and traceable

For every page marked for updating, prepare a short correction brief before rewriting. Specify the customer question, the inaccurate or missing passage, the evidence needed and the person authorised to confirm the business detail. Replace vague improvement instructions such as “make this more authoritative” with an observable task: explain what information is required, identify an exception or remove an unsupported assertion.

Google encourages accurate authorship information and asks creators to consider who produced content, how it was produced and why it exists. It also says that attribution does not replace original effort. Accordingly, do more than attach a source link to an otherwise unchanged summary. Add an explanation that helps the reader apply the information to the decision at hand. Source: Google Search Central, helpful content.

Hypothetical example: revise a generic supplier preparation article by adding a clearly labelled sample checklist for an assessment request. Ask the business owner to confirm each requested item. Where the right instruction depends on the job, say what needs confirmation rather than inventing a universal rule.

Keep an internal change note stating what changed, what evidence supported it and who approved operational details. For English, simplified Chinese and traditional Chinese versions, use one shared checklist of facts and exceptions. Recommend completing the corresponding corrections in every published version before marking the task finished. If you display an updated date, associate it with the actual substantive revision.

4. Check the finished page against its purpose

After editing, ask someone who did not write the revision to attempt the original customer task using only the page. Can they identify what to prepare, what remains uncertain and how to take the next step? Record the point where they need an explanation from you. Use that observation to improve the page before commissioning more articles on the same topic.

Then check its presentation. Read the heading and description against the revised content, and follow the relevant links from another page on your website. Google recommends making content findable through internal links and keeping important information available in textual form in its guidance for AI features. These are useful checks for an updated article, rather than reasons to expand this audit into an unrelated website rebuild. Source: Google Search Central, AI features.

Keep acceptance criteria within your control: the correction is present, evidence is linked, operational details are approved and the customer task is answerable. Google says there are no additional special optimisations required for AI Overviews or AI Mode, and that meeting requirements does not guarantee crawling, indexing or serving. Do not equate a completed edit with a promised search or AI appearance. Source: Google Search Central, AI features.

This article’s factual references use the supplied Google documentation excerpts checked on 6 November 2026. The worksheet, four editorial outcomes and hypothetical examples are practical recommendations derived for this article, rather than a published Google scoring formula.

Questions before you start

Should I delete every blog post that is more than two years old?

Use a review decision rather than an automatic age cutoff. Check whether each article still answers a relevant customer question accurately. Google specifically says that removing older content primarily to make a site seem fresh will not improve rankings overall on that basis. [Source: Google Search Central](https://developers.google.com/search/docs/fundamentals/creating-helpful-content).

Can I refresh an article by changing its date and adding more words?

Recommend updating the answer where it needs correction or additional explanation, then recording the substantive change. Google cautions against changing dates without substantial changes and says it has no preferred word count. Neither a newer date nor extra length should replace a defined customer purpose. [Source: Google Search Central](https://developers.google.com/search/docs/fundamentals/creating-helpful-content).

Will updating old articles get my business into Google AI answers?

An update is not a placement guarantee. Google says a supporting page for AI Overviews or AI Mode must be indexed and eligible for a Search snippet, with no additional technical requirements. Even compliance does not guarantee crawling, indexing or serving. Prioritise correcting the customer answer. [Source: Google Search Central](https://developers.google.com/search/docs/appearance/ai-features).

Sources and evidence

  1. Google says adding or removing substantial amounts of content primarily to make a site seem fresh will not improve overall rankings on that basis.

    Checked

    Google cautions against changing page dates to suggest freshness when content has not substantially changed.

    Checked

    Google's content assessment questions address originality, completeness, substantial additional value and whether readers learn enough to achieve their goal.

    Checked

    Google encourages accurate authorship information and recommends evaluating who created content, how it was created and why it was created.

    Checked

    Google states that attribution or giving credit to other sources does not replace the need for original effort.

    Checked

    Google says it does not have a preferred word count.

    Checked

    Google Search Central: helpful content

    https://developers.google.com/search/docs/fundamentals/creating-helpful-content

  2. Google's AI features guidance recommends making content findable through internal links and making important content available in textual form.

    Checked

    Google states that no additional special optimisations are necessary for AI Overviews or AI Mode.

    Checked

    To be eligible as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to appear in Google Search with a snippet; there are no additional technical requirements.

    Checked

    Meeting Google's requirements, best practices and policies does not guarantee that Google will crawl, index or serve content.

    Checked

    Google Search Central: AI features

    https://developers.google.com/search/docs/appearance/ai-features

Tell us where marketing gets stuck

What you sell, who buys it and where your customers look for you. We will get back to you on WhatsApp or by email.

Discuss your businessWhatsApp us

WhatsApp