Thanks for taking the time to reply : )
“This is expected, yes, as a post cannot have views from before it “existed” – putting that in quotes, because technically the post did exist previously, but in a strict sense that post only exists from the moment set as the publication date in the post meta. Any data about the post that predates that moment, “can’t exist” if you approach it purely logically (which is how computers think), so Jetpack ignores it.”
“which is how computers think” ?? LOL
?? Logically the developers could just add a URL match that combines stats. They’re all still stored in the database.
—
“That does not refer just to your publication date, and simply updating a publication date without actually modifying any content won’t make Google think the post has been updated – it actually compares the current version of your post to the last version it crawled, to see if it has changed.”
Not sure what you’re referring to here? I didn’t mention not updating a post fully? and just changing the dates…
—
“So if you make an actual update to the post, it’s better to add a note with a new timestamp to the post,”
Sure, in some situations.
But in others,(*I think) it’s better to actually change the publication date. A best of 2020 article, labelled with a publish date of 2017, updated in 2020… why? when all the content is new?
Creating a new URL each year, would mean that you’d lose the benefit of the page rank built over many years.
And the CTR benefit of a new publish date on regularly updated content is huge.
—
So, we’ve established this is default jetpack Stats behavior : )
—
I think it would be useful for people to have the option of updating the publication date without losing all Jetpack Stats Access prior to that date. Maybe a request for the devs?
Guess, I’m gonna have to stick with GA for now. ??