Google Indexing API for WordPress: Eligibility Guide

Can WordPress Use the Google Indexing API?

Only when the target page meets Google's documented eligibility: a page with JobPosting structured data or a livestream page with BroadcastEvent embedded in a VideoObject. Ordinary WordPress posts, pages, products, and categories are not supported.

Prerequisites

• A Google Cloud Platform account (free to create)
• A GCP project with the Indexing API enabled
• A service account with a JSON key
• The service account added as an Owner in Search Console for your property

Step 1: Create a GCP Service Account

1. Go to console.cloud.google.com and create or select a project
2. APIs & Services → Enable → search "Web Search Indexing API" → Enable
3. IAM & Admin → Service Accounts → Create Service Account
4. Create a JSON key and download it

Step 2: Add to Search Console

1. Open Google Search Console → Settings → Users and permissions → Add user
2. Enter the service account email (ends in @developer.gserviceaccount.com)
3. Set permission to Owner

Step 3: Configure an Eligible WordPress Content Type

Option A — Indexaro: Verify the domain and configure credentials only after confirming the page template outputs valid eligible structured data. Indexaro can track API requests and quota; Google still validates eligibility and decides whether to index. The indexing API page covers what the API is, the 200 publish requests per day default, and the JobPosting and BroadcastEvent limit.

Option B — Custom integration:

add_action('publish_post', function($post_id) {
  $url = get_permalink($post_id);
  // Guard this call: the URL must be an eligible JobPosting
  // or livestream BroadcastEvent page.
  // Authenticate + call https://indexing.googleapis.com/v3/urlNotifications:publish
  // with body: {"url": $url, "type": "URL_UPDATED"}
});

Managing Quota

The initial default is 200 publish requests per day per Google Cloud project for onboarding and testing. Eligible production users can follow Google's approval and quota-request process. More credentials do not make unsupported WordPress content eligible.