Content Writing
How to Edit and Proofread Business Blog Posts
Edit in five separate passes, biggest problems first: purpose, structure, accuracy, sentences and voice, then proofreading in the live preview.
Edit a business blog post in separate passes, from the biggest problems to the smallest: first whether the post answers the right question, then its structure, then accuracy, then sentences and voice, and only then proofreading for typos, links and formatting. Doing it in that order stops you polishing paragraphs that are about to be cut, and doing each pass separately catches far more than one read trying to do everything.
Below is the five-pass method, what to look for in each, how long each typically takes for a 1,500-word post, and the techniques that actually improve error-catching.
Editing and Proofreading Are Different Jobs
Editing decides what the post says and how it is organised. Proofreading checks that what it says is printed correctly. They use different kinds of attention: editing needs you to read for meaning and argument, while proofreading needs you to slow down and look at individual words, which is exactly what reading for meaning stops you doing.
They are also different in value. A post with a typo is slightly embarrassing; a post that answers the wrong question, or buries the answer in paragraph six, fails completely. Spend your time accordingly.
The Five Passes
| Pass | Question it answers | Rough time for 1,500 words |
|---|---|---|
| 1. Purpose | Does this answer the question the reader searched for, early enough? | 10 minutes |
| 2. Structure | Is the order right, and does each section earn its place? | 15–20 minutes |
| 3. Substance and accuracy | Is every claim true, sourced and specific? | 20–40 minutes |
| 4. Sentences and voice | Is it clear, tight and on-brand? | 30 minutes |
| 5. Proof and publish | Are words, links, metadata and layout correct on the live preview? | 15–20 minutes |
That is roughly 90 minutes to two hours for a substantial post, and it is time well spent. The timings are a working guide rather than a benchmark; technical or regulated topics need longer in pass 3.
Pass 1: Purpose
- Read the title and the first paragraph only. Does the first paragraph answer the title? If not, rewrite it before anything else.
- Compare the draft with the brief: right reader, right search intent, right scope?
- Note anything that belongs in a different post. Tangents are cheaper to move now than to edit and then delete.
Pass 2: Structure
- Read only the headings, top to bottom. Could a reader understand the argument from them alone? If two headings say much the same thing, merge the sections.
- Check that each section contains something usable: a number, an example, a step or a decision rule. A section that only restates the topic should go.
- Move the strongest example nearer the top. Most readers do not reach the end; Nielsen Norman Group's early research found 79% of test users scanned new pages and only 16% read word by word.
Pass 3: Substance and Accuracy
Highlight every statistic, date, price, name, quotation and claim about a third party, and check each against its original source. This pass deserves its own process, and how to fact-check blog content before publishing sets it out step by step. At the editing stage, also ask whether the claims are specific enough: "fast turnaround" is not a claim, "two business days" is.
Pass 4: Sentences and Voice
Now, and only now, work line by line. A before-and-after shows the kind of change this pass makes:
Before (42 words): "It is important to note that there are a number of different factors that can potentially have an impact on the overall cost of a commercial cleaning contract, and it is therefore advisable to consider each of them carefully."
After (19 words): "Four things set the price of a cleaning contract: floor area, frequency, the type of space and access hours."
The edit cut more than half the words and added information. Common targets in this pass:
- Throat-clearing: "It is important to note that", "When it comes to", "In order to". Delete and start with the point.
- Hedges: "may potentially", "could possibly". One per paragraph is usually plenty.
- Long sentences: split anything over about 25 words, the threshold GOV.UK's writing guidelines give its own writers.
- Vague nouns: "solutions", "factors", "aspects". Replace with the actual thing.
- Voice drift: check terminology and tone against your voice sheet; keeping a consistent brand voice explains how to build one.
Pass 5: Proof and Publish
Proofread in the CMS preview, not the draft document. Formatting, link and layout errors only appear once the post is rendered.
- Title, headings and the first paragraph, read slowly. These are where errors are most visible and most often missed, because the eye skims familiar text.
- Every link clicked, internal and external. Check that it opens the right page, not just a page.
- Numbers, units and currency formatted consistently.
- Title tag, meta description and URL slug checked for typos and length; writing meta titles and descriptions covers what good looks like.
- Images have alt text, captions are correct, nothing overflows on a phone screen.
- Author name, date and category are set.
Techniques That Catch More Errors
- Read it aloud. A 2022 study by Cushing and Bodner in the Journal of Applied Research in Memory and Cognition, summarised in Psychology Today, found reading aloud improved detection of both misspellings and correctly spelled wrong words compared with silent proofreading. Participants did not expect it to help, and did not feel it was helping while they did it.
- Do not bother with hard-to-read fonts. The same study tested Sans Forgetica, a font designed to slow reading down, and found it did not help; participants caught fewer misspellings with it.
- Leave a gap. Overnight if you can. If not, edit something else for an hour. The gap is what lets you see what you wrote rather than what you meant.
- Read backwards for typos. Sentence by sentence from the end, so you judge each sentence on its own rather than following the argument.
- Use a checker, then ignore half of it. Spelling and grammar tools are good at catching doubled words and missed letters. They are poor judges of style and will happily "correct" deliberate choices.
Too many reviewers is its own error. When five people comment on one draft, the comments contradict each other and the post ends up written by committee. Decide who reviews what (a subject expert for accuracy, one editor for everything else) and give one person the final say.
Why It Matters for Search, Too
Editing is not only about appearances. Google's guidance on creating helpful content includes, among its self-assessment questions, "Does the content have any spelling or stylistic issues?" and "Is the content produced well, or does it appear sloppy or hastily produced?" It also asks whether the content has "any easily-verified factual errors". Those are the same questions passes 3 to 5 answer.
A Printable Pre-Publish Check
- First paragraph answers the title.
- Headings alone tell the story; no two say the same thing.
- Every section has a number, example, step or rule.
- Every fact checked against its original source and linked.
- No sentence over about 25 words without a reason.
- Voice and terminology match the voice sheet.
- Proofread aloud, in the preview.
- All links clicked; metadata checked; mobile view checked.
Copy that list into your publishing workflow and tick it for every post. If editing is the step that keeps getting squeezed, our copy editing service is handled by an in-house team, usually within two business days. Either way, keep the passes separate and in order; that alone fixes most of what goes wrong.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
Editing changes what a post says and how it is organised: the angle, structure, accuracy, clarity and voice. Proofreading is the final check that the agreed text is correct on the page, catching spelling, punctuation, broken links and formatting errors. Editing comes first, because proofreading text that will later be rewritten is wasted effort.
For a substantial post of around 1,500 words, budget roughly 90 minutes to two hours across all passes, with more for technical or regulated subjects where accuracy checking takes longer. A short news post may need only half an hour. If editing takes longer than writing, the brief or the draft usually needs fixing upstream.
Use one as a first sweep for doubled words, missing letters and obvious slips, then proofread yourself. Grammar tools often flag deliberate style choices and miss correctly spelled wrong words, such as 'form' for 'from'. Reading the preview aloud catches many errors that automated checks do not.
You can catch a great deal yourself if you leave a gap between writing and editing, work in separate passes and read aloud. What self-editing misses is assumed knowledge, because you know what you meant. For important posts, a second reader, even a colleague outside marketing, is the cheapest way to find unclear passages.
Check that the opening answers the title, the headings make sense on their own, every fact is sourced, every link works, and the title tag, meta description and slug are correct. Then read the post in the CMS preview on both desktop and phone, because formatting and layout problems only appear once the page is rendered.