Indexing APIs Configuration
Submit URLs instantly to search engines using IndexNow and Google Indexing API
Overview
ProRank SEO integrates with two major indexing APIs to help your content get discovered faster by search engines. Instead of waiting days or weeks for search engines to crawl your site, you can notify them instantly when content is published or updated.
Both APIs are configured in Technical SEO → Robots & Indexing → Indexing APIs taband work automatically once set up.
Core+ Feature: Indexing APIs require a Core+ license or higher. The APIs work automatically in the background once configured.
IndexNow API
What is IndexNow?
IndexNow is a protocol that allows websites to instantly notify participating search engines about content changes. Currently supported by:
- Microsoft Bing - Primary endpoint
- Yandex - Shared through Bing
- Seznam.cz - Czech search engine
- Naver - Korean search engine
Note: Google does not currently support IndexNow. Use the Google Indexing API for Google.
Setup Instructions
- Generate an API Key:Visit Bing IndexNow and generate a unique API key (32-128 character hex string)
- Enter Key in ProRank SEO:Go to Indexing APIs tab and paste your key in the "IndexNow API Key" field
- Enable IndexNow:Toggle "Enable IndexNow" to ON
- Validate Key:Click "Validate Key" to verify configuration
- Key File Creation:ProRank automatically creates the verification file at:
yoursite.com/[your-api-key].txt
Once configured, ProRank automatically submits URLs when you publish or update content. No manual intervention required!
How It Works
- • New Posts: Submitted when status changes to "publish"
- • Updated Posts: Submitted when published posts are updated
- • Automatic: Happens in the background within seconds
- • Error Handling: Failed submissions are logged and retried
- • Rate Limited: Prevents overwhelming the API
Google Indexing API
What is Google Indexing API?
Google Indexing API allows you to directly notify Google when pages are added or removed from your site. This results in much faster indexing compared to natural crawling.
Note: Google officially limits this API to job postings and livestream content, but it works for all content types in practice.
Setup Instructions
- Create Google Cloud Project:Go to Google Cloud Console and create a new project
- Enable Indexing API:Search for "Indexing API" in the API Library and enable it
- Create Service Account:Go to Credentials → Create Credentials → Service Account
Service account details:
- • Name: ProRank SEO Indexing
- • ID: prorank-seo-indexing
- • Role: No role needed
- Download JSON Key:Click on your service account → Keys → Add Key → Create new key → JSON
- Add to Search Console:Copy the service account email (ends with @...iam.gserviceaccount.com)In Search Console → Settings → Users & permissions → Add userAdd the email with "Owner" permission
- Configure in ProRank:Paste the entire JSON content into "Google Service Account JSON" field
- Enable and Validate:Toggle "Enable Google Indexing API" and click "Validate JSON"
JSON Format Example
{
"type": "service_account",
"project_id": "your-project-id",
"private_key_id": "key-id",
"private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
"client_email": "prorank-seo@your-project.iam.gserviceaccount.com",
"client_id": "1234567890",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/..."
}How It Works
- • URL_UPDATED: Sent when content is published or updated
- • URL_DELETED: Sent when content is unpublished or deleted
- • Delayed Submission: 30-second delay to allow for caching
- • Action Scheduler: Uses WordPress Action Scheduler for reliability
- • Error Logging: Failed submissions are logged for debugging
Comparison
| Feature | IndexNow | Google Indexing API |
|---|---|---|
| Search Engines | Bing, Yandex, Others | Google Only |
| Setup Complexity | Simple (API key only) | Complex (Service account) |
| Content Types | All content | All (officially limited) |
| Speed | Instant notification | Instant notification |
| Rate Limits | 10,000/day | 200/day |
| Verification | Key file on server | Search Console owner |
Monitoring & Debugging
IndexNow Monitoring
- • Check Bing Webmaster Tools for submission confirmations
- • Look for the key file at
yoursite.com/[api-key].txt - • Monitor WordPress debug.log for submission errors
- • Verify in Bing URL Inspection tool
Google Indexing API Monitoring
- • Check Google Cloud Console for API usage stats
- • Monitor quota usage (200 requests/day limit)
- • Use Search Console URL Inspection for verification
- • Check Action Scheduler for failed jobs
Common Issues
- IndexNow key file not found:Ensure WordPress has write permissions to site root
- Google API quota exceeded:Limited to 200 URLs/day - prioritize important content
- Service account not authorized:Must be added as Owner in Search Console
- Submissions not working:Check if Action Scheduler is running properly
Best Practices
Recommended Setup
- ✓ Enable both APIs for maximum coverage
- ✓ Test with a single post first
- ✓ Monitor initial submissions closely
- ✓ Keep API keys secure
- ✓ Set up error notifications
- ✓ Regular monitoring of quotas
When to Use
- • Time-sensitive content (news, events)
- • New product launches
- • Important updates to existing content
- • Seasonal content changes
- • After major site restructuring
- • Competitive niches requiring fast indexing
Performance Note: Submissions happen asynchronously in the background and don't affect site performance. Failed submissions are automatically retried.