Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the live-composer-page-builder 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 /home1/c375526/public_html/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home1/c375526/public_html/wp-includes/functions.php:6114) in /home1/c375526/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":2644,"date":"2020-05-27T13:48:50","date_gmt":"2020-05-27T13:48:50","guid":{"rendered":"http:\/\/www.jeshays.com\/?p=2644"},"modified":"2020-05-27T13:48:51","modified_gmt":"2020-05-27T13:48:51","slug":"10-blog-writing-guidelines","status":"publish","type":"post","link":"http:\/\/www.jeshays.com\/?p=2644","title":{"rendered":"10 Blog Writing Guidelines"},"content":{"rendered":"
\n
You\u2019re up against millions of other blogs when you post, so it\u2019s hard to make an impact. These tips will help you stand out among the crowd. Keep in mind that people skim, so use lists, bullet points, headings and a good font size to make things easy for your readers.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
Readability: Most people read at about a fifth-grade level. Before you hit \u201cpublish,\u201d check your readability level. You can use a software program like Grammarly, or just utilize Microsoft Word\u2019s spelling and grammar check. A) If you have a PC go to File > Options > Spelling & Grammar > Click the \u201cShow Readability Statistics\u201d Box. B) If you have a Mac Go to Word > Preferences > Spelling & Grammar > Click the \u201cShow Readability Statistics\u201d Box. Run the Spell Check and you will have your readability.<\/li>
Avoid passive voice: Instead of saying \u201cA deal was struck by the author and the publisher,\u201d say \u201cThe author and publisher struck a deal.\u201d<\/li>
Write in simple past tense: Avoid using \u201chave,\u201d \u201chas,\u201d or \u201chad\u201d unless you\u2019re actually using the verb \u201cto have.\u201d Instead of \u201cShe had gone to the pool,\u201d write \u201cShe went to the pool.\u201d<\/li>
Stick to one tense: Don\u2019t switch from past tense to present (or vice versa).<\/li>
Have lots of white space: Check the shape of your post. You should have sentences of varying lengths, lists, images, and plenty of space instead of long blocks of text.<\/li>
Avoid modifiers and qualifiers: Examples of these include \u201ca bit,\u201d \u201csome,\u201d \u201calmost,\u201d \u201ca lot of,\u201d \u201cvery,\u201d \u201cnearly,\u201d \u201cevery,\u201d and \u201cquite.\u201d<\/li>
Write from one perspective: pick a point of view and stick to it. If you write from several different viewpoints, you\u2019ll just confuse the reader.<\/li>
Write shorter sentences: This goes along with Number 1 and Number 5. Keep it short and simple. Avoid linking words like \u201cas,\u201d \u201cbut,\u201d or \u201cthen.\u201d Avoid excessive punctuation (commas, semi-colons, colons) and just write shorter sentences.<\/li>
Remove the words \u201cthe\u201d and \u201cthat\u201d whenever possible: Instead of saying \u201cIf you feel that you should be using the educated speech and longer sentences, you may assume that you will annoy your readers,\u201d say \u201cIf you feel you should use educated speech and longer sentences, you\u2019ll annoy your readers\u201d or even \u201cUsing educated speech and longer sentences will annoy your readers.\u201d<\/li>
Avoid clich\u00e9s: Examples include \u201cthinking outside of the box,\u201d \u201ctouch base,\u201d or \u201cignorance is bliss.\u201d These phrases just \u201cget under your reader\u2019s skin.\u201d<\/li><\/ol>\n\n\n\n