: Posting old content on a new website. Which date to use? I have been writing a sort of diary for quite some time (5 years) that I store locally on my computer. Now I have decided to make
I have been writing a sort of diary for quite some time (5 years) that I store locally on my computer. Now I have decided to make some if this content publicly available in the shape of a WordPress blog since I believe it can be useful for a particular niche.
My dilemma is the following; should I publish this content with the date it was created (let’s say 2012) or with the date it’s going to be published (let’s say today)?
My main concern is how this decision might affect the SEO of my new site. I wonder how Google with interpret a post dated in 2012 sitting on a site which was just launched in 2015. On the other hand it makes sense to use the creation date since some of this content might be slightly outdated and it can be useful for the reader to have that date for context.
Any solid arguments for or against using old creation dates on a newly launched site?
More posts by @Odierno851
3 Comments
Sorted by latest first Latest Oldest Best
You could provide both dates.
To make the difference machine-readable, you could use these Schema.org properties (e.g., for a BlogPosting):
dateCreated
The date on which the CreativeWork was created.
datePublished
Date of first broadcast/publication.
And, if you prefer, also:
dateModified
The date on which the CreativeWork was most recently modified.
There is some chatter that Google picks up some post dates and may display that. I to do not know this for a fact. From what I know about Google, it does not fit the schema and methodology which does not mean it does not happen. Unless someone can show me a good case that cements the notion in my mind, I am not buying it- at least for now. So far, it has been totally anecdotal or a claim from an SEO and we know these guy are never wrong... (sarcasm).
This is what I do know.
When Google finds a page that date/time is the inception (in lieu of a creation date) date. Google stores the source code along with the last access date, a period of time when the page should be submitted to the fetch queue, and a checksum number which is an algorithm that represents the source code with a unique number. When the page is fetched again, a new checksum is generated against the content. If the checksum changes, the source code is saved, the last access date is updated, and the last modified date is saved. These are the dates that Google uses in the SERPs. The reason for the inception date and modification dates is because the response header only returns a modified date that can be taken from a file modification date or machine generated from an application. Since the modifications date cannot always be trusted, this date is not relied upon.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.