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.

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!

Crash in wordpress 6.8.2 multisite

hasn't worked for a long time

It seems to work

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.

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.

Great plugin, but it doesn't have one of the most important features!
As you know and it is included in the plugin description, this is a sensitive feature and Google does not like spam requests.
The plugin should add a feature that has a checkmark before the content update to determine whether the plugin should send it to Google or not.
Otherwise, you have to go to the settings and disable and re-enable it every time, which wastes a lot of time

<!-- wp:paragraph --> <p class="">I tested it, the code works but it doesn't index quickly, it takes 2-3 days to index without this module, it indexes in 3-4 hours, to be precise, very disappointed with this module. site here</p> <!-- /wp:paragraph -->

great plugin.
I loved