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. Use --wait on one important URL when you need certainty.

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.

developer-tools

Abhay Khant

gsc-indexer: the CLI that asks Google to re-index your URLs

July 19, 2026 · 3 min read

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.

Stacked glowing blue document cards with a checkmark badge and a networked globe above a winding illuminated path

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

Written by

Abhay Khant

Hi, I'm Abhay Thakor

I'm a developer, builder, and technology enthusiast interested in turning ideas into useful products.

I enjoy working across web development, cybersecurity, automation, SEO, and content creation. Rather than only learning technologies individually, I like putting them together to build things that people can use.

One of my main projects is Toolsura, a free online utility platform that brings practical tools into one place. I'm building Toolsura as a product and a learning project where I can explore development, infrastructure, SEO, content distribution, automation, and product growth.

What I Build

My work currently revolves around several areas:

Web development with Next.js, React, Tailwind CSS, and modern web technologies
Backend development with Go, APIs, databases, and server-side systems
Automation using n8n, APIs, Docker, and connected services
SEO and content systems for building organic search traffic
Cybersecurity including web security, bug bounty, SOC concepts, and malware analysis
Content creation including video editing, YouTube content, graphics, and promotional videos

I enjoy going beyond tutorials and experimenting with complete systems, from the frontend interface all the way to the backend, deployment, automation, and distribution.

Toolsura

Toolsura is one of the projects I'm most actively building.

The idea is simple: create useful, accessible online tools that solve small problems quickly.

Toolsura includes utilities for things such as text, JSON, URLs, PDFs, images, security checks, and other everyday technical tasks.

Building it has also become a practical way for me to learn how a modern web product works.

That means working on:

Product → Development → Infrastructure → SEO → Content → Distribution → Automation → Growth

Technology & Learning

I'm particularly interested in understanding how systems work rather than simply learning how to use them.

My development work has included technologies such as:

Next.js · React · TypeScript · Tailwind CSS · Go · Gin · GORM · PostgreSQL · MongoDB · Docker · RabbitMQ · MinIO · Strapi

I've also worked with Linux environments and tools such as Kali Linux, Termux, and related security tooling.

My cybersecurity interests include web application security, bug bounty research, SOC analysis, and malware analysis.

Building in Public

I also create content around the things I build and learn.

This includes:

Tutorials and technical articles
YouTube videos
Product demonstrations
Visual explainers
Promotional videos
SEO-focused educational content

My goal is to turn projects and experiments into useful resources that other people can learn from.

Why I Build

For me, building is one of the best ways to learn.

Instead of learning a technology in isolation, I prefer starting with a real problem and figuring out what is required to solve it.

Sometimes that means writing code. Other times it's debugging a deployment at midnight, or working out why a page isn't being indexed, why an API isn't behaving correctly, or how to automate something that would otherwise take hours.

Those problems are part of the process.

Every project gives me another opportunity to understand how technology works in the real world.

What I'm Working Toward

I'm continuing to develop my skills across software engineering, cybersecurity, automation, and digital products.

At the same time, I'm building Toolsura into a useful platform and experimenting with different ways to create, distribute, and grow technical products.

There is still a lot to learn, but that's exactly what makes building interesting.

Let's Connect

If you're interested in web development, cybersecurity, automation, SEO, online tools, or building products, feel free to connect.

I'm always interested in learning, experimenting, and building something useful.

Build. Learn. Improve. Repeat.

Frequently Asked Questions

developer-tools

Abhay Khant

gsc-indexer: the CLI that asks Google to re-index your URLs

July 19, 2026 · 3 min read

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

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

Written by

Abhay Khant

Hi, I'm Abhay Thakor

I'm a developer, builder, and technology enthusiast interested in turning ideas into useful products.

What I Build

My work currently revolves around several areas:

Web development with Next.js, React, Tailwind CSS, and modern web technologies
Backend development with Go, APIs, databases, and server-side systems
Automation using n8n, APIs, Docker, and connected services
SEO and content systems for building organic search traffic
Cybersecurity including web security, bug bounty, SOC concepts, and malware analysis
Content creation including video editing, YouTube content, graphics, and promotional videos

I enjoy going beyond tutorials and experimenting with complete systems, from the frontend interface all the way to the backend, deployment, automation, and distribution.

Toolsura

Toolsura is one of the projects I'm most actively building.

The idea is simple: create useful, accessible online tools that solve small problems quickly.

Toolsura includes utilities for things such as text, JSON, URLs, PDFs, images, security checks, and other everyday technical tasks.

Building it has also become a practical way for me to learn how a modern web product works.

That means working on:

Product → Development → Infrastructure → SEO → Content → Distribution → Automation → Growth

Technology & Learning

I'm particularly interested in understanding how systems work rather than simply learning how to use them.

My development work has included technologies such as:

Next.js · React · TypeScript · Tailwind CSS · Go · Gin · GORM · PostgreSQL · MongoDB · Docker · RabbitMQ · MinIO · Strapi

I've also worked with Linux environments and tools such as Kali Linux, Termux, and related security tooling.

My cybersecurity interests include web application security, bug bounty research, SOC analysis, and malware analysis.

Building in Public

I also create content around the things I build and learn.

This includes:

Tutorials and technical articles
YouTube videos
Product demonstrations
Visual explainers
Promotional videos
SEO-focused educational content

My goal is to turn projects and experiments into useful resources that other people can learn from.

Why I Build

For me, building is one of the best ways to learn.

Instead of learning a technology in isolation, I prefer starting with a real problem and figuring out what is required to solve it.

Those problems are part of the process.

Every project gives me another opportunity to understand how technology works in the real world.

What I'm Working Toward

I'm continuing to develop my skills across software engineering, cybersecurity, automation, and digital products.

At the same time, I'm building Toolsura into a useful platform and experimenting with different ways to create, distribute, and grow technical products.

There is still a lot to learn, but that's exactly what makes building interesting.

Let's Connect

If you're interested in web development, cybersecurity, automation, SEO, online tools, or building products, feel free to connect.

I'm always interested in learning, experimenting, and building something useful.

Build. Learn. Improve. Repeat.

Comments

Leave a Review

Rate this tool