This guide walks you through requesting access to the Google Indexing API, which lets you notify Google about new or updated pages on your site so they can be crawled faster. You’ll need a Google Cloud project, a service account, and a verified site owner account. The approval process is not automatic—Google reviews each request—so following the exact steps below improves your chances.
What You’ll Need
- A Google account (the one you use for Search Console).
- Ownership or full control of a website (verified in Google Search Console).
- A Google Cloud project (free to create).
- Basic familiarity with JSON and HTTP requests (for testing the API after approval).
Step-by-Step
- Create a Google Cloud project – Go to console.cloud.google.com, sign in, and click the project dropdown at the top. Click “New Project,” give it a name (e.g., “Indexing API”), and click “Create.” Wait for the notification, then select the project from the dropdown.
- Enable the Indexing API – In the Cloud Console, go to “APIs & Services” > “Library.” Search for “Indexing API” and click on it. Click “Enable.” If you don’t see it, make sure you’re in the correct project.
- Create a service account – Go to “APIs & Services” > “Credentials.” Click “Create Credentials” and choose “Service Account.” Give it a name (e.g., “indexing-bot”), assign no roles (you’ll add permissions later), and click “Done.”
- Generate a private key – In the service account list, click the email of the service account you just created. Go to the “Keys” tab, click “Add Key” > “Create New Key.” Choose JSON and click “Create.” The key file downloads—store it securely; you’ll need it for API calls.
- Add the service account to Search Console – Open Google Search Console and select your property. Go to “Settings” > “Users and permissions.” Click “Add User,” enter the service account email (it ends with @project-id.iam.gserviceaccount.com), and set permission to “Full.” Click “Add.”
- Request approval from Google – Go to the Indexing API prerequisites page and find the “Request access” form. Fill it out with your project number (found in Cloud Console under “Project settings”), your site URL, and a short explanation of how you’ll use the API. Be specific—mention that you’ll notify Google only for new or updated pages, not for all URLs. Submit the form.
- Wait for the approval email – Google typically responds within a few days to a couple of weeks. The email will confirm whether your project is approved. If approved, your service account will have access; if not, you’ll need to reapply after addressing the feedback.
- Test the API – Once approved, use the private key JSON to authenticate. Send a test request using a tool like cURL or a script. For example, to notify a URL, use the endpoint
https://indexing.googleapis.com/v3/urlNotifications:publishwith a JSON body like{"url": "https://example.com/page", "type": "URL_UPDATED"}. You should get a 200 response.
Common Mistakes
- Not verifying site ownership – The service account must be added as a user in Search Console for the exact property (domain or URL prefix) you’re submitting. If you add it to the wrong property, the API will reject your requests.
- Using the wrong project number – The approval form asks for the project number, not the project ID or name. You can find it in the Cloud Console under “Project settings.”
- Submitting all URLs – Google’s guidelines say to use the API only for pages that are new or significantly changed. If you submit every URL on your site, Google may revoke access.
- Ignoring the service account email – When adding the user in Search Console, you must enter the full service account email, which includes the project ID. Copy it from the Cloud Console to avoid typos.
- Not enabling the API before requesting – If the API isn’t enabled in the project, the approval form may not recognize the project. Double-check that the API shows “Enabled” in the Library.
Tips
- Use a dedicated project – Create a separate Cloud project just for the Indexing API. This keeps permissions isolated and makes it easier to manage keys.
- Keep your private key secure – Never commit the JSON key to version control. Store it in a secure location and restrict access to only those who need it.
- Monitor your quota – The Indexing API has a default quota of 200 URLs per day. Check your usage in the Cloud Console under “Quotas” to avoid hitting limits.
- Use URL_UPDATED for changes – For pages that already exist but have new content, use
URL_UPDATED. For brand-new pages, useURL_UPDATEDas well—there’s no separate “new” type; the API treats both the same. - Test with a single URL first – After approval, try submitting one URL to confirm everything works before automating.
Troubleshooting
- Approval request rejected – Google may reject your request if your site doesn’t meet their guidelines (e.g., too many pages, or the site is new with little content). Improve your site’s quality, wait a few weeks, and reapply with a clearer explanation of your use case.
- API returns 403 Forbidden – This usually means the service account isn’t added as a user in Search Console, or the property doesn’t match. Verify the email and permission level in Search Console.
- API returns 400 Bad Request – Check the JSON payload. The
urlmust be the full URL (including https://) andtypemust be eitherURL_UPDATEDorURL_DELETED. - Cannot find the Indexing API in the library – Make sure you’re in the correct Cloud project. If you have multiple projects, switch to the one you created.
- Quota exceeded – The default quota is 200 URLs per day. If you need more, you can request a quota increase from the “Quotas” page in the Cloud Console, but approval is not guaranteed.
- Authentication errors – Ensure your code is using the correct service account email and private key. If you regenerated the key, update your code with the new JSON file.
Frequently Asked Questions
How long does approval take?
Google doesn’t publish a fixed timeline. In practice, it can take anywhere from a few days to several weeks. Check your email (including spam) regularly.
Can I use the Indexing API for any website?
No. The API is intended for sites that produce a high volume of new pages, such as job boards or news sites. If your site has a small number of pages, regular crawling may be sufficient.
Do I need to be a Google partner or pay for access?
No, the API is free. You only need a Google account and a verified site. There’s no cost to request access or use the API.
What’s the difference between URL_UPDATED and URL_DELETED?
URL_UPDATED tells Google to recrawl a page because it has new content. URL_DELETED tells Google to remove a page from the index (e.g., when a page is permanently removed).
Can I submit multiple URLs in one request?
No, each request handles one URL. To submit multiple URLs, you need to send multiple requests, but keep within the daily quota.
What happens if I submit a URL that isn’t in my Search Console property?
The API will return an error. The URL must belong to the property that the service account has access to in Search Console.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- How to Choose an Amplifier for Magico A3 Speakers
- How to Ban a Player from Your FiveM Server
- Pokemon Go Friend Codes: How to Add & Use Them33.33 XP/day
- Google Algorithm Change: Original Reporting Boost
- Create Folder for Selected Item on Mac: Full Guide
- Data Center Location Questions for AI Workloads