ProSEO
← Home

Getting started

Install the plugin, run one command, then decide whether you want a single check or the whole programme.

Install

  1. Add the plugin to Claude Code

    Clone the repository and point Claude Code at it as a plugin marketplace. The skills are auto-discovered from skills/, so there is nothing to register by hand.

  2. Let the Python runtime build itself

    The first command that needs a script creates an isolated virtualenv at ~/.claude/skills/pro-seo/.venv/. Python 3.10 or newer is required — the system Python on macOS is usually too old, so install a current one and set PRO_SEO_PYTHON if the runtime cannot find it.

  3. Check it works

    /pro-seo doctor validates the install, the runtime and any credentials.

  4. Optional: connect Google

    Only pro-seo google needs credentials. Everything else works without them. Run /pro-seo google setup and follow the prompts; config lives in ~/.config/pro-seo/, never in the repository.

The three commands worth learning first

CommandTimeWhat you get
/pro-seo page <url>Fast One page examined closely. No setup. Best first run.
/pro-seo technical <url>Medium Crawlability, indexability, security, Core Web Vitals, rendering. Start here when pages are not being indexed.
/pro-seo audit <url>Slow The full sweep — up to 15 specialists in parallel, then a health score.
You do not have to memorise the list. Type /pro-seo with a plain-English problem and the orchestrator routes to the right skill. The command names on this site are for when you already know what you want.

One check, or the whole programme?

The skills split into two ways of working, and it is worth knowing which you are in.

One-off checks answer a specific question right now — is this page good, is my schema valid, why is this not indexed. Run them whenever, in any order.

The lifecycle is a staged programme that keeps state between sessions in a pro-seo-lifecycle.json file, so it remembers what stage you reached and what it found. Use it when SEO is an ongoing job rather than a question.

Read the lifecycle guide →

Costs and credentials

Most skills read public pages and cost nothing beyond the model tokens. Three exceptions are worth knowing before you run them: