Keyword research workspace

Turn a keyword list into reviewable groups and page opportunities.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Keyword research workspace

Turn a keyword list into reviewable groups and page opportunities.

## Deliverable
An import, clustering and export workflow with a sample dataset.

## Stack and visual direction
- Recommended starting stack: Next.js and TypeScript with a small data model. Build the core workflow with fixtures before connecting external services.
- Swiss grid: Use a visible modular grid, aligned baselines, asymmetric composition and tight typographic hierarchy. Reflow the grid without shrinking essential text. Apply this direction to the interface while keeping data and controls easy to read.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [OpenSEO](https://openseo.so/docs/skills) (Skill) — Run an appropriate site audit, keyword or local visibility workflow when data access is available.
  Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges. [Official setup](https://openseo.so/docs/agent-setup). Fallback: Inspect local page metadata, internal links and available first-party exports. Label unavailable competitive or search-volume data as unknown.
- [TanStack Table](https://github.com/TanStack/table) (Repository) — Implement headless sorting, filtering and pagination while owning accessible table markup.
- [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure.
  [Official setup](https://nextjs.org/docs/app/getting-started/installation).

## Workflow
1. Support CSV import and deduplication, retain market and source provenance, and group by search intent. Treat unavailable volumes as unknown and let users edit keyword groups.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] Duplicate terms merge by normalized term and market.
- [ ] Export reflects edited groups and preserves missing values as unknown.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path.
- [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.

Recipe resources

Source, setup, and compatibility details.