The SEO Content Brief That Ranks on the First Draft

Most content briefs are two lines: a target keyword and a word count. The writer gets handed "best project management software, 1,800 words" and told to go. Then the draft comes back, it does not rank, and everyone blames the writing. The writing was probably fine. The brief was the problem. A brief that is just a keyword and a length tells the writer nothing about what the page has to be, so the writer guesses, and a guessed page ranks the way guessed pages do, which is to say barely. The fix is not a better writer or three rounds of edits. It is a brief that carries the things the page actually needs to win, decided before anyone writes a word.

Here is what those things are, why each one matters, and what a finished brief looks like. The whole point is that the research and the decisions happen up front, in the brief, so the first draft is already aimed at the right target instead of being rewritten toward it.

Start with intent and page type, read from the SERP

Before anything else, the brief has to name the search intent and the page type that serves it, and you get both by reading the live search results for the keyword, not by guessing. Google has already decided what kind of page wins for that query. The results page is that decision, written down. If the top ten are all listicles, the intent is "show me the options" and your page is a list, not a 1,200-word essay arguing for one tool. If the top results are product pages, a blog post is not going to break in no matter how good it is, because the searcher wants to buy, not read.

This matters because intent is the one thing you cannot out-write. You can have the best paragraphs on the internet and still lose if you built a how-to guide for a query that wants a comparison table. The brief names it plainly: intent is commercial-investigation, page type is a comparison listicle, primary format is a ranked list with a table up top. Now the writer is building the right shape of thing from sentence one.

Entities and questions, not a keyword-density target

The next thing a real brief carries is the set of subtopics, entities, and questions a complete answer has to cover. This is the part the keyword-and-wordcount brief misses entirely, and it is the part that decides whether the page reads as authoritative or thin.

You build this list from two places: what the pages currently ranking actually cover, and what People Also Ask shows for the query. Pull up the top five results and note the subtopics they all hit. If every ranking page on "email marketing for ecommerce" covers segmentation, automation flows, deliverability, and a few named tools, those are not optional. They are the table stakes Google has learned this topic requires. The questions in People Also Ask are the same signal in question form: real things searchers expect answered on the page.

Notice what this is not. It is not "use the keyword eight times." Keyword density has not been a real ranking lever for years, and writing to a density target produces stilted copy that repeats a phrase nobody says out loud. The brief should list concepts to cover, not a phrase to sprinkle. "Cover deliverability, including SPF and DKIM, and answer why emails land in spam" is a useful instruction. "Use the term email marketing 1.5% of the time" is cargo cult.

Scope taken from the SERP, not a guess

The word count belongs in the brief, but it should be measured, not invented. Look at the length of the pages currently ranking on page one and aim for the same neighborhood. If the top results run 1,400 to 1,800 words, a 600-word post will read as incomplete against them and a 4,000-word post is probably padded with things searchers did not come for. The SERP is telling you how much depth this query rewards. Match it.

The reason to measure rather than guess is that the right length is entirely query-dependent and not at all intuitive. "What time is it in Tokyo" wants one line. "How to migrate a WordPress site to a new host" wants a thorough walkthrough. Pulling the scope from the actual results keeps you from writing a thin page on a topic that needs depth, or a bloated one on a topic that wants a quick answer. Word count is a proxy for completeness, so treat it as the output of covering the subtopics well, not a number to hit for its own sake.

The H2 outline

A brief that has named the intent, the subtopics, and the scope is most of the way to an outline already, so write it down. Turn the required subtopics and the People Also Ask questions into the actual H2 and H3 headings the writer will fill in. This does two jobs at once. It guarantees every required topic has a home on the page, and it gives the writer a structure to write against instead of a blank document and a vibe.

The outline is also where you catch gaps before they cost you a rewrite. If you lay out the headings and realize there is no section answering the top People Also Ask question, you fix it in the brief in thirty seconds, not after the draft comes back. An outline in the brief is the cheapest possible place to find out the page is missing something.

Internal links and one URL per keyword

The brief should name the internal links to include: which existing pages this new piece should link to, and which existing pages should link back to it once it ships. This is how a new page inherits authority from the rest of the site instead of sitting on an island, and it is trivial to specify in the brief and easy to forget at write-time.

The bigger reason this belongs in the brief is keyword mapping. Every target keyword should map to exactly one URL on your site. The moment two of your pages both target "wordpress speed optimization," they compete with each other in the results, split the signals Google would have sent to one strong page, and you end up with two weak pages instead of one good one. That is cannibalization, and the brief is where you prevent it: before assigning the keyword, check that no existing page already owns it. If one does, the job is to improve that page, not write a second one to fight it.

The title and meta angle

Last, the brief names the title and the meta description angle, and it names them on purpose rather than leaving them as an afterthought. The title tag is the single biggest on-page relevance signal and the thing searchers actually click in the results, so it carries the target keyword near the front and a reason to click. The meta description does not directly move rankings, but it moves click-through, and click-through on a ranked result is worth real traffic.

Deciding the angle in the brief keeps the title aligned with the intent you read off the SERP. If the intent is comparison, the title promises a comparison. If it is how-to, the title promises the how-to. A title that promises something the page does not deliver gets the click and then the back-button, and a fast back-button is a signal you do not want to send.

What the whole brief looks like

Put it together and a real brief fits on one screen. Here is the shape of it, and below that a paste-in scaffold you can hand to a model or fill in yourself:

TARGET KEYWORD:   wordpress speed optimization
MAPPED URL:       /learn/performance/wordpress-speed-optimization (new)
                  (checked: no existing page owns this term)

INTENT:           informational, how-to
PAGE TYPE:        step-by-step guide with a checklist
SCOPE:            1,500-1,800 words (top 5 results run 1,400-1,900)

MUST COVER (from ranking pages + People Also Ask):
  - measure first: what a slow score actually means (LCP, TTFB)
  - caching (page cache, object cache)
  - image optimization (formats, lazy-load, sizing)
  - database cleanup
  - hosting and PHP version
  - PAA: "why is my WordPress site so slow?"
  - PAA: "does a caching plugin really help?"

H2 OUTLINE:
  H2 Measure before you optimize
  H2 Caching, the biggest single win
  H2 Images: the other half of the problem
  H2 Clean up the database
  H2 Hosting and PHP version
  H2 A repeatable speed checklist

INTERNAL LINKS:
  link to:   /learn/performance/core-web-vitals-2026-blueprint
  link from: /learn/wordpress (hub), /services/web-development

TITLE:   WordPress Speed Optimization: A Practical 2026 Guide
META:     The exact steps to speed up a slow WordPress site,
          measured, ordered by impact, with a checklist you can reuse.

Every line there is a decision made before writing, and every one of them is a decision the writer would otherwise have made by guessing, or not made at all. That is the difference. The bad brief pushes all of this onto the draft, which is why the draft needs three passes to claw its way toward something rankable. The good brief front-loads it, so the first draft is already pointed at the target.

The method, packed

This brief is one of 31 skills in the SEO Skillpack. The packed version does the slow parts for you: it reads the live SERP for your target keyword, pulls the intent and the page type off the actual results, gathers the entities and questions from what is ranking plus People Also Ask, measures the scope from the pages on page one, and then hands the finished brief straight to the writing step so the draft starts aimed. You do not have to buy anything to use the structure, though. The brief in this article is yours to copy and fill in by hand, and it works exactly the same whether a tool builds it or you do. The pack just builds it for you, every time, in a couple of minutes instead of an afternoon.