Paste the contents of your Google Service Account JSON key file. This never leaves your browser — all API calls go directly from here to Google.
Get this from Google Cloud Console → IAM → Service Accounts → Keys → Add Key → JSON
⚠ The Indexing API only works for job posting (JobPosting) and livestream (BroadcastEvent) structured data pages — OR pages explicitly owned in Google Search Console. Submitting arbitrary URLs will return errors unless your property is verified.
URLs to Index
Add Pages for Indexing
Enter one URL per line. Supports bulk paste from CSV, sitemaps, or direct entry. Max 200 per day per GSC property.
0 URLs detected
Minimum 100ms recommended. Google rate-limits aggressively.
Live Log
Submission Queue
All URLs queued or processed this session.
#
URL
Type
Status
Time
No URLs queued yet — add some in the Submit tab.
▸ The Google Indexing API lets you notify Google when pages are added, updated, or removed — skipping the crawl queue entirely for supported page types.
How to Set Up Google Indexing API
01
Create a Google Cloud Project
Go to console.cloud.google.com and create a new project (or use an existing one). Name it something like seo-indexing.
02
Enable the Indexing API
In your project, go to APIs & Services → Library, search for Web Search Indexing API, and click Enable.
03
Create a Service Account
Go to IAM & Admin → Service Accounts → Create Service Account. Give it a name like indexer. Skip the optional role/permission steps. Once created, click on it → Keys → Add Key → Create new key → JSON. Download the file.
04
Add Service Account to Google Search Console
Open Google Search Console. Select your verified property. Go to Settings → Users and permissions → Add user. Paste the service account's email (e.g. indexer@your-project.iam.gserviceaccount.com) and set role to Owner.
05
Paste Your JSON Key Here
Open the downloaded JSON file in any text editor. Copy the entire contents and paste it into the Service Account JSON Key field on the Submit tab. This tool uses it to sign OAuth2 requests client-side — your key is never stored or transmitted anywhere except directly to Google's token endpoint.
06
Add Your URLs and Submit
Paste your URLs (one per line) into the URL input box. Start with Dry Run checked to validate everything without API calls. Then uncheck it and click Submit to Google. Monitor results in the Live Log and Queue tab.
Rate Limits & Best Practices
Stay within Google's quotas to avoid errors and account flags.
→
200 URLs/day per Search Console property. This resets at midnight Pacific.
→
Supported pages only: JobPosting schema, BroadcastEvent schema, or verified GSC pages. Submitting random URLs may still result in a crawl, but Google's documentation specifies these types.
→
Use URL_UPDATED for new and updated pages. Use URL_DELETED when content is permanently removed — this helps Google deindex faster.
→
Add 200ms+ delay between requests. Burst-firing will trigger 429 errors from Google's API.
→
Combine with sitemaps: The Indexing API is a signal, not a guarantee. Keep your sitemap updated and submit it in GSC for the best coverage.