FAQ / Service Journalism

Platform: All platforms Type: FAQ / Service Journalism Article

⬇ Download this section

Where this format overrides General Guidelines: The headline formula is locked to [Topic] [Question Word]: [Specific Question Answered]—a question-based pattern that replaces the open principles in §1.2 and departs from the [Person/Topic] [Does/Is] [Thing] keyphrase format. The focus keyphrase is structured as an exact search query (e.g., “Social Security check dates 2025”) rather than the General Guidelines format. This format introduces requirements with no brand-level equivalent: a per-block word count (100–200 words per answer block), a mandatory answer-first structure optimized for featured snippet capture, and a 2–3 sentence paragraph maximum. H2 subheadings must include keywords drawn from Google Trends or People Also Ask. Text in red throughout this page marks anything that overrides or goes beyond the General Guidelines.

Purpose

An FAQ / Service Journalism article directly answers reader questions in a scannable, authoritative format. Its purpose is to capture long-tail search traffic, build reader trust, and position the site as a reliable resource for common questions. These articles perform well for People Also Ask (PAA) placements and Google featured snippets. Each H2 answer block is structured so the first 1–2 sentences can be pulled directly as a snippet.

Headline (H1)

(REQUIRED)

Required formula: [Topic] [Question Word]: [Specific Question Answered]

Examples:

Optimize before publishing. FAQ articles often compete directly with existing rich results and PAA boxes. Get the H1 and SEO title right before hitting publish.

SEO Title

(REQUIRED)

Dek

(REQUIRED)

Meta Description

(REQUIRED)

Focus Keyphrase

(REQUIRED)

Type Format
Primary "[Main search query]"—e.g., "Social Security check dates 2025"
Secondary (if applicable) "[Related PAA query]"—e.g., "When do Social Security checks come?"

</span>

Tone

(REQUIRED)

Authoritative, helpful, and conversational—clear and direct without being clinical. Write like you’re explaining something to a smart friend who needs a real answer fast. Confident, specific, and human. Never stiff or institutional.

Word Count

(REQUIRED)

Target: 100–200 words per question/answer block. Word count applies to each H2 answer block individually—not the article as a whole. Keep every block focused; tight, snippet-ready answers outperform padded ones.

Article Structure

(REQUIRED)

The following structure is mandatory for this format. General Guidelines do not prescribe article structure. Each distinct question gets its own H2—add as many H2 blocks as the topic requires.

[AI DISCLAIMER—CUE sites only]
"This article was created by content specialists using various tools, including AI."

[INTRO—1–2 sentences]
- Set up the question: why are readers asking this right now?
- Establish timeliness or relevance
- Get to the point immediately—no throat-clearing

[H2] [Keyword-rich question from Google Trends / PAA]
- Example: When Will Social Security Checks Arrive in April 2025?
- Example: What Happened to [Character Name] at the End of Season 1?

[DIRECT ANSWER—1–2 sentences, snippet-ready]
- This is the answer Google may pull for a featured snippet
- Lead with the answer—do not bury it

[SUPPORTING CONTEXT—2–4 sentences]
- Specifics: dates, dollar amounts, names, official sources
- Include an internal link to a related article where appropriate
- Cite official sources with attribution ("according to")

[Repeat H2 + answer pattern for each question]

[INTERNAL LINKS—embedded throughout body copy]
- 3–5 contextual internal links placed naturally within copy
- Not to be confused with Related Links, which break up inline copy

Formatting Rules

(REQUIRED)

(REQUIRED)

3–5 contextual internal links per article. See General Guidelines §1.4 for full anchor text rules.

Link to:

Hero Image

(REQUIRED)

General Guidelines do not specify image requirements. The following specs are mandatory for this format.

Spec Requirement
Minimum width 1200px (1600px+ preferred)
Aspect ratio 16:9
Resolution 300K+ pixels
Subject Relevant to the article’s topic—a person, place, product, or concept central to the questions answered
Logos NOT permitted
Text overlays NOT permitted
Generic stock NOT permitted

</span>

URL Structure

(REQUIRED)

General Guidelines do not prescribe URL patterns. The following is mandatory for this format.

Tags

(REQUIRED)

General Guidelines do not specify tags. The following are mandatory for this format.

What to Avoid

Prohibited Reason
Burying the answer after the H2 Format requirement—first 1–2 sentences must directly answer; Google pulls the opening lines for featured snippets
H2 headings without Google Trends / PAA keywords Format requirement—H2s must reflect real search queries to capture PAA placements
Vague answers with no dates, names, or specifics Format requirement—vague answers don’t rank and don’t serve readers
Long paragraphs (4+ sentences) Format requirement—readers come for quick answers; paragraphs must stay at 2–3 sentences max
Unsourced factual claims Credibility and Helpful Content risk—cite official sources with attribution; see General Guidelines §1.7
NSFW in any metadata field Suppresses article in feeds—see General Guidelines §1.3
Clickbait or misleading headlines Helpful Content algorithm penalty risk—see General Guidelines §1.2
Generic stock images Format image spec—hero must be relevant to the article’s topic
Affiliate links (unlabeled) Google penalty risk—see General Guidelines §1.4
“Click here” or “read more” as anchor text Poor UX and SEO signal—see General Guidelines §1.4
Publishing without human review Universal compliance rule—see General Guidelines §1.8

Pre-Publish Checklist