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

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.

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.

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. 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. 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. 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. 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.

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.

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. 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. 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. 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. 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. 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. 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.

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.

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. 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. 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. 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.

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.

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. 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. 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. 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. 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. 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. 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. 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”.

• 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.