A 10-Point Editing Checklist Before You Hit Publish
Most bad publishing decisions aren't bad ideas. They're good ideas shipped after a five-minute skim instead of a real edit. Ten checks, done deliberately, catch almost everything that a rushed final read misses.
1. Read it aloud (or have it read back to you)
This single step catches more real problems than any other on this list — awkward phrasing, run-on sentences, unclear pronoun references, and tonal shifts all surface when you hear the words rather than just seeing them. Your eyes skip over problems your ears won't. If reading aloud yourself feels awkward or you're short on time, a text-to-speech tool reading the draft back to you accomplishes almost the same thing — the point is hearing it, not who does the reading.
2. Check the headline against the actual content
Headlines get written first and content evolves during drafting, which means by the end they sometimes no longer match. Confirm the headline still accurately represents what the piece delivers — a mismatch here costs trust with readers who feel misled within the first paragraph. This is especially common in pieces that changed direction partway through drafting; the headline reflects the original plan, not the piece you actually ended up writing.
3. Verify the opening earns the next sentence
The first line's only job is getting read to the second line. Check that your opening isn't a throat-clearing warm-up (a broad, generic statement everyone already knows) but something specific enough to create curiosity or make a real claim. A useful test: could this exact opening sentence appear at the start of a dozen other articles on a similar topic? If yes, it's probably too generic to be doing real work.
4. Scan for sentence-length monotony
A paragraph where every sentence runs roughly the same length reads as flat, even if no individual sentence is wrong. Look for at least a little contrast — a short sentence after a run of longer ones, or vice versa — since that variation is doing real work for pacing. This is a fast check once you know to look for it: skim a paragraph and notice whether every sentence feels like it takes about the same amount of time to read, and if so, combine a couple and split a couple rather than leaving the rhythm untouched.
5. Hunt for filler words
Words like "just," "really," "actually," and "basically" creep in during drafting and rarely earn their place. A focused pass specifically looking for these (rather than trying to catch them during a general read) tends to tighten a piece meaningfully without cutting any actual content.
6. Check passive voice usage, but don't treat every instance as an error
Passive voice isn't automatically wrong, but stacked passive sentences in a row tend to flatten tone and obscure who's doing what. Check for clusters of it rather than banning it outright.
7. Confirm claims are supported or clearly framed as opinion
Anything stated as fact should be something you could defend if challenged. Anything that's actually your take or interpretation should read as opinion, not as an unqualified claim. Blurring the line between the two is a common way pieces lose credibility, especially with readers who already know the subject well enough to notice when a personal opinion is dressed up as settled fact.
8. Check internal consistency
Names, numbers, and terms should match themselves throughout the piece — if you call something "the readability score" in paragraph two, don't switch to "the readability rating" in paragraph six without a reason. Small inconsistencies like this are easy to introduce during editing and easy to miss without deliberately checking.
9. Verify links, formatting, and structural elements
Broken links, malformed tables, and inconsistent heading levels are the kind of thing that's invisible in your editor and glaringly obvious once published. A dedicated check of every link and structural element, right before publishing, catches issues a content-focused read will miss entirely.
10. Do a final readability check
After the structural and content edits, run the piece through a readability check to catch anything the earlier passes missed — a paragraph that's denser than it feels, a sentence that's grammatically fine but harder to parse than intended. This step works best last, after content is settled, since editing for content after a readability pass just means redoing the readability pass.
| Checklist point | Brief rationale |
|---|---|
| 1. Read aloud / listen back | Surfaces awkward phrasing your eyes skip past |
| 2. Headline matches content | Prevents reader distrust from a misleading title |
| 3. Opening earns the next line | First line's only job is getting the second line read |
| 4. Sentence-length variation | Prevents a flat, monotonous pacing across paragraphs |
| 5. Filler-word check | Tightens prose without cutting actual content |
| 6. Passive voice clusters | Passive isn't wrong alone, but clusters flatten tone |
| 7. Claims vs. opinion framing | Protects credibility by not blurring fact and interpretation |
| 8. Internal consistency | Catches drifted terminology/numbers introduced during editing |
| 9. Links and structural formatting | Broken links/tables are invisible in-editor, glaring once live |
| 10. Final readability check | Catches dense or unclear passages missed by content-focused edits |
Adapting the checklist for shorter pieces
Not every piece of writing needs the full weight of all ten checks. A short internal update or an informal message can reasonably skip the headline check and the deep readability pass, since the stakes and audience are different from a publicly published article. What shouldn't get skipped, even for shorter or lower-stakes writing, are the read-aloud pass and the internal consistency check — both catch real errors quickly and take relatively little time regardless of length. The general principle is to scale the checklist to the piece's visibility and permanence: something a thousand people will read and that will stay live indefinitely deserves the full pass; a quick internal note doesn't.
Why order matters here
Notice the sequence: structural and content checks come before the final readability pass, not after. If you check readability first and then keep editing content, you've invalidated the readability check and need to redo it. Doing the mechanical, objective checks (links, consistency, readability) last means they reflect the actual final piece, not an earlier draft of it.
None of these ten steps takes very long individually. Together, done as separate passes rather than one blurred skim, they catch the overwhelming majority of what makes published writing look rushed. The last step is the fastest to automate — running the final draft through Grammachine's readability checker gives you a quick objective read on sentence length, passive voice density, and overall score before you commit to publishing.
For more editing and readability breakdowns, sign up for the newsletter at /#lead.
Frequently asked questions
How long should a final editing pass take?
It depends on length, but budget real time for it rather than treating it as a five-minute skim. A rushed final pass tends to catch typos and miss the structural issues that matter more.
Should I edit for all 10 points in one pass or separately?
Separately if you can manage it. Trying to catch structure, tone, and typos all in one read tends to mean you catch the easy stuff and miss the harder structural issues.
What's the single highest-value item on this checklist?
Reading it aloud, or having a tool read it back to you. It catches more real problems — awkward phrasing, unclear sentences, tonal shifts — than almost any other single step.
Is spellcheck enough for the final pass?
No. Spellcheck catches misspellings, not misused words that are spelled correctly (their/there, affect/effect), and it says nothing about structure, clarity, or tone.
Do I need to do all 10 points for every piece I write?
For anything you're publishing publicly, yes, though some points take seconds (checking the headline) and others take longer (a full readability pass). Shorter internal writing can reasonably skip a few.