Database Error on Post Sitemap

@simonbbs We’re sorry to hear you are experiencing this error. To resolve this, can you please try the following?:

1. Install & activate the?Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Hit the “Reset Indexables & Migrations” button
4. Under SEO → Tools, click the “Start SEO Data Optimization” button.

Hey @devnihil

Thanks for the information!

We ran this test on staging but were blocked at step 4, as it is not a production environment.

I’m a little nervous about running this on production. Is there any possible downside or possibility or losing our data when running that on production?

Thanks so much!

-Simon

@simonbbs

SEO Data Optimization method should not cause you lost data on your production site. There is no downside of running this on production site.

However, for the health and safety of your site, we recommend creating regular backups of your site and database.

We’d like to clarify that the SEO data optimization only needs to be run on production sites, not on staging sites. The data optimization process indexes all your content on your website in a specific database table that our plugin uses to generate SEO data in the frontend. Running the SEO data optimization on non-production sites is not recommended as you may get mixed-up URLs in the SEO meta tags when pushing changes from staging to production. In fact, if the WP_ENVIRONMENT_TYPE constant is set to ‘staging’, the SEO data optimization function will be disabled in our plugin.

If this did not return true on your site, you can set the WP_ENVIRONMENT_TYPE constant to ‘production’ by adding the line below to the wp-config.php file.

define( 'WP_ENVIRONMENT_TYPE', 'production' );

Hey @suascat_wp,

Thanks for the information!

By the time I was able to get to it our server team had run the following tests, including that SEO data optimization, and is still not able to access the sitemap:

I’ve created a clone of the “Outdoor Command” staging site to run some further tests, but haven’t had any luck getting the post-sitemap.xml page to load. Here is a summary of the tests, while attempting to load the page after each step:

Deactivated all plugins except for wordpress-seo and switched the theme to a default WordPress theme (twentytwentyone).

Tried installing an older version of wordpress-seo (v14.8).

Completely deleted and manually installed a fresh copy of wordpress-seo 15.8.

Optimised the database via WP-CLI – as the database used InnoDB tables, it runs a “recreate and analyze” instead.

Ran Yoast’s SEO optimization.

Optimised the database using the wp-optimize plugin.

Bumped up the server memory to the maximum we can take it to (1024M).

This ultimately looks to be an issue with Yoast’s wordpress-seo plugin creating a memory leak of sorts on that page. We recommend reaching out to their support team from here! Do let us know if there’s anything else they’d like for us to try server-side to assist further ??

Given the above, are you aware of a way we can restore those sitemaps?

Thanks so much!

Thanks for your confirmation. The issue you’re currently experiencing with the post sitemap due to the server memory that is unable to handle all the requests from Yoast SEO plugin. So, you’ll need to either increase the memory limit from the server php.ini file or reduce the links per page in the sitemap from 1000 to 500 or so. You can find the relevant guides in the following:

• Increase the server memory limit;
• Change the default entries per sitemap page;

We hope this helps!

Hey @mazedulislamkhan

Thanks for the information!

We ran these tests and even when cutting down the sitemap to 50 links, we’re still seeing some of the individual sitemaps not load.

Is it possible there’s something else that would be preventing that from loading when there are so few links, or is that still going to be a memory issue?

Thanks so much!

Hi,

How many posts are you expecting to generate with the post sitemap? Also, is this a scenario where you have hundreds of posts all assigned to a single author, or is this not the case?

If you’ve already tried a fresh reinstallation of Yoast SEO for WordPress v15.8, and re-run the SEO data optimization, would it be possible for you to try and check if there is a plugin or theme conflict? You can learn more about it here — https://yoast.com/help/how-to-check-for-plugin-conflicts/

If you are still able to reproduce the issue with a default set-up and only the Yoast SEO plugin active, we would recommend logging a bug report on GitHub so our team can also take a further look at it.

Hey @mikes41720

Currently the staging site we’re working on has 586 posts.

One of our authors does have 388 posts, another has 63, then 42. But those are the largest author collections.

We’ve tested a fresh installation of Yoast with the SEO data Optimization, and have tested trimmed the site down to ONLY Yoast SEO and the default twenty seventeen theme, and that issue still exists. Even if we’re running the twenty seventeen theme with the function in place to trim it down to 50 entries per sitemap.

I’m going to log a report on Github, but if you have any other thoughts that may help here please let me know.

Thanks so much!

We are sorry to hear that you’re still experiencing the relevant issue on your end. Due to the nature of the issue, we’ll need to take a closer look at your setup. However, we are unable to do it here as this is a public forum.
So, if you have an active Yoast SEO Premium subscription or if you can consider buying one, we can investigate the issue further directly on your setup privately through email.

However, if you don’t wish to get the Yoast SEO Premium subscription, that’s completely fine. In this case, you’ll need to troubleshoot the issue further on your setup as we are literally out of any clue at this moment without taking a look at the setup. So, someone from the community might step forward as well who has experienced the issue or familiar with the parent/child breadcrumbs relationship.

Thanks for your understanding!

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Hey @mazedulislamkhan and @devnihil

Thanks so much for the information!

We’ve run some database cleanup tests and server resource increase tests per the development team at Github, and despite those tests we’re still seeing this error.

We’ve purchased a Yoast SEO premium subscription and are ready to give you / the team access to the staging site we’re working on.

Is there a way we can convert this existing thread into a ticket, or is our best path forward to relog the ticket through the site and point to this thread?

If we can convert this into a ticket please just let me know what information you need from our end.

Thanks so much!

@simonbbs Thanks for following up with us here. Since you have purchased the Yoast SEO Premium subscription now, please do feel free to send us an email directly at support@yoast.com email address with the current page link so that we can move forward with the issue further for you privately through email.

We look forward to hearing from you!