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>.

Related Skills

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
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation...
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
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and...
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
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or...
researchdata-analysismarketing
aso
coreyhaines31
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
data-analysisresearchmarketing
attribution
coreyhaines31
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you...
researchdata-analysismarketing