The direct answer

Scenario-specific content is written for a named user situation — explicitly describing who the content is for, what constraints they are working within, and what outcome they are trying to achieve. It is the highest-performing ASI format because AI systems match user queries to content by scenario, not by keyword. A page written for a specific scenario gets cited every time an AI encounters a user in that scenario, regardless of the exact words used — which is why well-written scenario pages consistently generate citations from queries the page never explicitly targeted.

Understanding how scenario matching works

When a user tells an AI “I run a small local service business and I want to show up when people in my city ask AI assistants for my type of service — what do I do first?” the AI is not matching keywords. It is matching the described scenario — small local service business, AI visibility goal, wants a first actionable step — to content that addresses that scenario. A page that says “This guide is for local service businesses trying to get cited in AI search” is a direct scenario match. A page that is technically about “AEO for local businesses” but never explicitly names the user situation produces a weaker match.

The three types of scenarios worth writing for

Type 1: Role-based scenarios

These describe the type of person and their professional or situational context. “A freelancer building their first client site,” “A small business owner who handles their own marketing,” “An in-house SEO at a mid-sized company.” Role-based scenarios are the broadest scenario type — they define the audience segment rather than a specific problem. Use them in Who This Is For sections and page introductions.

Type 2: Problem-state scenarios

These describe a specific situation the person is currently in. “You have a site that ranks well in Google but never appears in AI citations,” “You installed Rank Math but are not sure if your schema is working,” “You published a content cluster three months ago and your citation rate has not improved.” Problem-state scenarios are the highest-value type for citation because they match the exact framing of AI queries that include a problem description — which is the majority of high-intent AI queries.

Type 3: Constraint-based scenarios

These describe the limitations the person is working within. “Using free tools only,” “without a developer or technical help,” “on a tight timeline,” “managing multiple client sites simultaneously.” Constraint-based scenarios match queries where the constraint is stated explicitly — “I need to set up AEO without paying for any tools” — and also serve as differentiation that narrows your content to the specific audience it serves best.

How to write scenario-specific content: step by step

1. Name the scenario in the title or H1 — “AEO for Local Service Businesses” rather than just “AEO Implementation Guide.” The scenario in the title is the first signal AI systems use to match query to content.
2. Open with the scenario framing — the first two sentences should confirm who the page is for and what situation it addresses. This reinforces the title scenario match for AI systems reading the page top-to-bottom.
3. Write the body for the scenario, not the general topic — every example should be from the named scenario. A page for local service businesses should use local service business examples throughout, not generic website examples that could apply to anyone.
4. Include the scenario constraints in your recommendations — “using Rank Math free tier” not just “using Rank Math,” “for a one-person team” not just “for your team.”
5. End with the scenario-specific next step — the concluding call to action should reflect the scenario. “If you are a local service business starting from scratch…” is more effective than a generic “start implementing AEO today.”

How this connects to the other five disciplines

ASI is a writing discipline applied to every piece of content you publish — it works in combination with AEO (which structures pages for extraction), GEO (which builds topical authority), ANI (which ensures AI crawlers can access and read your content), and SEO (which handles keyword rankings and technical health). Content that is well-structured for AEO extraction, lives on a topically authoritative GEO site, is accessible to AI crawlers via ANI, and is written conversationally for ASI matching consistently outperforms content that only addresses one or two of these disciplines.

The ASI implementation habit

Unlike ANI (largely a one-time technical setup) or GEO (a content architecture project), ASI is a continuous writing practice. Every piece of content you publish should pass the read-aloud test, include a Who This Is For section, use second person throughout, and have a TL;DR box if it is over 1,000 words. Building these habits into your standard writing process takes about two weeks of conscious practice before they become automatic.

For existing content, prioritize your top 10 pages by traffic and do a full ASI retrofit on each — adding the TL;DR box, Who This Is For section, and voice pass. These pages already have traffic and topical authority signals working in their favor. Adding ASI improvements on top of existing content that is already being crawled produces the fastest citation rate improvements of any single optimization action available.

Related ASI guides

How to write a Who This Is For section · TL;DR boxes for AI citation · The full ASI checklist

The complete ASI guide library at teachmeoptimization.com/asi covers all 10 topics — from understanding how AI users phrase questions to the writing techniques that generate the most citations.