openseo-project-setup

Bind a repository to an OpenSEO project and initialize local SEO state directories.

31|5|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill openseo-project-setup-moizibnyousaf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openseo-project-setup
Source: https://github.com/MoizIbnYousaf/marketing-cli/tree/main/skills/openseo-project-setup
Command: npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill openseo-project-setup-moizibnyousaf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting SEO work on a fresh project requires a stable OpenSEO project binding, connected Google Search Console data, and prepared local state directories, and doing this manually is error-prone and easy to skip. ## Core Features & Use Cases - Project Binding: Resolves or creates the correct OpenSEO project via MCP and writes the canonical .seo/openseo.json binding file. - GSC Connection: Guides Google Search Console setup for hosted, self-hosted, or file-fallback modes and verifies connectivity with get_search_console_performance. - Cost-Safe Handshake: Uses only free whoami and list_projects calls for connectivity checks, never spending DataForSEO research credits during setup. - Use Case: You clone a repo and want to start keyword research. Run this skill once to link the repo to your OpenSEO project, confirm GSC access, and get routed to the right next SEO skill. ## Quick Start Set up OpenSEO for this site and connect Google Search Console so I can start keyword research.

Frequently Asked Questions about openseo-project-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an OpenSEO project for a new repository?▼

Run the setup workflow, which checks catalog readiness with mktg seo status, resolves or creates the OpenSEO project via MCP, and writes the binding to .seo/openseo.json. It is a one-time-per-repo handshake that prepares all downstream SEO skills.

How do I connect Google Search Console to OpenSEO?▼

For hosted OpenSEO, connect GSC in the project's Integrations page and verify with get_search_console_performance. Self-hosted setups need GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and a BETTER_AUTH_SECRET, or you can place CSV exports under .seo/gsc/ as a fallback.

Does OpenSEO setup work without an API key or MCP connection?▼

Without OPENSEO_API_KEY or an MCP connection, the skill stops after a gap note and points you to Exa-backed keyword research with metrics marked unknown. The binding and GSC steps require at least API-key-level configuration.

Why does the setup skill avoid running keyword research calls?▼

Every OpenSEO research call spends DataForSEO credit, so a setup handshake must not trigger them. Only the free whoami and list_projects calls are used to verify connectivity and resolve the project.

What happens if brand positioning files are missing during SEO setup?▼

The skill tolerates missing brand files and notes the gap, recommending the /cmo foundation workflow first. SEO inputs without positioning are treated as guesses, and brand/keyword-plan.md is left as a template until real research populates it.