The Editorial Content Quality Handbook

What Is Content Quality?

Content quality is not a single metric. It is the intersection of five separate judgments that, together, determine whether a page is worth publishing. A page can have perfect grammar and still fail because it omits critical information. It can be comprehensive but unreadable. It can be clear and complete but structurally chaotic. Quality requires all five dimensions to reach an acceptable threshold.

This handbook defines each dimension, provides concrete signals for assessment, and gives you a repeatable workflow for reviewing any draft before it goes live. The goal is not perfection. The goal is publication readiness: a state where the page serves its intended reader well enough that publishing it is a net positive for both the reader and your site.

The Five Dimensions

Every piece of content can be evaluated along five independent dimensions. These are not weighted equally. Their relative importance shifts depending on the content type and the reader's intent. But all five must be considered before publishing.

These dimensions are interdependent. Poor structure can make clear writing feel chaotic. Low specificity can make complete coverage feel hollow. But they are also distinct. You can have clear writing that is incomplete. You can have specific details buried in poor structure. The editorial task is to raise each dimension to an acceptable level before publishing.

1. Clarity

Clarity measures how much cognitive effort the reader must expend to understand your message. High-clarity writing feels effortless. Low-clarity writing feels like work. The difference is not intelligence. It is editorial discipline.

Signals of High Clarity

• Sentence length variance: A mix of short, medium, and long sentences. Short sentences punch. Medium sentences explain. Long sentences connect ideas. All three have a place. But the average should land between 15 and 20 words, with no more than 25% of sentences exceeding 25 words.
• Paragraph density: Paragraphs that stay under 80 words and rarely exceed 4 sentences. Dense paragraphs signal that the writer did not pause to give the reader a breather.
• Word choice: Common words over rare ones. "Use" instead of "utilize". "Start" instead of "commence". Jargon only when the audience expects it and understands it.
• Active voice: Subject-verb-object order. "The team launched the feature" not "The feature was launched by the team". Passive voice has its place (emphasizing the object, hiding the actor) but should be intentional, not default.

How to Improve Clarity

1. Read aloud. Your ear catches what your eye skips. If you stumble over a sentence, rewrite it. If you run out of breath, split the sentence.
2. Hunt "which" and "that". These words often introduce clauses that can be split into their own sentences. "The report, which was published on Tuesday, shows..." becomes "The report was published on Tuesday. It shows..."
3. Replace Latinate verbs. "Make a decision" → "Decide". "Conduct an analysis" → "Analyze". "Provide an explanation" → "Explain". The verb form is almost always shorter and clearer.
4. Break walls of text. Any paragraph over 80 words is a candidate for splitting. Look for natural breaks: a shift in topic, a new example, a contrasting point. Split there.
5. Define jargon on first use. If a term is not common knowledge, define it the first time it appears. "Organic reach (the number of people who see your content without paid promotion)..."

2. Completeness

Completeness measures whether the page answers the reader's core question. A complete page does not need to cover everything. It needs to cover what the reader came for. Incompleteness is the most common cause of low-quality ratings from both readers and search engines.

Signals of Completeness

• Word count relative to intent: A homepage hero section needs 50-100 words. A "how to" guide needs 1,200-2,500 words. A product description needs 150-300 words. The right length is the length required to answer the reader's question without padding.
• Subtopic coverage: For a guide: what, why, how, examples, common mistakes, next steps. For a product page: what it is, what it does, who it is for, proof, price, how to buy. For a local service page: what service, where, who provides it, proof of competence, how to contact.
• Unanswered questions: Every claim invites a question. "This tool improves content" → "How?" "Used by 10,000+ writers" → "Which writers?" "Results in 30 days" → "What results?" A complete page anticipates and answers the obvious questions.

How to Improve Completeness

1. Write the reader's question at the top of the draft. "How do I write a meta description?" "What makes a good product page?" "Which local SEO tactics work?" If the page does not answer that question, it is incomplete.
2. List the subtopics before writing. For a guide: definition, importance, steps, examples, mistakes, tools, FAQ. For a product: problem, solution, features, benefits, proof, price, CTA. Check each off as you write.
3. Read the page and write down every question that pops into your head. Then answer each question in the page itself. Do not defer to a "contact us" link unless the question is genuinely specific to the reader's situation.
4. Compare to the best competing page. Find the highest-ranking page for the same query. List what it covers. Add any subtopics it missed. This is not about copying. It is about ensuring your page is at least as complete as the alternatives.

3. Structure

Structure is the skeleton that holds content together. Good structure is invisible. Readers notice it only when it is missing. Poor structure makes even excellent content feel chaotic and untrustworthy.

Signals of Good Structure

• Heading hierarchy: One H1 (the page title). H2s for major sections. H3s for subsections. No skipped levels. Headings that describe the section, not cute phrases that require reading the section to understand.
• Logical sequence: Information presented in the order the reader needs it. For guides: what → why → how → examples → mistakes → next steps. For product pages: problem → solution → features → proof → price → CTA. For local pages: service → location → provider → proof → contact.
• Visual breaks: Lists, tables, images, callouts, and short paragraphs that give the eye a place to rest. A page that is 100% prose is a page that will be skimmed, not read.

How to Improve Structure

1. Write the heading outline first. Before drafting any prose, write the H1, H2s, and H3s. This forces you to think through the logical flow before you get attached to specific sentences.
2. Check heading descriptiveness. Cover the body text and read only the headings. Do you understand the page's argument? Can you predict what each section covers? If not, rewrite the headings.
3. Insert visual breaks every 200-300 words. After every 200-300 words of prose, ask: "Could this be a list? A table? A callout? An image?" Convert at least one-third of these candidates into visual elements.
4. Move information to match reader intent. If the reader came for steps, put steps first. If they came for proof, put proof above the fold. Do not make them hunt for what they need.

4. Specificity

Specificity is the difference between "this tool helps" and "this tool flags sentences over 25 words and suggests stronger verbs". Specific claims are trustworthy. Vague claims are not. Specificity is the most common differentiator between high and low quality content.

Signals of High Specificity

• Numbers: "15-20 words per sentence" not "short sentences". "1,200-2,500 words" not "long enough". "80 words per paragraph" not "reasonable paragraphs". Numbers are falsifiable. Vague claims are not.
• Names: "Google Search Central" not "search engines". "Nielsen Norman Group" not "UX experts". "Robert Gunning" not "readability researchers". Names signal that the writer did the work.
• Examples: "The feature was launched by the team → The team launched the feature" not just "change passive to active". Examples show the reader exactly what to do.
• Step-by-step instructions: "1. Read the page aloud. 2. Mark sentences where you stumble. 3. Rewrite each marked sentence." Not "read it over and fix what sounds bad".

How to Improve Specificity

1. Hunt vague claims. Search for: "helps", "improves", "better", "effective", "proven", "results". For each, ask: "How, exactly?" Add the mechanism.
2. Add numbers to every claim that can be measured. "Short sentences" → "Sentences under 20 words". "High contrast" → "WCAG AA, 4.5:1 ratio". "Fast loading" → "Under 2 seconds on 4G".
3. Replace generic examples with concrete ones. "For example, a product page" → "For example, a product page for a $200 ergonomic keyboard". "A local business" → "A plumbing company in Austin, TX".
4. Name your sources. If you are citing research, name the study, the author, the year. "Gunning (1952) found that..." not "Studies show...".

5. Publication Readiness

Readiness is the final gate. A page can be clear, complete, well-structured, and specific. But if the title does not match the content, if links are broken, if metadata is missing, or if there are obvious typos, the page is not ready. Readiness is about polish and consistency.

Signals of Readiness

• Title accuracy: The title (H1 and title tag) accurately describes the page content. No clickbait. No promise inflation. The reader should not feel misled.
• Metadata: Meta description (150-160 characters) that summarizes the page. Canonical URL. Open Graph tags for social sharing. These are not optional for publication.
• Internal consistency: Terms used consistently. No "SEO" in one paragraph and "search optimization" in the next. No "contact us" and "get in touch" used interchangeably.
• Polish: No typos. No broken links. No placeholder text. No "TODO" comments. No console errors. No missing images.

Pre-Publication Checklist

• [ ] Title tag matches H1 and accurately describes the page
• [ ] Meta description is 150-160 characters and summarizes the page
• [ ] All links work (internal and external)
• [ ] All images have alt text
• [ ] No placeholder text ("lorem ipsum", "TODO", "[insert example]")
• [ ] No console errors
• [ ] Canonical URL is set
• [ ] Open Graph and Twitter Card tags are present
• [ ] Author and last-updated date are visible
• [ ] Corrections/contact link is present
• [ ] Page is added to sitemap.xml
• [ ] Robots.txt allows crawling (if indexable)

Quality by Content Type

Different content types weight the five dimensions differently. A blog post can sacrifice some specificity for readability. A technical guide cannot. A product page must emphasize specificity and readiness. A local service page must emphasize completeness and proof. The table below shows the relative weight for each type.

The Review Workflow

Use this workflow to review any draft before publication. It takes 15-20 minutes for a standard page. For longer guides or cornerstones, budget 30-45 minutes.

Pass 1: Clarity (5 minutes)

1. Read the page aloud. Mark any sentence where you stumble or run out of breath.
2. Split every marked sentence into two shorter sentences.
3. Replace any word that a general audience would not know with a simpler synonym. Define necessary jargon on first use.
4. Break any paragraph over 80 words into two paragraphs.

Pass 2: Completeness (5 minutes)

1. Write down the reader's core question at the top of the page.
2. List every subtopic the reader would expect. Check if each is covered.
3. Read the page and write down every question that pops into your head. Answer each in the page.
4. If any subtopic is missing, add a section or link to a page that covers it.

Pass 3: Structure (3 minutes)

1. Cover the body text and read only the headings. Do they make sense alone?
2. Check heading hierarchy: one H1, H2s for sections, H3s for subsections, no skipped levels.
3. Insert a visual break (list, table, callout, image) every 200-300 words.

Pass 4: Specificity (5 minutes)

1. Search for vague claims: "helps", "improves", "better", "effective", "proven".
2. For each, add the mechanism: how, exactly?
3. Add numbers to every claim that can be measured.
4. Replace generic examples with concrete ones.

Pass 5: Readiness (5 minutes)

1. Run the pre-publication checklist above.
2. Check title accuracy: does it match the content?
3. Verify all links work.
4. Scan for typos and placeholder text.

Common Failure Modes

These are the most common reasons pages fail quality review. Knowing them helps you spot them faster.

The Bait-and-Switch

The title promises one thing. The page delivers another. This is the fastest way to lose reader trust. Fix: Rewrite the title to match the content, or rewrite the content to match the title.

The Wall of Text

No paragraphs over 3 sentences. No lists. No images. No visual breaks. Readers will not read this. Fix: Break every 200-300 words with a list, table, callout, or image.

The Vague Promise

"This tool improves your content." "Our service delivers results." "Proven method." No mechanism. No numbers. No proof. Fix: Add the how. Add the numbers. Name the source.

The Unanswered Question

The page raises an obvious question and does not answer it. "10,000+ users" → "Who?" "Results in 30 days" → "What results?" Fix: Anticipate and answer the obvious questions.

The Buried Lead

The most important information is 80% down the page. Readers will not scroll that far. Fix: Move the key information above the fold or into the first 200 words.

The Phantom Author

No author name. No date. No way to contact. This signals that no one stands behind the content. Fix: Add author, last-updated date, and contact link.

When to Publish Anyway

Perfection is not the goal. Publication is. There are times when publishing an imperfect page is the right call. The key is knowing which imperfections are acceptable.

Publish Even If...

• The score is 65-75. A score in this range means the page has issues but is fundamentally sound. Fix the top 3 revisions and publish.
• One dimension is weak. If four dimensions are strong and one is mediocre, publish and plan a follow-up revision.
• The page is time-sensitive. News, announcements, and time-bound offers should publish with a "good enough" standard. You can revise later.
• The page is a draft for feedback. Some pages need stakeholder input before final polish. Publish to a private URL and share for review.

Do Not Publish If...

• The title does not match the content. This is a trust-killer. Fix before publishing.
• There is placeholder text. "Lorem ipsum", "TODO", "[insert example]" signal an unfinished page. Remove before publishing.
• Key information is missing. If the reader's core question is unanswered, the page is not ready.
• There are broken links or images. These signal neglect. Fix before publishing.

Related Resources