Support » Plugin: All in One SEO Pack » Version 2.4 Broke My Sitemap

  • Resolved Nick M.



    I also installed today’s 2.4 update, and upon doing so my sitemap no longer loads too. When I click to view my sitemap, it says:

    “XML Parsing Error: no root element found
    Line Number 1, Column 1:”

    I’ve deleted cache and also tried resetting my sitemap’s settings to the defaults without any results. When I tried to check my sitemap via Google Search Console I also recieved an error. It says:

    “We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit… Network unreachable: HTTP Error: 500”

    Thank you,

    The page I need help with: [log in to see the link]

Viewing 5 replies - 16 through 20 (of 20 total)
  • Hi Michael,

    Thanks for your prompt feedback. PHP Memory Limit was already set to 256M.
    The sitemap contains only 5000 URLs. How can I find the right number per index?
    Would “Memory usage 56.34 MByte” (from AIOSEOP’s Performance Module) help here, or just trial and error?

    Michael Torbert


    WordPress Virtuoso

    Try 1000 URLs per page.

    I can confirm that aforementioned steps solved my problem with latest update. Now, Google indexes my sitemap much better than with previous version (and settings) on AIOSEO plugin – the XML Sitemap module. I would just like to say a big thank you to you and your team, Michael, for the prompt and efficient service.

    Michael Torbert


    WordPress Virtuoso

    Hi @nick-m

    Thank you for the kind words. Despite the glitches in this version with some installs (these issues don’t affect most), we’re pretty pleased overall.
    I appreciate your patience as we work through the issues to continue to improve the plugin.

    Michael Torbert


    WordPress Virtuoso

    Version 2.4.1 has been released and and should fix the sitemap issues.

    There are two possible issues that some sites had with 2.4:

    1) Running out of memory. If you had this issue, you’d know it because your sitemap would be blank. We now recommend using the Sitemap Index option and setting your Posts per Sitemap Page option to 1000 instead of 50,000.

    2) Parsing error in Google Search Console. This was due to some sites with code that used fake images (Amazon affiliate link code was a common one, but it could be different for everyone). This code fooled AIOSEOP into thinking it was an image, which got included in the sitemap, which caused a parsing error. This is now fixed.

    *Note: any temporary glitch in your sitemap would have no negative effect on your SEO.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Version 2.4 Broke My Sitemap’ is closed to new replies.