Are you #excited about Facebook hashtags?

Posted by on June 12, 2013

Aren’t you #excited! Facebook officially, (finally) rolls out hashtag support today. Coming from my past life as solely a social media account manager and specialist, it would pain me to see “friends” using hashtags in Facebook posts. I tried to fight the good fight by reminding them that hashtags are meant for Twitter and G+. It proved to be a losing battle as people posted diatribes or random status updates and finished them off with a #.

Confession: I must admit I have used a # a time or two or three on Facebook for what I call emphasis.

So here we are, the day Zucky and Facebook make it okay to # away! This feature allows for users of the book to search for and click on words preceded by the # symbol. The main difference between the Twitter # and the Facebook # functionality is that the search results in Facebook will be limited to only reflect public posts as well as posts made by a user’s friends. Something else to note: Facebook states that while hashtags have been enabled for some users, it’ll take a few weeks before everyone can interact with them. Facebook posted a blog describing the new feature and eluded to more “features” that will be rolling out soon.

Are you #happy Facebook added hashtags? Sound off in the comments below!


  1. I’m indifferent towards Facebook adopting hashtags. In one sense, it creates uniformity between social media platforms. This is especially handy when using HootSuite or if you have your Twitter and Facebook push out the same content for both sites. In the other sense, there seems to be a trend of “over-hashtagging” that’s only going to clog up Facebook.

    Looks like I’m on the fence about it!

  2. I’ve always been irritated with Facebook “hashtag violators” so I’m excited for this change. It will be interesting to see how this affects search, especially with Facebook’s privacy settings.

    Agree with Bailey as far as uniformity across social platforms!

Leave a Reply

Your email address will not be published. Required fields are marked *