Everyday we read about problems and opinions on how to solve these problems. If you ask Nigerians if they will like to serve as a politician to solve Nigerians people problems, 99 percent will say Yes. But if you are not currently spending time seeking and resolving the issues in your own locality what makes you think when you enter office, WordPress, as one of the most popular blogging platforms in the world, offers the ability for users to change the date on their posts, both before and after they have been published. This is a useful tool. You can set a post to appear in the future, scheduling your content drops. You can write and upload a dozen posts all at once, and set them to appear at set, reasonable intervals.
That’s all about future dating, though. What about backdating? What about changing the date on a current post to make it look older? Post scheduling is a valuable tool, but post backdating seems to offer very little potential reward. How can it be used, legitimately and illegitimately, and what is Google’s opinion on the practice?
Maintaining Post Dates for Site Moves
Sometimes, you have no choice but to make a drastic site move. You may have an archive of data, but the post dates are somehow lost in the translation. You have to manually upload your posts again, and the problem is, every post is now dated with the time you uploaded the replacement post. The original post dates are lost.
This is a legitimate instance where you may want to use post backdating. You can manually compare every post on your site with the date it was originally posted, assuming you have access to that information. You can then edit the post date to maintain consistency from one site to another.
Of course, these days a site migration generally includes post dates, unless you’re doing a drastic move from one blogging platform to another and your only backup doesn’t work with the new software. It’s very rare that you have to manually repost any content, unless you’re performing the migration incorrectly in some w
That’s all about future dating, though. What about backdating? What about changing the date on a current post to make it look older? Post scheduling is a valuable tool, but post backdating seems to offer very little potential reward. How can it be used, legitimately and illegitimately, and what is Google’s opinion on the practice?
Maintaining Post Dates for Site Moves
Sometimes, you have no choice but to make a drastic site move. You may have an archive of data, but the post dates are somehow lost in the translation. You have to manually upload your posts again, and the problem is, every post is now dated with the time you uploaded the replacement post. The original post dates are lost.
This is a legitimate instance where you may want to use post backdating. You can manually compare every post on your site with the date it was originally posted, assuming you have access to that information. You can then edit the post date to maintain consistency from one site to another.
Of course, these days a site migration generally includes post dates, unless you’re doing a drastic move from one blogging platform to another and your only backup doesn’t work with the new software. It’s very rare that you have to manually repost any content, unless you’re performing the migration incorrectly in some w
Post a Comment