devnihil

@dominicken We’re sorry to hear you are experiencing this issue on your site.

Based on the video you provided, you are encountering an error showing Something went wrong, please reload the page.

Checking for conflict on your site would be the next step to troubleshooting the issue. Please follow the steps below to complete the conflict check process:

Please test this on your development or staging site. This will act as a safety net for your site if anything to go wrong on your site. Some popular web hosts offer quick setups for a staging site, so please contact your web host for assistance. They will probably be able to help you out. If your web host does not offer staging sites, the WordPress plugin repository offers staging plugins or you can create your own staging site.

If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process. You can have a look at this help article on How to check for plugin conflicts.

Can you please try the aforementioned suggestions and let us know whether this resolves your issue?

@sa5awii92

Regarding the sitemap, we checked on the sitemap URL at https://www.dealinsi.com/sitemap_index.xml and do see it is appearing as blank. However, upon inspecting the source code of the page (see image here) we do see that all of the sitemap’s data is being generated correctly, so whereas the sitemap appears blank when you visit the page, this will not affect Google or any other search engine’s ability to read the sitemap data.

As for resolving the sitemap appearing blank, a blank sitemap is typically an issue with the stylesheet, a static file or a conflict in your setup. Please check the following:

• Check whether the source code of the sitemap shows you the data you would expect in an XML sitemap. If you’re not sure how to see the source code, follow the steps in this article: https://yoast.com/help/view-page-source-site/
• If you have a cache plugin or server side cache, please flush the cache. If the issue remains, please disable and re-enable the sitemap feature (steps here: https://yoast.com/help/xml-sitemaps-in-the-wordpress-seo-plugin/) to force a cache reset. If you are not sure how to clear caching from theme/plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider. To clear the cache from a browser use this guide: https://yoast.com/help/how-to-clear-my-browsers-cache/
• Our plugins create sitemaps on the fly. Using FTP or a file manager, please ensure there is not a physical file called sitemap_index.xml at the root of your WordPress installation. If there is, please rename or remove the static file.
• Check that the XSL file, linked in the very top of the XML file, is available. Sometimes this file gets blocked by .htaccess prevention of the wp-content directory. Learn more here about the Sitemap Stylesheet: https://yoast.com/help/my-sitemap-is-blank-what-s-wrong/#stylesheet
• Open the sitemap and the sitemap stylesheet in Firefox to see if any errors display. If an error displays, please read this article about common sitemap errors: https://yoast.com/help/xml-sitemap-errors/
• Yoast SEO uses the WordPress site URLs to generate the sitemap. In rare cases, these URLs may not match the preferred URL format of your site. Go to Admin > Settings > General and make sure the correct Site Address and WordPress address match the sitemap URL you are trying to view.

@p8dev We’re sorry to hear you are experiencing this issue with being unable to save the meta description on your site.

Regarding your issue, can you please confirm you are using the most recent version of Yoast SEO, version 19.14? You can learn more about updating here: https://yoast.com/help/how-can-i-update-my-free-plugin/

Also, can you confirm you are using WordPress 6.1.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/

If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?

If you have already confirmed that both Yoast SEO and WordPress are up to date and the issue is still occurring, we would next recommend performing a conflict check to determine whether another plugin or theme is interfering with the Yoast plugin.

The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like TwentyTwentyOne.

Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.

If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.

@dbase66 Please let us know what the results are once you’ve had time to test the issue.

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.