OpenSEO Keyword Clustering

Goal

Group keywords into page-level clusters and decide which existing or new page should target each cluster. This is a keyword mapping workflow, not just a semantic grouping exercise.

Required inputs

• projectId
• A keyword list, saved keyword tag, seed topic, or target domain
• Optional existing URLs/pages to map against

If keywords are not provided, use listsavedkeywords for saved sets, researchkeywords for seed discovery, or getranked_keywords when the user starts from a target domain.

Project context

The project-context tools are free and shared with the app and other agents.

1. Call getprojectcontext first and ground the mapping in it — the saved key pages are the existing pages clusters should map to, and the business and goal decide which clusters are worth targeting.
2. This skill needs key pages. If none are saved, run a minimal inline setup: ask the user for the pages that matter, or propose a shortlist from the site, an audit, or Search Console and confirm it, write it back with updateprojectcontext (addKeyPages), then continue the clustering. Never front-load the full interview; suggest seo-project-setup at the end for the rest.
3. Before spending credits, check the research log. If the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.
4. On finish, write back what is durable with updateprojectcontext — new or corrected addKeyPages entries with the topic each page now targets — and append a research log entry: { appendResearchLog: { summary: "Keyword clustering: <keyword set>. Verdict: <conclusion>" } }.

OpenSEO MCP tools

• listsavedkeywords: fetch an existing keyword set, optionally filtered by tags.
• research_keywords: expand a seed when the user starts from a topic.
• getrankedkeywords: gather exact ranking keywords and URLs when the user starts from a domain or page.
• getsearchconsole_performance: when Search Console is connected, pull real queries with dimensions: ["query","page"] to map terms to the pages already earning impressions and to surface cannibalization (one query splitting clicks across multiple URLs).
• getserpresults: validate whether keywords belong on the same page by checking SERP overlap and intent.
• getlocalserp_results: use for local SEO clusters when Maps/local-pack intent should affect page mapping.
• save_keywords: optionally tag final clusters after user confirmation.

Workflow

1. Gather the candidate keyword set.

- Use getsearchconsoleperformance (dimensions ["query","page"]) when Search Console is connected to start from real queries and the pages already ranking for them. - Use getrankedkeywords for domain/page-driven clustering. - Use searchlocalbusinesses and getlocalserpresults when proximity, local packs, or Google Business results determine whether terms belong on location pages.

1. Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
2. Build clusters around intent and page type:

- Same SERP intent and similar ranking pages belong together. - Different intent, buyer stage, or SERP format should be split. - Similar words do not guarantee the same cluster.

1. For important borderline terms, use a small getserpresults batch to check overlap.
2. Assign each cluster to:

- Existing URL, if supplied and appropriate - New page recommendation, if no existing page fits - Do-not-target / later bucket, if weak or off-strategy

1. Identify cannibalization risk when multiple pages would target the same intent. When Search Console is connected, confirm it from real data with getsearchconsole_performance (dimensions: ["query","page"]) — the same query sending impressions to multiple URLs.
2. Ask before applying cluster tags with save_keywords.

Output format

Start with a short mapping summary:

• Number of clusters
• Pages to create
• Existing pages to update
• Cannibalization or consolidation issues

Then include:

For each cluster, include a recommended page brief:

• Page type
• Searcher problem
• Required sections
• Internal-link opportunities
• Save/tag suggestion

Guardrails

• Do not over-cluster tiny keyword sets. If there are fewer than 10 usable terms, produce a simple map.
• Do not rely on lexical similarity alone. SERP intent wins.
• Do not replace tags broadly without explicit confirmation.
• If existing URL data is missing, label target pages as proposed.