It is recommended to create evergreen content in view of the fact that we rarely have to update it and it can be kept posted for long. So it reduces our work to update the published content. Even in cases we need to do some changes in it, these changes are very limited in nature. So in case of evergreen content too, we need to continue making updates to keep up with the requirements.
What needs to be done to manage content and keep it updated?
We should implement a process through which we can put a periodical content audit in place so as to evaluate what needs to be kept and what is to be removed. We can choose the frequency of audit according to our convenience and requirements. So seasonal content has to be updated frequently in order to keep your content relevant and informative and the content which is already published needs to be scheduled to be published on some future date. In the database settings there are fields, which will not allow the flagged content, scheduled for publishing on a future date to retweet, if you edit it for some reason. So you have to change the settings and over-ride the field in case you want it to be re-tweeted even in case of making some changes to it.
We also have to change our SEO habits of ‘batch mode’ publishing, as this will allow the customers and regular readers to be distracted. As in ‘batch mode’ we can publish a string of previously published files, to be published with minor updating. The good practice is to add one or two such previous files with regular new articles to be published. However there are different types of customer groups:
In this respect, we have to take extra precaution for the people who are mindful of your previous posts and may detect a rerun of articles with minor or no changes, whereas, this practice can still work for the people, who are not regular to your posts. Re-tweeting, however is still effective for such mass market and still has the potential to reach the not so regular people.
So we can summarize it as follows:
Leave a Reply