Content Briefs: Prevent Thin Pages Before Drafting
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Content Brief Template to Prevent Thin Pages |
| meta_description | Use a content brief template that defines intent, unique value, evidence, artifact, internal links, CTA, measurement, and publish QA criteria. |
| slug | content-briefs |
| primary_query | content brief template for SEO |
| secondary_queries | content brief template for SEO, content brief template for SEO checklist, content brief template for SEO template |
| search_intent | operational checklist |
| canonical_path | /resources/content-thinness-lab/content-briefs/ |
| og_title | Content Brief Template to Prevent Thin Pages |
| og_description | Use a content brief template that defines intent, unique value, evidence, artifact, internal links, CTA, measurement, and publish QA criteria. |
Search Intent
operational checklist. The article must answer the reader's operational question before any commercial route appears.
Reader Artifact
Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.
Internal Links
- Hub: /resources/content-thinness-lab/
- Related article: /resources/content-thinness-lab/thin-page-symptoms/
- Related article: /resources/content-thinness-lab/overlap-map/
- Related article: /resources/content-thinness-lab/rewrite-matrix/
- Related article: /resources/content-thinness-lab/qa-scoring/
- Tool/service route: /services/implementation-sprint/
Structured Data
Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/content-thinness-lab/content-briefs/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.
CTA Route
Primary route: /services/implementation-sprint/.
CTA label: Use the related checklist or diagnostic route.
CTA family: diagnostic_sprint.
Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.
The CTA stays measured and specific, with no public payment or account route on this page.
Measurement
| Event | Name |
|---|---|
| event_view_article | view_article_content_thinness_lab_content_briefs |
| event_click_artifact | click_artifact_content_thinness_lab_content_briefs |
| event_click_cta | click_cta_content_thinness_lab_content_briefs |
| utm_policy | No UTM on internal links; campaign UTMs only during approved external distribution. |
Public-Preflight NG Items
- Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
- Public account, form, payment, repo, domain, or outreach route before checks pass.
- Unapproved cross-brand, unrelated monetization, or off-topic trust route.
- Unsupported claims about SEO, ranking, revenue, or tool behavior.
- Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.
A strong brief makes the page's usefulness testable before drafting starts.
Content Brief Template
| Field | Required answer | Pass criteria |
|---|---|---|
| Page working title | What the page promises | Clear task, not broad topic label |
| Primary query | Main search job | One query, not a keyword pile |
| Search intent | Informational, troubleshooting, operational checklist, comparison, or content diagnostic | Matches title and artifact |
| Reader role | Who uses the page | Specific role or team function |
| Reader problem | What decision or task the page supports | Concrete enough to test |
| Unique job | Why this page exists instead of a sibling | Does not duplicate overlap map entries |
| Thinness risk | Which failure pattern to avoid | Chosen from symptom table |
| Required artifact | Table, matrix, checklist, rubric, runbook, template, or glossary | Reusable outside the article |
| Evidence needed | Source, example, field observation, or internal data type | No invented metrics or unsupported claims |
| Sections to include | Ordered outline | Each section advances the task |
| Sections to avoid | Topics that create overlap | Prevents drift into sibling pages |
| Internal links | Hub and sibling routes | At least hub plus three siblings |
| CTA route | Tool, template, diagnostic, or implementation placeholder | Natural after the artifact |
| Measurement events | View, artifact click, CTA click | Lowercase snake_case names |
| QA threshold | Minimum score before PM review | Defined before drafting |
Brief Example
| Field | Example |
|---|---|
| Page working title | Rewrite matrix for thin content fixes |
| Primary query | content rewrite matrix |
| Search intent | operational checklist |
| Reader role | SEO lead or content operations manager |
| Reader problem | The team has diagnosed weak pages but does not know which action each page needs |
| Unique job | Converts diagnosis into fix action, owner, and acceptance criteria |
| Thinness risk | Adding generic paragraphs instead of choosing action |
| Required artifact | Rewrite action matrix |
| Evidence needed | Symptom table result and overlap map score |
| Sections to include | Action types, matrix, queue template, acceptance criteria |
| Sections to avoid | General content marketing advice already covered elsewhere |
| Internal links | Hub, symptoms, overlap map, QA scoring |
| CTA route | /services/implementation-sprint/ |
| Measurement events | view_article_content_thinness_lab_rewrite_matrix, click_artifact_content_thinness_lab_rewrite_matrix, click_cta_content_thinness_lab_rewrite_matrix |
| QA threshold | 80 or higher with no zero in reader value, differentiation, evidence, route, or technical slots |
Brief Review Questions
Before drafting, ask:
Could a reader reuse the artifact without becoming a customer?
Does the brief explain why this URL should exist?
Does the outline avoid sibling overlap?
Are evidence requirements realistic and non-invented?
Does the CTA match the page's operational task?
Are measurement events planned before publication review?
Is the QA threshold clear enough for a reviewer to reject the draft?
Brief Failure Patterns
| Failure pattern | What it creates | Fix |
|---|---|---|
| Topic-only brief | Generic overview page | Add reader problem, unique job, and artifact |
| Keyword pile | Mixed intent article | Choose one primary query and one search intent |
| No evidence field | Unsupported claims | Define acceptable proof or remove claim-heavy sections |
| No overlap guard | Duplicate sibling | Add sections to avoid and link to overlap map |
| CTA-first brief | Sales-heavy page | Move CTA after artifact and tie it to the task |
| No QA threshold | Endless subjective review | Add scoring criteria before drafting |
Draft Handoff Format
Use this handoff after the brief is approved:
| Handoff item | Required value |
|---|---|
| Approved brief version | Local version label |
| Assigned draft owner | Role, not a private person name |
| Reviewer | Content lead, SEO owner, or marketing engineer |
| Required artifact | Named artifact and table structure |
| Forbidden drift | Topics, claims, routes, and examples to avoid |
| QA score target | Minimum score and zero-score blockers |
| Measurement owner | Role responsible for event naming |
| Publish gate owner | PM review route |
Optional CTA
Use the worksheet placeholder to turn thinness diagnosis into a page brief before drafting. For larger batches, a content diagnostic review can produce standardized briefs and route high-priority pages into an Implementation Sprint. The local route is planning-only until explicit public approval.