Problems with change frequency

Created on 22 September 2011, over 13 years ago
Updated 24 September 2024, 7 months ago

I've just updated xmlsitemap to 6.x-2.0-beta3 (from 6.x-1.something), which required completely uninstalling and reinstalling the module. And now we're running into some strange problems with the change frequency in the sitemap.

I understand that in the new version, change frequency is supposed to be calculated dynamically, based on the node modification dates and comment posting dates, as opposed to being able to be specified in the settings. But it doesn't seem to be doing it correctly in this case. This site has a fairly active discussion forum, but some posts in the forum are showing up with a change frequency of "yearly" or "never" despite receiving regular comments. The last modification dates seem to be correct (as in, date of most recent comment), but the change frequency listed in the sitemap is much lower than the actual frequency of activity in the forums.

Could this be just because the module has been freshly reinstalled? Does it have to have been running for a while to get a realistic sense of the actual change frequency? Or is this some kind of bug? I think it used to be possible to manually set the change frequency, so you could, for example, set all forums to daily.

Right now, our SEO person is reluctant to allow the sitemap to be sent to any of the engines, as it would essentially be like telling them that the forums are rarely or never updated and they shouldn't check back very often, when in fact the forums are the main feature of the site and updated quite often, so we'd really like them to be indexed regularly. Is there any way to fix this?

One thing I'd thought of was to just edit the sitemap.xml file manually for now, setting all the forums to daily, and hope that when the module later updated the file, it would be doing it on the basis of more current information. But that would depend on why it was setting them to yearly or never in the first place - there would be no point in correcting the file manually if the module was just going to overwrite it with wrong information at the first opportunity.

If anyone has any idea why this is happening or what to do about it, I'd very much appreciate it - thanks!

💬 Support request
Status

Active

Component

Code

Created by

🇨🇦Canada spidersilk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024