Now Reading
Do You Use Password Protected Posts?

Do You Use Password Protected Posts?

One of the features of WordPress that I find interesting, but not use often, is post-level password protection. This feature basically locks any single post with a password defined for just that post alone. It’s easily accessible from the post settings sidebar on the WordPress write post page. Just key in any word, phrase, or set of characters, and you’re all set. Your blog readers would see a message asking for a password, instead of the body of your blog post itself.

This post is password protected. To view it please enter your password below:

Once the reader enters the correct password, he/she can now view the post in its entirety. If other password-protected posts also share the same password, then these are automatically made available for reading, too.

If your intent is to limit access to the contents of an entire site or collection of information online, then there are other software and web applications that can do the job better. For one, if you really want to secure content on a bigger scale, then perhaps you should try HTTP directory protection, so accessing your site itself, or a subdomain/subfolder would require a password. Or if it’s for business or work, you can sign up for a collaboration site, which only those with accounts can access. Even Google Docs lets you limit sharing of information or documents to a select number of people.

However, WordPress’ password protection can be useful if your site is generally open to the public (and search engines), but with a few, select items that contain sensitive or private information. For instance, you’re using your blog as a personal journal and want to share certain posts with close friends only. Or perhaps you’re a developer and using your blog to update the public on the status on your work, and some posts are for colleagues’ eyes only. The possibilities are endless.

But the really interesting aspect of password-protected posts is the way you have something supposedly secret, but still tell the world about it (but not the content itself). Here’s how Jayvee Fernandez puts it (yes, the post is password-protected, but you can perhaps guess the password easily).

The effect is brain wrecking for most. What could that post be about? Why keep it secret? Why post it in public? It’s the online tease, ladies and gents.

How often do you use private posts, and to whom do you give access to? Won’t emailing a small group of friends achieve the same effect rather than telling the whole world that “hey I have a secret and its only between these guys?”

See Also
ada and wcag compliance

There are developers that have explored the concept of recastable blogging. This means a generic user from the public will see different content from someone who is logged into the system, and is identified as a friend of the blogger. This way, the generic user will not have an idea that some content is not accessible to him. There is no teaser. There are no brain wrecking moments (and perhaps no brute-force password attempts).

But as with Jayvee’s point, protected blog posts might serve to enhance reader interest. If a post is protected, then there must be something important, at least from the perspective of the author. And this might attract attention, say, from readers who usually just scan post titles and summaries using feed readers.

Do you use password-protected posts? And if so, what creative ways are you using this feature for?

View Comments (3)
  • I use them for just the purpose you mention. I have a “personal journal” type blog and occasionally have something more private that I just want people close to me to see. To avoid the “tease” factor I stick it in a month that was before the one in which I started blogging. So if I started blogging in April of ’04, I date the post in March of ’04. I then send out a group e-mail that alerts those people on my “friends” list that there’s a private post and what the password is. They know where to look for it. Yes, others see the a new month on my archive list but very few seem to care about anything but the present and immediate past so they don’t notice it.

    What I’d really like to see is the comments not show up in my comments feed. Although they’re marked password-protected and don’t show content, it’s just another tease for people, plus they now get to see who exactly is allowed to see the post while they are not. I’m not sure if it’s a function of the date (the post being dated to several years ago, the comments being new) but I find it frustrating.

  • But as with Jayvee’s point, protected blog posts might serve to enhance reader interest.

    But they might also annoy readers, simply because, well, we all don’t like to be sidelined, no? “So if the author didn’t send me the password for this protected post, fine, I shall not drop by anymore.”

    LOL. There are just 2 sides to a coin :)

    As for myself, I password-protected all published posts because my Supervisor insisted that I don’ blog about them. But since I refused to delete posts that I had put in so much time, research and effort into, I password-protect them instead.

Scroll To Top