Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I've realized that XML Sitemap generates an XML for everything just fine except the taxonomy term itself. The taxonomy term can be a page (I create this via views taxonomy_rewrite) that contains all the nodes related to it. Unfortunately, when I look at the XML I don't see last modification date and change frequency values for any of the taxonomy terms themselves.
I think this is a bug and an important one because you have to tell Google that taxonomy term pages are frequently being updated. To clarify what I wrote I am also attaching a screenshot.
Comment | File | Size | Author |
---|---|---|---|
screen-capture-10.png | 67.42 KB | xtrecoolx |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous 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 CreditAttribution: 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) CreditAttribution: Anonymous 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 CreditAttribution: Coupon Code Swap commentedbtw, a quick fix for this:
/sites/all/modules/xmlsitemap/xsl/xmlsitemap.xsl
Perhaps this could be incorporated as an option.