Wayback Submit

You are, of course, publishing your new articles to your own website.
But you could, by checking a box, make sure that the page was submitted right there and now and that the scraper form archive.org came around and grabbed your new content.

• You'll immediately have a permanent, secure offline history of your site's content.
• Archive.org will back you up, when you say you were the first outlet to break the story.
• Archive.org will be up to date with your site.
• You yourself, researchers and developers will have a quick, permanent link to the original story rendered in the original theme. That is useful every once in a while.

Setup

1. Install the module.
2. Grant permissions at People > Permissions.
3. Configure it at Configuration > Content > Wayback Submit.

Configuration
By default the Wayback Submit will submit all content types on schedule, meaning that a number will be submitted on cron with a predetermined interval set to 30 days.
But you can select settings for individual content types and fiddle with the time between submissions.
The options for the individual node type are

• Never
• On submit
• On submit, then on schedule
• On schedule

Daily use
Whenever someone publishes a new article it'll get submitted to Archive-org as dictated in the configuration.
You can, however, make sure the individual node is either submitted immediately to Archive.org or excluded from Archive.org using radio buttons in the vertical menu at the bottom of the node/edit-form.

Dependencies
Cron should be running if you use the scheduled submission. And, do not forget, the article should be published.

Related modules
Wayback Filter is a text filter that'll add a Wayback link to your old and possibly broken links in old articles.