gsc-indexer frequently asked questions
· 3 min read
gsc-indexer FAQ: does it index instantly, why www vs non-www matters, API key vs service account, 403 causes, and how many URLs you can process.
Short answers to the questions people ask most. For deeper detail, follow the links.
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 days. Need certainty on one important URL?
--wait 15m polls until it flips to indexed or the timeout hits; skip it on
batches. See what "submit for indexing" means
and understanding results.
Why does www vs non-www (or http vs https) matter?
They're different GSC properties: if your property is
https://www.toolsura.com/, inspecting https://toolsura.com/ (no www) gives
a 403. Match the property prefix exactly. See
property setup.
API key or service account. which do I use?
Service account (-creds / GSC_CREDENTIALS). The GSC URL Inspection API
requires OAuth; an API key returns 401. See
troubleshooting 401.
Can I use multiple properties?
One property per run, set with -site (defaults to
https://www.toolsura.com/). All URLs in a run must belong to that property.
The service account needs Full access on each property you target.
My big run stalled / errored partway. Why?
Google rate-limits sustained inspect volume. Raise -delay
(e.g. -delay 10s) and use -q for a clean progress line. See
throttling.
Is my sa.json safe?
It's a credential: anyone with it can inspect (and read stats about) your property. Keep it private, don't commit it to git, and store it as a secret in CI. Rotate it from Google Cloud if it ever leaks.
"NOT INDEXED" showed up. did the run fail?
No. The inspection succeeded; Google just doesn't have the page indexed. Only network/HTTP/parse errors count as failures (and trigger a non-zero exit code). See understanding results.
How many URLs can I process?
As many as you like. Sitemap expansion is capped at 50,000 URLs as a safety
limit. For very large sites, use a polite -delay so Google doesn't throttle
you.
Can I tell Google my sitemap changed?
Yes. After a run (or on its own), pass
-ping-sitemap "https://www.toolsura.com/sitemap.xml" and the tool pings
Google's sitemap endpoint to request a re-fetch. Keep your <lastmod> dates
accurate; the ping is a nudge, not a trigger. See
batch files and sitemaps.
Can I schedule it?
Yes. cron, GitHub Actions, or any CI. Use -json for parseable output and
rely on the exit code for pass/fail. See
automating in CI.
Why do I get 403 even though I own the site?
Almost always the service account isn't added to the property, or was
added as Restricted instead of Full. Add its client_email as a Full
user. This is the #1 issue; the full fix is in
service-account setup.
Where's the source code?
In the GitHub repository. The README there links back to these guides.
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 (request indexing)
- Indexing API (JobPosting/BroadcastEvent only)
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.