The Draft Bench
Editing Systems

How to Audit a Blog Post Before Publishing

The Draft Bench · Updated 2026-07-19 · 4 min read
How to Audit a Blog Post Before Publishing
Quick answerAudit a blog post in separate passes. Compare the title, opening, headings, conclusion, and metadata promise with the body. Next verify numbers, date, quote, named source, specification, price, and consequential claim; recompute arithmetic and search for values across body and FAQ. Then inspect structure, examples, steps, tables, care boundaries, external sources, and internal links. Align title, answer block, and FAQs; render at multiple widths; test keyboard use, downloads, images, and links; read aloud; and search for unfinished stand-ins or malformed text. Record files, checks, caveats, status, and reviewer at handoff.
Contents

Audit in passes, not one heroic reread

A pre-publication audit checks whether the article answers its question, supports its claims, works as a page, and matches the delivery contract. Separate those jobs. Reading once for facts, tone, links, headings, and commas guarantees that the comma will receive an exquisite review while a broken source waves from paragraph six.

Save a review copy or use version history. Record material changes, especially factual corrections. Do not silently “improve” a number without tracing its source and recomputing every place it appears.

Pass 1: compare promise with delivery

Read only the title, opening, heading list, conclusion, and metadata answer. Write the promise in one sentence. Then ask whether the body actually delivers it.

A title promising “best tools” needs criteria, a verdict, tradeoffs, and evidence. “How to” needs prerequisites, ordered steps, verification, and failure handling. A recipe needs yield, quantities, pan or equipment, times, temperatures, and doneness. If the format fails its type, polish will not rescue it.

Check that the primary reader appears in the examples and that the opening answers rather than merely announces a journey. Remove throat-clearing that delays the useful sentence.

Compare against the editorial brief and note every intentional deviation. Research may justify a better angle; undocumented drift merely creates an argument during review.

Pass 2: verify claims and arithmetic

Highlight every number, named institution, quote, date, specification, legal or health statement, product feature, price, place detail, and causal claim. For each, open the source and confirm it supports the exact wording in context.

Prefer primary and current sources when the subject requires them. Distinguish what the source states from your inference. Check publication and event dates separately. A page updated yesterday may describe a policy from ten years ago; an old page may still hold the current standard.

Recompute arithmetic from inputs. Verify unit conversions, totals, percentages, per-serving quantities, date counts, and table/body consistency. Search the whole package for each corrected number. The fact that 4 × 225 equals 900 in one paragraph does not stop a forgotten FAQ from confidently serving 950.

Remove invented precision, unattributed quotes, and statistics that cannot be verified. Generalize honestly when detail is unavailable.

Pass 3: inspect structure and usefulness

Read the first and last sentence of every section. Each should answer one distinct question and lead to the next. Merge repetition; split sections that perform several jobs. Make headings describe reader value rather than cleverness alone.

Test every instruction as a sequence. Are prerequisites available before use? Are destructive steps labeled before the command or click? Does the reader know what success looks like and what to do when it fails? Add one complete example where abstraction remains high.

Tables should compare like with like. Every column needs a purpose, units must be consistent, and cells should remain understandable on small screens or in an accessible alternative.

Browse editing systems for recipe, code, comparison, and location-specific audit variants.

Open every external link. Confirm the destination is the intended page, not a home page that vaguely discusses the topic. Check anchors honestly describe the supporting source. Replace stale redirects when an authoritative current page exists.

Open internal links in the actual site inventory. Do not link to drafts, nonexistent slugs, the current article itself, or a vaguely similar title. Use enough context in the anchor to explain why the next page helps.

Check the care line. Health content defers to qualified care; recipes protect time and temperature; travel details avoid invented hours; product guides disclose what was and was not tested; technical articles flag irreversible actions; cultural writing does not turn a community into decoration.

Pass 5: align title, metadata, and FAQ

Count title length under the publication rule and front-load the reader's query without making syntax limp. Verify the title's promise at the section level.

Read the metadata answer as a standalone result. It should answer the primary question, not advertise that the body contains an answer. Check its word range. Each FAQ question should add information a reader plausibly needs, and each answer must remain correct when surfaced without the surrounding article.

Search for contradictions between body, table, answer block, FAQs, image captions, and structured data. Metadata is content, not a backstage area where old numbers go to retire.

Pass 6: render and interact

Preview the page at narrow and wide widths. Inspect heading hierarchy, lists, code wrapping, table overflow, callouts, images, captions, alt text, focus order, and contrast. Use keyboard navigation and relevant assistive technology checks. Confirm the body begins and ends cleanly without frontmatter or unfinished production tokens leaking into view.

Click links and controls in the rendered page. Validate downloadable files. Check images for misleading content, licensing records, crop problems, and people or places the caption identifies incorrectly.

Pass 7: read aloud and hand off

Read the article aloud or use text-to-speech. Listen for repeated openings, tangled sentences, missing words, artificial rhythm, and jokes that interrupt a safety instruction. Replace robotic signposting with direct transitions, but keep necessary warnings explicit.

Run spelling and grammar tools last, reviewing each suggestion rather than accepting the machine's sudden campaign against technical vocabulary. Search for unfinished-task flags, generic stand-in names, malformed characters, and duplicate spaces, and unsupported “best,” “always,” or “guaranteed.”

Finish in planning tools by recording status, files, checks run, unresolved caveats, and reviewer. The article is ready when the evidence, page, and handoff agree—not when the author has stared at the same paragraph long enough for it to achieve diplomatic immunity.

FAQ

Why audit a blog post in separate passes?

Different review tasks compete for attention. A single reread may catch punctuation while missing a citation mismatch or broken promise. Separate passes let the editor focus on delivery, facts, structure, links, metadata, rendering, and language in turn. They also produce a clearer record of what was checked. Save version history so a factual correction can be traced and does not silently create new contradictions elsewhere.

Which claims need verification before publishing?

Verify every number, date, quotation, named institution, law, health or safety statement, product feature, price, specification, place detail, and causal claim. Open the source and confirm the exact wording in context, using current primary material when appropriate. Distinguish the source's statement from your inference. Remove unverifiable precision and recompute totals, percentages, conversions, dates, and examples rather than trusting the draft's arithmetic.

How do I audit internal and external links?

Open every link. External anchors should describe a destination that directly supports the attached claim, not merely a relevant home page. Internal targets must exist in the site's current inventory, help the reader, and not point to the article itself, an unpublished draft, or an uncertain slug. Check redirects and rendered behavior. A linked article may provide context, but an internal link does not substitute for external evidence.

What should I check in blog metadata and FAQs?

The metadata answer should solve the primary question when read alone, stay within its word range, and avoid promises the body cannot fulfill. FAQ questions should add plausible reader value rather than repeat headings. Each answer must remain accurate when surfaced without surrounding context. Search body, tables, captions, answer, FAQs, and structured data for contradictory numbers, dates, terminology, or safety guidance after every material correction.

What belongs in a final content handoff?

List the delivered files, status, checks run, source or data caveats, known limitations, unresolved decisions, and designated reviewer. Confirm filenames, format, encoding, word limits, title rules, link targets, and required assets. Include rendered or interaction checks when layout matters. Do not hide a skipped requirement inside a general “done” message; name it and its effect. A useful handoff lets another person verify the work without reconstructing the entire assignment.