This guest post is by Luke Palder of ProofreadingServices.Us.
It should come as no surprise that writing for a blog is different from writing for other types of media. Blogs are free to read and there are tons of them, so people tend to decide very quickly if they’d like to move on to the next one. Only great content will cause a new visitor to read beyond the first paragraph of one of your posts, but there are many ways to scare a new reader away. Publishing content with glaring errors is one of them.
Git my pointe? (Don’t run away just yet. Instead, find out how easy blog proofreading can be.)
The aim of blog proofreading is to build credibility with new readers as quickly as possible so that they stick around, share your content and maybe even throw you a link or two. Below are 11 actionable proofreading tips for bloggers that are going to help you polish your posts quickly and effectively.
1. Walk away
Bloggers usually write a post and then immediately publish it. Don’t. Wait instead. When you’ve stared for too long at the same draft, any proofreading you undertake will be ineffective. Step away from your keyboard for half an hour or an entire day (gasp!) if you can and then check your work. This way, you’ll spot more errors.
2. Ask a friend for help
No matter how sharp you are at spotting errors, your eyes naturally skip over errors in your own work. Enlisting a friend’s help to read a draft post and point out your mistakes can help you correct them.
3. Use a spell-checker
You might be a flawless speller, but everyone includes a typo here and there, especially when hurriedly typing, which is the modus operandi of many of my blogging brethren. Always run your blog posts through a spell-checker or use a browser that detects spelling errors. This is one of the quickest proofreading tips you can implement, and there’s no reason not to use a tool that’s so widely available.
4. Use a grammar-checker
Like spell-checkers, grammar-checkers are immeasurably useful, but only if you actually use them (for many word processing programs, this means you’ll actually have to click “start”). A grammar-checker will scan your post for issues such as parallel structure errors, comma splices and run-on sentences, all of which are easy to miss when rushing to publish. Grammar-checkers aren’t perfect, but they’ll point