Md Mazedul Islam Khan

Sorry to hear that you’re having trouble in Yoast SEO. Can anyone please confirm how can I reproduce the issue? I tried reproducing it on a fresh WordPress installation with the latest version of Yoast SEO, Classic Editor, and the default theme installed but didn’t see the relevant error.

Before Yoast SEO v19.8, setting wpseo_robots to false was still outputting the robots meta but with the max-image-preview:large value on it.

In the latest version of Yoast SEO, setting wpseo_robots to false now set the content value to noindex, nofollow.

So, I doubt setting up wpseo_robots to false before disabling the robots meta completely on your site.

That said, while I don’t have a solution to remove the robots meta completely from your website, I do know that it has no effect when there’s no value in the content key. So, you may want to return an empty string i.e., from the wpseo_robots filter to see whether it return an empty value for you in the robots meta.

• This reply was modified 2 years, 1 month ago by Md Mazedul Islam Khan.

Sorry to hear that you have an error during the plugin Yoast SEO update. It looks like a file went missing during the plugin update, and you see the relevant error.

You can remove and reinstall the Yoast SEO plugin, which shall fix the issue for you!

Let us know whether the issue persists.

@illuminice I understand that you hate seeing the thread mark as closed even when the issue isn’t. As you have already seen in the past, we tried to reproduce the issue and are still open to doing it. However, there are no exact steps that you were able to share, which makes it extremely hard for us to reproduce the issue on our end. If we can’t reproduce it, finding out what’s causing the issue is challenging.

That said, we close a thread after a few days of inactivity to keep the overview. However, that doesn’t mean we forget the issue or are not interested in offering any assistance. If you can still share more information on how to reproduce it, we can deep dive into this again.

?? I am afraid whether we have a hook or filter available to hook the content from a different source simultaneously. I highly recommend you to deep dive into our public repository and developer documentation to find out more information and fix the puzzle ??

• Yoast Developer Portal
• Yoast GitHub Public Repository

So sorry to hear that you’re having a conflict between Google Web Story and Yoast SEO plugins. The issue you are experiencing is a known bug that we are already aware of. We can confirm that our development team is working to have a fix ready for this.

We appreciate your continued patience on this!

That’s very odd. Sorry to hear that you guys are having the same issue @emanuelmozes and @tim342. We are having a tough time reproducing the issue on our end.

Can you please confirm whether the issue persists on a fresh WordPress installation with only Avada + builder and Yoast SEO plugin active? Additionally, can you please confirm how large your website is? How many pages does it contain, and what types of servers are you using?

Thank you everyone for explaining the situation. I have opened a request internally (IM-1930) to introduce an option or filter to disable the relevant feature for you.

Thank you everyone for your continued patience. I have tested this on our end and was able to reproduce this. However, I am not convinced whether it’s a bug. When Yoast SEO is active on a multisite network level, the robots.txt output all the subsite’s sitemap index URL. This is expected since Yoast SEO now references all the subsites through the robots.txt. When activating Yoast SEO through each site level, the same operation occurs as well.

So, can anyone please elaborate on why you want to disable outputting all sitemap index URLs in the robots.txt except the main site’s sitemap index? Don’t you want to search engines to find all of your subsite’s sitemap index URLs?

Thanks for sharing all the information everyone. I just want to let you know that we were able to reproduce the issue and is currently being investigated further. It’s an unfortunate regression in the latest version that’s showing the relevant error in the server error log but that will not impact anything negatively in terms of SEO on your website.

That said, we have already opened a bug report internally for further investigation. In the meantime, please keep your discussion running on the relevant GitHub issue since the development team is far more active there. You can find the relevant GitHub issue here: https://github.com/Yoast/wordpress-seo/issues/18688

Sorry to hear that you’re seeing an error in the latest version of Yoast SEO. We are already into this but having a hard time reproducing it. Can you please share a bit more information on how can we reproduce the error on our end? Where do you see the relevant notice? Is there a specific page that we can take a look at? When exactly does the error occur?

Just to let you know, the issue isn’t specific to PHP v8.1 but specific to web hosting providers. The issue occurs when the web hosting provider disables the php_uname() function for security reasons. A PR has already been submitted to take care of this.

If you want this to be fixed as soon as possible, please reach out to your web hosting provider and ask them to enable the relevant PHP function on your server for you.

Thank you for following up @illuminice. What frontend publishing tool is that you are using? How does that work with your site? Do you have the exact file name and line number for me that you believe is the cause of the issue on Yoast SEO that flushes rewrite rules?

We are so sorry to hear that you guys are still having this issue. We are open to investigating the issue further. However, we have no idea what to look at and how to reproduce it as the issue occurs randomly and doesn’t provide any information at all.

So, if anyone could share the relevant information that would help us to deep dive into this further, we can start working on it internally from our end.

Thank you everyone for sharing all the relevant information that I have requested. I was able to reproduce the issue and open a bug report internally. Additionally, I will set it a high priority to ensure it gets fixed soon.

In the meantime, everything should be fine on your website as it doesn’t impact anything, but an unnecessary HTTP GET request to MyYoast.

Thanks for your understanding!