Active
Project:
XML sitemap
Version:
7.x-2.0-rc1
Component:
xmlsitemap.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Nov 2012 at 10:29 UTC
Updated:
29 Nov 2012 at 16:02 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedhttp://www.sitemaps.org/protocol.html
The "modification date" and "change frequency" are only suggestions and not required. However, a "changefreq" of "always" for this entity would be good since that is the most likely scenario for taxonomy. And since the "changefreq" is always a "lastmod" of the time of page generation would also be good even though that may be a lie. To stop the lie would require a DB hit for each tag, I don't think that is wise for this.
Comment #2
xtrecoolx commentedSo based on your suggestion, can we assume that Google and other search engines do not care about these values and there is no need to worry about? If so, then why do we have nodes with frequency values?
Comment #3
Anonymous (not verified) commentedRight, the search engines shouldn't care, although Google may be a bit picky with the Webmaster Tools reports.
Because the change date of a node is given in the node object when we are given it we can add it easily for the node entity.
Comment #4
Coupon Code Swap commentedbtw, a quick fix for this:
/sites/all/modules/xmlsitemap/xsl/xmlsitemap.xsl
Perhaps this could be incorporated as an option.