Two WordPress Articles Answer the Same Question: Merge or Separate

Keep two overlapping articles when each one serves a different reader, task, or product, and make that difference obvious in their titles and openings. Merge them when they answer the same question for the same reader, so you maintain one complete answer instead of two partial ones. Decide by comparing what each page actually says, not by a shared keyword, and settle the editorial decision before anyone touches URLs.

The content maintenance section of the WordPress SEO reference introduces keeping, improving, and combining pages. This guide covers the specific case of a pair: how to map them, how to choose, and what to hand to whoever implements the change.

Confirm the overlap is real

Two articles on the same subject are not necessarily duplicates. Before comparing content, check whether they compete in practice.

In Google Search Console’s Performance report, open the Queries tab, click a query, then open the Pages tab to see which of your URLs Google showed for it. Google’s Performance report common tasks, checked September 27, 2026. If both articles appear for the same queries, readers searching that question may land on either one. If they appear for different queries, the overlap may be only in your mind.

Then ask the people who use the pages. If support sends customers to one article and never the other, that is evidence too.

Map what each page actually answers

Read both articles and fill in a comparison. Work from the text, not the titles.

The last three rows protect material you might lose in a merge. A short article can still hold the only photograph of a technique, a form sales relies on, or the address in a printed brochure.

Choose separate purposes or one complete article

Use the map to pick one of three outcomes.

Google’s helpful content guidance asks whether a reader leaves feeling they learned enough to achieve their goal, and whether content leaves them needing to search again. Google’s guidance on creating helpful content, checked September 27, 2026. Two half-answers can fail that test where one complete answer passes it. But the same guidance warns against removing a lot of older content mainly because you believe it will help rankings by making the site seem fresh, so merge because readers are better served, not to reduce a page count.

Two worked decisions

These examples use the fictional garden.example site and are illustrative.

A justified merge. “When to prune roses” (2022) and “Rose pruning calendar” (2024) both tell homeowners which month to prune shrub roses. The newer article has a clearer calendar; the older one has a section on climbing roses and a diagram of where to cut. Same reader, same task. Decision: move the climbing roses section and the diagram into “Rose pruning calendar”, check the facts in both, then redirect the 2022 URL to it.

A justified decision to keep both. “How to prune roses” is a homeowner’s step-by-step guide. “Rose pruning service” describes what the studio’s visit includes, the area served, and how to book. They share the phrase “rose pruning” and some background, but one helps a reader do the job and the other helps a reader decide whether to hire someone. Decision: keep both. Trim the repeated background from the service page, and link each page to the other where the reader’s choice arises.

Write the consolidation and redirect handoff

Once the editorial decision is made, write it down for whoever will implement it. A clear handoff prevents a developer or a later editor from guessing.

CONSOLIDATION HANDOFF

Keep URL:      /rose-pruning-calendar/
Retire URL:    /when-to-prune-roses/
Material moved: Climbing roses section; cut diagram (with alt text)
Material dropped: 2022 weather note (outdated)
Redirect:      /when-to-prune-roses/  ->  /rose-pruning-calendar/  (301)
Internal links to update: 4 posts (listed below)
Menus, forms, printed material that use the old URL:
Title and description for the kept page: revised, attached
Approved by:   Editor, factual owner

Google’s guidance supports redirecting consolidated pages. Its site move documentation warns against redirecting many old URLs to an irrelevant destination such as the homepage, which might be treated as a soft 404, but says that when content from several pages has been consolidated into one, you can redirect the old URLs to that consolidated page. It also recommends keeping redirects for as long as possible, generally at least one year. Google’s documentation on site moves with URL changes, checked September 27, 2026. A permanent redirect is a signal that the target should be the canonical URL. Google’s redirects documentation, checked September 27, 2026.

If you use WP Visibility, turning on the Redirects module lets you add the 301 rule from the old path to the kept one; the procedure and its checks are in Redirect a changed URL. The rule does not take the retired post out of the plugin’s sitemap while that post is still published, so move it to draft or trash once the redirect works. The plugin carries out a decision you have made. It does not judge whether two articles serve the same reader.

Check the result

1. Open the retired URL in a private window and confirm it lands on the kept article with a single redirect.
2. Confirm the kept article includes the moved material and reads as one piece, not two pasted together.
3. Update internal links so they point straight to the kept URL rather than through the redirect.
4. Check that the retired URL no longer appears in your sitemap.
5. Revise the kept article’s title and description so they describe the combined content.
6. Record the change and the date in your content inventory.

If you decided to keep both, check that their titles and openings now make the difference plain, and that each links to the other. For the broader question of which articles need attention first, see choose which WordPress articles to update first.