Official statement
Other statements from this video 38 ▾
- 1:07 Is Google automatically switching back to mobile-first after fixing asymmetry errors?
- 1:07 Is it true that mobile-first indexing is stuck: how long until automatic unlocking?
- 3:14 Does Google flag missing images on mobile: Should you ignore these alerts if your mobile version is intentionally different?
- 3:14 Should you really fix the missing images detected by Google on mobile?
- 4:15 Does mobile-first indexing really improve your ranking on Google?
- 4:15 Does mobile-first indexing really impact your page rankings?
- 5:17 How does Google blend site-level and page-level signals to rank your pages?
- 5:49 Should you prioritize domain authority or optimize page by page?
- 11:16 Does functional duplicate content really harm your SEO ranking?
- 11:52 Is Google really ignoring duplicate boilerplate content without punishment?
- 13:08 Do you really need multiple questions in an FAQ schema to get a rich snippet?
- 13:08 Should you really abandon the FAQ schema on single-question product pages?
- 14:14 Does schema markup really help you land featured snippets?
- 15:45 Do featured snippets really depend on structured markup or visible content?
- 18:18 Is Google penalizing CSS-hidden FAQ content in an accordion?
- 18:41 Does the FAQ schema really work if answers are hidden in a CSS accordion?
- 19:13 Should you merge two cannibalizing pages or let them coexist?
- 20:58 Can you really combine canonical and noindex without risking your SEO?
- 21:36 Can you really combine canonical and noindex without risk?
- 23:02 Does the exact order of keywords in your content really affect your Google ranking?
- 23:22 Does the order of keywords on a page really impact Google rankings?
- 27:07 Does the order of keywords in the meta description really affect CTR?
- 27:22 Should you really align the word order in your meta description with the target query?
- 29:56 Does Google really understand your synonyms better than you do?
- 30:29 Should you really stuff your pages with synonyms to rank on Google?
- 31:56 Should you create mixed pages to cover all meanings of a polysemous keyword?
- 34:00 Should you create specialized pages or general pages to rank effectively?
- 35:45 Should you optimize your site for synonyms, or does Google really handle it all by itself?
- 37:52 Does Google really give a 6-month notice before any major SEO changes?
- 39:55 Does Google really announce its major algorithm changes 6 months in advance?
- 43:57 Why are multilingual footer links crucial on every page?
- 44:37 Why do your hreflang links fail when they point to a homepage instead of an equivalent page?
- 44:37 Why does linking to the homepage undermine your hreflang strategy?
- 46:54 Subdomains or Subdirectories for Internationalization: Which Hreflang Architecture Does Google Really Favor?
- 47:44 Should you opt for subdirectories or subdomains for a multilingual site?
- 48:49 Should you add footer links to your multilingual homepages in addition to hreflang?
- 50:23 Does your shared IP really harm your SEO rankings?
- 50:53 Can shared cloud IPs really harm your SEO?
Google confirms that merging two pages on the same topic only makes sense if they are already struggling to rank. When two pieces of content are already occupying top spots, consolidating them won’t yield any extra gains—and could even reduce your coverage on varied queries. The decision should be made on a case-by-case basis, depending on current performance, not based on a mechanical rule of consolidation.
What you need to understand
Why does this statement challenge a common SEO practice?
For years, content consolidation has become something of an SEO reflex. Two pages on the same topic? Just merge them. The idea—not inherently wrong—is to avoid keyword cannibalization and to concentrate relevance signals on a single URL.
Mueller introduces a critical nuance here: this logic only applies if the pages underperform. If your two pieces of content are already in 1st or 2nd position, merging them won't skyrocket your traffic. Worse—you're at risk of losing coverage on query variants that each page was capturing independently.
What is keyword cannibalization in this specific context?
Cannibalization occurs when Google hesitates between two of your pages for the same query and neither really rises. The result: you plateau on page 2 or 3, while a single stronger page could have reached the top 3.
But if your two pages are already well-ranked, it’s no longer cannibalization—it’s strategic coverage. Each might be targeting a slightly different intent or a semantic variant, which explains why they coexist without harming each other.
When does merging become counterproductive?
Imagine you have a page titled “Best CRMs for SMEs” in position 1, and another “Free CRMs for SMEs” in position 2. Merging them risks diluting the specificity of each: the intent of “free” vs “best” is not the same, and Google may no longer know which query you are targeting.
Then you could lose visibility on one or both pages. This is exactly what Mueller wants to avoid: a mechanical consolidation that ignores current performance and the nuances of intent.
- Merging pages only makes sense if they struggle to rank (page 2, 3, or beyond).
- Two well-positioned pages often cover distinct intent variants—merging them can reduce your reach.
- The decision should be made on a case-by-case basis, analyzing the current performance and the queries each URL captures.
- A blind consolidation, without prior analysis, can do more harm than good.
SEO Expert opinion
Is this statement consistent with practices observed in the field?
Yes—and it’s even a welcome confirmation of a recurring observation. In audits, we regularly see sites that have merged high-performing content purely out of an obsession to “clean” their structure. The result: traffic drop, loss of positions on secondary queries, sometimes irreversible.
Mueller sets the record straight: consolidation is not an end in itself. It's a lever to be activated when signals show that two pages are stepping on each other’s toes without either emerging. If they complement each other, why sabotage them?
What nuances should be added to this rule?
The first nuance: Mueller talks about pages in 1st or 2nd position, but what about positions 3 to 5? This is a gray area. A page in 4th position could rise to 1st with enhanced content… or lose ground if merged with another page in 6th that targets a too different variant. [To verify]: no clear directive from Google on this intermediate zone.
The second point: the query volume. Two well-ranked pages but on keywords with 10 searches/month might justify a consolidation if it simplifies maintenance. The decision also depends on the opportunity cost—maintaining two pieces of content takes time, updates, and interlinking.
In what scenarios does this rule not apply?
If your two pages have radically different user intents—for example, “how to choose a CRM” (comparison guide) vs “installing a CRM in 5 steps” (technical tutorial)—merging them would be a strategic mistake, even if they target the same semantic universe.
Another borderline case: pages with high transactional potential vs informational content. A product page “CRM X” and a guide “reviews on CRM X” should never merge, even if they target the same keyword. Google distinguishes intentions, and so do your users.
Practical impact and recommendations
What steps should you take before deciding to merge two pages?
First step: export GSC data for the last 12 months, filtered by URL. Identify for each page the queries where it appears, its average position, and its organic traffic. If both pages capture different queries, even slightly, the merge is risky.
Next, check the incoming backlinks: a page with 50 quality links shouldn’t be redirected lightly. You might be losing potential juice, especially if the anchors point to specific content that you're going to dilute. Use Ahrefs, Majestic, or SEMrush to map those links.
What mistakes should be avoided during content consolidation?
Classic mistake: redirecting with a 301 without incorporating the strong elements from each page. If you merge A and B, ensure that the new page C includes the key sections, secondary keywords, and on-page optimizations from both sources. A simple redirect without a redesign = a sure loss.
Another trap: forgetting internal linking. If 30 pages were pointing to the old URL B, make sure they now point to C with coherent anchors. Don’t leave it to Google to recalculate on its own—guide it.
How can you check if the merge has harmed your performance?
Strict tracking in GSC: compare the 30 days before and after the merge. Total traffic, average positions, number of queries captured. If you see a drop of more than 15% in traffic or indexed queries, it’s a red flag—perhaps the pages were targeting too different intents.
Also use a position tracking tool (Ranks, SEMrush, Monitorank) to track the specific keywords of each old page. If one of them drops drastically, consider recreating a dedicated page or enriching the corresponding section in the merged content.
- Export GSC data from both pages over 12 months to compare captured queries
- Check the backlink profile of each page before any redirects
- Incorporate the strong elements (sections, keywords, optimizations) from both content pieces into the merged page
- Update internal linking to point to the new URL with coherent anchors
- Monitor post-merge performance for at least 60 days (traffic, positions, queries)
- Have a plan B: if the merge fails, be able to quickly reactivate a dedicated page
❓ Frequently Asked Questions
Dois-je fusionner deux pages si l'une est en 1re position et l'autre en 6e ?
Comment savoir si deux pages se cannibalisent vraiment ?
Une fusion de pages fait-elle perdre du PageRank via les redirections 301 ?
Peut-on défusionner des pages après coup si ça ne fonctionne pas ?
Combien de temps faut-il attendre pour mesurer l'impact d'une fusion ?
🎥 From the same video 38
Other SEO insights extracted from this same Google Search Central video · duration 52 min · published on 14/05/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.