Error 422 with new Instant Indexing

#333303
  • Resolved RedaĆ§Ć£o Agora
    Rank Math free

    Hi!

    I’m having a problem since the new version of Rank Math was released.

    I get an error 422 – The URLs don’t belong to the host or the key is not matching the schema in the protocol – with every new post.

    This is a RAW response:

    12:38:59 bing_submit: https://agoranors.com/2022/01/arena-gremio-caxias/
    {
    “error”: {
    “code”: 422,
    “message”: “Unprocessable Entity”
    }
    }
    ——————————————————–

    Leonardo Severo
    Agora RS

Viewing 14 replies - 1 through 14 (of 14 total)
  • Anas
    Rank Math business

    Hello,

    Thank you for contacting Rank Math, and sorry for any inconvenience caused.

    Are you using the Instant Indexing API plugin for Google on your website?

    If yes, please disable the Instant Indexing plugin for the Google API temporarily and submit a couple of URLs for Bing without the plugin active.

    Then reactivate the plugin and submit it again for the IndexNow API. This should help resolve the issue.

    Donā€™t hesitate to get in touch if you have any other questions.ā€‹ā€‹ā€‹ā€‹ā€‹

    Hi, Anas!

    Instant Index is not enabled as it is returning the following error:

    Um erro do tipo E_ERROR foi causado na linha 218 do arquivo /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/firebase/php-jwt/src/JWT.php. Mensagem de erro: Uncaught DomainException: OpenSSL unable to sign data in /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/firebase/php-jwt/src/JWT.php:218
    Stack trace:
    #0 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/firebase/php-jwt/src/JWT.php(186): Firebase\JWT\JWT::sign()
    #1 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/google/auth/src/OAuth2.php(1394): Firebase\JWT\JWT::encode()
    #2 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/google/auth/src/OAuth2.php(460): Google\Auth\OAuth2->jwtEncode()
    #3 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/google/auth/src/OAuth2.php(494): Google\Auth\OAuth2->toJwt()
    #4 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/google/auth/src/OAuth2.php(534): Google\Auth\OAuth2->generateCredentialsRequest()
    #5 /var/www/agoranors/wp-content/plugins/fast-indexing-api/vendor/google/auth/src/Credentials/ServiceAccountCredentials.php(201): Google\Auth\OAuth2->fetchAuthToken()
    #6 /var/www/agoranors/wp-content

    Error 422 is showing up all this time with Instant Index disabled.

    Hello,

    Yes, it is certainly possible that the issue is due to the domain mismatch. Is the issue happening when you publish/update posts and pages? If yes, then it might be possible to fix this issue, using the rank_math/instant_indexing/publish_url filter hook available in the plugin. You may try to add something like this to the functions.php file of your theme or child theme, to force the Instant Indexing module to send the correct URL to the API:

    add_filter( 'rank_math/instant_indexing/publish_url', function( $url, $post ){
    	return str_replace( 'controle.', '', $url );
    }, 10, 2 );

    Hope that helps.

    Hi! I installed the code in functions.php, but there was no effect.

    I keep getting error: “Failed to submit URLs. See details in the History tab; 422 – Unprocessable Entity – The URLs don’t belong to the host or the key is not matching the schema in the protocol.

    If Instant Index plugin is active, returns error 500.

    Message from WordPress

    “When seeking help with this issue, you may be asked to provide some of the following information:
    WordPress version 5.9
    Current theme: JNews – Child Theme (version 1.0.0)
    Current plugin: Instant Indexing (version 1.1.4)
    PHP version 7.4.27”

    Hello,

    You only need the Instant Indexing plugin if you plan to use Google’s Indexing API alongside Bing’s IndexNow. Is that the case for you? Please keep in mind that officially, Google’s API can only be used for pages containing Live Streaming or Job Application structured data. If you don’t want to use that, you can keep the Instant Indexing plugin disabled, and simply use the IndexNow module available in Rank Math, which is a universal tool that can be used for any kind of content.

    The HTTP 500 error code refers to an Internal Server Error, the details of which you should find in the server’s error logs. Please share the error message so we can help you with this issue. If you don’t know how to find the error log, please contact your hosting provider about this.

    As for the HTTP 422 error, that could be caused by a number of reasons. First off, can you please check if the URLs that are sent to the API are the correct page URLs? You can check it in the History tab of the Instant Indexing page. Also, please try saving the Instant Indexing Settings once (without changing anything) to make sure that its settings are correctly saved in the database.

    Hope that helps.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hi.

    Website log is in the Sensitive Data

    We use instant indexing for Google because we work with local and daily news. Some of them are instant coverage (example: live traffic).

    But let’s go back to the issues for a solution as I know this must be affecting other customers. Let’s start from the beginning:

    Problem #1: Rank Math version 1.0.81 conflicts with the IIP (Instant Index Plugin). Error 500 to save posts and pages.

    #2: rollback was useless as it continued to show error 500.

    #3: IIP update to version 1.1.4 had no effect.

    #4: If IIP is disabled, I get a 422 error from the IndexNow API. If enabled, I have error 500.

    #5: Leaving the IIP active, but without Google JSON, “Please navigate to the Settings tab to configure the plugin” appears. Clicking “On Instant Indexing: Submit to IndexNow” on the posts page takes you to the Plugin Configuration page.

    #6: On the RankMath Dashboard, the Instant Index block says that there were no permissions to access /wp-admin/admin.php?page=rank-math-options-instant-indexing if IIP 1.1.4 was active. In version 1.1.6 it was fixed.

    #7: Leaving the IIP disabled again, error 422 occurs again.

    #8: Publishing/updating a post even works, but returns error 422 to IndexNow API.

    #9: Change requested in this topic also had no effect.

    Honestly, I don’t know what else to do on my side.

    Waiting for a solution or update,
    Leonardo Severo

    Hello,

    The error message you mentioned, ā€œOpenSSL Unable to sign dataā€ seems to suggest an issue with the SSL certificate, or some other server-side configuration issue with the OpenSSL module. Please contact your hosting provider about this matter.

    The 422 error is most probably related to your WP configuration, where the wp-admin is accessible from a subdomain. Have you checked the URLs in the History tab, are those correct? If yes, then the issue might be related to the API key: either the key is not accessible at all, or not at the location provided by the plugin. In order to troubleshoot this, we will need FTP access to your site. Please share the FTP access details in the Sensitive Data field so we can try some changes in the plugin code.

    Thank you. Looking forward to helping you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    I am also facing the same issue while i submit urls in instant index it gives error 422 it gives 422 response on submitted urls ? is my api setting wrong ?

    In addition
    What the difference between Google Publish/update URL and IndexNow: Submit URL?
    Which one can be indexed instantly?

    Hello,

    Thank you for sharing the FTP details.

    Can you please include your WordPress logins as well in the designated Sensitive Data section?

    It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
    https://wordpress.org/plugins/temporary-login-without-password/

    You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
    https://wordpress.org/plugins/wp-security-audit-log/

    We really look forward to helping you.

    What the difference between Google Publish/update URL and IndexNow: Submit URL?
    Which one can be indexed instantly?

    Hello @robinluo

    The IndexNow is an initiative by Bing and Yandex ā€“ this API allows pages to be indexed almost instantly, and it can be used for any type of content. Google’s Indexing API, on the other hand, can only be used for specific time-sensitive types of content, such as live streaming and job applications ā€“ it might work for other types of content too, but it is officially not supported. Another key difference is that Google’s API requires a rather lengthy and complicated setup procedure, while IndexNow can be used straight away, without any kind of setting up.

    Google representatives have expressed their interest in IndexNow in the past, so they too might adopt this API in the future. When that happens, IndexNow will be a very powerful tool. Until then, it is essential only for sites that get a decent amount of traffic from Bing or Yandex, but in any case, it certainly doesn’t hurt to enable it for any site.

    IndexNow can be used with the base Rank Math SEO plugin, while Google’s Indexing API can only be used after installing the stand-alone Instant Indexing plugin.

    Hope that helps. If you have any other question, please open a new ticket, so we can better assist you. Thank you.

    Hello,

    Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.

    If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.

    Thank you.

Viewing 14 replies - 1 through 14 (of 14 total)

The ticket ‘Error 422 with new Instant Indexing’ is closed to new replies.