@ayanishevskiy
We checked your sitemap at https://www.virtuozzo.com/page-sitemap.xml and do see the page is generating an error of ‘XML parsing error’.
The ‘XML parsing error’ is most often caused when another plugin or theme adds code or white space to the beginning of the sitemap file. You can view the source code of the page-sitemap.xml document in order to confirm this.
We have information on how to resolve this error at: https://kb.yoast.com/kb/xml-sitemap-error/.
Also, this issue can sometimes be caused by an empty line at the end of your theme’s functions.php file. If there is no empty line in this file, we highly recommend running a conflict check to identify what outputs the empty white space.
I found the issue.
There are some orphaned pages in my site.
When I remove it, sitemap shows right structure.
But i need pages which yoast marked as orphaned.
What i need to do to fix it and save my pages?
Hi @ayanishevskiy
The orphaned pages shouldn’t affect how the sitemap outputs. Upon checking your page sitemap again (https://www.virtuozzo.com/page-sitemap.xml), it appears blank.
We checked and the page source is loading, and the stylesheet is loading also, so you may want to check if it’s an issue with cache, invalid XML code, or mismatched URLs. You can learn more about it here – https://yoast.com/help/my-sitemap-is-blank-what-s-wrong/#blank
I tested this functionality on dev environment and sitemap shows correct info.
I removed one specific page and sitemap was been restored.
Can’t give the link, but i’m sure that page crushes my sitemap.
Maybe, you know what is wrong?
Hi,
We’d need to investigate further in order to pinpoint if that specific page is what is causing the page sitemap not to load, but we are unable to do so over these public forums.
You may want to consider Yoast SEO Premium so we can provide you with personal premium support. The most likely cause is due to one of the usual reasons or causes mentioned in this article regarding a blank sitemap. Otherwise, we’ll be leaving this forum thread open for a few days to see if any other users would have suggestions or advice on this issue.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
