Koray Content Brief — Semantic Brief Templates for Writers

Core Concept: What Is a Semantic Content Item Brief?

A content brief is NOT a keyword list or topic outline. It is an algorithmic set of instructions that tells an author what to write, in what order, at what depth, using which entities, with which answer format for each section. A well-built brief removes subjectivity from content production — a writer following it correctly cannot produce an off-brief article.

The brief is built AFTER the topical map and the contextual vector. It operationalizes them.

Brief Components

1. Page Identity

Slug and URL
Title tag (verbalized from entity + attribute)
Meta description (40-55 words, declarative, contains primary entity + attribute)
Target keyword + 3-5 supporting keywords
Central Search Intent statement (copy directly from topical map)

2. Contextual Vector

The complete H1-H3 structure in order. Each heading includes:

Heading text
Answer format required (definition / comparison / procedure / value / Boolean)
Target word count for that section
Key entities to include (minimum 3 per section)
Key context terms (minimum 5 per section)
Featured snippet indicator (yes/no — if yes, first sentence must be 40-60 words, declarative)

3. Entity Checklist

List of all entities that MUST appear in the document:

Primary entities (required in multiple sections)
Supporting entities (required in specific sections only)
Forbidden entities (would create topical confusion — list explicitly)

4. Answer Construction Rules

For each H2 section, specify:

Which answer format applies (see koray-microsemantics for format definitions)
Minimum numeric data points required (0, 1, 2, or 3+)
Citation requirements (none, general, specific institutional source)
Discourse integration note (e.g., "transition from processing time to rejection reasons via bridge sentence")

5. Contextual Borders

Explicit list of what belongs in main content vs. supplementary for this specific page. Prevents writers from burying important entities in sidebars or expanding supplementary beyond its role.

Root Brief vs. Node Brief

Root Brief — For the main document (central entity page, pillar page). Covers the full entity at macro level. Longer, more comprehensive. Internal links seed from here.

Node Brief — For individual attribute pages. Narrower scope, deeper within that attribute. Must include: explicit link instructions back to Root Brief page.

Scalable Brief Templates

When building topical maps with many similar entities (e.g., a visa site covering 30 countries), brief templates allow scaling:

Build the root brief manually for the primary entity (e.g., Germany visa)
Identify template variables: {country}, {processing_time}, {fee_range}, {embassy_location}
Create a template brief where variables can be substituted
Validate template against 2-3 test entities before mass production
Flag entities where the template does not apply (countries with unique requirements get custom briefs)

Quality Gate: Brief Review Checklist

Before sending a brief to a writer:

[ ] Every H2 has an answer format specified
[ ] Minimum entity count per section defined
[ ] Featured snippet targets identified and marked
[ ] Contextual bridges specified between H2 sections
[ ] Forbidden entities listed
[ ] Internal link targets identified (which pages to link to + anchor text)
[ ] Word count per section totals to a realistic overall length

Cross-References

koray-topical-map — brief is built after the map assigns each node
koray-contextual-vector — heading structure from contextual vector populates the brief
koray-microsemantics — answer format definitions for each section
koray-content-audit — audit function verifies the delivered article matches the brief

#seo-sop #seo #semantic #koray #content-brief #algorithmic-authorship