Rank Math Instant Indexing: Setup, Limits and Errors

Rank Math's Instant Indexing plugin sends a Google Indexing API notification each time you publish or update a post, so Googlebot can come and crawl it sooner than it would through the sitemap. Setting it up takes a Google Cloud project, a service account with a JSON key, and Owner access for that service account in Search Console; after that the plugin needs the JSON pasted into one settings tab. It inherits Google's rules: 200 requests per day, and an API that Google documents for job posting and livestream pages only.

What the plugin is

The plugin is called Instant Indexing for Google (slug fast-indexing-api) and is published by Rank Math SEO as a free, separate plugin. It works with or without the main Rank Math SEO plugin. When read on WordPress.org on 11 October 2026 it had 200,000+ active installations, was at version 1.1.22, had last been updated 11 months earlier, and carried the notice that it had not been tested with the latest three major WordPress releases.

What it does:

• Sends URL_UPDATED to the Indexing API when a post of a selected type is published or updated.
• Lets you submit URLs by hand, up to 100 at a time, from a console inside WordPress.
• Lets you send URL_DELETED for a post you removed, and query the last notification Google holds for a URL.
• Adds bulk actions to the Posts list for the same operations.

It does not check whether Google indexed anything. For that you still need URL Inspection in Search Console.

Read this before you connect it

Google's documentation says the Indexing API can only be used for pages with JobPosting structured data or livestreams with BroadcastEvent markup. Rank Math's own setup article repeats this, says the author does not recommend it on "money websites", and tells you to proceed at your own risk. In practice the API accepts other URLs, many sites use it that way, and Google has not said what it does beyond ignoring requests and revoking access. If your WordPress site is a job board, you are inside the rules. If it is a blog, you are relying on Google's tolerance. Decide that before step 1. The background is in the Google Indexing API guide.

Step 1: create the Cloud project and enable the API

1. Open the Google Cloud Console, click the project selector at the top and choose New Project. Name it after the site and click Create.
2. With that project selected, open the API library and search for Web Search Indexing API. Click Enable.

One project per site keeps the 200 per day quota and the keys separate, and it is what Google expects. Do not create several projects for one site to multiply the quota; Google's documentation names that as abuse.

Step 2: create the service account and the JSON key

1. In the Cloud Console go to IAM & Admin > Service Accounts and click Create Service Account. Give it a name and click Done. Copy the email address it was given (it ends in .iam.gserviceaccount.com).
2. In the service account's row, open the actions menu, choose Manage keys, then Add Key > Create new key, keep JSON and click Create. The file downloads.

Treat that file like a password. Anyone holding it can send Indexing API requests for every property the service account owns. The full click path, including what each screen looks like in 2026, is in create a Google Indexing API key.

Step 3: make the service account an Owner in Search Console

1. Open Search Console and select the property that contains your site. A Domain property covers every host and protocol; a URL prefix property must match the exact scheme and host your posts use.
2. Go to Settings > Users and permissions and click Add user.
3. Paste the service account email, set the permission to Owner, click Add.

This step causes most of the support threads. The Indexing API verifies ownership of each URL you send against Search Console, and only Owner is enough. Full user fails with 403 Permission denied. Failed to verify the URL ownership.

Step 4: configure the plugin

1. Install and activate Instant Indexing for Google from Plugins > Add New.
2. Go to Rank Math SEO > Instant Indexing.
3. On the Google API Settings tab, paste the contents of the JSON file into the text area, or upload the file.
4. Tick the post types that should be submitted automatically. Posts and pages are the usual choice; leave out attachments and any post type that is noindexed.
5. Click Save Changes.

From now on, publishing or updating a post of a selected type triggers one URL_UPDATED request.

Submitting and checking by hand

The Console tab is where you test the setup and push URLs that are not posts.

1. Paste one or more URLs, one per line.
2. Set the action to Google: Publish/update URL and click Send to API.
3. The response appears below. A 200 with the URL echoed back means Google accepted the request.

The other two actions are Remove URL (sends URL_DELETED; make the page return 404 or 410 first, or carry noindex, which is what Google's documentation requires) and Get URL Status, which returns the last notification Google holds for the URL, with its timestamp. It does not tell you whether the page is indexed; it tells you what you sent. Rank Math notes that a status request for a URL you never published returns 404 Requested entity was not found, which is expected.

On the Posts list, the same actions are available as bulk actions, with the 100 URL cap per batch.

Errors you will see

Message	Cause	Fix
403 Permission denied. Failed to verify the URL ownership	Service account is not an Owner of the matching property	Step 3; check that protocol and host match the property
403 Indexing API has not been used in project ... or it is disabled	API not enabled in the project that issued the key	Step 1, point 2, in the right project
404 Requested entity was not found on Get URL Status	No notification was ever sent for that URL	Publish it once, then query
429 Quota exceeded	200 requests used today	Wait for midnight Pacific; submit fewer, changed URLs only
400 invalid URL	URL malformed, contains a space, or uses the wrong scheme	Check the URL in the Console tab
"Error Undefined"	URL belongs to a different domain than the site making the request	Send only URLs of this site's verified property

The 200 per day limit

Everything the plugin sends counts against 200 publish requests per day for the Cloud project, publish and remove together. Bulk submissions do not get around it: 100 URLs in one batch is 100 requests. The counter resets at midnight Pacific time. If you update 50 posts in a batch edit, that is 50 requests, so turn automatic submission off before mass edits that do not change what a reader sees (tag cleanups, template tweaks, bulk category moves) and turn it back on afterwards.

The quota is also why "submit everything" is the wrong habit. A post that already shows "URL is on Google" gains nothing from another notification unless its content changed. Spend the 200 on new posts and real updates. The arithmetic and the quota increase form are in Google Indexing API quota.

Check what you are about to submit

The plugin submits whatever matches the selected post types; it is your job to make sure those URLs are fit to be indexed. Three things to test once:

• Publish a test post set to noindex in your SEO plugin and use Get URL Status on it. If a notification went out, Google was asked to crawl a page it is told not to index, and you need to leave that post type unticked or set noindex posts aside.
• A post you publish and immediately unpublish has already been sent. Keep drafts as drafts until they are ready.
• After a slug change, make sure the old URL redirects, then send the old URL as a removal from the Console tab if you want Google to drop it sooner.

The free indexability checker shows what a URL currently answers (status, meta robots, canonical) if you are not sure what you are about to submit.

Bing and the other engines

Bing does not use Google's Indexing API; it uses IndexNow. Rank Math's main SEO plugin has an Instant Indexing module built on IndexNow for Bing, Yandex and the other participants, and the Instant Indexing for Google plugin's changelog lists an option to submit posts through IndexNow as well. Turn one of them on, not both, so each change is sent once. Setup on WordPress is in IndexNow for WordPress.

Without a plugin

If you would rather not hold an API key inside WordPress, or you run sites on more than one CMS, TurboIndex does the same job from the outside: it reads the sitemaps submitted in Search Console, fetches each new or changed URL with TurboIndexBot first so a noindex page, a redirect or a 404 is never submitted (see the crawler page), sends the rest to the Indexing API and to IndexNow, and then checks each URL through the URL Inspection API to show whether Google indexed it. It works for any CMS, including a WordPress site with no plugins at all, and the same 200 per day quota and the same Google policy apply.