sitemap_index.xml couldn’t be crawled

  • Resolved Claudio P.

    (@claudiop58)


    3 years, 3 months ago

    Dear Yoast-Team,
    I use Yoast SEO standard version (not Premium). The option to generate the sitemap is activated since months, and everything was ok until now. I have an automatic site check by Semrush, running automatically every month. The last time it run, yesterday, it told me that

    https://www.valeriabovina.com/sitemap_index.xml

    couldn’t be crawled! (see screenshot)

    https://abload.de/image.php?img=bildschirmfoto2021-08tbjey.png

    Now, I submitted the page to Google Search Console months ago, when I first started the site, and never changed anything. The “sitemap” Menu option of Google search console says the last time crawled was August, 4th, 2021, everything ok.

    If I just type in the browser the sitemap address, it seems to be perfectly ok!

    So my question is: have Yoast in a recent update (I do have automatic updates of plugin ON) changed some naming conventions or the like?

    I never cared about the sitemap, my understanding is that, once submitted, it is automatically maintained by Yoast SEO, is that correct?

    Thanks a lot for your help, appreciate a lot!
    Regards
    Claudio

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support devnihil

    (@devnihil)

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

    The source code for the sitemap is empty. This typically means your site has a static file on the server or there’s a conflict with a plugin or theme. Please remove any static sitemap files as Yoast SEO does not create a physical file on your server. If you do not find any static sitemap files, this may be a plugin or theme conflict. Please disable all plugins except Yoast SEO, and use one of the default (Twenty*) themes. If the problem goes away, enable plugins one by one to identify the source of your troubles. If you can install plugins, the Health Check & Troubleshooting plugin offers a troubleshooting mode that will disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site. Once in the troubleshooting mode, please activate only Yoast SEO and attempt to reproduce the issue you described. If you are 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

    Thread Starter Claudio P.

    (@claudiop58)

    Hi devnhil,

    thanks a lot for the quick answer.

    I certainly did not create anything on the server, first because I only use WordPress and I do not know how to access or create files on the server, secondly because I did absolutely nothing on the site since at least one month (but I do have all automatic plugin updates activated).

    I have noticed a strange behaviour, before I begin to disable the plugins:
    this is the error message that I receive if I am logged out of the WordPress dashboard, if I try to access the page (I have a german language Safari browser)

    https://monosnap.com/file/bKr0aLw88lhQ4B3qKS1FadfNmJqrY9

    If I log-in to my WordPress Site Dashboard, now this is what I see:

    https://monosnap.com/file/yHYAC6vJuPGo30VRExp8t321J0gJAg

    Does this make sense to you? it seems Yoast SEO does create the file only if I am logged in to WordPress!

    I will now try to disable the plugins manually (though I can install plugins, I still prefer to try the manual way, i.e. not via Health-Check-Plugin).

    Thanks a lot
    Regards
    Claudio

    Thread Starter Claudio P.

    (@claudiop58)

    I think I have found it.

    It was “WP Super Cache“!!!

    I now tried two times and it seems that the error comes if I
    1) activate WP Super Cache
    2) go in the settings (as required) and activate the Cache.

    I will delete the Plugin and see what happens.

    Greetings and thanks really a lot for your help
    Claudio

    • This reply was modified 3 years, 3 months ago by Claudio P..
    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    We’re glad to hear that you were able to find the solution and that the sitemap is now loading as expected.

    This thread has been marked as resolved as the original poster confirmed the issue as resolved on their site.

    If you are not the original poster and continue to experience a similar issue, please open a new request. That way it’s easier for us to match replies with a specific problem. Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘sitemap_index.xml couldn’t be crawled’ is closed to new replies.