keyword-research
Keyword research
Keyword work decides what a site should try to rank for and which page should do it. The demand that matters most is the demand the site already touches: Search Console shows the queries earning impressions, and provider metrics (volume, keyword difficulty, CPC, intent) are estimates layered on top. The workflows come from every-app/open-seo's agent skills keyword-research, keyword-clustering, competitive-landscape and competitor-analysis (MIT, Copyright (c) 2026 Ben Senescu), with OpenSEO's tool calls reduced to the job they do so they work with any keyword-data provider; facts are checked against Google's Search Console API and Search Central docs. OpenSEO keeps project facts in its own project context; here they live in .agents/product-context.md, defined in anti-slop-copy CONTEXT.md. Search Console data itself (what the reports mean, the API, its limits) is search-console SKILL.md; on-page and technical SEO is seo SKILL.md; demand in AI assistants is ai-search-visibility SKILL.md.
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
| Seeds to a prioritized keyword set: Search Console striking-distance queries first, the workflow, local demand, prioritizing by fit, rank-tracking sets, the report | KEYWORDS.md |
| Grouping keywords by SERP intent, mapping each cluster to an existing, new or later page, confirming cannibalization from query and page rows | CLUSTERING.md |
| Who wins a search market (query set, domain types, local pack), one competitor's footprint, themes and weak spots, SEO vs business competitors | SEO-COMPETITORS.md |
Shared SEO project context and research reuse and report delivery, including the HTML starter, live with SEO.