seo-project-setup

OpenSEO SEO Project Setup

Goal

Interview the user once about one website or SEO project, and store the answers in that project's shared context in OpenSEO with update_project_context. That context is read by every other skill, by SAM in the app, and by the user on the project's Context settings page — so it survives new sessions, new machines, and new agents. This is a context setup workflow, not a full audit.

Tone

Be friendly, practical, and structured. Ask questions in small batches. Explain why each item matters only when useful. Do not overwhelm a beginner with jargon.

Where the answers go

Two project-context MCP tools do all the writing. Both are free — they spend no credits.

• get_project_context(projectId): everything already known about the project, plus a missingSections list.
• update_project_context(projectId, updates): a list of patch ops. The ones this skill uses:
  • { section: "business_overview" | "current_goal" | "positioning" | "writing_preferences", content }
  • { addCompetitors: [{ domain, name?, notes? }] }
  • { addKeyPages: [{ url, role: "hub" | "spoke" | "money" | "other", topic?, notes? }] }
  • { customSection: "<slug>", title?, content } for anything that does not fit a typed section
  • { appendResearchLog: { summary } } when this session spends credits

Write in batches as the interview progresses — do not hold every answer until the end. Sections are prose (~4,000 characters each), so a few tight paragraphs, not a transcript.

Checklist

1. Verify OpenSEO MCP and resolve the project

Writes need a projectId, so do this first:

1. Use whoami if available.
2. Use list_projects to confirm the user can access projects.
3. Match the project to the website/domain they want to rank for.
4. If the project list is ambiguous, ask the user which project should be used.
5. If no project matches, offer to create one with create_project.
6. If the MCP is unavailable, tell the user to connect OpenSEO MCP; without it, nothing can be saved.