Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /srv/users/sandra/apps/sandra/public/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /srv/users/sandra/apps/sandra/public/wp-includes/functions.php:6114) in /srv/users/sandra/apps/sandra/public/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":10836,"date":"2018-05-23T08:00:57","date_gmt":"2018-05-23T12:00:57","guid":{"rendered":"https:\/\/buildbookbuzz.com\/?p=10836"},"modified":"2023-12-07T21:36:10","modified_gmt":"2023-12-07T21:36:10","slug":"book-launch-mistakes-on-social-media","status":"publish","type":"post","link":"https:\/\/sandra.oddjar.com\/book-launch-mistakes-on-social-media\/","title":{"rendered":"Don\u2019t make these 3 book launch mistakes on social media"},"content":{"rendered":"

I\u2019m seeing a lot of authors killing it with their book launch on social media.<\/p>\n

They understand how social media works and they use it effectively.<\/p>\n

For example, they know that each social media site has its own personality, so they don\u2019t share the same content across all networks. Each post is tweaked according to the social media platform\u2019s unique needs.<\/p>\n

I’m also seeing a lot of book launch mistakes on social media.<\/p>\n

This can turn into a real issue for authors making several of them because it can kill their connections quickly.<\/p>\n

Here are the three I\u2019m seeing most often, along with suggestions for turning them around.<\/p>\n

1. Every single thing you post on every single platform is about your book.<\/h2>\n

Every. Single. Thing.<\/p>\n

I\u2019m interested in your new book. Really, I am. I am all about books and your books in particular.<\/p>\n

But I\u2019m connected to you on Facebook, Twitter, and Instagram, and all I\u2019m seeing from you is how excited you are that your book will soon be published\/is being published today\/was just published.<\/p>\n

People will tolerate that for a few days, but three weeks of nothing but new book posts is pretty intense.<\/p>\n

At first, we might think, \u201cOh, that\u2019s interesting! I\u2019ll have to check it out.\u201d As we see more and more posts, we start to think, \u201cIs that all you\u2019ve got going on these days?\u201d Eventually, we disconnect from you because of the constant repetition.<\/p>\n

During your book launch period, share some of the content you usually share, too, so you\u2019re not a one trick pony.<\/p>\n

Maddie Daws, the pen name of best-selling author Sandi\u00a0Kahn\u00a0<\/span>Shelton, is an example of somebody who has\u00a0this<\/span>\u00a0figured out. Her Instagram account<\/a> has a nice mix of book and everyday life content as she approaches the launch of a book that is part of Amazon’s May “First Reads” program for Prime subscribers.<\/p>\n

\"book<\/a><\/h2>\n

2. You\u2019re doing what everyone else is doing.<\/h2>\n

Classic example: The \u201cOMG My First Case of Books Arrived\u201d video post. One I saw recently went on for at least five minutes. That was four minutes and 30 seconds too long.<\/p>\n

If you\u2019re doing it because you\u2019re certain that your network truly can\u2019t wait to see you cut open a box of books, then go for it.<\/p>\n

But if you\u2019re doing it because everyone else is doing it, don\u2019t. Try something different to capture interest and attention.<\/p>\n

Start by asking yourself: \u201cWhat does my audience need to know about this book?\u201d or \u201cWhat about this book will excite my readers?\u201d<\/p>\n

3. You aren\u2019t helping us help you.<\/h2>\n

We want to help you let the world know about your wonderful new book, but we\u2019re all pressed for time, ya know?<\/p>\n

So, when you ask, \u201cCan you help me spread the word about my book?,\u201d give us the tools we need to do that.<\/p>\n

Please provide:<\/p>\n