I did an import for a site that’s running
This makes Google users made because they say “Yay! a post from September 2020 with my exact problem!” and then they get to the site to find it’s actually from January of 2015.
Is this a feature or a bug?
Is there a way to make it so that the post date presented in the search-engine view has the actual date of the post rather than the import date?
Presuming that I could “fix” the date presented to Google, is there a way to have them re-index the site with the correct dates or is the damage simply done?
Edit: I see this in the meta tags:
<span class="crawler-post-infos"> <meta itemprop='datePublished' content='2015-01-11T03:19:59Z'> <time itemprop='dateModified' datetime='2020-09-09T20:05:21Z' class='post-time'> September 9, 2020, 8:05pm </time> <span itemprop='position'>#1</span> </span>
So I suppose I could do a replace to set
created_at for all posts before the migration. But, would it help?
And the site is on a subfolder, and their sitemap points to an out of date sitemap. If they were to install the sitemap plugin and update their sitemap to include a stanza pointing to /subfolder/sitemap.xml, would that help?