Merge overlapping blog posts when they answer the same question for the same reader and one coherent page can preserve their useful material. Keep them separate when they help readers make different decisions or complete different tasks.
Before retiring a URL, decide what must survive, where the combined article will live, and how someone following an old link will reach it. A merge is an editorial change with a URL plan. It doesn't guarantee better rankings or AI citations.
Check whether the posts solve the same problem
A shared topic can contain different reader tasks.
Read both articles before comparing their keywords. For each one, finish this sentence: “After reading this, a person should be able to…”
If both endings describe the same outcome, investigate the overlap. If one article helps someone plan a project and the other helps them fix a failure during that project, they may deserve separate pages even when their vocabulary is similar.
Use these distinctions to make an initial decision:
| What you find | A useful next step |
|---|---|
| The same reader, question, and outcome, with repeated explanations | Consider a merge and identify the distinct material worth preserving. |
| A shared subject but different tasks or stages | Clarify each page's purpose and link between them where useful. |
| An article with an accurate purpose but missing or outdated information | Update that article. |
| Duplicate or very similar versions that must remain available at different URLs | Investigate canonicalization separately from an editorial merge. |
| Low traffic without an identified content problem | Gather more evidence before removing or combining anything. |
For example, “how to prepare a photo book” and “how to fix blurry photos in a photo book” share a subject. They don't promise the same result. A person troubleshooting one image shouldn't have to work through the whole planning guide to find the relevant help.
Our guide to choosing blog topics your customers need explains how to define a useful question before assigning it a page.
Use search data as evidence to investigate
Google Search Console's Performance report lets you review clicks and impressions by page or query and change the date range. Look at the relevant queries alongside the actual content and any documented customer questions.
A query appearing against two pages doesn't, by itself, establish that one should disappear. Ask what each page contributes to the person making that search.
The query table is incomplete: Google omits anonymized queries and limits the rows it stores and shows. An absent query therefore doesn't prove that nobody needs the answer. See Google's query details and limitations.
If the question is which existing article deserves attention first, start with our content update guide.
Write a merge plan that preserves useful material
Map the useful material before retiring a source article.
Choose the surviving page by its fit for the combined reader task. Review its URL, existing links, search history, useful content, and place in the site. A shorter address or a larger recent traffic figure shouldn't settle the decision on its own.
Then list what each source article contributes. Separate repeated introductions from useful examples, instructions, tables, images, and qualifications. Write a new outline around the reader's task before moving sections into it.
A worked example: three articles from a fictional photo-book service
Imagine a service with these three articles. The pages, paths, and content inventory below are invented for this example. They are not a real site's audit or evidence of measured search performance.
| Article and hypothetical path | Reader outcome | Useful material |
|---|---|---|
“How to prepare a photo book” — /blog/prepare-a-photo-book |
Gather photos, arrange the book, and review it before ordering | A clear preparation sequence and an example showing how captions relate to photographs |
“Your photo book preparation checklist” — /blog/photo-book-checklist |
Check that the book is ready for review | Repeated preparation advice, plus a useful photo-to-page planning table and a compact final checklist |
“How to fix blurry photos in your book” — /blog/fix-blurry-photos |
Investigate a problem with a particular image | A focused troubleshooting procedure |
The first two articles serve substantially the same preparation task in this fictional inventory. Combine their useful material at /blog/prepare-a-photo-book. Keep the troubleshooting article separate and link to it at the point where readers check their images.
That decision follows from the content described here. Different real pages could justify a different choice.
Map each useful element into the finished guide
A merge plan should say where the material goes:
| Material to preserve | Its home in the combined article | What the editor should check |
|---|---|---|
| Preparation sequence from the main guide | The article's main sequence | Each step appears once, in an order a beginner can follow. |
| Photo-to-page planning table from the checklist article | The section about arranging photographs | The table keeps its useful fields and has a short explanation. |
| Caption example from the main guide | The section about matching photographs and captions | The example still makes sense after the surrounding text changes. |
| Final checks from both articles | One review checklist near the end | Repeated items are combined and distinct checks remain. |
| Link to the troubleshooting guide | The image-review step | Readers with a specific problem can reach the focused answer. |
This produces a combined guide with a visible sequence: gather the photographs, arrange them, match their captions, and review the result. It preserves the planning table and example without making readers read two introductions.
Before removing the second article, compare the combined version against both source pages. Can someone who relied on either old page still find the useful material they came for?
Save the originals and the mapping in your internal editorial record. That record gives you something concrete to inspect if a reader later reports that a useful detail disappeared.
Give the old URL a useful destination
Old links should lead directly to a relevant replacement.
When an article permanently moves into a replacement, use an appropriate permanent redirect for the retired URL. Google recommends a server-side redirect where possible; HTTP 301 and 308 indicate a permanent move. See Google's redirect guidance. Your CMS or hosting setup determines how to implement it.
For the fictional example, the intended result is:
| Address | Intended behavior after the merge |
|---|---|
/blog/prepare-a-photo-book |
Remains available with the combined guide. |
/blog/photo-book-checklist |
Permanently redirects directly to the combined guide. |
/blog/fix-blurry-photos |
Remains available as a separate troubleshooting article. |
The destination must fulfill the old page's purpose. Google allows old URLs to redirect to a relevant consolidated page, but warns against redirecting unrelated pages to an irrelevant destination such as the homepage. See its site-move guidance.
If the proposed destination doesn't contain the material the old article promised, finish the editorial work or reconsider the mapping before retiring the page.
A canonical link serves a different purpose
A canonical declaration indicates a preferred representative URL for duplicate or very similar pages. Google treats it as a signal; it doesn't forward a visitor's browser to that page. A redirect handles the visit to an address you're retiring.
Use the approach that fits whether the old version still needs to remain accessible. Don't add a canonical declaration to two different-purpose articles merely because both mention the same topic. Google's canonical URL guidance explains the supported methods and the importance of consistent signals.
Verify the change from both addresses
Give the person handling the URL change a concrete check:
- Open the retired address and confirm that its permanent redirect goes directly to the intended replacement.
- Confirm that the replacement loads successfully and contains the promised table, examples, qualifications, and any retained media.
- Check that the replacement's canonical URL points to the intended surviving address.
- Update your internal links to point directly to that address and keep the sitemap consistent with the pages you intend to publish.
Google's canonical guidance recommends linking to the preferred URL and avoiding conflicting canonical signals. Its migration guidance covers updating internal links and sitemaps.
Keep the redirect working beyond launch. For URL migrations, Google recommends retaining redirects for as long as possible, generally at least a year, and considering longer retention for visitors following old links.
Our guide to internal links that help readers can help you choose the new link placement and wording.
Record the result before judging its effect
Record the source URLs, surviving URL, material preserved, date of the merge, and the reason for the decision. Save a baseline for the relevant search queries and pages, alongside any customer task or business purpose the content serves.
After launch, check that the retired address still reaches the correct destination and that the combined guide remains usable. For search observation, review the old and surviving pages together over comparable periods. A decline at a retired URL is expected after moving its content; that number alone can't tell you whether the combined guide helps readers.
Google's migration guidance notes that search visibility can fluctuate during URL moves. Don't turn an early change into a claim that the merge succeeded or failed. Investigate the destination, relevant queries, demand, and other changes before assigning a cause.
The immediate completion test is concrete: one coherent article preserves the useful answers, distinct tasks still have suitable pages, and old links reach the right destination.