Nuxt SEO Pro
Nuxt SEO Pro watches a production Site and records what changed. It crawls pages, reads Google Search Console, runs Lighthouse scans, tracks keywords, and opens Tickets for the problems worth fixing.
These docs cover the three surfaces that reach that data from outside the dashboard.
Three access surfaces
| Surface | Use it when | Auth |
|---|---|---|
| CLI | You work in a terminal, a script, or a coding agent with shell access | Team API token |
| MCP | Your client cannot run a terminal, such as ChatGPT or Claude.ai | OAuth, or a Team API token header |
| API | You call the service from your own code | Team API token |
The CLI is the primary surface. Its exit codes report request outcomes. They do not turn an SEO finding into a failed build. It pipes into other tools. It needs no client configuration file.
MCP is the compatible backup. Use it when the client has no terminal.
The CLI and SDK use the versioned public API. MCP is a transitional transport with its own tool catalog. Check each surface's guide for supported operations.
Start here
npx @nuxtseo/cli login
npx @nuxtseo/cli sites listlogin opens your browser, pairs the terminal, and stores a Team API token. Read the CLI guide for the full command list.
Your Site data stays yours
A Team API token reaches only the Sites its Team can access. Operations also check the token's role, granted scopes, and required entitlement. Revoke it under Settings > API tokens. Revoking stops every surface that uses it.