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":2706,"date":"2022-09-14T07:00:41","date_gmt":"2022-09-14T12:00:41","guid":{"rendered":"http:\/\/buildbookbuzz.com\/?p=2706"},"modified":"2023-12-07T21:34:00","modified_gmt":"2023-12-07T21:34:00","slug":"how-to-e-mail-a-press-release-to-journalists","status":"publish","type":"post","link":"https:\/\/sandra.oddjar.com\/how-to-e-mail-a-press-release-to-journalists\/","title":{"rendered":"How to email a press release to journalists: The biggest mistake to avoid"},"content":{"rendered":"

Affiliate Disclosure:<\/strong> This post contains an affiliate link, which means if you click on it and make a purchase, I will receive a small commission (at no extra charge to you). <\/em><\/p>\n

When I won the public relations industry’s equivalent of an Academy Award for a publicity campaign built entirely around press releases in the ’90s (!), I sent press releases via postal mail.<\/p>\n

Those days are gone.<\/p>\n

And yet, authors and others regularly ask me if they should mail a printed press release when they have newsworthy information to share.<\/p>\n

Nope.<\/p>\n

In today’s digital society, the only time you should send a printed press release is when you’re tucking it inside a review copy<\/strong>. You need to email a press release to a journalist.<\/p>\n

There’s a right way … and there’s a wrong way<\/h2>\n

There are several reasons why we send press releases with email:<\/p>\n

    \n
  • It’s the 21st century<\/strong>.<\/li>\n
  • Email lets journalists copy and paste<\/strong> from a press release. Otherwise, they have to retype what’s in the printed document.<\/li>\n
  • It’s fast<\/strong>.<\/li>\n
  • It’s so much more cost effective<\/strong>. You’re not paying for paper and postage; nobody is spending time labeling and stuffing envelopes.<\/li>\n
  • It’s eco-friendly<\/strong>.<\/li>\n<\/ul>\n

    Seems obvious, right?<\/p>\n

    What’s less obvious is that there\u2019s a right way to do it, and there\u2019s a wrong way to do it.<\/p>\n

    And many, many people who send press releases for a living \u2013 publicists \u2013 do it the wrong way. I know because I receive their press releases daily.<\/p>\n

    Their mistake makes sure their message hits the recipient\u2019s trash bin quicker than I close Facebook when I see a snake photo.<\/p>\n

    You don\u2019t want to make their mistake.<\/p>\n

    Video tutorial: How to email a press release<\/h2>\n

    I created a step-by-step video to show you how to email a press release to journalists the right<\/em> way. You can also read the loose transcript of my video instructions under the video. (To see the video steps better, use the “full screen” icon in the lower right of the video box.)<\/em><\/p>\n