What is gsc-indexer? (and what "submit for indexing" really means)
Posted on July 19, 2026 by Abhay khant
Key Takeaways
What is gsc-indexer? A command-line tool that asks Google to crawl and re-index your URLs through the Search Console URL Inspection API.
Why this tool exists
You published or updated a page on your site, but Google hasn't picked it up yet. In Google Search Console (GSC) you can click Request indexing. but only one URL at a time, by hand.
gsc-indexer does that same "ask Google to look at this URL" step from the
command line, for one URL or ten thousand, using the GSC URL Inspection
API.
What it actually does
For every URL you give it, the tool calls the URL Inspection API. That API asks Google to crawl / re-fetch the URL. Think of it as tapping Google on the shoulder: "hey, this page changed, come take a look."
It does not force Google to index the page. Google still decides. But requesting a re-crawl is the legitimate, supported way to speed up discovery of new or updated content.
URL Inspection API vs the Indexing API v3
There are two Google APIs that sound similar. We use the URL Inspection API, and on purpose:
| API | Works for | Requires |
|---|---|---|
| URL Inspection API (this tool) | any URL on a property you can access | service account with property access |
| Indexing API v3 | only JobPosting / BroadcastEvent structured data |
service account as Owner |
The Indexing API v3 rejects general blog pages and demands Owner-level access,
so it does not apply to normal websites. That is why gsc-indexer uses URL
Inspection.
"Indexed" vs "re-indexed"
- New page, not yet in Google → the tool requests indexing (asks Google to discover it).
- Existing page you changed → the tool re-indexes (asks Google to refresh what it has).
Same command, same API. the difference is just the page's current state.
Honest limitations
- Google decides whether and when to index. Typical delay is hours to days, not seconds.
- GSC rate-limits sustained inspect volume; very large runs need a polite delay (see the throttling guide).
- You must have at least full-user access to the GSC property the URL belongs to.
Next steps
- New here? Start with creating and verifying a GSC property.
- Then set up the service account. the step that unblocks everyone.
- Ready to run? Install and do your first inspection.
Sources
- Google Search Console
- URL Inspection API documentation
- Google Search APIs overview
- Service account OAuth (Google Identity)
- About service accounts (Google Cloud IAM)
- Verify site ownership
- Property types: URL-prefix vs Domain
- URL Inspection tool help
- Indexing API (JobPosting/BroadcastEvent only)
- Request indexing / inspect a URL
Frequently Asked Questions
What exactly does gsc-indexer do?
It asks Google to crawl and re-fetch a specific URL through the Search Console URL Inspection API. Inspecting a URL already submits it for re-crawl, so the tool is how you push a new or changed page into, or refresh it in, Google's index without waiting for a natural crawl.
Is this the Google Indexing API?
No, and the difference matters. The Indexing API is restricted to JobPosting and BroadcastEvent pages, so it cannot touch a normal article. gsc-indexer uses the URL Inspection API, which works for any URL you own. That is also why you need a service account, not a plain API key.
Does it force Google to index a page instantly?
No. It requests a re-crawl; Google decides whether and when to index, usually within hours to a few days. Inspection confirms the request was accepted, not that the page is live in search. Treat it as a nudge, not a guarantee of immediate inclusion.
What do I need before I can run it?
You need a verified Search Console property for the site, a service account with Full access to that property, and the service account's JSON key file. The property prefix must match the URL exactly, including https and www. Those three prerequisites are covered in the setup guides.
Why would I use a CLI instead of the Search Console UI?
The UI only inspects one URL at a time. gsc-indexer handles hundreds or thousands from a batch file, a sitemap, or stdin, and it can run inside cron or CI. If you manage a large site or want automation, the command line is dramatically faster than clicking through the console.