Three of your pages chase one query.
One query, one owner.

One install gives your agent a 6-phase SEO workflow whose spine is cannibalization governance: a mandatory ownership audit before any title, H1 or content change — with a fallback that works without Search Console access.

1 owner per query 6 phases 3 reference checklists 0 API keys

for coding agents · free, open, no auth

install

Copy one line. Get an owner map.

Detects Claude Code, Cursor, Codex, Qoder and more, then writes the skill into the right folder. Add --dry-run to see the plan first.

npx skills add arm-pz/keyword-guard

the six phases

Audit first. Content second.

The workflow is fixed, and phase 3 is a blocker: no title, H1, meta or content change is proposed until the ownership map is clean and signed off. Complements seo-audit (technical) and programmatic-seo (scale).

Plan 2

Baseline what ranks now, then build the cluster.

  • discovery
  • cluster architecture

Execute & measure 3

Only after the map is clean.

  • on-page
  • authority
  • measurement

The blocker 3

Every route into the audit: from Search Console when you have it, from the sitemap when you don't, and a hard check across the whole cluster.

  • gsc page × query map
  • sitemap fallback
  • title + H1 collision check

house rules

How it advises, always.

One query, one owner

The page with the most clicks and impressions owns the query. Every rival gets de-optimized and links to the owner instead of competing with it.

Concrete or silent

Recommendations cite data and specific pages — never "improve your content". Every choice is framed through search intent and query ownership.

White-hat, honest about time

No link schemes, no cloaking, no keyword stuffing. Ranked by impact × effort, with a straight warning that SEO compounds over months, not days.

Stop three pages fighting over one search result.

Free, open, and it runs entirely inside the agent you already use.

Install keyword-guard Read the source