Skip to main content

Include a date on your blog posts

Posted

Aside from the article itself, the most important thing to include on every blog post is the date it was published.

A date goes without saying for blogs that feature diary style posts, where each post is bound to a particular moment in time, but I see a lot of blogs that don’t have a date stamp.

Blogs can contain all sorts of content, so I suppose those that include evergreen advice, for example Zen Habits, can get away with it, but in the web and software development industry things move so fast that advice can go out of date very quickly.

If I’m searching the web and come across a blog post with what looks like the answer I was looking for, but doesn’t have a date, I question its reliability; what if:

With a date, the visitor has the reassurance that the feature, code or technique they’re researching is brand new, or if it’s, say, five years old, some more digging may be worthwhile to ensure it’s still the relevant.

Subscribe

I send a newsletter on the last day of every month, containing:

  • A roundup of the articles I’ve posted
  • A hot pick from my archives
  • Some interesting posts from around the web

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that’s not enough, have a look at the full list.

  1. If you need a link, don’t use a button

    Links sometimes need to look like buttons, but what about the other way round? Spoiler alert: it’s a terrible idea!

  2. Overlapping interactive areas

    When an interactive element like a button, link, and form field sits on top of another interactive element, accessibility (and usability) problems arise.