Keyword to URL Mapping for an Existing Site
Assign every keyword to exactly one URL and expose the pages that are cannibalising each other.
Maps a keyword set onto the URLs of an existing site, assigning one owner page per keyword, flagging cannibalisation where several pages compete, and recommending consolidate, redirect, rewrite or create for each gap.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are an SEO consultant building a keyword-to-URL map.
Context:
- Keywords: {{keyword_list}}
- Site URLs with their titles and topics: {{url_inventory}}
- Site type: {{site_type}}
Task: Produce a mapping table with:
1. Keyword
2. Owner URL (exactly one)
3. Confidence in the assignment (high / medium / low)
4. Competing URLs that could also claim it
5. Verdict: OWNED, CANNIBAL, GAP, WRONG-FIT
6. Recommended action (keep, consolidate into X, redirect A to B, rewrite, create new)
7. Effort (S / M / L)
Rules:
- One owner URL per keyword. If two pages fit equally, mark CANNIBAL and name the page that should win.
- Mark GAP only when no existing page could reasonably be rewritten to serve the keyword.
- Never recommend a new page where a rewrite would do.
- Do not invent URLs that are not in the inventory.
- Distinguish suspected overlap from cannibalisation supported by supplied query-level evidence.
- Explain every medium/low-confidence assignment and identify the missing evidence.
- Deduplicate redirects across keyword rows; flag chains, loops and conflicting destinations before presenting the consolidation plan.
Finish with: a consolidation plan listing every redirect in the form OLD -> NEW, and the keywords each move protects.Estimated results
Editor's note
Why this prompt matters
On any site older than a year, the cheapest ranking gains are almost never in new content. They are in the pages you already have that quietly compete with each other, splitting links and confusing Google about which one to serve. This prompt builds the map that makes that visible: one owner URL per keyword, every competing page named, and a verdict on each row. The consolidation plan at the end is often a short list of redirects that recovers positions no amount of new publishing would have.
Anatomy
Prompt engineering breakdown
Role
Context
Goal
Constraints
Output format
What you'll get
Expected output
Worked example: an outdoor-storage retailer
This generic retailer wants to commission more content, but its supplied inventory suggests that overlapping collections need attention first. The example uses relative URLs exactly as provided; it does not assume any unlisted pages exist.
The inventory contains five pages:
/storage-boxes: “Outdoor Storage Boxes”; the main collection, covering all sizes and materials./garden-boxes: “Garden Storage Boxes”; a second collection showing substantially the same products./deck-boxes: “Deck Storage Boxes”; a narrower collection for patio and deck placement./guides/box-care: “Storage Box Care”; cleaning and maintenance advice, with little weatherproofing detail./bike-sheds: “Bike Sheds”; a dedicated bicycle-storage collection.
Keyword ownership
Confidence describes the strength of the assignment from the supplied inventory, not the likelihood of ranking. Effort estimates cover editorial and structural work, excluding development dependencies.
| Keyword | Owner URL | Confidence | Competing URLs | Verdict | Recommended action | Effort | |---|---|---|---|---|---|---| | outdoor storage boxes | /storage-boxes | Medium | /garden-boxes | CANNIBAL | Consolidate /garden-boxes into /storage-boxes | M | | garden storage boxes | /storage-boxes | Medium | /garden-boxes | CANNIBAL | Redirect /garden-boxes to /storage-boxes after consolidation | M | | deck storage boxes | /deck-boxes | High | /storage-boxes | OWNED | Keep; clarify deck-specific selection criteria | S | | how to weatherproof a storage box | /guides/box-care | Medium | None identified | WRONG-FIT | Rewrite with material-specific maintenance and limitations | M | | bike sheds | /bike-sheds | High | None identified | OWNED | Keep | S |
Why these assignments win
The two broad box collections appear interchangeable. /storage-boxes is the provisional winner because its stated scope includes the whole range, not because its slug is inherently better. Before implementation, compare query-level performance, inbound links and conversions. Stronger evidence for /garden-boxes could reverse the proposed destination.
The deck collection should remain separate: its narrower shopping task can support useful product selection. A broad parent collection appearing as a possible competitor does not, by itself, prove cannibalisation.
The care guide is a rewrite opportunity, not a GAP. Its informational purpose fits the weatherproofing query, but its current coverage does not. Verify material-specific instructions against product documentation; do not imply that maintenance makes every box waterproof.
Consolidation plan
/garden-boxes -> /storage-boxes
Protected keywords: garden storage boxes, outdoor storage boxes.
Move useful selection advice before redirecting. Confirm that the destination retains the relevant products, then update internal links and remove the old URL from the sitemap. This is one redirect supporting two keyword rows, not two separate implementation tasks.
Under the hood
Why this prompt works
The one-owner rule is the constraint that produces the insight. Forcing a single URL per keyword means the model must resolve every contested case rather than listing both pages, and the CANNIBAL verdict is what falls out of the conflicts. Requiring a rewrite recommendation before a new-page recommendation biases the output toward the cheaper fix, and banning invented URLs keeps the whole map executable against your real site rather than an imagined one.
Model fit
Best AI models for this prompt
Claude
Best at spotting genuine cannibalisation and at choosing a rewrite over a new page.
ChatGPT
Handles the largest URL inventories. Paste page titles and a topic line with each URL.
Gemini
Strongest when you supply current ranking positions per URL so it can pick the winning page on evidence.
When to use
- Before approving new briefs for an established site.
- When query reports show alternating ranking URLs.
- Before migration redirect decisions are finalised.
- After an inventory reveals overlapping collections or guides.
When not to use
- On a new site without existing pages.
- Without a sufficiently complete URL inventory.
- For discovering or validating keyword demand.
- For proving cannibalisation without query-level performance data.
- For approving redirects without human and technical review.
Get more from it
Pro tips
- 1
Supply titles, topics and page types for every URL; bare slugs encourage guesses.
- 2
Review CANNIBAL rows first, but prioritise confirmed overlap and business impact—not the label alone.
- 3
Check every redirect for intent continuity, retained products, useful content and existing redirect chains.
- 4
Re-run after restructuring, using the updated inventory rather than obsolete URLs.
- 5
Include query-to-page performance data to distinguish actual competition from similar subject matter.
- 6
Label canonical, redirected and noindex URLs so they are not selected as owners accidentally.
- 7
For a second pass, challenge medium/low-confidence assignments with page excerpts and ask what evidence would change each winner.
Don't ship this
Common mistakes
✗ Letting two pages own the same keyword.
Fix — Force the single-owner rule and act on the CANNIBAL verdict.
✗ Creating a new page where a rewrite would do.
Fix — Check whether an existing URL could be rewritten before commissioning anything.
✗ Applying the redirect plan unchecked.
Fix — Review each OLD -> NEW pair against live traffic before shipping.
People also ask
Frequently asked questions
Q.What is keyword cannibalisation?
It is when several pages on your site compete for the same query, splitting internal links and confusing search engines about which to rank. The usual result is that none of them ranks as well as one consolidated page would.
Q.Should I consolidate or just deoptimise the weaker page?
Consolidate when both pages cover the same intent; deoptimise and re-angle when the weaker page has a legitimate separate purpose. The prompt names the winner and gives you the redirect pair when consolidation is the right call.
Q.How large a site can this handle?
A few hundred URLs in a single pass. For larger sites, run it per section or per template type, then reconcile the section maps to catch cross-section cannibalisation.