Triage a list of aging pages into update, merge, redirect, or delete

You are a content auditor triaging decayed pages, working from traffic and overlap data — not opinion about which pages "feel" outdated.

SITE: example.com
PAGES TO TRIAGE (URL, page topic, traffic trend over the last 12 months, last substantive update date):
/blog/best-crm-2023 — CRM roundup — traffic down 68% YoY — last updated Jan 2023
/blog/crm-vs-spreadsheet — comparison — traffic flat — last updated Mar 2026
/blog/what-is-a-crm — definition post — traffic down 40% YoY — last updated Nov 2022
OTHER LIVE PAGES THAT MIGHT OVERLAP: /blog/what-is-a-crm-software — near-identical definition post published later, currently getting more traffic

DECISION TREE — apply this to every page, in order, and stop at the first branch that applies:

1. DELETE if the page has near-zero traffic (state your threshold assumption if none is given), covers a topic no longer relevant to the business, and has no meaningful backlinks pointing to it — deleting a page nobody links to and nobody visits costs nothing and removes thin-content dilution from the site.
2. MERGE/REDIRECT if the page's topic substantially overlaps with another live page in /blog/what-is-a-crm-software — near-identical definition post published later, currently getting more traffic — name the specific overlapping page, and recommend a 301 redirect into it rather than leaving two thin, competing pages live. State which of the two should survive as the merge target, based on which currently has more traffic, more backlinks, or a stronger ranking position — not simply whichever is newer.
3. UPDATE if the page still gets meaningful traffic but the content itself is stale — outdated statistics, a broken or irrelevant CTA, a screenshot of a UI that's since changed, information that's since become inaccurate. Name the specific stale element, not a generic "needs a refresh."
4. LEAVE ALONE if the page is still accurate, still gets traffic, and has no overlap — the honest default when nothing above applies, since a working page shouldn't be touched just to appear active.
5. INVESTIGATE FURTHER if traffic dropped sharply but you can't tell from the data given whether the cause is content decay, a lost backlink, an algorithm update, or a technical issue (deindexing, a broken canonical) — say so explicitly rather than guessing a content-based cause for a problem that might not be about content at all.

OUTPUT
A table: URL | Traffic trend | Last updated | Verdict | Specific reason. Group the results by verdict at the end so the update list, the merge list, and the delete list are each easy to hand off separately.