Google Indexing API lets you index any page on Google free in under 5 minutes using a Python script to bypass standard crawl queues. This guide covers the complete setup process with OAuth 2.0 and service accounts, a ready-to-use Google Indexing API Python script, official rate limits and quota details, supported page types, and the 5 most common setup mistakes.
What Is the Google Indexing API?
The Google Indexing API notifies Google directly when a page is created, updated, or deleted, requesting immediate crawl instead of waiting for Googlebot to discover the change organically. Traditional indexing can take days or weeks. The Google Indexing API reduces that to minutes or hours for supported page types. In 2026, with AI-generated content flooding every vertical and Google's crawl budget becoming a finite resource, the google indexing api is the fastest way to get new or updated pages into Google's index. Before using the API, ensure your pages pass on-page SEO quality checks, because Google still evaluates every submitted page against its quality guidelines.
The Indexing API is officially designed for JobPosting and BroadcastEvent structured data pages. However, Google has confirmed it works for any page with these schema types. Many SEOs use it for other page types with success, though Google technically limits it to these categories. The default quota is 200 URLs per day. For pages not using JobPosting or BroadcastEvent schema, use sitemap submission or the URL Inspection tool instead.
How Does the Google Indexing API Work?
The Google Indexing API works by sending a direct notification to Google's crawler infrastructure rather than waiting for Googlebot to discover your page during its regular crawl cycle. When you submit a URL, Google schedules that page for a fresh crawl within minutes to hours. The API does not guarantee the page will be indexed. It guarantees Googlebot will be notified immediately.
What happens after you submit a URL
- Notification received: Google acknowledges the submission and adds the URL to a priority crawl queue
- Crawl scheduled: Googlebot visits the page, typically within minutes to 2 hours of submission
- Indexing decision: Google evaluates the page against its quality guidelines. Indexing is never guaranteed regardless of how you submit the URL
- Status checkable: You can query the API to check when Google last processed each submission for a given URL
The Google Indexing API vs sitemaps
For websites with many short-lived pages like job postings, the Indexing API prompts Googlebot to crawl sooner than updating a sitemap. However, Google still recommends submitting a sitemap for full site coverage. Use the API for priority pages that need fast indexing. Use sitemaps for bulk coverage of your entire site. The two tools serve different purposes and work best together.
How to Set Up the Google Indexing API in 5 Minutes
These four steps take approximately 5 minutes the first time. After setup, submitting new URLs takes seconds. Before starting, ensure you understand the technical SEO fundamentals that determine whether Google actually indexes pages after receiving the notification.
Go to console.cloud.google.com. Create a new project. Enable the Indexing API under "APIs and Services." No billing account is required for quota testing up to 200 URLs per day.
Under "IAM and Admin," create a service account. Download the JSON key file. Keep it secure. Anyone with this key can submit indexing requests for your domain. Store it outside your public repository.
Go to Google Search Console. Navigate to Settings, then Users and permissions. Add the service account email as an Owner. Without this step, the API cannot submit URLs for your domain. This is the most commonly missed step.
Use the Python script below or the Google API client to submit URLs. The API supports URL_UPDATED for content updates and URL_DELETED for removals. Submit URLs one at a time or batch up to 100 per HTTP request.
Python Script for Bulk Indexing
Copy and paste this script. Replace the SERVICE_KEY path and update the URLs list with your pages. The script submits each URL and prints the response. For production use, add error handling for failed submissions.
from google.oauth2 import service_account
from googleapiclient.discovery import build
SERVICE_KEY = "path/to/your-service-key.json"
def notify_google(url):
creds = service_account.Credentials.from_service_account_file(
SERVICE_KEY, scopes=["https://www.googleapis.com/auth/indexing"]
)
service = build("indexing", "v3", credentials=creds)
body = {"url": url, "type": "URL_UPDATED"}
return service.urlNotifications().publish(body=body).execute()
urls = [
"https://yoursite.com/new-page-1/",
"https://yoursite.com/new-page-2/",
"https://yoursite.com/new-page-3/",
]
for url in urls:
try:
result = notify_google(url)
print(f"Indexed: {url} -> {result}")
except Exception as e:
print(f"Failed: {url} -> {e}")
When to Use the Google Indexing API
Not every page needs the Indexing API. Use it for pages where speed matters: time-sensitive content, newly published articles, or updated pages where the old version is still ranking. For bulk indexing of an entire site, stick to sitemaps.
| Use Case | Recommended | Why |
|---|---|---|
| New job listings | Yes | Official supported use case |
| Live stream events | Yes | Official supported use case |
| New blog posts | Use carefully | Works but not officially supported |
| Product page updates | Use carefully | Works but not officially supported |
| Updated service pages | Use carefully | Works for content refreshes |
| Bulk URL submission (100+) | No | Use sitemap.xml instead |
When not to use it
- Pages with crawl issues: the API notifies Googlebot but does not fix crawl errors. Fix your Google Search Console sitemap issues first
- Low-quality pages: Google may crawl the page and decide not to index it. The API handles notification, not quality evaluation
- Bulk indexing: for hundreds of URLs, sitemaps are more efficient and officially supported across all page types
- Pages without schema: while the API may work without JobPosting or BroadcastEvent schema, results are not guaranteed for unsupported page types
Common Mistakes with the Google Indexing API
Not adding the service account to Search Console. This is the most common setup failure. The API returns a 403 error because the service account has no permission to access the domain. Add the service account email as an Owner in Search Console settings before submitting any URLs.
Exceeding the 200 URL daily quota. The default quota is 200 URLs per day per service account. Exceeding it returns errors without warning. Monitor your submission count. For higher volume, request a quota increase through Google Cloud Console. Spam attempts or multiple accounts to bypass quotas may result in API access being revoked.
Submitting pages expecting guaranteed indexing. The API guarantees crawl notification, not indexing. Google still evaluates each page against its quality guidelines. If the page has thin content, duplicate content, or technical issues, Googlebot will crawl it and choose not to index it. The API is a notification tool, not an indexing shortcut for low-quality pages.
No error handling in the submission script. Network failures, quota exhaustion, and malformed URLs all produce exceptions. Without try-catch blocks, one failed submission stops the entire batch. Wrap each submission in error handling and log failures for retry.
Storing the service account key in a public repository. The JSON key file grants full indexing access to your domain. Anyone with this key can submit URLs on your behalf. Store it outside your codebase, add it to .gitignore, and use environment variables to reference the path. A leaked key is a domain-level security risk.
Frequently Asked Questions About the Google Indexing API
Yes. The Indexing API is free within Google's quota limits: 200 URLs per day for regular use. Exceeding this limit requires requesting a quota increase through Google Cloud Console. For most small to medium websites, 200 URLs per day is more than sufficient for new content and content updates. There is no paid tier for the Indexing API itself.
Most URLs submitted via the Indexing API are crawled within minutes to 2 hours. In some cases, it may take up to 24 hours. The API does not guarantee instant indexing. It guarantees that Googlebot is notified immediately rather than waiting for organic discovery. For pages that need both fast indexing and GEO visibility, combine the API with proper schema markup.
Google officially limits the Indexing API to JobPosting and BroadcastEvent pages. In practice, it works for other page types including blog posts and product pages. Many SEOs use it across multiple content types without issues. However, Google could enforce the limitation at any time. For bulk indexing or unsupported page types, use sitemap.xml submission instead.
The Indexing API submits URLs programmatically in bulk through code. The URL Inspection tool submits one URL at a time through the Search Console interface. Both request indexing, but the API is designed for automated workflows where new pages are created regularly. The URL Inspection tool is designed for manual checks and single-page submissions. For a site publishing daily, the API saves hours of manual submission time.
The default quota is 200 URLs per day per service account. Google provides this quota for API onboarding and submission testing. For higher volume, request additional quota through Google Cloud Console. The quota applies to the combined total of URL_UPDATED and URL_DELETED submissions. Batch up to 100 URLs per HTTP request to reduce the number of connections your client makes.
A 403 error means the service account does not have permission to access the domain you are submitting URLs for. The fix: go to Google Search Console, navigate to Settings, then Users and permissions, and add the service account email as an Owner. This is the most commonly missed setup step. The service account must have Owner-level access to submit indexing requests.
No. The Indexing API guarantees crawl notification, not indexing. After Googlebot crawls the page, Google evaluates it against the same quality guidelines it applies to all pages. Pages with thin content, duplicate content, spam signals, or technical issues may be crawled and not indexed. The API is a speed tool, not a quality bypass. Fix quality issues before submitting.
Use both. The Indexing API is for priority pages that need fast crawl notification. Sitemaps are for full site coverage. Google still recommends submitting a sitemap even if you use the API. The API handles speed-sensitive pages. Sitemaps handle site-wide crawl discovery. Together they provide the fastest indexing speed with the broadest coverage.
Yes. The Indexing API is designed for automation. Integrate the submission call into your CMS publishing workflow. When a new page is published, trigger an API call automatically. Most content management systems support webhooks that fire on publish events. Connect the webhook to a script that extracts the new URL and submits it through the API. This eliminates manual submission entirely.
The API returns a quota exceeded error and rejects further submissions until the quota resets. The quota resets daily. Repeated quota violations or attempts to bypass quota using multiple service accounts may result in API access being revoked. Implement quota tracking in your submission script and pause submissions when you approach the limit. Request a quota increase if you consistently need more than 200 URLs per day.
Final Thoughts
The Google Indexing API is the fastest path from publish to index for priority pages. Set it up once in 5 minutes. Submit new and updated URLs programmatically. Respect the quota. Fix quality issues before submitting. The API handles notification speed. Your content quality handles indexing.
Get a free technical SEO audit from Clienvora. We diagnose indexing issues and implement the fixes.