Writing Question-Format Headers

Last updated: June 24, 2026

Most people interact with AI by asking questions. When your H2s mirror the way a reader phrases a query, the engine matches the question directly to your answer block, which dramatically improves your citation odds. This article is about writing the headings (the technical side of hierarchy is covered separately).

Why H2 phrasing is worth the work

Two reasons AI engines weight question-format H2s heavily:

Query alignment. Users ask "what features does X support?" Engines look for pages with headings that match that exact phrasing.
Chunk labeling. Each H2 labels the chunk beneath it. A question-form label tells the engine precisely what question this chunk answers, instead of forcing it to infer.

Flat or statement-form H2s make the engine guess. Question-form H2s tell it.

Before and after

Weak H2 (statement)	Strong H2 (question)
Features	What features does Rankscale support?
Use Cases	Who should use Rankscale?
Pricing	How much does Rankscale cost?
Setup	How do I set up Rankscale in my team?
Integrations	What tools does Rankscale integrate with?
Comparison	How does Rankscale compare to [alternative]?
Benefits	Why use Rankscale over [alternative]?
About Us	What is Rankscale and who built it?

The 4 writing rules

Rule 1: One H1 per page, matching the target prompt. If your prompt is "mobile phone plans," the H1 is "Mobile Phone Plans" or "Best Mobile Phone Plans for [audience]", not your brand slogan or "Welcome to Our Site."

Rule 2: 3 to 8 H2s, all questions. Fewer than three and the page is too shallow for most topics. More than eight and you should split into two pages. Each H2 is phrased as a question a reader would actually type.

Rule 3: H3s are parallel sub-answers. Under "How does Rankscale compare to [alternative]?", the H3s might be "On pricing," "On coverage," "On support." Keep them parallel, short, and scannable.

Rule 4: Never skip a level. H1 → H2 → H3 → H4, never H1 → H3. Skipping breaks chunking logic.

The visual vs. semantic trap

Marketing pages often use styled <div> or <span> tags that look like headings. The visual hierarchy looks right but the semantic hierarchy is empty. Always use real <h1>, <h2>, <h3> tags. If a designer wants more visual control, the styling can be applied on top. Screen readers and AI crawlers only see the semantic tags.

How this works with chunkability

Chunks are bounded by headings. Clean question-format H2s with parallel H3s create cleanly scoped chunks; flat or missing headings create ambiguous chunks that get deprioritized. The two reinforce each other.

Do this now

Open your priority page, list every H2, and rewrite any non-question H2 into a question. Ship the change. It takes about 20 minutes for most pages.

What Is a Content Gap?
Fixing Your Heading Hierarchy
Making Your Content Chunkable for RAG
Writing a BLUF Answer