Why most SEO briefs get ignored

Most SEO briefs land in a writer's inbox and never get read carefully. The writer skims it, picks up the title and word count, then writes the article they were going to write anyway. The SEO team wonders why their carefully researched briefs aren't producing carefully researched articles.

The reason is usually the brief, not the writer. A brief that's a wall of keywords, a list of "include these phrases naturally," and a vague structure prompt isn't a useful document. It's a checklist disguised as a brief, and writers correctly ignore it.

A brief writers actually use does six specific things.

The six elements of a brief that gets used

A target keyword and the SERP intent it represents

Not just "target keyword: emergency plumber Phoenix." That's a string. The brief should explain what intent the SERP currently shows for that keyword:

  • Is the top result a service page? A blog post? A list-style article?
  • Are there featured snippets, People Also Ask, local pack, video carousels?
  • What does the buyer landing on this page actually want?

The writer needs this to know what kind of content they're writing. "Emergency plumber Phoenix" with a service-page SERP intent gets a service page. "How to fix a frozen pipe" with a how-to SERP intent gets a step-by-step guide. The writer knows the difference if you tell them.

An H1/H2/H3 outline — opinionated, not exhaustive

Not 25 H2s the writer should consider. 4-7 H2s the writer should hit, in the order suggested. Each H2 with a one-sentence description of what that section needs to cover.

The opinionated outline does two things:

  • It tells the writer what the page must include for SEO depth (matches what top-ranking results cover)
  • It frees the writer from outlining themselves, which is the bottleneck step in most editorial work

A bad brief lists 20 possible sections "consider for inclusion." A good brief commits to 6 sections and tells the writer to write them.

Entities and concepts to cover

The brief should list the specific terms, products, technologies, regulations, or concepts the page needs to mention to be topically complete. Not as keywords to stuff — as concepts to weave naturally.

For an emergency plumbing page in Phoenix, this might be: slab leak, hard water, monsoon flooding, BBB rating, ROC license number, emergency dispatch, after-hours fee, payment options accepted.

The writer reads the entity list before writing and weaves the relevant ones into their natural argument. The page ends up topically complete without the writer having to research what topical completeness means in this niche.

People Also Ask questions worth answering

Pulled from the actual SERP. The brief should list the PAA questions Google is currently surfacing for the target keyword and identify which ones to address in the body, which to address in an FAQ, and which to ignore.

This is one of the highest-ROI sections of a brief. Writers don't have time to manually pull PAA questions for every article. When the brief includes them, writers usually use them. When it doesn't, the page misses opportunities to rank for snippet questions.

Internal link suggestions

Specific suggestions: this anchor text from this page on the site should link to this other page. Not "include some internal links" — that's the kind of vague instruction writers ignore. Specific instructions are followable.

Even better: tell the writer which existing pages should be updated to link to the new page once it's published. That's the often-skipped part of internal linking work, and putting it in the brief makes it harder to skip.

Brand voice notes — short and specific

Not "be helpful and authoritative." That's nothing. Specific:

  • "We say 'water heater' not 'hot water cylinder' (US English)"
  • "We avoid jargon like 'thermal expansion'; we say 'hot water making your plumbing knock'"
  • "We sign off service pages with a phone CTA, not a 'request a quote' form"
  • "We never compare our pricing to competitors by name"

Three to five voice notes, each specific and memorable, beats a long voice document the writer half-remembers from onboarding. Repeat the most important ones in every brief.

What you can leave out

A common mistake is treating a brief as a planning document for everyone — SEO, marketing, the writer, the editor. Briefs that try to serve everyone serve no one well. A brief is for the writer.

Things that don't need to be in the brief:

  • The original keyword research that justified writing the page
  • Stakeholder approval status
  • Marketing campaign context
  • Future internal linking plans for related-but-not-yet-built pages
  • Per-paragraph keyword density targets (this hasn't been a real ranking factor in 15 years)
  • Long lists of LSI keywords without context (the entity list above replaces these)

Keep the brief tight enough that a writer reads the whole thing in 4-5 minutes. If they're skimming because it's too long, you've failed the brief.

A typical brief structure

In rough order:

  1. Target keyword and search intent (2 sentences)
  2. Title variations (3-5 options)
  3. Meta description options (2 options)
  4. Suggested H1
  5. H2/H3 outline (4-7 H2s, each with a 1-sentence description)
  6. Target word count range (a 200-word window, e.g. "1,400-1,600")
  7. Entities and concepts to cover (a bulleted list)
  8. People Also Ask questions to address (with notes on body vs FAQ placement)
  9. FAQ block (3-5 questions with notes on what the answers should hit)
  10. Internal link suggestions (specific anchor + target page pairs)
  11. Schema recommendations (the JSON-LD types that should appear on this page)
  12. Brand voice notes (3-5 specific guidelines)
  13. Out of scope (1-2 sentences explicitly noting what this page should NOT cover, to prevent scope creep)

Total length: 600-1,200 words. Format: clean Markdown or PDF, not a 40-tab spreadsheet.

The grading rubric — closing the loop

A brief is only useful if the resulting draft is checked against it. A grading rubric is the simplest closing-the-loop tool:

  • Did the draft hit the H2 outline (yes/no per H2)?
  • Did the draft cover the listed entities (count out of total)?
  • Did the draft answer the PAA questions (yes/no per question)?
  • Did the draft hit the word count range?
  • Did the draft include the suggested internal links?
  • Did the draft follow the voice notes?

A 30-second rubric check reveals whether the writer used the brief or ignored it. Over time, this changes writer behavior — they start writing from the brief because they know they'll be measured against it.

How WordBinder generates briefs

WordBinder's Briefs pillar produces all of the above automatically. The intake collects your brand voice notes, internal link suggestions are surfaced from your indexed site, SERP analysis comes from DataForSEO, and the structure is generated through the per-vertical Claude skill so the brief reflects how content in your vertical actually needs to be structured.

The brief lands as a clean document the writer can open, read in five minutes, and ship from. The grading rubric is built in — once the draft is back, you can check coverage against the brief without manual work.

The takeaway

The difference between a brief writers ignore and a brief writers use isn't length or polish. It's whether the brief commits to specific, actionable guidance — opinionated outline, specific entities, specific link suggestions, specific voice notes — instead of hedging into a list of "considerations." Commit to the guidance. Trust the writer to follow it. Check the draft against the brief afterward. The articles get better fast.