Old blog posts are not weeds that must be cut to make a Toronto business site rank. Some need a fact update. Some compete with a better page and should be combined. Others answer a question the business no longer serves. PPC Guru's update–merge–delete decision guide helps owners choose deliberately, especially when a blog supports an SEO service page or local offer. Our monthly SEO services checklist shows how page ownership fits into ongoing work; this article addresses the broader old-content portfolio.
The short answer: Keep a useful post that still answers a real question. Update it when facts or examples are stale. Merge pages when one stronger destination can answer an overlapping task. Remove a page only when it no longer serves readers and has no suitable replacement, with the right URL treatment. Do not delete merely because a page has low traffic; Google does not say that mass pruning makes a site “fresh” or ranks it higher.
Start with the reader, not a traffic threshold#
A two-year-old guide may get few clicks yet answer an important question during a sales conversation. A high-traffic article may be inaccurate or attract people outside the business's market. Neither should be judged by sessions alone.
For each candidate URL, review four things: reader need, factual freshness, unique contribution, and business fit. Then inspect current search queries, internal links, backlinks where available, assisted conversions and whether a better page already exists. Document what you can actually verify; a missing metric is not a zero.
Google's helpful-content guidance explicitly cautions against adding or removing lots of content chiefly to make a site seem fresh. The right question is what the visitor needs now.
The decision matrix#
| Situation | Better first action | Why |
|---|---|---|
| Useful topic, stale dates or claims | Update and fact-check | Keep the existing resource and make it trustworthy. |
| Two articles answer the same question | Compare, then merge if one destination is clearly stronger | Reduce duplication while preserving useful material. |
| Low traffic, but answers a genuine client question | Keep or improve its discoverability | Traffic alone does not measure usefulness. |
| Obsolete offer with a close replacement | Redirect to the most relevant live page after a content and link check | Help existing visitors reach the new answer. |
| Obsolete content with no honest replacement | Remove and return an appropriate status; repair internal links | Do not mislead visitors with an unrelated redirect. |
| A URL variant duplicates the main page | Check canonical/redirect handling | This is a technical duplicate, not an editorial rewrite. |
The matrix is a decision aid, not a promise that any action will improve rankings. The right choice depends on the URL's audience and the website's structure.
When is an update enough?#
Update when the core question remains valid but the answer has aged. Verify every material number, screenshot, policy link and product instruction. Add missing context that helps the current reader decide. Do not just change the year in the headline; show a material improvement and preserve the date honestly.
For example, a GTA contractor's guide to choosing project photography might still be useful, but outdated portfolio examples and consent wording need review. That is illustrative. If the page earns relevant leads and has a clear unique role, deleting it would be a poor first move.
When should you merge two posts?#
Merge when readers would get a better answer from one coherent page. Compare the two posts by query and intent. Keep the strongest explanations, examples and links; remove repetition; then route the retired URL to the genuinely relevant page. Google's redirect documentation describes how redirects signal a moved page. A redirect should not send a niche old post to the home page merely to avoid a 404.
Check internal links, navigation and sitemaps after the change. If a partner or customer uses the old URL, test what they will actually see. For very similar URL variants rather than two editorial posts, consult Google's canonical guidance instead of automatically rewriting both articles.
When is deletion reasonable?#
Deletion can be sensible when a page is no longer accurate, relevant or maintainable and there is no honest replacement. Before removing it, record its purpose, inbound links, current search queries, and any contact or sales use. Repair site navigation and any links that pointed to it. If the information was confidential or harmful, the removal decision may be urgent and outside ordinary SEO prioritization.
Do not treat “no traffic in 30 days” as permission to delete. Also do not keep a misleading page live solely because it has impressions. Accuracy and reader usefulness come first.
A low-risk review process for a small business#
- Inventory the ten oldest or most questionable posts, not the entire archive at once.
- Assign each post a job: educate, compare, diagnose, qualify or support a service page.
- Record evidence and the proposed update, merge, keep or remove decision.
- Make a small batch of changes and test every affected URL, link and CTA.
- Recheck Search Console and qualified enquiries over a sensible period without crediting every change to the edit.
If the site also has pages missing from Google, separate that technical issue from content pruning. Our Toronto indexing diagnosis covers that investigation.
If you want an independent decision on a set of underperforming pages, ask PPC Guru about an SEO content audit. Share the URLs and the services they are meant to support. The outcome should be a defensible keep/update/merge/remove list with implementation notes—not a blanket instruction to delete old posts.
Source check: 14 September 2026. The decision matrix is an editorial tool. No ranking lift from updating, merging or deleting is guaranteed.