Who Is This For? Audience Block Rules

A Who is this for block is a short qualification element near the beginning of a page. It names the people, situations, and constraints the page serves so a reader can decide whether to continue. A clear “not for you” decision is a successful outcome: it prevents wasted reading and poor-fit conversion.

Who is this for?

This specification is for content designers, SEO leads, and developers building reusable page systems where audience fit changes the advice or offer. It is not for pages whose title already identifies one unambiguous audience, or for teams using persona labels without observable needs or constraints.

Why this element matters

Attention has an opportunity cost. Before a reader accepts a page’s argument, instructions, or offer, they quietly ask, “Was this made for a situation like mine?” If the page forces them to infer the answer from several sections, every claim remains provisional. A qualification block settles that question early and gives the remaining content a clear frame.

This is why a page that tries to serve everyone often converts nobody. Broad promises such as “for teams of every size” remove the distinctions people use to judge relevance: their goal, level of control, available resources, risk, and required outcome. The copy can sound inclusive while failing to give any reader a decisive reason to trust the fit. Narrowing the audience does not reduce the usefulness of a genuinely broad offer; it explains the specific conditions under which that offer becomes useful.

Leaving early is not a lost conversion. A reader who discovers that a guide assumes developer access, or that a service starts with a six-month engagement, has learned something valuable before investing more time. The publisher avoids an unqualified lead, avoidable support work, or a disappointed customer. Honest exclusion can therefore be part of good conversion design, provided it describes real boundaries rather than manufacturing scarcity.

The same explicitness helps machines. Machine extractability means a bounded passage retains its meaning when a search system, retrieval model, or agent reads it away from the surrounding page. An audience block combines a named subject with observable fit conditions. A machine can associate the page with “in-house SEO teams managing multiple sites” more reliably than with a vague claim such as “built for ambitious businesses.” This does not guarantee ranking or citation; it reduces ambiguity about who should apply the page’s advice.

When to use it

Use this element when audience fit changes what follows. The change may affect eligibility, prerequisites, recommended option, implementation path, purchasing decision, or expected outcome. A technical guide that assumes command-line access, a buying guide for teams above a defined data volume, and a service page limited to regulated organizations all benefit because proceeding without that context could lead to the wrong decision.

Use it when a page serves several named segments but gives each one a distinct reason to continue. “For agency owners managing 10–50 client sites” and “for in-house leads consolidating three regional sites” are useful because scale and operating model affect the workflow. Segment labels earn their place by predicting a material difference, not by filling a card grid.

Near-miss cases are common:

• A generic persona list: “marketers, founders, and creators” does not qualify anyone unless the page states the shared problem or the different fit condition for each group.
• A demographic profile: age, location, company size, or industry should appear only when it changes the problem, access, compliance duty, price, or result.
• A benefits summary: “save time, grow traffic, and work smarter” describes hoped-for outcomes, not who can realistically obtain them.
• A prerequisites box: required accounts, permissions, tools, and inputs may deserve their own checklist. The audience block may mention one decisive constraint but should not become setup documentation.
• A disclaimer: legal, medical, financial, or safety limitations require explicit policy language in the relevant position. Do not soften them into audience copy.

Omit the block when the H1 already qualifies the reader completely, such as “VAT filing checklist for UK sole traders,” and no additional fit condition changes the instructions. Also omit it on short universal references where qualification would merely repeat the title. An element must earn attention; routine insertion weakens its signal.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Where to place it

Qualification only saves time when it arrives before commitment. Place the block after the page’s direct answer or short introductory promise and before the first detailed section. On a commercial page, it should appear before feature grids, pricing comparisons, proof, or a lead-generation form. On an editorial page, it should appear before the table of contents when audience choice changes which sections matter; otherwise it may sit immediately after that navigation aid.

The block must not sit directly beside a competing callout, advertisement, newsletter capture, testimonial, trust-badge row, price card, or primary call to action. Those elements ask for attention, belief, or action; the audience block asks for an unpressured fit decision.

Anatomy

The element contains a visible label, one framing sentence, a set of positive fit conditions, and an optional exclusion. Each condition combines an identifiable reader or situation with the reason it matters. The exclusion describes a genuine mismatch and, when possible, points toward a more suitable route without turning into a promotional CTA.

1. Label: uses the literal question “Who is this for?” so the purpose is clear without color or iconography.
2. Frame: states the shared job, decision, or outcome in one sentence.
3. Fit conditions: name 2–4 audiences or observable situations and explain why each belongs.
4. Exclusion: names the decisive mismatch in calm language; it is optional only when no meaningful exclusion exists.
5. Boundary: visually groups the content, but the text and document order must preserve meaning if styling disappears.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Design examples

Three variants cover the useful information shapes. Choose by the number of genuine distinctions, not by the amount of empty space in the layout.

The compact variant is the default for one audience with one or two fit conditions. The split variant is appropriate when exclusion prevents a costly mistake and deserves equal visibility. The cards variant works for two to four segments whose reasons for continuing genuinely differ. Do not create a carousel: qualification choices must remain visible together and readable without interaction.

Parameters

Parameters keep qualification logic separate from decorative presentation. The limits prevent the component from expanding into a persona report, benefits section, or hidden policy notice.

The exclusion becomes required when a known mismatch would make the instructions invalid, the recommendation unsuitable, or the offer unavailable. Follow the shared element writing rules for the precedence rule: use this typed element when the passage performs audience qualification; platform syntax or visual convenience does not justify flattening it into free text or repurposing another box.

Syntax and code examples

All three representations below carry the same title, fit conditions, exclusion, and split variant. The portable directive is the canonical content model; adapters should preserve it without inventing platform-specific copy.

Portable Markdown directive

:::who-is-this-for{variant=split}
## Who is this for?

::audience{label="In-house SEO leads"}
Use this playbook when you own standards across several writers, sites, or markets.
::

::audience{label="Content system designers"}
Use it when reusable components must preserve meaning across publishing platforms.
::

::not-for
This is not a fit for a one-off personal article with no repeatable production workflow.
::
:::

Hugo shortcode

{{< who-is-this-for variant="split" >}}
## Who is this for?

{{< audience label="In-house SEO leads" >}}Use this playbook when you own standards across several writers, sites, or markets.{{< /audience >}}
{{< audience label="Content system designers" >}}Use it when reusable components must preserve meaning across publishing platforms.{{< /audience >}}
{{< not-for >}}This is not a fit for a one-off personal article with no repeatable production workflow.{{< /not-for >}}
{{< /who-is-this-for >}}

WordPress block

<!-- wp:amicited/who-is-this-for {"variant":"split"} -->
<h2>Who is this for?</h2>
<!-- wp:amicited/audience {"label":"In-house SEO leads"} -->
<p>Use this playbook when you own standards across several writers, sites, or markets.</p>
<!-- /wp:amicited/audience -->
<!-- wp:amicited/audience {"label":"Content system designers"} -->
<p>Use it when reusable components must preserve meaning across publishing platforms.</p>
<!-- /wp:amicited/audience -->
<!-- wp:amicited/not-for -->
<p>This is not a fit for a one-off personal article with no repeatable production workflow.</p>
<!-- /wp:amicited/not-for -->
<!-- /wp:amicited/who-is-this-for -->

These examples define a portable contract; they do not claim that every renderer is already registered. Until a platform implements the typed component, render the same structure as a labelled semantic section with a heading and list. Do not substitute a warning, because being outside the intended audience is not inherently dangerous or incorrect.

Examples

Good: observable fit with an honest exit

Who is this for?

This migration checklist is for technical SEO leads moving more than one hostname while preserving existing URL equity, analytics continuity, and rollback options. It is not for a simple domain redirect with no CMS, template, or tracking changes; use the registrar’s verified redirect procedure instead.

This works because the role is connected to a task, scale, and consequences. A reader can test “more than one hostname,” “analytics continuity,” and “rollback options” against reality. The exclusion describes a different job and gives a neutral next route.

Bad: everyone is welcome, nobody is qualified

Perfect for everyone

Whether you are a founder, marketer, enterprise leader, freelancer, beginner, or expert, this powerful guide is for anyone who wants better results and faster growth.

This fails because the labels cover nearly every possible reader while predicting nothing about the page’s usefulness. “Better results” and “faster growth” have no defined measure. “Powerful” is unsupported promotion. A poor-fit reader cannot identify a reason to leave, and a strong-fit reader receives no evidence that the page understands their situation.

Schema markup and accessibility

The block does not create a standalone Schema.org entity. On an editorial page, it remains part of the enclosing Article, TechArticle, or WebPage. On a genuine product or service page, the same audience facts may inform supported audience properties only when the site’s structured-data policy and the real offer justify them. Do not copy aspirational persona language into JSON-LD, and do not mark each audience item as a separate FAQ, review, or HowTo step.

Its machine value comes primarily from visible content and document structure. The element binds a page subject to an audience, task, and constraint in a short passage. Structured data must reflect that visible meaning; it cannot repair vague qualification copy.

For accessibility, use a real heading and a semantic list when there are several items. Keep positive and negative fit labels in text rather than expressing them only through green and red colors, checkmarks, or crosses. Do not hide exclusions behind an accordion or tooltip. Preserve a logical reading order on narrow screens: title, framing sentence, suitable audiences, then exclusions.

The block is informational, not interactive. Cards must not receive button roles unless they actually navigate. If an item links to a more appropriate resource, use descriptive anchor text and leave the rest of the card non-clickable. A screen-reader user should hear the same qualification logic as a sighted reader without needing visual position to infer “good fit” versus “not a fit.”

Writing rules

Qualification works only when readers can test it against observable facts. Begin with the shared job or decision, then name the condition that changes the page’s value. “For teams publishing in five or more markets” is testable; “for ambitious teams” is not. Every label must earn its place by predicting a relevant need, constraint, workflow, risk, or outcome.

Use these limits:

• Use one block per page, with one visible title.
• Write 1–4 positive audience items; prefer 2–3 when the page serves distinct segments.
• Keep each label to 2–8 words and each reason to 8–30 words.
• Use no more than two exclusions, each 15–35 words.
• Keep the complete block between 50 and 180 words, excluding the heading.
• Use at most one link, and only when it gives a poor-fit reader a clearly better route.

Tone matters because exclusion can easily become contempt. State mismatches calmly and specifically: “not designed for teams without access to server configuration,” not “not for beginners.” Describe the missing condition, not a judgment about the person. Prefer “use this when” and “choose another route when” over “only serious companies qualify.”

Never put unsupported superlatives, invented urgency, pricing, testimonials, conversion buttons, legal disclaimers, safety warnings, sensitive demographic profiling, or an exhaustive persona biography inside the block. Do not promise an outcome merely because someone matches the audience. Fit means the page or offer is relevant, not that success is guaranteed.

When several audiences need different instructions, the block may qualify them at the top, but it cannot replace routing in the body. Give each audience a clearly headed path or publish separate pages if their goals, evidence, and actions diverge substantially.

Post types that use it

The postTypes array is the source of truth for this mapping. The element is conditional in every type: include it only when fit changes the content, recommendation, or offer.

QA checklist

• The block helps a reader make a real continue-or-leave decision.
• Every audience label is paired with a need, task, constraint, risk, or outcome.
• The complete block remains between 50 and 180 words and contains no more than four positive items.
• Any exclusion describes an observable mismatch without belittling the reader.
• A known invalidating mismatch appears explicitly rather than being hidden later.
• The block follows the opening answer or promise and precedes detailed content or commercial conversion elements.
• It does not sit beside a CTA, form, price, testimonial, trust badges, advertisement, or competing callout.
• The title, positive fit, and exclusion remain understandable without color, icons, or card position.
• Lists use semantic list markup, cards are not falsely interactive, and mobile reading order is logical.
• The content does not duplicate prerequisites, benefits, disclaimers, or the page title.
• Markdown, Hugo, and WordPress representations preserve the same fields and item order.
• The selected post type appears in postTypes, and the block’s placement matches the mapping above.
• The typed element follows the shared precedence and mapping rules rather than borrowing a generic callout.

FAQ

The questions below cover the decisions most likely to cause misuse: whether the element is required, whether an early exit counts as failure, which audience labels are valid, whether conversion belongs inside the block, and whether structured data is necessary.