// Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
| name | seo-project-setup |
| description | Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake. |
Help the user set up a local SEO workspace for one website or SEO project. The folder is where the agent saves notes, goals, exports, briefs, reports, preferences, and project context over time. This is a workspace and context setup workflow, not a full audit.
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.
Suggest that the user choose or create a local folder for SEO work, for example:
~/SEO/<company-or-site>/~/Documents/SEO/<company-or-site>/Explain that keeping notes, exports, briefs, scraped pages, reports, and preferences in one folder helps the agent build context over time. Future SEO workflows can use that folder rather than starting from a blank conversation.
Recommended starter structure:
seo-workspace/
README.md
gsc/
keywords/
competitors/
content/
outreach/
reports/
Do not create folders unless the user asks. If file tools are available and the user asks, create a simple structure and a short README.md with the current goals, known sites, and user preferences for how the agent should approach SEO for this project.
Ask for:
Ask the user what they want from SEO:
Ask for success metrics and timeframe. If goals are vague, help turn them into measurable goals such as "increase non-branded organic signups" or "rank top 10 for 20 buying-intent terms."
Ask what research they have already done about the company, product, audience, and competitors. Request any notes, docs, customer interviews, positioning docs, pitch decks, landing pages, or strategy memos they can share.
Probe for:
If the user has not done this yet, offer to help research positioning using the company website, competitor pages, reviews, forums, and web search.
After the user has described the company, website, goals, and positioning, check that OpenSEO MCP is configured and mapped to the right project:
whoami if available.list_projects to confirm the user can access projects.Do not run research tools just to test connectivity; whoami and list_projects are enough.
Ask the user to export a CSV from Google Search Console and place it in the SEO working folder.
Recommended exports:
Ask them to drop files into gsc/ and use names like:
gsc/queries-last-3-months.csv
gsc/pages-last-3-months.csv
gsc/queries-last-16-months.csv
gsc/pages-last-16-months.csv
Explain that GSC data reveals existing impressions, near-ranking terms, cannibalization, and pages that already have search demand.
Ask for or discover:
After intake, recommend one next OpenSEO workflow:
keyword-research: when the user needs ideas from seed topicskeyword-clustering: when they have keywords or GSC data to map to pagescompetitive-landscape: when the market is unclearcompetitor-analysis: when they know a competitor to studylink-prospecting: when they have a linkable asset or target pageUse a checklist with statuses:
| Step | Status | Notes | Next action |
|---|
Then summarize:
Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.
Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.
Cluster keywords by intent and map them to existing or proposed pages.
Discover keyword opportunities, evaluate metrics and SERPs, and save/tag promising terms.
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.