• Home
  • Get help
  • Ask a question
Last post 5 hours 58 min ago
Posts last week 247
Average response time last week 17 min
All time posts 56622
All time tickets 8814
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#8864 – Sitemap could not be read

Posted in ‘4SEO’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Sunday, 26 June 2022 01:47 UTC


I pass the side map in the google search console. sitemap.en-GB.4seo.1.xml.gz couldn't fetch. Sitemap could not be read. Please help

Monday, 27 June 2022 07:53 UTC


I pass the side map in the google search console

You don't have to, this is done automatically when the sitemap is ready.

Sitemap could not be read. Please help

Your sitemap is ready and working fine:

The most likely reason this happened is that you submitted the sitemap to Serach console before it was actually ready, and so Google faced an error. 

You should just rely on the automated submission system in 4SEO, it pings Google whenever the sitemap is ready.

In any case, before you submit anything, you should also test it in your browser to be sure it works as expected.

This error will go away in GSC as the sitemap files are working as expected (but GCS is not very quick to update actually).

Best regards

Yannick Gaultier

weeblr.com / @weeblr



Monday, 27 June 2022 23:31 UTC

ok. noted. Tq

Tuesday, 28 June 2022 07:44 UTC


You're welcome! Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.

Best regards

Yannick Gaultier

weeblr.com / @weeblr


This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.