Readibility problems

Hi @jspsegarra86,

Thank you for reaching out to us!

We understand that you were able to get our feedback working before and that it doesn’t seem to work at this time. Let us find out what is happening.

First, can you confirm that every plugin and theme on your WordPress site is up-to-date and that you are running WordPress 5.5.1? If not, we would encourage you to install any open update and see if the issue persists.

Apart from that, if the issue persists, we would like some more information:

A) Are you using any page builder to write your product content?
B) Is the red bullet only visible in the product overview page or does the same happen when you are on the product editing screen?
C) Do you have the same issue on other post types such as posts or pages?

Looking forward to your reply.

Thank you Jeroen for answering.

Yes, I confirm that every plugin and theme in my site is updated, WordPress as well.

A) No, I’m using the classic builder from WooCommerce, for pages Elementor and SiteOrigin.
B) Both
C) Yes the same

Hoping to solve it soon ??

Thank you for your support!

Hi @jspsegarra86,

Thank you for that information.

If you have the issue on all post types, we don’t think this is related to products or WooCommerce but a plugin or theme that conflicts with our plugin. We would like you to do a conflict check with the Health Check plugin so you can find the culprit. This plugin has a troubleshooting mode which disables all plugins and switches to a default theme for your user only, site visitors or other users are not affecting while testing this. Then you can see if the issue appears when you only activate Yoast SEO. If not, you can then switch back to your theme in the troubleshooting mode and check again. If it still works, you can 1 plugin at a time while checking each time if the issue appears.

When it does, you’ve found what combination of plugin/theme is causing this. We have more information on how to do this here: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/.

Please let us know what you can find, happy to help troubleshoot this further.

I could find this message on the state of health page: cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (http_request_failed).

Can be possible that is related to maintenance mode?

@jspsegarra86 The cURL error is related to the use or Ryte. The Ryte check is a single call to the Ryte services. They, in turn, try to reach your website to see if it’s accessible / indexible by robots. If they see your website, this check passes. If you’re on a development / staging website, they probably can’t see your website and this health check will report an error.

The?cause?of these errors can lie anywhere on the route between your website and the Ryte servers.
? Your own website / server can have (security) protocols or even plugins or code in place that prevent this request from completing.
? The route over the internet from your website to Ryte can be broken somehow (extremely unlikely, but still).
? Some system in between your website and Ryte does not allow / process this call, maybe due to security reasons / because your website is on a blacklisted server.

While it’s not a nice error to see, it’s difficult to pinpoint why this happens. And it’s almost impossible for someone who is not the website owner / host to determine this.

Having said that, this is an error that does?not?influence your site rank in any way. If the error would say that your website can’t be found by search engines, that would be reason to investigate. You can read more in this article (?https://yoast.com/yoast-seo-ryte/?) and there are even a few links to run this test manually.

Thank you for answering Carl!

Happy to help @jspsegarra86.

If you do the conflict check I mentioned earlier, please let us know what you find in regards to the feedback being red. We do know that there is currently a bug in the Site Origin plugin together with the Classic Editor. It might be related to what you are experiencing.

The team at Site Origin are investigating this, you can follow their progress here: https://github.com/siteorigin/siteorigin-panels/issues/811

Thanks a lot Jeroen!

I don’t know what it happened but today seems that work good! Hallelujah, god exists xD!

@jspsegarra86 Thanks for confirming that the issue has been corrected for you. We are going ahead and marking this issue as resolved but please let us know if you require any further assistance.