Search and indexing

Fast Google indexing from WordPress: set it up step by step

Tell Google about new, changed and removed posts through the Google Indexing API from your own site: the Google Cloud steps, the key, Search Console ownership, quotas, and the honest limits.

Step 1: create a service account in Google Cloud

1. In Google Cloud, create a project (or pick one).
2. Enable the Web Search Indexing API for it.
3. Create a service account and download a JSON key for it.

Step 2: give the plugin the key

1. Open OnlyAI SEO, Indexation and find Fast Google indexing.
2. 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.
3. The plugin now shows the service account's email address. Copy it.

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

1. In Search Console open Settings, Users and permissions.
2. Add the service account's email as an Owner of your site.

Step 4: test and switch on

1. Back in the plugin, press Test the connection. A 403 almost always means step 3 is missing.
2. Switch Fast Google indexing 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, and the same post is not sent twice within six hours.
• 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 never sends posts marked noindex, password-protected posts or drafts.
• It keeps a short log, with Google's reason when something failed.

Quota

Google's default is 200 addresses a day for your Google Cloud project. The plugin counts them (Google's day ends at midnight Pacific time), sends the newest first, stops at the day's limit and stops at once on a 403 or 429. You can set a lower daily limit.

Why not the one-click Google sign-in?

The sign-in that connects Search Console and Analytics shares one quota across everyone who uses it. The 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.