What Is X Pages: Structure and Examples
Build a what-is page that answers a question in 40–60 words, explains the concept through examples and boundaries, and prevents glossary cannibalization.
A what-is page answers a named question by defining the subject in 40–60 self-contained words, then expanding from simple meaning to precise boundaries, purpose, mechanics, examples, mistakes, exclusions, and related concepts. It serves a curious reader who may stop after the first paragraph or continue until they can explain the subject accurately.
Purpose: turn an unfamiliar or ambiguous concept into a clear mental model without forcing the reader through a complete field guide.
Reader question: “What is X, what does it mean in practice, and how is it different from the things I might confuse it with?”
This awareness-stage format belongs in the SEO post types system because definition queries need a distinct answer shape. The opening is the answer; every later section earns its place by making that answer more precise, useful, or difficult to misapply.
Questions it answers
Readers rarely ask only for a dictionary sentence. Their query may be two or three words, but the real questions usually unfold in this order:
- “What is X in plain English?”
- “What exactly counts as X?”
- “Why does X exist, and what problem does it solve?”
- “How does X work?”
- “What would X look like in a concrete situation?”
- “Why do people misunderstand or misuse it?”
- “What is close to X but not actually X?”
- “Which related idea should I understand next?”
The page supports two reading modes: a complete answer in the first 40–60 words and a deeper explanation that never contradicts that definition.
When to use this post type
A short reference definition and a question-led explanation solve different information problems. A glossary term page is anchored on a term: it supplies a canonical meaning, usage, aliases, and relationships that remain useful when readers arrive from elsewhere on the site. A what-is page is anchored on a question: it has room for context, origin, implications, examples, misconceptions, and the reasons the concept matters.
The distinction prevents a common information-architecture error: two pages making the same promise. Keyword cannibalization occurs when multiple pages compete for substantially the same query and purpose, obscuring which one is canonical. Avoid it by assigning each format a different job.
Give a topic both pages only when the term needs a stable reference, research shows demand for a fuller explanation, and the explainer can complete the depth ladder. Let the glossary own “X definition,” aliases, and brief distinctions. Let the what-is page own why it exists, how it works, examples, mistakes, and consequences. Link both ways, labeling the glossary as the terminology reference and the explainer as the deeper treatment.
| Choose this type | When the reader’s main job is | Expected answer shape | Do not use it when |
|---|---|---|---|
| What-is page | Understand a concept from first principles | 40–60-word answer followed by a depth ladder, example, boundaries, and related concepts | The page would only restate a short reference definition |
| Glossary entry | Look up a term and verify its canonical meaning | Concise definition, aliases, usage, and nearby terms | Context, mechanics, history, and implications are the real value |
| Ultimate guide | Master a broad subject with several subtopics | Comprehensive hierarchy, evidence, tools, decisions, and next actions | One question and one central concept define the scope |
| How-to guide | Complete a procedure and verify the outcome | Prerequisites, ordered steps, checkpoints, and troubleshooting | The reader first needs understanding rather than instructions |
Ready to Monitor Your AI Visibility?
Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.
Best for these business types
The format is useful across business models, but not equally urgent. Rank it by how often the business must explain a category, method, technical mechanism, or unfamiliar buyer problem before a commercial page can make sense.
- SaaS . SaaS companies often sell a new category or technical capability. The explainer builds the model prospects need before product, use-case, and comparison pages; it should stay educational rather than turn immediately into a pitch.
- B2B services . Buyers need shared vocabulary for methods, risks, regulations, and service models before evaluating providers. A clear explainer also demonstrates subject competence.
- Media publishers and affiliates . Durable explainers support topic coverage and give comparisons or listicles a precise destination for readers missing background.
- Ecommerce . Shoppers may need to understand a material, standard, mechanism, fit, or compatibility term before choosing. Teach the category before routing qualified readers to products.
- Marketplaces . Explain the transaction model, participant roles, trust mechanism, or category vocabulary. Name the participant in scope rather than mixing buyer and provider questions.
- Local services . Use this selectively for unfamiliar diagnoses, methods, legal concepts, or technical terms. Familiar services normally need a service page instead.
Search intent
Search intent is the purpose behind a query. For “what is X,” the dominant intent is informational: the reader wants meaning before evaluation or action. Search modifiers reveal the depth required. “X meaning” may tolerate a compact reference; “what is X and how does it work” asks for mechanics; “what is X in marketing” adds a domain boundary; “X examples” makes abstraction the problem.
Review the current search engine results page and AI answers before drafting because answer shapes change by subject and market. Record whether results lead with a definition, favor reference sources, include diagrams, or expose follow-up questions. For AI answers, record the definition, retained qualifiers, citations, and near-miss contrasts.
Use the review to identify the minimum answer contract and an unanswered need, not to imitate ranking copy. Keep one direct answer after the H1 and put essential qualifiers there because extraction may separate it from later caveats.
Stay Updated on AI Visibility Trends
Get the latest insights on AI mentions, brand monitoring, and optimization strategies.
Page structure
The ranges are controls, not quotas. Depth means resolving distinct questions, not repeating the definition with new adjectives.
| Section | Word range | Purpose | Status |
|---|---|---|---|
| Direct definition | 40–60 | Answer the H1 completely, naming the subject, category, distinguishing feature, and essential qualifier | Required |
| Plain-language orientation | 80–150 | Translate the definition into everyday language without replacing its precise terms | Required |
| Precise definition and scope | 120–220 | State what qualifies, where the definition applies, and which boundary conditions matter | Required |
| Why it exists | 150–250 | Explain the problem, limitation, or historical condition that made the concept useful | Required |
| How it works | 250–450 | Describe the mechanism or sequence at conceptual level, not as a task tutorial | Required |
| One disciplined analogy | 60–120 | Supply one mental model and state exactly where the analogy stops being accurate | Conditional: use when mechanics remain abstract |
| Concrete example | 180–300 | Trace one realistic case from inputs through mechanism to observable result | Required |
| Where people get it wrong | 150–250 | Correct common reasoning, implementation, or interpretation errors | Required |
| What it is not | 150–250 | Resolve two to five near-miss confusions with explicit contrasts | Required |
| Implications | 150–300 | Explain what changes for the reader, organization, or system once the concept is understood | Conditional: use when consequences are material |
| Related concepts | 100–180 | Define the relationship to prerequisite, sibling, and next-step concepts | Required |
| FAQ | 200–400 | Answer five to eight residual questions that are not repetitions of headings | Required |
| CTA | 30–80 | Offer one next action matched to an awareness-stage reader | Required |
An analogy trades precision for familiarity. Use one, label it “Analogy,” and state its limit; stacked comparisons obscure the mechanism.
Required elements
Reusable elements have canonical specifications; ordinary sections do not. The example, “what it is not” list, and diagram remain anatomy requirements without being invented as new element types.
| Element | Always or conditional | Exact position | Why |
|---|---|---|---|
| Direct answer block | Always | Immediately after the H1 | It satisfies the query before navigation, scene-setting, or promotion can delay the answer |
| Definition box | Always, merged with the direct answer | Same opening position; one box, not two repeated blocks | On this post type, the definition and direct answer perform the same job and must share one canonical wording |
| Annotated screenshot | Conditional | Beside the first passage that explains a user interface or observable visual state | It turns an otherwise vague interface reference into inspectable evidence; use a conceptual diagram instead for an abstract mechanism |
| Related content block | Always | After related concepts and before the FAQ or CTA | It offers a glossary reference, a broader guide, or a procedure without expanding this page beyond its question |
| FAQ structure | Always | After the main explanation and before the CTA | It resolves real follow-up questions while keeping the main depth ladder coherent |
| CTA block | Always | Final authored element | It gives an informed reader one relevant continuation instead of interrupting the explanation with sales copy |
| Frontmatter specification | Always | Document metadata, before rendered body content | It gives the page a stable entity, taxonomy, schema inputs, and synchronized FAQ records |
Frontmatter
The entity is the subject, not the question wording. For “What Is Content Pruning?”, use entity = "content-pruning", not entity = "what-is-content-pruning". Titles may change while the entity remains stable.
Use Article as the primary schema type and identify the subject through about when supported. Add FAQPage only when visible answers, frontmatter, and structured output match and current policy permits it. Do not mark the whole article as DefinedTerm; this is a question-led article, not the concept record itself.
| Field | Required value or rule |
|---|---|
title | Natural question title: What Is [X]? or What Does [X] Mean? |
seoTitle | Primary question plus a useful differentiator; do not stack synonyms mechanically |
entity | Canonical subject identifier, normalized and stable, such as content-pruning |
description | 150–160 characters; answer what the page explains and give a reason to click |
type | academy |
playbookPillar | post-type for this specification; use the site’s normal taxonomy on produced articles |
playbookFamily | definition-and-entity |
journeyStage | awareness |
elements | Ordered list of rendered elements actually present |
businessTypes | Only models the subject genuinely serves, in priority order |
schemaType | Article; optionally an additional FAQPage node when eligible |
date and lastmod | Publication and material-review dates; update lastmod when meaning, examples, or boundaries change |
keywords | Six to eight natural variants and domain qualifiers used for editorial scope, not repetition |
[[lnks]] | One record for every internal body link, with anchor text matching text exactly |
[[faq]] | Five to eight records, identical to the visible questions and answers |
Full example
This copy-pasteable skeleton uses a real subject. Replace each bracketed content contract with researched copy; the opening definition already demonstrates the required length.
# What Is Content Pruning?
Content pruning is the deliberate process of removing, merging, redirecting, or substantially improving pages that no longer serve a useful audience or business purpose. It is not indiscriminate deletion: each URL is evaluated against evidence, site structure, and future value before a team decides to keep, update, consolidate, redirect, or retire it.
## Content pruning in plain English
[Explain how pages become outdated or overlapping and why pruning chooses a useful future state rather than merely reducing URL count.]
## The precise definition and scope
[Define the evaluated unit, evidence window, possible actions, and approval boundary. Distinguish pruning from routine edits and technical cleanup.]
## Why content pruning exists
[Explain how facts, products, and page purpose change, and why leaving every URL untouched has a maintenance cost.]
## How content pruning works
[Describe inventory, evidence gathering, classification, action selection, dependency review, publication, and monitoring. Reserve execution details for a how-to.]
### Analogy: tending a reference library
[Map page maintenance to tending a reference library, then state the limit: URLs have links, redirects, search history, and conversion paths.]
## A concrete content-pruning example
[Trace three overlapping articles through evidence review, merge, redirect, and monitoring decisions.]
## Where teams get content pruning wrong
[Explain deleting by traffic alone, ignoring seasonality or links, merging different intents, and making changes without a baseline.]
## What content pruning is not
- It is not deleting every low-traffic URL; some pages serve narrow but important audiences.
- It is not rewriting every old article; unchanged pages may still be accurate and useful.
- It is not a one-time purge; the library needs a review cadence and decision history.
- It is not a substitute for fixing crawl, indexing, measurement, or product problems.
## What content pruning changes
[Explain clearer topic ownership, current answers, simpler maintenance, and better reader routes without promising rankings.]
## Related concepts
[Relate consolidation, redirects, audits, information architecture, and governance; link only to destinations with distinct jobs.]
## FAQ
[Add five to eight residual questions about evidence windows, redirects, seasonality, approval, monitoring, and reversal.]
## Decide the next action
[Offer one continuation: a related concept, procedural guide, or inventory evaluation.]
Design examples
The gallery tests hierarchy, not decoration. Every capture uses the same content-pruning example and keeps the answer immediately after the H1.
Replace comments only when the exact files exist. The diagram must explain relationships or flow; decoration does not satisfy the requirement.
Quality checklist
A reviewer should be able to check every criterion against visible copy, not infer compliance from the writer’s intention.
- The first 40–60 words answer the H1 without preamble, undefined pronouns, or dependence on the next paragraph.
- The opening answer names the subject’s category, distinguishing feature, and any qualifier that changes the meaning.
- Plain-language orientation and precise scope add different value instead of paraphrasing each other.
- The page completes the ladder: answer, definition, purpose, mechanics, example, mistakes, exclusions, and related concepts.
- One concrete example traces the concept through recognizable inputs, mechanism, and result.
- Any analogy is explicitly labeled, used once, and followed by its limit.
- “What it is not” contrasts two to five genuine near misses and explains the decisive difference.
- A diagram is included when relationships or flow would otherwise require a dense explanation; its caption carries the essential meaning.
- The glossary and what-is pages have distinct titles, primary queries, scopes, and internal-link roles when both exist.
- Every factual claim that could change has a source and checked date in the production evidence record.
- Five to eight FAQs answer residual questions and match the frontmatter records exactly.
- The final CTA offers one awareness-appropriate next action.
Common mistakes
- Delaying the definition. A story, trend claim, or sales introduction before the answer breaks the format’s central promise.
- Writing a circular definition. “AI visibility is how visible you are in AI” repeats the label without adding meaning.
- Defining jargon with jargon. Opening terms must be familiar, defined inline, or introduced immediately afterward.
- Publishing a glossary article twice. A longer word count does not create an explainer if both pages own the same query and sections.
- Turning “how it works” into a tutorial. Detailed steps, prerequisites, and troubleshooting belong in a procedural sibling.
- Stacking analogies. Use one labeled analogy with a stated limit.
- Omitting exclusions. Without “what it is not,” readers can leave with a plausible but wrong near-miss interpretation.
- Listing related terms without relationships. State whether each is a prerequisite, component, sibling, alternative, or consequence.
- Claiming universal benefits. Explain consequences under named conditions; do not promise rankings, revenue, safety, or compliance.
Internal linking
The what-is page should receive links from glossary entries, guides, product education, use cases, comparisons, and academy documentation that use the concept. Put the first useful link where the concept becomes necessary and use descriptive anchor text.
Link outward according to the reader’s next unresolved job:
- Link to the glossary for canonical terminology, aliases, or a concise reference.
- Link to a broader guide for the surrounding field.
- Link to a procedure when understanding is complete and the next question becomes “How do I do this?”
- Link to a product or use case only after the educational explanation makes its relevance clear.
- Link to prerequisite and adjacent concepts with their relationship stated; select two to four for the closing block.
Do not duplicate the glossary’s reference job, the ultimate guide’s breadth, or the how-to’s procedure. Connect glossary and explainer in both directions with explicit promises such as “how X works” and “X definition and terminology.”
How to measure results
Measure answer discovery, correct understanding, and useful continuation. Baseline the primary question, meaning and domain variants, and two or three near-miss questions before publication. Use AmICited prompt tracking to check whether AI answers mention the entity and preserve its qualifier.
Review source and citation intelligence to see whether the page itself is cited for those prompts and whether another site is being used for the definition, example, or contrast. In the AmICited Cockpit , compare visibility and citation movement with organic impressions, engaged visits, movement to the selected related pages, and the final CTA action. A citation that strips the qualifier or confuses the entity is not a clean win, even if the brand is mentioned.
Use the SEO results framework to choose an action after a defined observation window: keep, refresh the opening answer, strengthen the example, clarify a boundary, consolidate an overlapping page, or change the internal-link route. Do not attribute a commercial outcome to this page from timing alone; its awareness job often contributes before a later page converts.
FAQ
How long should a what-is page be?
Use the shortest length that completes the depth ladder. Most substantial subjects need roughly 1,200–2,500 words, but scope, ambiguity, and the number of useful examples matter more than a fixed total.
What is the difference between a what-is page and a glossary entry?
A glossary entry is a stable reference for a term. A what-is page answers a question and can develop why the concept exists, how it works, examples, mistakes, boundaries, and implications.
Can a topic have both a glossary entry and a what-is page?
Yes, when readers need both a canonical term reference and a substantial question-led explanation. Give each page a distinct job, use different primary queries, and link them in both directions.
Should a what-is page include steps?
Only a short process overview when steps are necessary to explain how the subject works. If completing the procedure is the reader’s main goal, publish a separate how-to guide.
Should the direct answer and definition box repeat each other?
No. On a what-is page they perform the same opening job, so combine them into one 40–60-word definition box immediately after the H1.
Does a what-is page need FAQ schema?
Not automatically. Write five to eight visible FAQs when real residual questions remain, and add FAQPage schema only when the implementation matches the visible answers and current search-engine policies.
Build the first answer before the rest of the page
Start with the reader’s exact question, draft the 40–60-word answer, and test whether it survives when copied alone. Then use the depth ladder to prove, illustrate, qualify, and connect that answer. Open the AmICited Cockpit to baseline the question and its near-miss variants before publication.
More tutorials in this section
Ready to put it into practice?
Free check · 7-day trial · no credit card