Every blog that’s been running for a few years develops the same quiet problem: two or three posts that all answer nearly the same question, written months or years apart, each one unaware the others exist. This isn’t the plagiarism kind of duplication search engines penalize outright. It’s subtler and more common — self-inflicted overlap, where a site competes against itself for the same keyword instead of consolidating its authority into one strong page.
This post covers how to recognize that overlap, decide what genuinely counts as duplication versus healthy depth, and merge posts without losing whatever value each one had built up individually.
Overlap Versus Healthy Depth
Not every pair of related posts is a duplication problem. A cluster is supposed to have multiple posts covering the same broad topic from different angles, which is the entire point of the content clustering approach covered earlier in this series. The distinction that matters is whether two posts are answering different specific questions within a topic, or whether they’re answering the same specific question twice.
A post about choosing a grind size for pour-over and a post about choosing a grind size for espresso are related but distinct, since a reader with one question doesn’t necessarily have the other. Two posts both titled something like “the best grind size for pour-over coffee,” written eight months apart because the second one was written without remembering the first existed, are genuine duplication. The test isn’t topical closeness, it’s whether the same search query would reasonably be satisfied by either post interchangeably.
Why Self-Competition Actually Hurts
When two of your own posts target the same query, they don’t add up to double the ranking strength. In practice they tend to split whatever authority and relevance signal exists between them, meaning both posts often rank worse than a single consolidated post would. Search engines also have to guess which of your two pages is the more authoritative answer, and that guess doesn’t always land on the better-written one — sometimes the weaker, older post outranks the newer, more thorough one simply because of accumulated backlinks or age.
There’s a reader-facing cost too. Someone who finds both posts, notices they say almost the same thing, and can’t tell which one is meant to be the current or better version comes away with a slightly worse impression of the site’s overall quality and organization, even if each individual post is fine on its own.
Finding Overlapping Posts
The content audit covered earlier in this series is the natural starting point, since grouping posts by topic tends to surface overlap automatically once you can see everything side by side. Within any group that has four or more posts, read the titles and opening paragraphs together and ask which ones are answering literally the same question.
A useful confirming check is looking at Search Console data for the group. If two posts are both getting impressions for very similar or identical queries, and their average positions bounce around or trade places from month to month, that’s a strong signal search engines themselves are uncertain which of your pages should be the primary answer — a pattern that’s a fairly reliable fingerprint of genuine duplication rather than healthy topical breadth.
Doing this comparison by eye works fine for a handful of suspected pairs, but reading full post bodies against each other to judge genuine semantic overlap, rather than just similar titles, is slow and easy to get wrong when you’re the one who wrote both posts and remembers the distinctions you intended even if a reader wouldn’t notice them. This is one of the more valuable places to bring in something more systematic than memory and skimming, since the judgment of “would the same search query be satisfied by either page” is exactly the kind of comparison that benefits from reading full content rather than titles alone.
How to Merge Two Overlapping Posts
Once you’ve confirmed genuine overlap, pick the stronger post as the one that survives. Strength here usually means some combination of better current ranking, more backlinks, better structure, and simply being the more complete or better-written treatment of the topic — not just whichever one happens to be longer.
Go through the weaker post and pull out anything genuinely useful that the stronger post is missing: a subtopic it doesn’t cover, an example that’s better than what the survivor has, a statistic or detail worth preserving. Fold that material into the surviving post in the place it fits naturally, rather than appending it awkwardly at the end.
Once the surviving post has absorbed everything worth keeping, set up a 301 redirect from the weaker post’s URL to the surviving one. This tells both search engines and any existing backlinks or bookmarks pointing at the old URL where the content has moved, and it consolidates whatever ranking signal the old post had accumulated into the page that’s actually still live.
What Not to Merge
Occasionally what looks like duplication on the surface turns out to be genuinely distinct once you read closely — two posts that use similar language but are actually answering different reader intents, one more beginner-oriented and one aimed at an advanced audience, for instance. Merging these would actually reduce the site’s coverage rather than improve it, collapsing two useful, differently-targeted pages into one that serves neither audience as well.
The safeguard here is the same test from earlier: would the same search query reasonably be satisfied by either post interchangeably. If the honest answer is no, because the posts serve meaningfully different readers or questions despite surface similarity, they’re a candidate for better internal linking and differentiation, covered in the pillar page and internal linking posts earlier in this series, rather than for merging.
Preventing Future Overlap
The root cause of most duplication is simply forgetting what you’ve already written, which becomes more likely the larger a blog gets. Before starting a new post, a quick check of your own site for existing coverage of the same specific question is worth the two minutes it takes, and it’s a habit worth building into your writing process permanently rather than something you only do during an occasional audit.
Keeping an up-to-date map of which posts belong to which cluster, and what specific question each one answers within that cluster, makes this check far faster, since you’re scanning a structured list of questions already answered rather than trying to recall the contents of dozens or hundreds of old posts from memory.
The next post in this series turns the question around: once your clusters are cleaned up and merged, how many posts actually belong in a healthy topic cluster, and at what point does adding more content start working against you instead of for you.