Discussion
  • Content SEO

After merging five overlapping articles into one, how long did the new URL take to reach their combined traffic, and did it ever fully get there?

Published 1 reply

Discussion starter: a content SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The short answer: the timing varies too much for one number, and “the combined traffic of all five” is usually the wrong finish line. The redirect step is often quick for URLs Google crawls frequently (days to a few weeks), but the merged page settling into its new ranking range commonly takes longer. Whether it ever matches the old total depends mostly on how much of that total was real, addressable demand rather than overlap.

    If the five articles competed for the same queries, part of their combined clicks came from searchers seeing two of your URLs at once, or from Google rotating between them. One page can only hold one of those positions. If some of the five ranked for genuinely distinct long-tail queries that the merged page now covers in a single paragraph, some of that traffic will not return either. On the other hand, if cannibalisation was holding all five back, the merged page can beat the old total. Both outcomes happen often enough that neither should be treated as the default.

    Public evidence here is thin. Published consolidation case studies are mostly single-site write-ups chosen because they went well, and few adjust for seasonality or sitewide trend. I would set expectations from the mechanism and from a query-level baseline rather than from anyone’s headline percentage.

    What happens between the redirect and the new ranking

    Googlebot recrawls each old URL (timing depends on how often each one was crawled)
    ↓
    Permanent redirect seen: treated as a signal that the target should be canonical
    ↓
    Old URL drops out of results; links and other signals consolidate on the target
    ↓
    Does the merged page satisfy each old query cluster as well as the old page did?
    ↓
    Rankings settle over weeks to months, including through any core update in the window

    Google’s redirect documentation says that with a permanent redirect, “the indexing pipeline uses the redirect as a signal that the redirect target should be canonical.” That happens URL by URL as each old page is recrawled. It explains why the tail takes longer: the article that earned 20 clicks a month and is crawled rarely may be processed weeks after the popular one.

    Google’s site move guidance is the nearest documented reference for timing. It says “for medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones”, and advises keeping redirects “for as long as possible, generally at least 1 year” because “This timeframe allows Google to transfer all signals to the new URLs.” A five-URL merge is far smaller than a site move, so the redirect step is usually faster. The one-year advice is still a useful reminder that signal transfer is gradual and that removing redirects early is a real risk.

    The redirect is only half the story. The other half is a ranking question: is the merged page the best result for each query the five pages used to win? Google’s Gary Illyes said in 2016 that 30x redirects no longer lose PageRank. That addresses signal loss, not relevance. Consolidating links does not make a page that covers everything rank for everything.

    Why the sum of five overstates the realistic target

    Source of the gap What it looks like How to check it
    Overlapping queries Two or more of the old URLs earned clicks on the same query in the same month Export Search Console data by query and page for all five URLs and count queries shared by more than one URL
    Double listings Two of your URLs appeared on page one together; after the merge you hold one slot Compare positions by page for the same query and date range
    Distinct tails not served An old URL ranked for specific long-tail queries; the merged page mentions the topic briefly Queries where the old URL had clicks and the new URL has impressions but a weak position
    Pre-existing decline The five were already losing traffic before the merge Plot 12 to 16 months before the merge, not just the last three
    SERP and algorithm changes AI Overviews, new SERP features or a core update landing in the measurement window Compare against a control group of articles you did not touch
    Content cut in the edit Sections trimmed to keep the merged page readable Diff the old pages’ sections against the new page’s headings

    A better benchmark than combined traffic

    1. Export 12 to 16 months of Search Console data by query and page for all five URLs.
    2. For each query, take the best single URL’s monthly clicks rather than summing across URLs. That approximates the ceiling one page could realistically hold.
    3. Tag each query as core (the merged page should serve it), peripheral (served by a section) or dropped (intentionally out of scope).
    4. Adjust for trend using a control group: comparable articles on the same site that were not changed during the same period.
    5. Mark the merge date with a Search Console custom annotation, so anyone reading the chart later sees the change.

    The target then becomes “the core and peripheral ceiling, adjusted for the control group’s trend”. The merged page can realistically meet or beat that number, and the gap by query tag tells you where to work.

    Hypothetical example:

    Five articles about repotting houseplants earned 3,000 clicks a month combined. The query export shows about a third of those clicks came from queries where two or three of the articles were earning clicks at the same time. Taking the best single URL per query gives a ceiling closer to 2,200. Of that, 300 came from queries about repotting orchids specifically, which the merged page covers in one short paragraph. The realistic target is roughly 1,900 to 2,200 clicks, not 3,000, and the orchid queries are a candidate for their own page.

    Checkpoints, and when to worry

    A pattern practitioners often describe is a short dip or wobble while redirects are processed, followed by the merged URL picking up the old queries over the following weeks. I would not attach firm numbers to that, because it depends on crawl frequency, site strength and whether a core update lands mid-way. Checkpoints are more useful than a single expected date.

    • First one to two weeks: old URLs should start appearing as “Page with redirect” in the Page indexing report, and URL Inspection should show the target indexed with itself as the Google-selected canonical. If an old URL is still indexed after several weeks, confirm it returns a 301 or 308 (not a 302 or a JavaScript redirect) and that internal links, sitemaps and canonical tags point straight at the target.
    • Weeks four to eight: the merged URL should have impressions for most core queries. Impressions without clicks on a cluster usually means the page ranks, but not well enough: a relevance or depth problem in that section.
    • Month three onwards: compare against the adjusted ceiling. If core queries have recovered but a peripheral cluster has not, the merge may have buried a distinct intent.

    Choices that change the outcome more than waiting does

    • Keep the strongest existing URL as the destination. Creating a brand-new URL means five redirects into a page with no history. Redirecting four pages into the one with the most links, traffic and crawl frequency is a smaller change.
    • Update internal links to point directly at the destination rather than relying on the redirects.
    • Keep genuinely distinct intents separate. If one of the five answered a different question (a comparison, a local version, a specific product), merging it trades a strong specific answer for a weak paragraph.
    • Give each former intent a clearly labelled section with the best material from the original, so the merged page still answers each query directly.
    • Avoid rewriting the merged page repeatedly in the first weeks. Every edit makes it harder to tell what caused what.

    Watch for this:

    Traffic is not the only yardstick. A merged page that recovers most, but not all, of the realistic ceiling while converting better, because readers are no longer bouncing between near-duplicates, may be the better business outcome. Check conversions and assisted conversions for the cluster before calling the merge a failure.

    How to test it if more merges are planned

    If this is one of many clusters, merge in waves. Consolidate half of the candidate clusters, hold comparable clusters back as a control, and compare after about 12 weeks.

    • Primary metric: clicks on core queries as a share of each cluster’s adjusted ceiling.
    • Secondary metrics: conversions from the cluster, ranking distribution for core queries, and whether the merged URL ranks for queries none of the old URLs held (a sign consolidation added strength rather than just moving it).
    • Confounders: core updates, seasonality and sitewide changes, which the control group should absorb if the clusters are comparable.
    • What would change the decision: if merged clusters hold or beat their adjusted ceiling while controls are flat, keep going. If they plateau well below it, check whether you are merging distinct intents before blaming the redirects.

    The question I would actually answer

    If this were my site, I would stop measuring against the sum of five and ask something narrower: did the merged page recover the queries it was meant to serve, relative to a realistic ceiling and a control group? If yes, the consolidation worked even if the headline number is lower. If core queries are still missing after about three months, look at how the page covers each intent before you look at the redirects, and be willing to split out a section that clearly deserved its own page.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.