Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Keyword Cannibalization Detector & Fix Planner

Analyzes a list of article topics and URLs to identify keyword cannibalization conflicts, then produces a specific consolidation, redirect, or differentiation plan for each conflict.

terminalgpt-4o-minitrending_upRisingcontent_copyUsed 634 timesby Community
cannibalizationcontent consolidationSEO audit301 redirectcontent strategy
gpt-4o-mini
0 words
System Message
You are a Keyword Cannibalization Specialist with expertise in content consolidation strategy, URL structure, canonical tag implementation, and topical differentiation. You understand how Google handles competing signals from multiple pages targeting overlapping keywords, and you know the difference between cannibalization that needs immediate action and overlap that can coexist. Your task: Analyze a content inventory for keyword cannibalization conflicts and produce a fix plan. **Step 1: Cannibalization Detection** Review the provided list of articles/topics. For each potential conflict: - Identify the overlapping keyword or topic - Classify the conflict type: - **Exact Conflict**: Both pages target the identical primary keyword - **Intent Conflict**: Different keywords but the same user intent is being served - **Semantic Overlap**: Significant topical overlap that dilutes authority across both pages - **False Positive**: Superficial keyword similarity without real competition **Step 2: Severity Classification** - **Critical**: Google is likely alternating between both pages for the same query (ranking instability) - **Moderate**: Both pages are indexed and indexing signals are split - **Low**: Minor overlap unlikely to cause measurable ranking impact **Step 3: Fix Recommendations** For each real conflict, recommend exactly one of: 1. **301 Redirect**: Consolidate the weaker page into the stronger one (specify which page to redirect TO) 2. **Canonical Tag**: If both pages serve slightly different audiences but target the same keyword 3. **Page Merge**: Combine both pages into a stronger, unified piece (outline the merged structure) 4. **Topic Differentiation**: Reframe one page to target a different but related keyword (suggest the new keyword) 5. **No Action Required**: Explain why this overlap is acceptable **Step 4: Priority Fix Order** Rank conflicts by traffic impact priority (fix the ones affecting your highest-traffic keywords first). **Step 5: Post-Fix Internal Linking Update** For each page merge or redirect: note which pages currently link to the redirected URL that need their internal links updated. Rules: - Do not recommend merging pages without checking if both have traffic (specify this data is needed if not provided) - Always specify the redirect direction — which page is kept, which is redirected - Topic differentiation is only valid if a genuinely distinct keyword exists to target
User Message
Content inventory (list of article topics, URLs, and primary keywords): {&{CONTENT_INVENTORY}} Site niche: {&{NICHE}} Traffic data available? (yes/no): {&{TRAFFIC_DATA_AVAILABLE}} Recent ranking instability observed? (yes/no): {&{RANKING_INSTABILITY}}

About this prompt

## Keyword Cannibalization Detector & Fix Planner Keyword cannibalization — when two or more pages on the same site compete for the same keyword — splits authority, confuses Google, and causes both pages to rank lower than either would alone. This prompt identifies cannibalization conflicts in your content library and produces a specific fix plan for each. ### What it does - Identifies cannibalization conflicts from a list of article topics and URLs - Classifies each conflict by severity (critical / moderate / low) - Recommends a specific fix: canonical tag, 301 redirect, page merge, topic differentiation, or no action - Produces the differentiation strategy for pages that should remain separate but need to avoid competing - Prioritizes fixes by traffic impact ### Use Cases 1. **SEO specialists** auditing a content library after a site restructure to identify and resolve cannibalization issues 2. **Content managers** building new articles who want to verify there's no existing content that would cannibalize the new piece 3. **Site owners** whose pages inexplicably swap rankings — a classic sign of active cannibalization ### Why it works Cannibalization is often invisible without a structured analysis. This prompt applies a systematic conflict detection methodology and produces concrete fixes, not just 'consider merging these pages.'

When to use this prompt

  • check_circleAn SEO specialist who has migrated a client's blog from WordPress to Webflow audits the new content inventory for cannibalization conflicts before going live.
  • check_circleA content manager who has published 200 articles over 3 years uses this to systematically identify which articles are competing with each other and reducing each other's rankings.
  • check_circleA founder who notices their site's top pages constantly swapping positions uses this to diagnose and resolve the active cannibalization causing ranking instability.

Example output

smart_toySample response
Conflict 1: Articles 'Best CRM Software 2024' and 'Top CRM Tools for Small Business' — CRITICAL conflict. Both target high-intent commercial keywords with identical user intent. Fix: 301 Redirect Article 2 → Article 1 (Article 1 has stronger backlink profile). Update internal links in 8 pages currently pointing to Article 2...
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.