Others

⌘K
  2. Home
  4. Others
  6. Keyword Cannibalization Killer

Keyword Cannibalization Killer

With Keyword Cannibalization Killer, you can automatically detect keyword cannibalization across your WordPress site, understand why it’s happening through Claude AI-powered search intent analysis, and resolve it directly from your WordPress admin dashboard with 301 redirects, canonical tags, or content repositioning guidance, no manual spreadsheet audits required.

In this article, you’ll learn how to set up and use every feature of Cannibalization Killer.

For detailed instructions, please continue reading the full documentation. If you still have any questions, feel free to submit a support ticket.

Table Of Contents
  1. Overview
  2. Installation
  3. Dashboard
  4. Cannibalization Issues (Main Workspace)
  5. Issue Detail Page (Individual Deep Audit Workspace)
  6. Technical Fixes
  7. Settings & APIs
  8. Quick Setup Guide (Step-by-Step)
  9. FAQ's
  10. Changelog

Overview

Keyword Cannibalization Killer is an enterprise-grade WordPress SEO plugin designed to:

  1. Detect keyword cannibalization, instances where multiple pages on your site compete for the same search query, splitting your ranking authority, impressions, and clicks.
  2. Analyze search intent using Claude AI to determine whether competing pages are true duplicates (technical issue) or serve genuinely different user intents (editorial issue).
  3. Execute automated technical resolutions, applying 301 redirects, canonical tags, or content repositioning guidance directly from your WordPress admin dashboard.

The plugin connects to two external services to do this:

  • Anthropic’s Claude AI, for reading and reasoning about page content and search intent.
  • Google Search Console (GSC), for pulling real search query, impression, click, and ranking position data.

Installation

  1. Install the Keyword Cannibalization Killer plugin & activate it.
  2. After activation, a new menu, Cannibalization Killer, will be added to your WordPress admin sidebar.
  3. Navigate to Cannibalization Killer > Settings & APIs to begin.

Dashboard

The high-level command center for your site’s search health:

  • Active Collisions, total cannibalization clusters currently detected and unresolved. Shows how many are High Priority (competing on Page 1 of Google).
  • High Severity (Page 1), the number of conflicts where competing URLs rank in the top 10 search results, directly splitting click-through rates.
  • Resolved / Ignored, issues resolved via 301 redirects, canonical tags, or marked resolved.
  • Cannibalization Severity Distribution, a visual breakdown bar showing High, Medium, and Low severity proportions.
  • Top Collision Clusters, quick-access list of the highest-impact collisions with a direct Review > button.
  • Recent Scans, overview of recent scan executions and dates.
Image 40

  Cannibalization Killer dashboard overview and insights. 

Download Now

Cannibalization Issues (Main Workspace)

This is where you review, triage, and manage keyword conflicts.

Category Segmented Tabs (Top Filter)

  • All Conflicts, displays every detected conflict on the site (both analyzed and unanalyzed).
  • URL Redirection, shows technical issues verified by Claude AI that require 301 redirects, page merges, or canonicalization.
  • Content Repositioning, shows editorial issues verified by Claude AI where pages serve distinct search intents (e.g., a commercial product page vs. an informational documentation page) and should not be redirected, but rather have their titles, headings, and copy differentiated.
Image 39

Segment and analyze conflicts by category in Keyword Cannibalization Killer.

  • Search input, search by keyword query or URL slug.
  • Scan Selector, filter by a specific historical scan or view all scans combined.
  • Traffic Filters, quickly isolate queries with Has Clicks (>0), 500+ Impressions, or 1,000+ Impressions.
  • Severity Filters, filter by All, High, Medium, or Low.
  • Status Filters, filter by Detected (new), Analyzed (audited by Claude), or Resolved.
  • Sort Dropdown & Table Header Arrows, sort by Impact Score, most Impressions, most Clicks, Search Query(A-Z), Severity,Competing  URLs, Conflict Type, or Resolution Status.
Image 42

Search, filter, and sort conflicts in Keyword Cannibalization Killer.

Strategic Tools

  • Top Priority, an AI-powered high-level analysis that groups all collisions into prioritized executive action plans, cutting through keyword noise.
  • Consolidate Clusters, automatically deduplicates and merges identical URL signatures into clean master clusters.
  • Batch Actions, check multiple rows and click Analyze Selected to run Claude AI audits in bulk.
Image 48

           Strategic tools for prioritizing and managing conflicts in Keyword Cannibalization Killer. 

Table Columns

Each row in the issues table is made up of several columns that together summarize the conflict.

  • Search Query column shows the target keyword query, and displays a badge (e.g., +3) if multiple query variations are combined for the same URL set; clicking it expands the row to preview those child queries. 
  • Conflict Type column shows URL Redirection or Repositioning once the issue has been audited by Claude, or a dash if it is still awaiting AI analysis. 
  • Impact column is a composite score, from 0 to 100, calculated from search visibility, impression volume, and position proximity. 
  • Severity column is labeled HIGH if the pages rank on Page 1, MEDIUM if they rank on Pages 2 to 3, or LOW if they rank beyond Page 3. 
  • Traffic column shows the total Impressions and Clicks recorded for that query. 
  • URLs column shows the number of competing pages involved, and clicking it expands the row to preview each individual URL and its statistics. 
  • Resolution column shows the Claude recommendation, MERGE, 301 REDIRECT, DIFFERENTIATE INTENT, or Not Analyzed if no recommendation has been generated yet.
  • Actions column contains a Review > button that opens the deep audit workspace for that specific issue.
Image 49

Each row shows a conflict with query, impact, and resolution details in Keyword Cannibalization Killer.

Issue Detail Page (Individual Deep Audit Workspace)

Clicking Review > on any issue opens the detailed conflict resolution screen:

Header Bar:

  • Query name, conflict category badge, severity badge, impact score, and total impressions/clicks.
  • Preview Payload, lets you view the exact scraped page contents and prompt sent to Claude before execution.
  • Mark as Resolved / Reopen, manually mark an issue as solved or reopen it.
Image 44

  Top header displaying conflict summary, badges, and resolution controls 

AI Conflict Analysis and Strategy:

  • Strategy, the AI recommendation (MERGE, REDIRECT, CANONICALIZE, DIFFERENTIATE_INTENT, or LEAVE_ALONE).
  • Confidence Score, AI confidence level percentage (e.g., 85%).
  • Rationale, detailed reasoning explaining why the conflict exists and why this strategy was chosen.
  • Re-Analyze Conflict, re-scrape the live pages and re-run Claude AI.
Image 43

AI-driven strategic action plan card for resolving conflicts in Keyword Cannibalization Killer 

Implementation Road Map:

  • For Merge / Redirect, lists specific sections, topics, code snippets, or FAQs that exist on the secondary URLs that must be copied into the primary page so search ranking signals are preserved.
  • For Content Repositioning, provides step-by-step instructions on updating titles, H1/H2 headings, and internal linking to cleanly separate user intents without deleting either page.
Image 46

Step-by-step content recommendations for resolving conflicts and separating search intent

Competing URLs Section:

  • Primary Destination Card (Golden Crown), the statistically mandated primary page based strictly on Search Console data (highest clicks and impressions).
  • Secondary Page Variant Cards:
    • Shows URL, position, impressions, and clicks.
    • Action (301 Permanent Redirect), click the purple 301 Redirect button to instantly create a live 301 redirect rule in WordPress pointing to the primary page.
    • Canonical Override, option to set a custom rel=”canonical” tag pointing to the primary URL.
Image 52

Competing URLs section showing primary destination and secondary page variants in Keyword Cannibalization Killer 

Affected Search Query Variations Table:

  • Displays all secondary search queries contributing to this URL collision, along with individual impressions, clicks, and ranking position ranges.
Image 41

Affected search query variations contributing to each URL collision 

Technical Fixes

Manage all automated technical rules applied by the plugin:

Active 301 Redirects:

  • View all managed redirects with source paths and target URLs.
  • Track real-time hit counts for each redirect.
  • Toggle redirects active/inactive without deleting them.
  • Manually create custom 301 redirect rules.
Image 45

Manage and monitor automated 301 redirect rules in keyword Cannibalization Killer.

Canonical Overrides:

  • View custom canonical tags injected by the plugin into the WordPress <head>.
  • Edit or remove canonical overrides at any time.
Image 47

View and manage canonical overrides injected into the WordPress 

Settings & APIs

  • Claude AI Engine, API key management, model selection (Sonnet 3.7 vs. Haiku 3.5), word limit ceilings, and token pricing telemetry.
Image 51

Claude AI Engine

  • Search Console OAuth, Google OAuth Client ID/Secret, active connection status, and disconnect button.
Image 53

Search Console OAuth

  • Detection Rules, sensitivity settings, scoring weights, and custom excluded keywords.
Image 54

Detection Rules

  • Data & Storage, view row counts across all plugin database tables (ck_issues, ck_scans, ck_redirects, ck_ai_analysis). Includes options to prune old raw GSC data or perform a full factory reset.
Image 50

Data & Storage

  • System Health & Logs, diagnostics on PHP version, memory limits, database tables, and real-time log viewers for troubleshooting.
Image 56

System Health & Logs

Download Now

Quick Setup Guide (Step-by-Step)

Step 1: Configure the Claude AI Engine

  1. Go to Cannibalization Killer > Settings & APIs.
  2. Stay on the Claude AI Engine sub-tab.
  3. Paste your Anthropic Claude API Key (obtainable from console.anthropic.com).
  4. Choose your AI Model Selection:
    • Claude 3.7 Sonnet (Recommended), delivers superior reasoning for search intent (e.g., accurately protecting documentation/support pages from being accidentally redirected to sales pages).
    • Claude 3.5 Haiku, a fast, budget-friendly model for large websites with high volume.
  5. Set the Content Ceiling Per Page (default: 8,000 words). This controls how much page content is scraped and sent to Claude for analysis.
  6. Click Save All Settings & Test Connection. A green “Key Configured” badge will appear in the top right once the connection is verified.
Image 55

Configure Claude AI engine, select model, and connect API key in Keyword Cannibalization Killer settings.

Step 2: Connect Google Search Console (GSC)

  1. In Settings & APIs, switch to the Search Console OAuth sub-tab.
  2. Enter your Google Cloud OAuth Client ID and Client Secret (with the Google Search Console API enabled in your Google Cloud Console).
  3. Click Authorize with Google and select the Google account that owns the verified property.
  4. Once authenticated, your Search Console status in the top navigation bar will turn green (Connected), displaying your active property URL.
Image 57

Connect Google Search Console via OAuth and link your verified property in Keyword Cannibalization Killer settings.

Step 3: Configure Detection & Exclusions (Optional)

  1. Switch to the Detection Rules sub-tab in Settings:
    • Minimum Impressions / Clicks Threshold, filters out low-volume search queries that don’t meaningfully impact your SEO.
    • Custom Excluded Keywords, enter branded or navigational terms (e.g., your brand name, “login,” “my account”), separated by commas. Branded queries naturally rank across multiple pages and should not be treated as cannibalization.
  2. Click Save Detection Rules.
Image 59

Configure detection rules and keyword exclusions to refine SEO cannibalization analysis in Keyword Cannibalization Killer 

Step 4: Run Your First Search Console Scan

  1. In the top navigation bar, click Run GSC Scan (or + New Scan).
  2. Select your Search Console Property.
  3. Choose your Date Range:
    • Last 28 Days, best for recent cannibalization conflicts.
    • Last 3 Months, best for comprehensive authority analysis.
    • Custom Date Range
  4. Click Start Scan.
  5. The plugin queries the Google Search Console API in chunks, consolidates query variants into distinct URL clusters, calculates impact scores, and creates conflict candidate records.
  6. Once complete, click View Issues to inspect the results.
Image 58

Run a Search Console scan to detect and analyze keyword cannibalization issues in Keyword Cannibalization Killer 

Download Now

FAQ’s

1. Does Keyword Cannibalization Killer require a Google Search Console property to work?

Yes. The plugin relies on real Google Search Console data (impressions, clicks, and ranking positions) to detect cannibalization clusters and calculate impact scores, so a verified GSC property connection is required before running a scan.

2. Which Claude model should I use?

Claude 3.7 Sonnet is recommended for most sites, since it provides more accurate search intent reasoning (for example, correctly distinguishing a documentation page from a sales page). Claude 3.5 Haiku is a faster, lower-cost option better suited to large sites with a high volume of pages to analyze.

3. Will the plugin automatically redirect my pages without my approval?

No. Claude AI provides a recommended strategy (MERGE, REDIRECT, CANONICALIZE, DIFFERENTIATE_INTENT, or LEAVE_ALONE) with a rationale and confidence score, but 301 redirects and canonical overrides are only applied when you click the corresponding action button on the Issue Detail Page.

4. What happens to pages that serve different search intents?

If Claude determines that two competing pages serve genuinely different user intents (e.g., a commercial page vs. an informational page), it will classify the conflict as Content Repositioning rather than URL Redirection, and provide guidance on differentiating titles, headings, and copy instead of recommending a redirect.

5. Can I exclude branded or navigational keywords from detection?

Yes. Under Settings & APIs > Detection Rules, you can add custom excluded keywords (e.g., your brand name, “login,” “my account”) that will not be treated as cannibalization candidates.

6. Can I undo a 301 redirect or canonical override created by the plugin?

Yes. Both are fully manageable from the Technical Fixes screen, where you can toggle redirects active/inactive or edit/remove canonical overrides at any time.

Changelog

1.0.0

  • Initial Release.

How can we help?