Set up an SEO project
Create durable project context before running research. Keep this workflow local unless the user explicitly asks to associate it with Rankizz.
Invoke Rankizz MCP tools
When using Rankizz through MCP, the initial tool list is intentionally compact. Call search_tools with a capability query or exact domain-tool name and set includeSchemas: true unless the arguments are already known. Invoke a discovered tool with call_read_tool when its readOnlyHint is true; use call_tool for every other tool. Pass the discovered name as tool and its original input object as arguments. REST callers continue to use the direct /api/v1/tools/<tool-name> endpoint.
Gather the minimum context
Inspect the current workspace before asking questions. Reuse information already present in briefs, analytics exports, repository files, or an existing project summary.
Collect only missing information that affects the work:
- canonical website and relevant subdomains
- business model, products, and positioning
- target audiences and their problems
- primary countries, languages, or local markets
- business and SEO goals
- known business and search competitors
- conversion actions that matter
- constraints, exclusions, compliance needs, and tone
- available sources such as Search Console, analytics, keyword exports, audits, or Rankizz
Do not block setup on unknown fields. Mark them as unknown and list the most valuable follow-up question.
Create or update the workspace
Use an existing user-selected folder when provided. Otherwise create an seo-project folder in the current working directory. Do not overwrite existing content without reviewing it.
Create this minimal structure only when it is useful:
seo-project/
PROJECT.md
audits/
keywords/
competitors/
research/
reports/
Write PROJECT.md using references/project-template.md. Keep facts separate from assumptions and record the source and date for important evidence.
Do not store passwords, API keys, OAuth tokens, private customer data, or copied credentials in the workspace.
Associate Rankizz only when requested
If Rankizz MCP is already connected and the user wants cloud workflows:
- Call
list_projectsbefore creating anything. - Match by canonical domain and organization context.
- Ask before calling
create_projectwhen no safe match exists. - Save only the returned project ID and public project URL in
PROJECT.md; never save credentials.
Rankizz-hosted API or MCP access requires at least 10 credits. If access reports a low balance, link the user to https://www.rankizz.com/billing and continue the local setup without Rankizz.
Finish
Return:
- the workspace path
- a short project summary
- known evidence sources and their dates
- assumptions and unanswered questions
- the next best skill to run
Recommend one next workflow based on the user's goal: site audit, keyword research, clustering, competitive landscape, competitor analysis, or link prospecting.
- Downloads
- 76All time
- Security audit
- Pass
- Last updated
- 2d ago
- Current version
- v1.0.0
- License
- MIT-0
