Share your site in this keyword cannibalization tool and get a severity-ranked conflict list with a specific fix for each competing page pair.
Juma connects to your Google Search Console data and cross-references query-level performance to detect keyword cannibalization across every indexed page on the site. It identifies where multiple pages compete for the same query, where position oscillates because Google keeps alternating between pages, and where split authority holds both pages out of the top 5. Every conflict gets a severity rating and a specific verdict: merge with a 301 redirect, sharpen each page's keyword focus, or archive the weaker page.
Once the analysis flags two pages that should be combined, this step produces the merged content. You get the strongest sections from both pages, a consolidated keyword target, a new title and meta description, and the 301 redirect instruction for the page being retired.
Some pages overlap on keywords but serve different search intents and should both stay live. This step redefines the keyword focus for each page, rewrites their titles and metas to stop them from competing, and recommends internal links between them so they support each other instead of splitting authority.
A Juma Project is a shared space where the team stores everything Juma needs to know about a client. Create one project per client, add context as you go, and Juma will use what's relevant every time the team runs a flow. If the project already exists from other work, just add the items below.
Add a short description in the project's info field that tells Juma what each file contains and when to use it. For example: "Content Inventory: full page list with keyword targets, last updated March 2026. Past Audit: January 2026 audit, check if past cannibalization issues were resolved. Site Architecture: topic cluster map showing pillar pages and supporting content."
This Flow replaces a full working day of manual Search Console analysis with an automated report that delivers in minutes. A 100-page site requires 6-8 hours of manual cross-referencing to map query overlap. A 500-page site takes multiple days and still misses position volatility patterns that only appear in week-over-week comparisons.
The severity ranking rates each conflict as critical, moderate, or low. Critical means both competing pages sit outside the top 5 on a high-volume keyword, directly costing traffic. Moderate means one page ranks well but the other suppresses its authority by appearing in the same results. Low means minimal traffic impact with little urgency to act immediately.
Critical conflicts are the highest priority because they represent active traffic loss. Google cannot decide which page is more relevant and keeps alternating between them, preventing either from accumulating the ranking authority it needs. Resolving a critical conflict, typically through a merge or a strong differentiation, produces the fastest measurable ranking improvements. Moderate and low conflicts are worth resolving but can be batched into a content maintenance cycle rather than treated as urgent fixes.
This keyword cannibalization tool detects conflicts by cross-referencing Search Console query data across every page, not just on-page keywords. It identifies where Google shows multiple pages from the same site for the same query, and where position oscillates week to week because Google keeps alternating between two competing pages.
Standard SEO audits check on-page keyword overlap, but two pages can share no exact keywords and still cannibalize each other on queries neither directly targets. On-page analysis alone misses these hidden conflicts. The combination of query-level overlap detection and volatility analysis catches keyword cannibalization SEO problems that stay invisible in standard content audits, performance reviews, and even manual Search Console exports. Many of the conflicts this Flow surfaces are ones the team did not know to look for.
Every conflict receives one of three verdicts: merge (redirect the weaker page to the stronger one with a 301), differentiate (rewrite titles and metas so each page targets a distinct intent), or archive (remove the weaker page if it adds no unique value). Each verdict gives the team a clear path to fix keyword cannibalization on that specific conflict. The recommendation depends on content overlap, traffic levels, and each page's ranking potential.
Merge applies when two pages cover the same topic and intent, and neither adds unique value the other lacks. Combining them into one authoritative page is the strongest fix for critical conflicts. Differentiate applies when the pages serve genuinely different intents but are written too similarly for Google to rank them separately. Archive applies when the weaker page has no meaningful traffic, no inbound links, and no content the other page does not already cover.
Keyword cannibalization analysis returns the most value for sites with 50 or more indexed pages covering overlapping topics. Smaller sites with fewer clearly distinct pages rarely generate enough query overlap to produce actionable conflicts. The Flow still runs accurately on smaller sites and will return no conflicts if none exist.
Large blogs, ecommerce category pages, multi-author publications, and agency client sites with years of archived content are the most common cases where the analysis surfaces a meaningful number of conflicts. The ideal site has a growing content library where the same broad topics appear across multiple pages, often written at different times by different authors. Over time, even well-organized sites develop cannibalization as the content library grows and keyword targeting decisions from earlier publishing phases stop matching the current strategy.
