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
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code...
developmentdata-analysisapi
ads
coreyhaines31
사용자가 Google Ads, Meta(페이스북/인스타그램), 링크드인, 트위터/X 또는 기타 광고 플랫폼에서 유료 광고 캠페인에 대한 도움을 원할 때 사용합니다. 또한 사용자가 'PPC', '유료 미디어', 'ROAS', 'CPA', '광고 캠페인', '리타겟팅', '오디언스 타겟팅', 'Google Ads', '페이스북 광고', '링크드인 광고', '광고 예산', '클릭당 비용', '광고 지출' 또는 '광고를 해야 할까요'를 언급할 때도 사용합니다. 캠페인 전략, 오디언스 타겟팅, 입찰 및 최적화에 사용합니다. 대량 광고 소재 생성 및...
data-analysisresearchmarketing
ai-research-explore
lllllllama
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 candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding,...
data-analysisresearchapi
analytics
coreyhaines31
사용자가 분석 추적 및 측정을 설정, 개선 또는 감사하려는 경우. 또한 사용자가 "추적 설정", "GA4", "Google Analytics", "전환 추적", "이벤트 추적", "UTM 매개변수", "태그 관리자", "GTM", "분석 구현", "추적 계획", "이것을 어떻게 측정하나요", "전환 추적", "기여 분석", "Mixpanel", "Segment", "내 이벤트가 제대로 작동하나요", 또는 "분석이 작동하지 않습니다"를 언급할 때 사용합니다. 누군가가 무언가가 제대로 작동하는지 확인하는 방법을 물을 때마다 사용하세요...
researchdata-analysismarketing
aso
coreyhaines31
사용자가 앱스토어 또는 구글 플레이 리스팅을 감사하거나 최적화하려 할 때. 또한 사용자가 'ASO 감사', '앱스토어 최적화', '내 앱 리스팅 최적화', '앱 가시성 개선', '앱스토어 순위', '내 리스팅 감사', '사람들이 내 앱을 다운로드하지 않는 이유', '내 앱 전환율 개선', '앱 키워드 최적화', '내 앱을 경쟁사와 비교'를 언급할 때 사용합니다. 사용자가 앱스토어 또는 구글 플레이 URL을 공유하고 이를 개선하려 할 때 사용합니다.
data-analysisresearchmarketing
attribution
coreyhaines31
사용자가 어떤 마케팅이 실제로 전환과 매출을 유도하는지 파악하려 하거나, 기여 모델을 선택하거나 해석하려 하거나, 여러 도구 간의 상충되는 수치를 조정하려 할 때 사용합니다. 또한 사용자가 "기여", "기여 모델", "퍼스트터치 대 라스트터치", "멀티터치", "어떤 채널이 매출을 유도하는지", "실제 CAC는 얼마인지", "대시보드가 서로 다르게 나와요", "Google/Meta는 X라고 하는데 GA는 Y라고 해요", "미디어 믹스 모델", "MMM", "증분성", "지오 리프트", "홀드아웃 테스트", "어떻게 했는지..."라고 언급할 때도 사용합니다.
researchdata-analysismarketing