DANA: New one. A site has built up around sixty old pages over the years, blog posts, a few thin product descriptions, some event pages from things that already happened. Most of them pull almost no traffic. The owner’s instinct is clean house, delete all sixty, on the theory that dead weight is dragging the whole site down. Do we back that?
MARCUS: Before anyone says “it depends,” let me steelman the delete instinct, because it’s not stupid. There’s a real idea underneath it, that a site bloated with low-quality pages can look weaker overall, and trimming the dead wood can help the pages that matter. That mechanism exists. So the owner isn’t wrong that quality across the site is a thing. They’re wrong that “delete sixty” is the same as “improve quality.”
HANNAH: And I want to flag the assumption baked into “no traffic” before we act on it. No traffic from where? If that’s organic search only, some of those pages might still earn links, get referral visits, or rank for something nobody’s tracking. “It gets no traffic” and “it has no value” are two different claims, and the owner is treating them as one. I’d want the actual data per page before a single deletion.
NOAH: Sixty pages is also not one decision, it’s sixty. Group them. My read on the instinct: the owner is pattern-matching all sixty into a single pile called “old and useless,” but the pile almost certainly splits. Some are genuinely dead, an event from three years ago that will never recur. Some are thin but on-topic and could be merged. Some are quietly useful and the owner just never looks at the analytics for them. One action across sixty mixed pages is the mistake.
ELENA: Right, and each of those groups has a different correct move, which is the part the owner is collapsing. A dead event page with no links and no value, fine, remove it and let it return a not-found, or redirect it if the URL has any equity. Several thin posts circling the same subject, those don’t get deleted, they get combined into one strong page that absorbs the topic. A thin page that’s still relevant gets expanded, not killed. And a page with no traffic but real backlinks gets kept or redirected so the link value isn’t thrown away. Same shelf, four different decisions.
PRIYA: And strategically, deletion is the move with the least upside and the most risk. If you improve or consolidate, worst case the page stays where it is. If you delete in bulk, you can remove URLs that were holding links, ranking for long-tail terms, or supporting a topic cluster, and you find out only after the traffic you didn’t know you had disappears. The owner sees sixty liabilities. Some of those are quiet assets.
SOFIA: There’s a question nobody’s asked the owner, and it changes everything. Why do they think the dead pages are dragging the site down? Is there an actual decline they’re reacting to, or is this housekeeping anxiety, a feeling that a tidy site must perform better? Because if there’s no measured problem, “delete sixty pages” is a risky cure for a disease we haven’t diagnosed.
MARCUS: That’s the real hit. The owner has a solution looking for a problem. “Bloat hurts us” is a hypothesis, not a finding. Show me the finding first.
GRACE: And once we know which pages survive in some form, there’s a content judgment on the merges that’s easy to botch. Combining four thin posts into one isn’t copy-paste. The merged page has to read as a single coherent piece, not four stitched-together fragments with the seams showing. A bad merge is just thin content at greater length. If we recommend consolidation, we own making the result actually good, not merely bigger.
THEO: Process layer, because this request will come back. The owner reached for “delete everything” because they don’t have a way to evaluate a page. So the deliverable isn’t sixty individual verdicts handed down from us. It’s a simple sorting question they can run on any page, now and next year. For each page: does it get any value, traffic, links, or relevance? If yes, keep or improve it. If it overlaps another page, merge them. If it’s genuinely dead, remove it and handle the URL. Teach the sort, not just the cleanup.
AIKO: And the systems angle on top of that. Sixty pages accumulated because nothing was ever retired on a schedule. The fix that prevents a repeat isn’t this one cleanup, it’s a habit, a periodic content review where pages get sorted before sixty of them pile up. One-time cleanups treat the symptom. A review cadence treats the cause.
MARCUS: Better. Though I’ll point out we’ve now talked the owner out of the easy thing and into real work across sixty pages. That’s correct, but somebody should say out loud that “audit and sort sixty pages” costs more than “delete sixty pages,” and the owner needs to know the trade before they agree to it.
DANA: Good, say it plainly then. Here’s the decision. We don’t delete sixty pages in one swing. Not because deletion is never right, but because sixty mixed pages don’t share one right answer, and bulk deletion is the only option here that can destroy value we can’t get back. What we do instead, in order. First, ask the owner what problem they’re actually seeing, because we may be solving nothing. Then pull per-page data, traffic, links, and relevance, and sort the sixty into keep, improve, merge, and remove. Then act per group, and if we merge, we make the merged pages genuinely strong, not just longer. And we set up a review rhythm so this doesn’t rebuild. Marcus is right that this is more work than the delete button, so that trade goes to the owner up front, in plain words, before we start.
HANNAH: Which protects whatever quiet value is sitting in that pile instead of bulldozing it to feel tidy.
DANA: That’s the frame. The goal was never sixty fewer pages. It was a stronger site, and you don’t always get there by subtraction.