BUGS with the sitemap, please fix them
-
Hi developer team of AIOSEOP, I discovered a few fundamental problems with your sitemap. Anyone who uses the sitemap as is currently and has a larger blog with thousands of posts and uses sitemap split, is going to have serious problems with Google.
1 – Newest posts are always written in the first sitemap. For example, when sitemap is split in 5 chunks, 1000 posts per split, in sitemap5.xml 1000 in 4 1000, 3 1000, 2 1000, Sitemap1 will have the newest posts but when that fills up with 1000, sitemap1 will change name into sitemap 2, 2 will change name into 3, 4 into 5 and so on. This is a very bad practice which according to Google themselves causes deindexing:
https://www.seroundtable.com/google-dynamic-sitemap-file-names-25187.html
Please fix this. YOAST SEO has figured it out, its the only sitemap out there which has the oldest 1000 posts in sitemap1 and gradually the newest posts in the last sitemap, lets say 5. After 5 is full with 1000 newest posts, that will remain the same, unchanged, FOREVER, and sitemap6 will be created and filled with the newest posts. This is the most intelligent way a sitemap should behave.In short, please put the newest posts at the bottom and the oldest on top or simply just give an option in the settings and let users choose the order.
2 – Even though you give the option to choose the split number, if I choose 2000 per split instead of default 1000, I am haunted by a pop-up message showing up everywhere annoying me to set it to 1000 because this is how its recommended! There is a little X but if I close the popup and simply navigate to a another page, it will show up again and again and again. There is no way to permanently disable this annoying notification to force me to have 1000 posts per split.
3 – Please also add instant PING notification when I publish or edit a post instead of just Schedule Updates: Daily, Weekly, Monthly.
4 – Images included in the sitemap are only the ones uploaded on my host but external images such as the ones hosted on photobucket or tinypic aren’t included. This is the most easiest thing to fix, just make the sitemap include all .jpg, .png .gif .bmp extensions found inside a post.
Please take my advises into consideration. At first problem is severe the others are moderate to low.
-
@justatest47 For some reason notifications on this site aren’t working for me anymore, so I’m only just now seeing your reply.
Also, it’s rather difficult to try and follow a discussion in multiple places, which is why I encourage this to be moved to Github.For point 3, you’ve only read the first comment by me. After I investigated the code, I determined that it only happens on publishing of new posts for static sitemaps, and not at all for dynamic. We’ll change that in a future update.
For point 4, you can find documentation on the filter hook here: https://semperplugins.com/documentation/support-external-images-in-the-xml-sitemap/
However, you’re welcome to make a case (in the Github issue preferably) that externally hosted images should be included by default. This is an open source project, and as they say, “decisions are made by those who show up.” 😉For the notification that won’t go away, we’re unable to reproduce that at all, and unfortunately we can’t fix what we can’t reproduce. This appears to be an issue specific to your site’s environment, whether a server issue or a plugin/theme conflict.
You can contact us directly here if you’d like us to investigate your site to determine the problem and come up with a fix. https://semperplugins.com/contact/ Copy/paste this forum thread’s URL where it asks for a license key.——
Please, for the benefit of users, developers, etc who are following along, let’s stay on Github for these issues. 🙂
I’ve marked this thread as resolved.
- The topic ‘BUGS with the sitemap, please fix them’ is closed to new replies.
