SEO Skill
io.github.iannuttall由 GitHub 账号 iannuttall 发布v0.4.0更新于 Oct 15, 2026
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
发布方自己的服务：SEO Skill
概览
让 AI 助手基于你真实的 Google Search Console、Analytics 和 Bing 数据及站点抓取来回答 SEO 问题，而不是靠猜测。
- 可以做什么
- 获取站点的 Search Console 总量、热门页面与查询，以及快速见效、点击率偏低、流量衰减等问题
- 检查单个网址的实时页面、Google 索引状态与排名查询，或批量核查索引原因
- 对比某一日期前后的数据，并对照 Google 算法更新日期
- 读取原始 Search Console 或 Bing 数据行，以及 Google Analytics 或 Clicky 的落地页
- 使用你自己的 DataForSEO 或 Ahrefs 密钥做关键词、竞品和外链调研
- 抓取整站的技术问题与 AI 代理可读性，并给出内链建议（仅限 CLI）
- 适用场景
- 适合让助手基于你真实的 Search Console 数据诊断流量下滑、找出接近首页的页面、检查收录情况或审计站点可抓取性，而不是给出通用 SEO 建议或第三方估算。
- 运行要求
- 可使用托管的远程端点，或在本地用 Node.js 运行 npm 命令行包。需要用有 Search Console 权限的 Google 账号登录，CLI 会把登录信息存入系统钥匙串。关键词与竞品调研需要自备 DataForSEO 或 Ahrefs 密钥。抓取和 Bing 数据通过 CLI 在本地运行。
安装
在 SourceWeft 中
- 打开 控制台中的 SEO Skill，将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.iannuttall%2Fseo/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"seo-skill": {
"type": "http",
"url": "https://seoskill.dev/mcp"
}
}
}README
SEO For Agent-Native Teams
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
Codex
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)
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
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 reportshows 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 comparelines 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 pageloads one URL and asks Google whether it's indexed.seo indexchecks every page that lost its clicks.seo crawlchecks 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
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
- Documentation
- Cloud agents and CI
- Add your own analytics source
- Changelog and contributing
- Questions and bugs
Apache-2.0. The name and artwork are covered by the brand policy.
来源：README.md，提交 1de89cf
工具
0版本历史
2- v0.4.0最新Oct 15, 2026
- v0.3.0Oct 15, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。
- 已声明认证方式必需10 分
请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分