Facebook kills post scheduling without warning – Another reason you must move faster!

Estimated read time: 2 minutes


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 68,861 other subscribers



I’ve been auto scheduling posts to my Facebook profile via Hootsuite for a few weeks. It seemed to help with my communications and business goals.

Positives:

    That spread posts out some.
    It kept my updates moving along.

Then on Aug. 1, 2018, Facebook killed all third-party scheduling. More from Hootsuite here. A fellow content marketer told me about this maybe two days ago, but two days isn’t much of a warning either.

Social media purists and people who can’t get social media to work for business will say this is good.

But it’s not. It helped from a business perspective. I stayed top of mind, it was easy, etc.

Facebook is recommending that you can just use a page for updates and that scheduling apparently still works, but with the ongoing Facebook monetization algorithm updates Facebook page posts aren’t seen by many – unless you pay Facebook for a wider distribution.

Check out what ads your competitors are running here.

LinkedIn and Twitter still allow third-party scheduling. Thank you.

This is also a reminder that if you think you have the luxury of time to implement – you don’t!

I was sharing this tactic with somebody as recently as four weeks ago. They were going to think about how to add it into their strategy. If they didn’t start it’s now a moot point. Facebook killed it. Implementation probably needs to run parallel to planning.

I’ve said before that Facebook is a waste of time for content publishers but this was a bright spot.

Now, it’s gone and we need to look for the next wave to ride.

Express Writers and Buzzsumo named Christoph Trappe as the No. 21 top content marketers globally! Need help? Fill out the form below to contact him directly.

Need help with your digital marketing strategy? Fill out the form below and I’ll help: