Value "last update" in xml sitemap is not correct
In generated xml sitemap for every page a value "last updated" exists. This value seems to be the date where the page was indexed for the last time.
But Google expects the date of the last change of the page instead. Google wants to know, which pages need to be crawled again, because their content has changed.
Right now, Google gets the message, that the content of every page has changed, so Goolge has to re-crawl all pages every time.
So: is there a possibility to take the date a page was really changed for the last time?
Updated by Christian Clemens about 7 years ago
- The value "last updated" of a page is refreshed quasi every day = every time the page is viewed in frontend (and so indexed again)
- There is a scheduler task "Sitemap garbage collection" which deletes all pages of the xml sitemap which has not been re-indexed for the last 60 days.
- This task needs the currently used information saved in "last updated" to work correctly.
- So we need 2 database fields: "last indexed" - which is needed for the scheduler task - and "last updated" - which is needed for the xml sitemap.
Updated by Markus Blaschke about 7 years ago
- Category set to Sitemap
- Status changed from New to Needs Feedback
I could query the last change timestamp from the page. But if you have some sort of eg. product database plugin on this page this isn't possible because the content elements are not chaning but the content of the page will change from time to time.
Maybe i can check if there is a plugin included on the page. I will check this possiblity but also you could use flexible content elements of include your plugins with SetupTS so this check could be very complicated.
Updated by Thomas Mayer over 6 years ago
maybe related: https://github.com/mblaschke/TYPO3-metaseo/issues/67
Updated by Thomas Mayer over 4 years ago
Latest news on this is that you can optionally disable the tag now (since metaseo 2.0.4+): https://github.com/mblaschke/TYPO3-metaseo/issues/363