Authentication
Upload your GCP service account JSON. The private key is used to sign JWT tokens entirely in your browser — nothing is transmitted except the signed token to Google's OAuth endpoint.
Drop your service account JSON here or click to browse
Must be a valid GCP service account key (.json)Website & Sitemaps
Enter your property URL exactly as registered in Search Console (with or without www). The tool auto-discovers sitemaps from robots.txt and common paths. Add custom sitemap URLs below if needed.
URL Selection
Select which URLs to submit. Use patterns to quickly filter large lists. Add custom URLs that are not in any sitemap.
Submit to Indexing API
Results
Understanding the Indexing API
The Google Indexing API allows site owners to notify Google when pages are added, updated, or removed. This helps search engines discover important pages faster instead of waiting for normal crawling cycles.
While officially intended for JobPosting and BroadcastEvent pages, it can still be used for broader URL submission workflows depending on your setup and verification status.
Frequently Asked Questions
Yes. All authentication and URL processing happens entirely in your browser. Your service account JSON is never uploaded or stored on any server.
The default Google Indexing API quota is 200 requests per day per project. Each submitted URL counts as one request.
The API is officially designed for JobPosting and BroadcastEvent pages, but other URLs may still be processed depending on Google's indexing behavior.
Yes. You can submit URLs in batches with configurable size and delay, making it suitable for large-scale indexing workflows.