SEO Skill

io.github.iannuttallPublished by GitHub account iannuttallv0.4.0Updated Oct 15, 2026

Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.

The publisher's own server: SEO Skill

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Gives AI agents your real Google Search Console, Analytics and Bing data plus site crawls, so SEO questions are answered from your own numbers.

What you can do
  • Pull Search Console totals, top pages and queries, and quick-win or decay findings for a site
  • Inspect a single URL's live page, Google index status and ranking queries, or check indexing reasons across URLs
  • Compare periods before and after a date alongside Google update dates
  • Fetch raw Search Console or Bing rows and landing pages from Google Analytics or Clicky
  • Run keyword, competitor and backlink research using your own DataForSEO or Ahrefs key
  • Crawl a site for technical issues and AI agent access, and suggest internal links (CLI only)
When to use it
Useful when you want an assistant to diagnose traffic drops, find near-page-one pages, check indexing, or audit a site's crawlability from your actual Search Console data instead of generic SEO advice or third-party estimates.
Requirements
Either the hosted remote endpoint or the npm CLI package run locally with Node.js. Sign-in with the Google account that has Search Console access; the CLI stores sign-in in the system keychain. Keyword and competitor research needs your own DataForSEO or Ahrefs key. Crawls and Bing data run locally through the CLI.
Before you install
It asks for Google account access to your Search Console and Analytics data, and optionally third-party API keys. The hosted server stores linked Google accounts and saved keys, encrypted, and states it does not keep Search Console data, reports or request logs. Crawls and page checks fetch your live site; review the privacy policy before connecting.

Installation

In SourceWeft

  1. Open SEO Skill in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.iannuttall%2Fseo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "seo-skill": {
      "type": "http",
      "url": "https://seoskill.dev/mcp"
    }
  }
}

README

[SEO Skill]

SEO For Agent-Native Teams

[npm]

The SEO data I give my agents every day, so they work from my real numbers instead of guessing.

Most AI SEO tools do one of two things. They hand your agent a checklist of generic advice, or they feed it estimates from a keyword tool that has never seen your site. Either way you end up with the same pages everyone else is publishing. Pages written from a keyword list aren't SEO. They're slop.

This works the other way round. It's a Google Search Console MCP server and CLI, and it doesn't tell your agent what to do. It gives it the facts: your clicks, impressions and positions from Search Console, your visits from Google Analytics or Clicky, your Bing data, the dates of Google updates, and a crawl of your site. Your agent works out what matters, and you decide what changes.

It's free and open source. Hack around with it. Make it your own.

Installation (30-second setup)

1. Connect it to your agent

Claude Code
bash
claude mcp add --transport http seoskill https://seoskill.dev/mcp
Codex
bash
codex mcp add seoskill --url https://seoskill.dev/mcp
Any other agent

Add https://seoskill.dev/mcp as a remote MCP server. Cursor, Claude Desktop, VS Code and most other agents support it.

The CLI (for crawls and Bing, which run on your machine)
bash
npm i -g seoseo start

seo start signs you in, connects your agents and installs the skill.

2. Sign in with Google

Your agent opens a Google sign-in. Pick the account that can see your Search Console. That's your account. There's no password and no signup form.

3. Ask it something real

text
Why did clicks drop on example.com last month?

That's it. You're ready to go.

What you can ask it

  • "Why did clicks drop last month? Was it the core update?"
  • "Which pages are close to page one, and what do they rank for?"
  • "Is this page indexed? If not, why not?"
  • "Which searches does this page show up for that it never mentions?"
  • "Can ChatGPT, Claude and Perplexity read my site?"
  • "Who am I up against in search, and is there demand for a 'vs' or alternatives page?"

Your agent picks the commands, reads the results and shows you what it found.

Why it exists

I built this because agents kept failing at SEO in the same few ways.

#1: The agent makes things up

The problem. Ask an agent why your traffic dropped and you get a tidy list of possible causes. Algorithm update, technical issues, content quality. None of it comes from your site, so none of it helps.

The fix is to give it your numbers:

  • seo report shows your totals against the last period, the pages and queries that moved, and the places worth a look: quick wins, low click-through rates, pages stuck on page two, decay and cannibalization.
  • seo compare lines up the weeks before and after a date, with the Google updates in between.

#2: Keyword tools are guessing too

The problem. Ahrefs and Semrush estimate your traffic from a sample. They miss most of the long tail, and they rarely agree with each other.

The fix is to start from your own data. Search Console is the source of truth for Google. When you do need keyword volumes or competitor data, seo research uses your own DataForSEO or Ahrefs key, and it keeps those estimates apart from your real numbers.

#3: The agent says it's fixed when it isn't

The problem. Agents trust their own edits. Then you find the page is still noindexed, still redirecting, or still not in Google.

The fix is to check the live site:

  • seo page loads one URL and asks Google whether it's indexed.
  • seo index checks every page that lost its clicks.
  • seo crawl checks the whole site, including what AI agents can read.

#4: Too many reports

The problem. SEO tools love reports. The first version of this had about 70 of them, and almost nobody used most of them.

The fix was to cut it down to a handful of commands. Each one takes a site or a URL, and dates if you want them. There are no settings to tune. Every result ends with the command to run next, so your agent always knows where to go.

Reference

CommandWhat it returns
seo reportYour Search Console overview for --site, then the top rows of each section
seo pageOne URL: the live page, its Google index status and its queries
seo compareBefore and after a date, with Google updates
seo indexGoogle's indexing reasons for known URLs, labelled from live checks, and pages that lost their clicks
seo researchKeywords, search results, competitors and backlinks from your own key
seo dataRaw Search Console or Bing rows
seo analyticsLanding pages from Google Analytics or Clicky
seo crawlTechnical issues and AI agent access across a site (CLI only)
seo internal-linksInternal links to add across a site or to one page (CLI only)

Every command is also an MCP tool, such as seo_report. Add --json to any command when you're scripting it.

What it keeps

As little as possible. The hosted server keeps your linked Google accounts and any keys you save, encrypted. It doesn't keep your Search Console data, your reports or request logs. The CLI keeps your sign-in in your system keychain. The privacy policy has the details.

Links

Apache-2.0. The name and artwork are covered by the brand policy.

Source: README.md at commit 1de89cf

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.4.0LatestOct 15, 2026
  2. v0.3.0Oct 15, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Seoskill integrations

SEO Skill

dev.seoskillOfficial publisher

An SEO data MCP server that gives an assistant your real Google Search Console, Analytics, Bing and crawl data so it can diagnose traffic and indexing issues.

Streamable HTTPWeb executableAuth
Web Search & ScrapingCredential requiredOct 24, 2026