• I had to optimize SEO data today after update. Unfortuantely I do get an error:

    Error parsing the response to JSON.

    The answer is an Error 500.

    My console sais:

    /wp-json/yoast/v1/link-indexing/posts:1

       Failed to load resource: the server responded with a status of 500 ()

    The JSON anwer if I try that URL is: {“code”:”rest_no_route”,”message”:”Es wurde keine Route gefunden, die mit der URL und der Request-Methode identisch ist.”,”data”:{“status”:404}}

    I have tried the YOAST Test plugin and the suggestions stated in the other threads including the troubleshooting plugin. Nothing helps. The error subsides. I have never changed any configuration in the last months so there has to be an error in an update between WordPress and Yoast. No debug mode, no tool or plugin that might shut down WordPress Rest API. Two weeks ago, everything worked fine, also the last few updates had no issues.

    Any more ideas?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @sonnenlanze

    I’m sorry you couldn’t complete the SEO data optimization analysis. The feature uses the WordPress REST API to scan posts/pages for the right internal links to show. Your server returned a 500 error when accessing the REST API.

    Please contact your web host to review your server setup to determine why the REST API returns the error. There may be a server setting or module that needs to be adjusted such as mod_security. If you are using security plugins they can block access to /wp-json/yoast/ file pathway. You may need to contact them or your host provider and whitelist that URL. Once the server no longer returns the error, we would expect the SEO Data feature to load and work correctly.

    In addition, if you are using caching on your site (varnish or otherwise), you may need to adjust cache settings to remove wp-json/yoast from the cache. If you are not sure how to do that, please contact your host provider and/or caching plugin authors.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.