Plugin Pulse
← Pulse

Instant Indexing for Google

by Rank Math SEO · Uncategorized

Also makes 1 other plugin · 4.2M+ installs across the portfolio →

A very efficient yet simple plugin to take care of your indexing woos and helps get your content crawled by search bots instantly.

How scoring works →
70 Health · B
Maintenance 74/100
Rating quality 66/100
Support 70/100

70 health vs 56 average across 16,378 Uncategorized plugins

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

89 / 100

Excellent listing optimization

Well tuned across the board

Update recency 83/100
WP compatibility 88/100
Rating quality 78/100
Listing tuning 100/100
Support resolution 100/100

Daily downloads

Since 2022-10-05 · 1,421 days · wp.org + Plugin Pulse archive

+4% vs prior 30d
427Downloads · Aug 26

30-day downloads

Rolling 30-day volume · peaks are release surges

12.4K

now · peak 345.2K

12.4K30d downloads · Aug 26

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

Instant Indexing for · #263 you Aabir Indexing Api · #53002 IndexNow Plugin · #338 Bing URL Submissions · #871

Rating trend

Star average over time · dips mark rough releases

3.6Stars · Aug 26

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

62per 1k installs · Aug 26

Release cadence

Occasionally updated
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

1

releases in the last 12 months

9mo ago

latest release · v1.1.22

22

tagged releases on record

Recent releases

1.1.22 · 9mo ago1.1.21 · 1.9y ago1.1.20 · 2.0y ago1.1.19 · 2.0y ago1.1.18 · 2.4y ago1.1.17 · 3.2y ago1.1.16 · 3.4y ago1.1.15 · 4.2y ago1.1.14 · 4.2y ago1.1.13 · 4.4y ago1.1.12 · 4.5y ago1.1.11 · 4.6y ago1.1.10 · 4.6y ago1.1.9 · 4.6y ago

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v1.1 100%
v1.0 0.2%

Estimated active installs

The public count shows “200K+”. Our estimate pins where the real number sits.

tracked estimate
200K–300K ≈260K

Refined from the date this plugin crossed into its current band.

Install history · since 2020-04-29 · 1,431 observations

200KInstalls · Aug 26

Estimated value

What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.

Est. annual revenue

N/A

Est. acquisition value

N/A

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price.

Details

Version
1.1.22
Last updated
9mo ago
Added
2019-09-24 · 6 yrs old
Requires WP
5.6
Tested up to
6.6.7
Requires PHP
7.2.5

Recent reviews

All reviews on wp.org ↗
  1. jesyna
    8mo ago

    always shows 404 on ‘get status’. but when submit it shopws success. Even a URL is on google, this plugin shows: Error 404

    Read on wp.org ↗
  2. partho8181
    12mo ago

    I followed Rankmath instructions to configure it. but didn’t work for me. always shows 404 on ‘get status’. but when submit it shopws success. Even a URL is on google, this plugin shows: Error 404 Requested entity was not found. This topic was modified 10 months, 1 week ago by partho8181.

    Read on wp.org ↗
  3. Mohammad
    1.0y ago

    Hello, I’m reaching out because I’ve been seeing a persistent error on my WordPress site whenever I activate your plugin. The error message is as follows: Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fast-indexing-api domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in -----\wp-includes\functions.php on line 6121 I’ve noticed that this message only appears when the fast-indexing-api plugin is active. When I deactivate it, the error goes away completely. Based on what I’ve read, it seems the issue is related to how and when the plugin loads its translations. Could you please let me know if there’s a recommended solution or workaround for this issue? I’d also appreciate any information about whether a fix will be included in an upcoming update of the plugin. Thanks in advance for your help!

    Read on wp.org ↗
  4. tagarjatim
    1.1y ago

    Crash in wordpress 6.8.2 multisite

    Read on wp.org ↗
  5. travis42
    1.1y ago

    hasn’t worked for a long time

    Read on wp.org ↗
  6. Просування сайтів
    1.5y ago

    It seems to work

    Read on wp.org ↗
  7. elsoar
    1.8y ago

    The submission is a sham. There’s no real interaction between Google and the link; you only receive a green message confirming the action, but in reality, nothing has happened. The links have not been, and will not be, indexed.

    Read on wp.org ↗
  8. Nicolas Lemoine
    2.0y ago

    Hello, I’m using in a composer based WordPress stack and I’m having issues with with your plugin dependencies. Choosing Composer in the context of a WordPress plugin implies certain prerequisites and responsabilities. You have three (unique) solutions: Provide your plugin without autoload/vendor via Composer (as Yoast or ACF do) so that a WordPress project managed with Composer (which is very often the case on “pro” sites using Bedrock or equivalent stacks) is aware of your dependencies/constraints and can warn the user of a compatibility problem or manage the constraints of other dependencies (the whole point of a dependency manager). Prefix your dependencies (for example, with Yoast), which allows you to isolate your dependencies (by automatically modifying their namespace – PHPScoper does this very well) and avoid conflicts. You may provide a bundled plugin, but composing it should only be used for its autoload functionality (no dependencies). Your plugin is using very popular dependencies (Monolog, Guzzle) that may conflict with a user based installation or another plugin. If you intend to use external dependencies, please do it the right way. This topic was modified 1 year, 10 months ago by Nicolas Lemoine.

    Read on wp.org ↗

Latest updates

via wp.org changelog

Recent releases and news for this plugin

  1. Version 1.22 Fixed: Changing the API Key in the IndexNow settings was not working Fixed: PHP warning triggered by the _load_textdomain_just_in_time function 1.22
  2. Version 1.21 Fixed: JS error on the console page due to changes in the Google API 1.21
  3. Version 1.20 Fixed: Adjusted limits as per Google’s new guidelines 1.20
  4. Version 1.19 Added: WordPress 6.6 Compatibility 1.19
  5. Version 1.18 Added: WordPress 6.5 Compatibility Fixed: Missing Instant Indexing page for editor role when Rank Math plugin is active 1.18
  6. Version 1.17 Fixed: PHP notice on the plugin settings page. Fixed: Double submission of posts to the Google Indexing API. Fixed: “Submit to IndexNow” action showing even when IndexNow is disabled. Fixed: PHP 8.2 compatibility issues. 1.17

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 8.1.12 · WP 6.8.3

Low memory footprint
Low page-speed impact
Runs on latest PHP + WP
No PHP errors
No JS errors
Activates cleanly
No resource errors
No external HTTP errors
Optimized database use
Frequently updated

Languages

via translate.wordpress.org

Translated into 21 languages, 15 at 90% or more

Dutch 100%
Dutch (Formal) 100%
English (UK) 100%
German 100%
German (Austria) 100%
German (Formal) 100%
German (Switzerland) 100%
German (Switzerland) Informal 100%
Persian 100%
Portuguese (Brazil) 100%
Russian 100%
Spanish (Chile) 100%
Spanish (Spain) 100%
Ukrainian 100%
Vietnamese 100%
Japanese 70%
Swedish 55%
Spanish (Mexico) 47%
French (France) 31%
Dutch (Belgium) 28%
Greek 20%

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2026-01-20 300K+ → 200K+ down after 1 days in tier
  2. 2026-01-19 200K+ → 300K+ up after 1 days in tier
  3. 2026-01-18 300K+ → 200K+ down after 836 days in tier
  4. 2023-10-05 200K+ → 300K+ up after 345 days in tier
  5. 2022-10-25 100K+ → 200K+ up

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Compare head to head →

Embed this report card

Drop a live Pulse card for Instant Indexing for Google into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/fast-indexing-api" width="480" height="300" style="border:0" loading="lazy" title="Instant Indexing for Google — Plugin Pulse"></iframe>
Preview card ↗

Instant Indexing for Google: 200K+ active installs, 3.6★ (36 reviews). Plugin Pulse (WP Mayor), as of 2026-08-25. https://plugins.wpmayor.com/plugin/fast-indexing-api