Hi John!
I'm having some trouble with sitemap.xml generation. Jsitemp is showing bad <lastmod> entries with wrong date : mass of content with current date only!
JSitemap seems to generate a <lastmode> for each article without having a "Modified Date" field...
and I'm using ObRSS with now more than 7000 articles (with automatic creation) where Modified Date field is not generated...
So as a result, JSitemap is parsing articles and generating a bad sitemap with a huge number of <lastmode> for old articles (ObRSS)
Bots are then not able to identify new real legitimate articles with correct <lastmode> VS those without modified data, with a <lastmode> throwing the current time....
I've searched but ObRSS is not giving chance to create/force this "Modified Date"....
All hand written articles are correctly parsed by Jsitemap, with correct lastmod date.
My SEO is not progressing and indexation is not going so well maybe it's coming from this <lastmod> consideration. (lots of page, bad lastmod...)
I don't want to disable <lastmode> as it's efficient for bots for new content, but want to correct this f***g problem!
My sitemap:
https://www.akaoma.com/index.php?option=com_jmap&view=sitemap&format=xml&lang=fr
Any idea John??!! How to solve???
Thanks again for your expertise!
Chris
PS:The problem is not coming from your latest 4.2 release as it was same before, but I didn't catch this clearly before...
Here is a sample:
<url>
<loc>
https://www.akaoma.com/ressources/cve/bypass-something/7735-cve-2016-1461
</loc>
<lastmod>2016-08-05T14:12:38Z</lastmod>
<changefreq>daily</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>
https://www.akaoma.com/ressources/cve/bypass-something/7755-cve-2016-5668
</loc>
<lastmod>2016-08-05T14:12:38Z</lastmod>
<changefreq>daily</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>
https://www.akaoma.com/ressources/cve/bypass-something/7756-cve-2016-5667
</loc>
<lastmod>2016-08-05T14:12:38Z</lastmod>
<changefreq>daily</changefreq>
<priority>0.5</priority>
</url>