Two pages, one query. Decide the winner, then write for it.

One install chains two skills: Keyword-Guard audits the cannibalization — which pages compete for which query, who should own it, from Search Console or straight from the sitemap when you have no access — and Wordsmith writes the alternative titles, H1s and meta descriptions that de-conflict the non-owner. The audit is a blocker: nothing gets rewritten before the map is clean.

Install keyword-resolver Read the source
1 owner per query 2 audit paths 2-3 options per conflict 0 cross-canonicals

for coding agents · free, open, MIT

install

Copy one line. Settle the map, then settle the copy.

The install line from the repo README. This skill is a chain: keyword-guard and wordsmith must be installed too — if either is missing it says so and stops.

npx skills add arm-pz/keyword-resolver --skill keyword-resolver

the workflow

Audit, ownership, rewrite. In that order.

Phase one runs Keyword-Guard and blocks until the ownership map is signed off. Phase two hands each conflict to Wordsmith for alternatives that keep the loser's secondary traffic instead of gutting it.

Cannibalization audit blocker

Every page ranking for a target query is listed, from GSC (page+query dimension) or the sitemap fallback.

  • GSC cross-page query map
  • sitemap + title/H1 grep
  • homepage anchor flagged
  • mixed-language pairs checked
  • one owner assigned per query

De-optimization plan per loser

Non-owners lose the competing primary keyword and gain a distinct long-tail modifier, plus links toward the owner.

  • strip primary keyword
  • self-referencing canonicals kept
  • internal links point to the owner
  • merge only when pages truly duplicate

Alternatives 2-3 each

Wordsmith rewrites title, H1 and meta per conflict; hreflang sets for mixed-language sites are drafted with reciprocity checked.

  • owner keeps the primary phrase
  • loser gets a long-tail modifier
  • A points to B and B back to A
  • copy-paste ready

Outside its boundary 2 siblings

Technical crawl, index and performance diagnosis is the seo-audit skill's job; pages generated at scale belong to programmatic-seo. This skill settles who wins which query and rewrites accordingly. It does not touch your CMS — it hands back copy and a map.

  • no crawl diagnosis
  • no page generation
  • no direct site edits

ground rules

What it refuses to do.

One query, one owner

The page with the most clicks and impressions, the closest semantic match, or the designated pillar owns the query. Proposals without an owner assignment are not proposals, they are a second cannibal.

No cross-canonicals as a shortcut

Canonicaling one competing page to another hides the fight instead of settling it — it suppresses the non-canonical page. Ownership first; canonicals stay self-referencing unless pages genuinely merge.

Say which path was taken

GSC-measured and sitemap-inferred findings are labelled differently. A fallback audit is honest about being a fallback, because its blind spots are the traffic you cannot see.

Exactly one page wins each query — then the copy follows.

Free, open, and every rewrite traces back to an ownership decision.

Install keyword-resolver Read the source