SEO Skill

The only SEO skill your agent needs to grow organic and AI search visibility.

Give your agent 50+ SEO audit tools to find and fix issues, measure your performance, and improve your organic and AI search visibility.

One command installs everything. Then run seo start to sign in, save a project, and add the SEO skill and MCP server to your agents.

npm i -g seo

Run seo start for guided Google sign-in and project setup.

Your agent audits your site without you.

It crawls the site, finds the technical SEO and AI-readiness issues, and hands back specific fixes. You stay in your editor while it does the busywork.

Data other tools keep behind a dashboard.

Give your agent owner-verified Search Console and GA4 data on your machine, joined to crawl findings, so it sees what is actually losing visibility.

One skill, not fifty stuffed into your context window.

The CLI and MCP server do the heavy lifting. Your agent carries one short skill and asks for the detail on each tool only when it is about to use it.

Your search visibility grows while you ship.

Your agent fixes issues, tracks new and resolved ones build over build, and measures the impact across organic and AI search.

See your agent in the loop

It reads your crawl findings and Search Console data, finds what is hurting visibility, then drafts the fix in your stack.

Example SEO audit agent

What should I fix first on example.com?

Claude
Ran 2 seo commands

I ran the main report, then ranked the follow-up work. Three fixes lead the queue, and each one is tied to pages that already earn impressions.

  • 17 indexable URLs canonical to a redirected page
  • 6 URLs with Search Console clicks now return 404
  • 9 retained queries average positions 10 to 20

Reports for a complete SEO audit

52 reports and tools across crawl health, Search Console and GA4, opportunities, AI readiness, and monitoring.

Questions people ask before giving an agent SEO evidence

Give the best models better SEO evidence without replacing Claude, ChatGPT, Codex, Cursor, or the agent workflow you already use.

No. It gives Claude, ChatGPT, Codex, Cursor, and other agents better SEO context. The model still does the reasoning, writing, and implementation work, and the CLI provides the crawl data, Search Console data, GA4 data, and report evidence.

Dashboards are useful when you want to click around, but the CLI is built for the way agents work. They discover reports, run them, and read structured evidence without leaving your editor or terminal.

It gets JSON or Markdown with the date range, units, caveats, evidence, recommendations, and useful next commands. That gives the model enough context to explain the problem and help fix it.

Search Console proves you can access the site and gives reports real search demand. That lets your agent find page-two queries, weak CTR, decaying pages, cannibalisation, and indexing candidates using your own data. The CLI requests read-only access.

No. Crawls and Search Console reports work without GA4. Connect it when traffic, landing-page, engagement, or conversion context would change how you prioritise the work.

Reports, project profiles, tokens, crawls, and caches stay local. The CLI only sends the requests needed to fetch the site and call the Google APIs you connect.

The CLI does not publish changes by itself. It gives your agent the evidence it needs to edit code or content, draft a fix, or open a ticket inside the tools you already use.

No. Use the CLI directly, import the package in TypeScript, or run it in CI. MCP is the easiest way to give a compatible agent the same local report engine.

Fifty skill files would sit in your agent context window on every session, whether or not you are doing SEO work. This is one short skill that teaches your agent to discover the tools at runtime. The agent asks the CLI to describe a report only when it is about to run it, so it gets the full detail at the moment it matters and nothing before that.

Run seo report after setup. It checks the evidence available for the project, explains skipped sections, ranks the first investigation queue, and points to focused follow-up reports.

Generic advice guesses from best practices, but your agent works from the site, crawl, queries, search demand, and analytics data in front of it. It can inspect the evidence behind each finding instead of trusting a generic score.

Developers, founders, SEO consultants, agencies, and technical teams who want their agents to work from clean SEO evidence instead of screenshots or copied dashboard rows.