nc9nc9/skills/google-indexing/SKILL.md

google-indexing

Skill4 starsChanged 54 days agoMITView on GitHub

Submit, remove, or check indexing status of URLs via Google's Indexing API and Bing's Webmaster URL Submission API. Use to notify Google or Bing about new, updated, or deleted pages, or to speed up crawling of a site.

Reads credentials

In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ai-writing-detectorSkill
- animate-svgSkill
- browserbaseSkill
- clickhouseSkill
- commitSkill
- geist-designSkill
- generate-faviconSkill
- generate-imageSkill
- google-search-consoleSkill
- google-searchSkill
- humanizerSkill
- keyword-researchSkill
- parallelSkill
- remove-backgroundSkill
- reviewSkill
- web-uiSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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

Very specific:
All URL commands take positional URLs, --file urls.txt, or stdin.
line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Search Engine Indexing (Google + Bing)

Tell Google and Bing that pages were added, updated, or removed, and read back what was last notified.

Requirements

GOOGLE_INDEXING_KEY_FILE — path to a Google Cloud service account JSON key. The service account email must be added as an Owner of the property in Search Console.
BING_WEBMASTER_API_KEY — account-level key from Bing Webmaster Tools → Settings → API access. It covers every site verified under that account; unverified sites return NotAuthorized.

Google

./scripts/google_indexing submit "https://example.com/new-post"
./scripts/google_indexing remove "https://example.com/old-page"
./scripts/google_indexing status "https://example.com/page" -f table
./scripts/google_indexing quota

All URL commands take positional URLs, --file urls.txt, or stdin. Options: -k/--key-file, -f/--format json|table, --file, -b/--batch-size (max 100).

Bing

./scripts/bing_submit sitemap example.com                       # every URL in sitemap.xml
./scripts/bing_submit submit https://example.com https://example.com/new-post
./scripts/bing_submit submit https://example.com --file urls.txt
./scripts/bing_submit quota https://example.com

submit takes the site URL first — it must match the Bing Webmaster Tools property exactly. URLs come from positional args, --file, or stdin. -f/--format json|table.

Quotas

Quota	Limit
Google publish requests	200/day, resets midnight PT
Google metadata reads	600/min
Google batch size	100 URLs/request
Bing submissions	~100/day, ~1600/month per site (grows with site age and trust)
Bing batch size	500 URLs/call (auto-chunked)

Gotchas

Bing rejects a batch wholesale when it exceeds the remaining quota, so bing_submit pre-checks quota and reports the overflow as "deferred": N — re-run the next day to send the rest.
Google's Indexing API is officially supported only for JobPosting and BroadcastEvent pages; other URLs are accepted but Google may ignore the hint.
The Bing Webmaster API does not fan out to IndexNow partners (Yandex, Naver, Seznam, Yep). That needs a real IndexNow ping plus a /{key}.txt file served at the domain root.
Submitting is a hint, not indexing. Use status (Google) to confirm what was notified, and Search Console / Bing Webmaster Tools to confirm what was actually indexed.

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