Features

Fast Google indexing, built into WordPress (and the honest limits)

12 October 2026 · 2 min read

How OnlyAI SEO tells Google about new, changed and removed posts through the Google Indexing API from your own site, how to set it up, and what it can and cannot promise.

Google's Indexing API lets a site tell Google "this address is new", "this one changed" or "this one is gone". OnlyAI SEO now does that from inside WordPress, on your server, with nothing to download or run on a computer.

First, the honest part

Google documents this API for job-posting and livestream pages only. It often accepts other pages, but that use is outside what Google documents, Google can withdraw it, and a successful send does not make Google crawl sooner or index the page. Your sitemap, internal links and the quality of the page still decide indexing. Think of this as a supplement, used in moderation. The plugin shows this warning on the screen where you switch it on.

Setting it up (about five minutes, once)

In Google Cloud, create a project and enable the Web Search Indexing API.
Create a service account and download a JSON key for it.
In OnlyAI SEO, Indexation, paste the key (or choose the file) and press Save key. It is stored encrypted on your site, never shown again and sent only to Google.
In Search Console, Settings, Users and permissions, add the service account's email (the plugin shows it) as an Owner of your site.
Press Test the connection, then switch it on.

What it does once it is on

About a minute after a post is published or updated, your site tells Google. Several quick saves become one send.
When a post is deleted or unpublished, it sends a removal notice.
Older posts are sent only if you tick "Also send older posts", a few at a time, newest first.
It stays inside the daily limit (200 by default; you can lower it), counts it for you (Google's day ends at midnight Pacific time) and stops at once if Google says the limit is used up or the key is not allowed.
It never sends posts marked noindex, password-protected posts or drafts, and does not send the same post twice within six hours.
It keeps a short log of what happened, with Google's reason when something failed.

Why a service account and not the Google sign-in

The one-click Google sign-in that connects Search Console and Analytics shares one quota across everyone who uses it. Google's 200-a-day limit belongs to the Google Cloud project that owns the key, so each site uses its own key and its own quota.

Who it suits

News and fast-moving sites, job boards and event sites will get the most from it. For a normal blog, a good sitemap and sensible internal links do more, and the plugin gives you both.