# When to merge two pages, and how to do it without losing the ranking

You have two pages on the same topic and neither wins. This page shows when to merge, how to choose the keeper URL, how to combine the content, and how to set the 301. It also covers links, sitemaps and what to expect after the change.

Updated 2026-09-14 · Source: https://porteur.ai/guides/when-to-merge-pages

## When a merge beats a refresh

Merge when two pages rank on the same queries and neither does well, or when two pages answer one intent. A refresh keeps a single URL and updates it. A merge folds two or more into one better page and redirects the rest.

- Two URLs share queries and positions hover on page 2 or 3.
- You split one intent in two posts, each thin on its own.
- Clicks decay on both pages while rivals roll one strong guide.
- You published a follow up that duplicates half the first.

Do not merge if the intents differ. A “how to” and a “pricing” page should live apart. Merge only when one page can answer the query fully.

## Audit first, then decide keep, refresh, merge or remove

Run a lightweight content audit. List every page with clicks and impressions over 12 months, inbound links, date and purpose. Give each one decision: keep, refresh, merge, redirect or remove. Repeat each quarter and judge on the next quarter’s figures.

Content decay is steady loss of clicks and impressions over months while the rest of the site holds. Find it in Search Console. If both posts decay on the same queries, a merge often helps. If one holds and one decays, fold the weak into the strong.

> Delete only when a page has no clicks, no impressions, no links and no purpose for a year. Return 410 or 404. If a close equivalent exists, 301 instead.

## Check cannibalisation in Search Console

Open the Performance report, Pages. Compare the last three months to the previous three months. For seasonal sites, compare to the same period last year. Sort by the difference in clicks. Click into a falling page and read its queries. If the same queries also trigger another of your URLs, you likely split one intent.

1. **Find overlapping queries** Switch the tab from Pages to Queries for URL A. Export the list. Do the same for URL B. Look for the same head terms and modifiers.
2. **Judge intent** Open the results page for the top queries in an incognito window. If rival pages are single guides that cover both angles, you split one intent.
3. **Check which page Google prefers** In the Pages tab filtered by a query, see which URL got most impressions. Keep that URL if it also has more links and clicks.
4. **Confirm demand vs page drop** If impressions for the query fell, demand fell. If impressions stayed steady but average position worsened, your pages fell. A merge can help in the second case.

> A page family earns when each page holds data or an answer of its own that a reader would want. Do not make near-duplicates at scale.

## Which URL to keep

Keep the URL with more links and clicks. This preserves equity and reduces risk. If both are weak, choose the cleaner slug that fits the intent and has some history.

- More inbound links from good sites.
- More clicks over the last 12 months.
- A slug that matches the primary query, for example “/blog/merge-blog-posts-seo”.
- A page that already earned internal links from key pages such as “/pricing” or “/guides”.
- A page not blocked by parameter quirks or legacy query strings.

If one URL sits in a dead section like “/news/2019/…”, move its content to the healthier section by folding into the better URL. Keep the winner’s address intact.

## How to fold the content into one page

You are not pasting two posts back to back. You are building one clear page that answers the intent end to end. Keep the keeper’s structure if it fits. Pull across the parts from the other page that were better than yours.

1. **Map the overlaps and gaps** Mark duplicate sections. Mark unique value on each page. Keep the best version. Remove repetition. Fill gaps the results page now demands.
2. **Rework the title and h1** Match the primary query within about 60 characters for the title. Write a clear h1. Do not stuff variants. Make one promise and keep it.
3. **Answer the current results page** Search your head term. Note People Also Ask, featured snippets, and common subtopics. Bring missing answers in. Do not add fluff.
4. **Update facts, screenshots and links** Fix stale dates, prices and UI captures. Replace dead links. If a tool changed, rewrite the steps. This is a real update, not a repaint.
5. **Consolidate media and anchors** Move the best images and diagrams. Keep one set of anchor IDs if you have a table of contents. Fix any in-page links.
6. **Add a short note for returning readers** At the top, one line: “Updated September 2026: combined with our X guide, added steps for Y.” Keep it factual.

> Show a visible date and the same date in datePublished and dateModified. Only change the date for a significant update. Do not roll dates without edits.

## Set the 301, canonicals and sitemap entries

Redirect every merged URL to the keeper with a 301. This tells browsers and search engines the move is permanent. Update rel=canonical on the keeper to self reference. Remove or update canonicals on the old URLs after the redirect lands.

- Put the 301s at the server or framework level, not via JavaScript.
- One hop only. Old URL to keeper. No chains.
- Keep query parameters you still support. If not, drop them cleanly.
- If you had language versions, review hreflang and point all variants to the merged equivalents.
- Update your XML sitemap so only the keeper appears. Remove the merged URLs from the sitemap.

In Search Console, use the URL Inspection tool to test the keeper. Then request indexing for the old URLs after the 301 is live. The Index Coverage will show Page with redirect for those soon after the next crawl.

## Fix internal links and navigation

Update every internal link that pointed at the old pages. This includes blog posts, nav menus, footers, sidebars, and any hub pages. Change anchor text to match the new focus where it makes sense. This helps the crawler and keeps users on a single path.

1. **Find links to the old URLs** Search your codebase for the old slugs. Crawl the site with your preferred crawler and export inlinks. Fix them in templates first, then in content.
2. **Repair breadcrumbs and hubs** If you have a pillar page that linked both, update it to link the keeper only. Remove duplicate nav items that point to the same intent.
3. **Check for orphan risks** If you removed the only links to a related deep page, add a link from a relevant section in the merged page.

## What to expect after the merge

Expect some fluctuation in the first weeks. Google needs to crawl the redirects, consolidate signals and test the new page. If you chose the stronger URL and improved the content, steadier impressions and better average position should follow as of the next few crawls. Watch queries, not vanity spikes.

- Clicks to the old URLs will drop to zero in Search Console. Their report rows will show Page with redirect.
- The keeper’s queries list will grow as signals fold in. Average position may wobble before it settles.
- Featured snippets and People Also Ask can switch hands. If you targeted them in the merge, you can win them back.
- If demand fell for the query itself, a merge cannot fix that. Your impressions will reflect the market.

Set a reminder for 28 days and again at 3 months. Compare the last three months to the previous three months in the Performance report. Judge on clicks, impressions and position across the combined queries. If results are flat, revisit gaps on the current results page and your internal link support.

## Worked example: two posts into one

Say you have “/blog/merge-blog-posts-seo” posted in 2023 and “/guides/consolidate-content” posted in 2024. Both rank for “merge blog posts seo” and “combine similar pages”. Each sits at positions 12 to 18. Neither earns steady clicks. You decide to merge.

1. **Pick the keeper** “/blog/merge-blog-posts-seo” has five decent backlinks and more historic clicks. Keep it. You will fold the guide into it.
2. **Plan the structure** Your outline becomes: When to merge. Check cannibalisation. Choose the URL. Fold content. Set 301. Fix links. What to expect. FAQ.
3. **Move the unique value** The guide had a good section on internal link fixes and a table on redirect rules. You move those, edit for flow, and remove duplicates.
4. **Refresh for 2026** You add a callout on Google’s spam policies as of March 2024. You rewrite steps to match the current Search Console layout. You retake screenshots.
5. **Revise title and h1** Title: “Merge blog posts for SEO: when and how to do it”. H1: “When to merge two pages, and how to do it without losing the ranking”.
6. **Publish and set redirects** 301 “/guides/consolidate-content” to “/blog/merge-blog-posts-seo”. Update the XML sitemap to remove the old URL. Update nav and any hub links.
7. **Track outcomes** In 28 days, impressions start to concentrate on the keeper. At 3 months, average position improves across the shared queries. You keep iterating.

A fixed page looks like one clear guide that answers the full intent. It holds one URL, one title and a clean set of internal links pointing at it from related posts and key pages like “/guides/seo”.

## Avoid pitfalls: thin merges, date games and scale abuse

- Do not glue two weak posts and call it done. Add missing answers the results page shows today.
- Do not republish with a new date unless you made a significant update. Show visible dates and use datePublished and dateModified.
- Do not create many near-duplicates to chase variants. Scaled content abuse, site reputation abuse and expired domain abuse are all in Google’s spam policies as of 2026.
- Do not chain redirects. One hop only. Fix internal links to the keeper to avoid chains you built yourself.

## Questions

### How do I know if two posts target the same intent?

Look at the queries each page earns in Search Console. If 70 percent of the head and mid terms match, and the results page shows single comprehensive guides, you split one intent. Open the results page and read the common subtopics. If one page can cover them all without bloating, merge.

### Should I change the keeper URL’s slug when I merge?

No. Keep the proven URL. It already has links and clicks. Change the title and on page content to fit the new scope. If the slug is very off topic and has no equity, consider a separate clean-up project with a redirect map, but do not mix that with the merge.

### Will I lose rankings after a 301 merge?

You may see short term dips while signals consolidate. If you chose the stronger URL, improved the content and fixed internal links, rankings usually stabilise or improve. Track queries on the keeper and judge after 28 days and again at three months.

### Do I need to update the XML sitemap after a merge?

Yes. Remove the old URLs and keep only the merged URL. A sitemap is not a directive, but it helps discovery. It also keeps your reports cleaner, because Page with redirect entries you list in sitemaps can distract you.

### What if demand fell for my main query?

A merge will not create demand. Check impressions for the query in Search Console. If those fell while your position held, the market shrank or the results page layout changed. In that case, refresh to meet the new layout or target adjacent queries with new pages where the intent differs.

## Read next

- [Keyword cannibalization: two pages, one search, and how to fix it](https://porteur.ai/guides/keyword-cannibalization): Two pages ranking for one query cost you clicks. See it in Search Console, pick a winner, merge or canonicalise, and know when to keep both.
- [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each.
- [A content audit for a small site: one table, one decision a row](https://porteur.ai/guides/content-audit): Build a one-table content audit you can finish in a day. See what to keep, refresh, merge, redirect or remove, and what to fix first next quarter.
- [How to refresh a page that lost its traffic](https://porteur.ai/guides/content-refresh): Find why a page lost clicks, refresh what searchers want now, and measure the result. Keep the same URL, update facts, sections, links and date.
- [Delete or redirect an old page: 301, 404 or 410](https://porteur.ai/guides/delete-or-redirect-old-pages): Decide per page: 301 if a clear equivalent exists, else 404 or 410. Check links and clicks first, avoid home page redirects, and monitor what Google drops.
- [Internal linking for a small site: which pages link to which](https://porteur.ai/guides/internal-linking-for-seo): Decide which pages rank. Build hubs, write clear anchors, fix orphans, and crawl your site to map links you control.
- [SEO for a marketplace: two sides, category pages, and the listings](https://porteur.ai/guides/seo-for-marketplaces): Build category and location pages for demand. Let listings win the long tail only when they help searchers. Control facets, schema, and pruning.

Paste a URL, and get a free check in about thirty seconds that reads your site and the searches around it, plus three findings you can act on today. Free check: https://porteur.ai/