HubDB dynamic pages last modification date incorrect on sitemap
Hello!
I'm trying to show the last update date of a HubDB row on my dynamic pages template, and I noticed we have only hs_created_at, and not modified date variable for the rows.
Then I remembered that Hubspot CMS adds the dynamic child pages automaticaly to the sitemap, but the <lastmod> date on the sitemap is the parent page last modification date, and not the row.
So with this, Google, or other services like Indexnow, will check the sitemap and 1.000 dynamic pages generated by rows in a table are showing the same modified date as the parent page.
When we update the dynamic parent page, the lastmod date on the sitemap is changed for every row page, even though they were not updated.
Couldn't this be a red flag for Google?
Is there a way to change how the sitemap shows the dates for the dynamic child pages from rows in a HubDB table?
HubDB dynamic pages last modification date incorrect on sitemap
We ran into the same issue, today. We have a site with thousands of items, with dynamic pages based on these items. We're trying to find out, how to configure the sitemap so that each entry reflects the last modified date of the corresponding item. Any documentation would be appreciated, and even a short "nope" would be better than no response at all, because at least then we can stop looking.
Microsoft Bing posted a new blog post saying "for XML sitemaps, one of the most critical tags you can include in your sitemap is the "lastmod" tag." And it will become even more critical as Bing is reworking its crawl scheduling stack to rely more on this lastmod field.
Yes, by June, the way Bing decides what to crawl will be more dependent on the lastmod tag. Fabrice Canel from Microsoft wrote, "we are revamping our crawl scheduling stack to better utilize the information provided by the "lastmod" tag in sitemaps." This is being done so it can "enhance" the "crawl efficiency by reducing unnecessary crawling of unchanged content and prioritizing recently updated content."
"We have already begun implementing these changes on a limited scale and plan to fully roll them out by June," he added.