agentleFS
Sign inStart free
nc9nc9/skills/google-search-console/SKILL.md

google-search-console

Skill4 starsChanged 54 days agoMITView on GitHub

Query Google Search Console — URL indexing status, search performance (clicks, impressions, CTR, position by query/page/country/device/date), submitted sitemaps, and verified properties. Use for indexing checks, rankings, or search traffic.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use google-ads.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • webrenewSkill

    google-ads

    Plan, build, audit or run Google Ads search campaigns for a local service business (plumber, dentist, roofer, cleaner, lawyer, clinic) on a small budget, with the agent drafting and the owner approving every change that spends money. Use this skill for a new Google Ads account or campaign, keyword research from customer questions, match types, negative keywords, location targeting, responsive search ads and assets, landing page message match, conversion tracking from GA4 or the Google Ads tag, budgets and bidding, Local Services Ads, a weekly check, and when the user says "PPC", "Google Ads is not working", "too expensive per lead", "wasted ad spend", "search terms" or "should we run Google ads".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only Search Console API wrapper: inspect, performance, sitemaps, sites.

    line 9
  2. Very specific:

    Search Console data lags 2-3 days, so the tail of a --days range is usually empty.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Search Console

Read-only Search Console API wrapper: inspect, performance, sitemaps, sites.

Requirements

  • GOOGLE_INDEXING_KEY_FILE — service account JSON key path (shared with the google-indexing skill)
  • Service account added as a user on the property; Search Console API enabled in the Cloud project

Commands

./scripts/google_search_console inspect [URLS...] -s sc-domain:example.com [--file urls.txt]
./scripts/google_search_console performance -s sc-domain:example.com [options]
./scripts/google_search_console sitemaps -s sc-domain:example.com
./scripts/google_search_console sites

Options

OptionDescriptionCommands
-s, --siteProperty, e.g. sc-domain:example.comall but sites
-k, --key-fileKey path, overrides envall
-f, --formatjson (default) or tableall
--fileFile of URLs, one per line, # comments skippedinspect
-d, --dimensionquery (default), page, country, device, dateperformance
--daysDays back from today (default 28)performance
--start-dateYYYY-MM-DD, overrides --daysperformance
--end-dateYYYY-MM-DD (default today)performance
-q, --queryFilter: query containsperformance
-p, --pageFilter: page URL containsperformance
-n, --limitMax rows, default 1000, clamped to 25000performance

Output

JSON. inspect: {site, results[]} per URL with verdict, coverage_state, last_crawl_time, page_fetch_state, robots_txt_state, indexing_state, google_canonical, user_canonical, crawled_as, error. performance: {site, start_date, end_date, dimension, rows[]}, rows carrying keys, clicks, impressions, ctr, position. sitemaps: path, submit/download times, warning and error counts. sites: site_url + permission_level.

Gotchas

  • -p on performance is a page filter, not pagination. There is no paging; raise -n. One -d dimension per call, so no query x page breakdowns.
  • Search Console data lags 2-3 days, so the tail of a --days range is usually empty.
  • inspect reads URLs from stdin when none are given as args or via --file; a per-URL failure lands in that row's error and the run still exits 0, so check error before trusting a null verdict.
  • Omitting -s prints the available properties to stderr before exiting — quickest way to find the property string.

API Quotas

QuotaLimit
URL Inspection2,000/day per property, 600/min
Search Analytics1,200 queries/min
Sitemaps / SitesStandard quota

Examples

./scripts/google_search_console inspect "https://example.com/page" -s sc-domain:example.com
./scripts/google_search_console performance -s sc-domain:example.com -d page -n 20 -f table
cat urls.txt | ./scripts/google_search_console inspect -s sc-domain:example.com

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free