seo

作者: iannuttall

Free Google Search Console MCP server and CLI for AI agents. Reads your real Search Console, Google Analytics, Bing Webmaster Tools, Clicky and Simple Analytics data, plus DataForSEO and Ahrefs keyword research. Use it for any SEO question - why Google traffic or clicks dropped, organic traffic decline, quick wins, low CTR, striking distance keywords, content decay and declining pages, keyword cannibalization, indexing and URL inspection, one page's queries, Google update impact, the...

npx skills add https://github.com/iannuttall/seo --skill seo

seo

seo reads Search Console, Google Analytics, Bing Webmaster Tools, Clicky and Simple Analytics data, crawls sites, checks live pages, and gets keyword and backlink data from DataForSEO or Ahrefs.

Use the MCP tools when they are connected (hosted at https://seoskill.dev/mcp, or local with seo mcp serve). Otherwise use the CLI: seo, or npx -y seo. Add --json for JSON.

seo crawl --url <url> needs no sign-in and works on any site, local and staging too. The other commands need the person's data: seo login prints a link for them to approve, then run it again.

CLIMCP toolReturns
seo next --site <site>seo_nextThe next step in the SEO loop for the site, with its jobs; start here when asked to work on a site's SEO
seo report --site <site>seo_reportSearch Console overview and sections; with no site, last week across the sites in the weekly site audit; --section teardown when asked to write a teardown of any site
seo page --url <url>seo_pageOne URL: live page, index status, queries
seo compare --site <site> --date <date>seo_compareBefore and after a date, with Google updates
seo index --site <site>seo_indexGoogle's indexing reasons, labelled, and pages that lost their clicks
seo submit <url...>, --indexmysiteseo_submitAsk Bing and others to crawl pages (IndexNow, free, after seo submit key <site>), or send them to Google with Index My Site (the person's credits; quote first, send with --yes or confirm: true only after they agree)
seo research <action>seo_researchKeywords, keyword ideas, SERP (organic position, mobile) and SERP overlap, whether Google indexed any URL (index_check), top pages, competitors, backlinks, pages by backlinks, link gaps, AI answer citations, link and listicle targets (--pages, or ai_answers with competitors), for a site, subfolder (example.com/blog/) or page; provider optional; next pages are free for a day
seo data --site <site>seo_dataRaw Search Console, Bing, Clicky, Simple Analytics or Google Analytics rows
seo crawl --url <url>seo_crawlTechnical issues across a site
seo internal-links --site <site> or --url <url>seo_internal_linksLinks to add across a site, or to one page
seo lint <files> or --url <url>seo_lintLines in a draft, title, description or live page that read as AI-written, each with a fix; --only ai for AI patterns alone; no sign-in
seo feedbackseo_feedbackSend a bug or idea about these tools, with your proposed fix, to the maintainer; show the person the text and send only if they agree
seo sitesseo_sitesThe properties the person can read
seo site new <folder>, then seo site guide <step>CLI onlyBuild a new data-driven site on Astro and Cloudflare, one step at a time. Its build runs seo site check

Each result ends with the command to run next. Start small and ask for more: a site, then a --section (section), then --detail rows or full. seo <command> --help shows the options.

The SEO loop

When the person asks you to use seo or improve a site's SEO without a narrower question, run seo next. It keeps the site's business context (what it sells, who buys, conversion pages) and its issues list, and returns one step: research the business context, unblock pages, improve pages that rank, or plan new pages and earn links. Do the step's jobs, ask the person before anything goes live, mark each job, then run seo next again.

Issues kept between sessions

seo report --site <site> --section issues (section "issues") checks the site again and keeps a list of what it found, each with an id, the latest check and what the person marked it. Record what the person decided: --mark fixed or --mark ignored with --issues <id>,<id> (mark, issues, optional note). "Fixed" is the person's word; the list says when the check still finds it. The hosted server, and a CLI linked with seo login, keep the list with the account, for every site; an unlinked CLI keeps it on this machine. If the person has a list saved from before, such as .seo/issues.json, pass its contents once as saved to carry its marks over.

Google updates

When the person asks whether a Google update hit the site, run seo report --site <site> --section google-updates (section "google-updates"). It compares the latest ranking update's days with the same days before and says whether that is outside the site's normal movement. --end-date (end_date) picks an earlier update. Report it as timing, never as the cause.

Indexing reasons each week

seo index inspects known URLs in a fixed order (lost-click pages, Search Console pages by clicks, the sitemap, the rest), 100 by default, and labels each Google reason fix, check, expected or indexed from a live check. In the CLI or local MCP, --max-urls (max_urls) asks for more, up to today's quota, and reuses saved inspections up to 7 days old, so paging or --detail full costs no quota. Run it once for a baseline and keep the full result (--detail full). Run it again each week with the same number and compare by URL and reason: a new reason, or a URL that moved to fix, is what to report. seo keeps no history, so you store the results. Once this runs weekly, the person can turn off Search Console's indexing emails. For one URL from such an email, run seo page --url <url>.

相關技能

conversion-tracking
coreyhaines31
When the user wants to set up, audit, or fix conversion tracking to Google Ads, Meta, GA4, LinkedIn, and TikTok, or asks why conversions are missing or doubled: GTM, pixels, CAPI, Enhanced Conversions, offline imports. Fire on confirmed success, not the submit click; verify a test conversion arrives; diagnose before changing; offer free paths and disclose partner tools. For tracking plans, see analytics. For attribution, see attribution. For bidding, see ads.
marketingdata-analysisapi
ab-testing
coreyhaines31
當使用者想要規劃、設計或執行A/B測試或實驗,或建立成長實驗計畫時使用。也適用於使用者提及「A/B測試」、「分割測試」、「實驗」、「測試這個變更」、「變體文案」、「多變量測試」、「假設」、「我該測試這個嗎」、「哪個版本比較好」、「測試兩個版本」、「統計顯著性」、「這個測試該跑多久」、「成長實驗」、「實驗速度」、「實驗待辦事項」、「ICE評分」、「實驗...
researchdata-analysismarketing
add-analytics-instrumentation
amplitude
適用於 PR、分支、檔案、目錄或功能的端到端分析追蹤工作流程。讀取程式碼、找出應追蹤的事件,並一次產出具體的追蹤計畫。當使用者想為 PR 新增分析追蹤、詢問「為這個 PR 加上追蹤」、「為這個分支新增追蹤」、「這個檔案需要哪些分析追蹤」、「為結帳流程加上追蹤」、「執行完整的追蹤工作流程」,或提出任何暗示要從程式碼著手……的請求時,請使用此技能。
developmentdata-analysisapi
ads
coreyhaines31
當使用者需要協助處理 Google Ads、Meta(Facebook/Instagram)、LinkedIn、Twitter/X 或其他廣告平台上的付費廣告活動時使用。也適用於使用者提及「PPC」、「付費媒體」、「ROAS」、「CPA」、「廣告活動」、「再行銷」、「受眾鎖定」、「Google Ads」、「Facebook 廣告」、「LinkedIn 廣告」、「廣告預算」、「每次點擊成本」、「廣告支出」或「我該投放廣告嗎」等詞彙時。用於廣告活動策略、受眾鎖定、出價與優化。適用於大量廣告素材生成及……
data-analysisresearchmarketing
ai-research-explore
lllllllama
We need to translate the given English text into Traditional Chinese. The text describes a skill for an agent, related to deep learning research exploration. We must preserve the name "ai-research-explore" if it appears, but it does not appear in the provided text. The text includes technical terms like "Rigor Explore", "skill slug", "SOTA", "current_research", "explore_outputs/", etc. We should keep those as is or translate appropriately? The instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." So technical terms like "Rigor Explore", "skill slug", "SOTA", "current_research", "explore_outputs/" should be preserved as they are. Also "README-first" might be a term. We need to translate the rest into Traditional Chinese. Let's break down the text: "Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants
data-analysisresearchapi
analytics
coreyhaines31
當使用者想要設定、改善或稽核分析追蹤與衡量時使用。也適用於使用者提及「設定追蹤」、「GA4」、「Google Analytics」、「轉換追蹤」、「事件追蹤」、「UTM參數」、「標籤管理工具」、「GTM」、「分析實作」、「追蹤計畫」、「我該如何衡量這個」、「追蹤轉換」、「歸因」、「Mixpanel」、「Segment」、「我的事件是否觸發」或「分析功能無法運作」時。每當有人詢問如何確認某項功能是否正常運作或...時使用。
researchdata-analysismarketing
aso
coreyhaines31
當使用者想要審核或優化 App Store 或 Google Play 的產品頁面時。也適用於使用者提及「ASO 審核」、「應用程式商店優化」、「優化我的應用程式頁面」、「提升應用程式能見度」、「應用程式商店排名」、「審核我的產品頁面」、「為什麼沒有人下載我的應用程式」、「提升我的應用程式轉換率」、「應用程式關鍵字優化」或「比較我的應用程式與競爭對手」時。當使用者分享 App Store 或 Google Play 的網址並希望改善該頁面時,也適用。
data-analysisresearchmarketing
attribution
coreyhaines31
當使用者想要弄清楚哪種行銷真正驅動轉換和營收時,選擇或解讀歸因模型,或調和不同工具之間的數據差異時使用。也適用於使用者提到「歸因」、「歸因模型」、「首次觸點 vs 最後觸點」、「多觸點」、「哪個渠道驅動營收」、「我真正的CAC是多少」、「我的儀表板數據不一致」、「Google/Meta說X但GA說Y」、「媒體組合模型」、「MMM」、「增量性」、「地理提升」、「保留測試」、「你是怎麼...
researchdata-analysismarketing