Good list! If only more news organizations followed this checklist. :)
Here are my additional tweaks.
6. If by "keywords" you mean <meta name="keywords"> I'd skip this to save time, as the search engines haven't used this tag in forever (if you're a Google News-indexed source then I'd encode the news_keywords tag, which is
used by Google news).
6a. Create optimized descriptions. Of course, this should be a part of "optimize it," but from a quick spot check I see TMB descriptions are either too long or fragmented (i.e. truncated mid-sentence). This is fairly important, IMO, because your descriptions are
reproduced on Facebook (meta ... og:description), for Twitter Cards (meta ... twitter:description) and (conditionally) in search results (meta ... description) - and a complete, well-crafted description that summarizes the article will always result in a higher click-through rate than when a description if absent, programmatically produced or poorly written. The maximum length supported by Google of around 156 characters (or less if a date is present) works well for most other description manifestations. See:http://www.seomofo.com/snippet-optimizer.html
To be really thorough, for 12-14 I'd add the pre-step for each "add campaign parameters" so that in Google Analytics you'd be able to see the source of clicks from each of those networks (as often as not the referring domain itself is lost), but that's a bonus implementation. :)
8a. Check that links resolve correctly
9a. Check that links resolve correctly
While (8a) may be covered under 8, just highlighting this as I don't know what's entailed by "check it." But (9a) a definite additional step, as links in a live environment may differ from links in a live environment.
11b (i.e. before
12 - "tweet it"). Shorten it. An unshortened URL in a link in a tweet is a tragic waste of characters and an assault on readability - plus there's meaningful metrics to be had if a link is shortened with an API connected to a service like bit.ly
(some TMB authors
are doing this, but it's arguably more important to do this at the site level, but you're not: if I may be so bold as to suggest you read this - http://bit.ly/LE91bz