Choose one specific question your ideal client is already asking an AI, write a complete 40–60 word direct answer as your opening paragraph, then expand with H3 subheadings and structured detail. The question becomes your H1. That structure — query headline, direct answer, supporting depth — is an authority node.
The most common mistake is writing in essay format: building context before delivering the answer. AI systems extract the first substantive prose block as their citation — if the answer is buried in paragraph three, the page will not be cited. [1][2] The answer must be first.
Pick a question you answer instinctively on every client call. You already know this answer cold — the writing challenge is not knowledge, it is structure. Answer first, expand second.
- The H1 headline is a full question — not a topic title, not a keyword phrase, but the actual question your ideal client types into an AI.
- The opening paragraph is the citation block — 40–60 words of plain prose that answers the question completely enough to stand alone.
- H3 subheadings organize the supporting detail after the direct answer — they help both AI systems and readers navigate depth without obscuring the extractable block.
- One question per node — nodes that try to answer multiple questions become unfocused and fail to match any single query precisely.
- Write what you already know — the best first nodes are answers you have already given a hundred times; the structure is the work, not the expertise.
Get Recommended by AI
-
1
Watch the free training 3 Roadblocks to Getting AI-Recommended
-
2
Get Aligned See exactly how AI interprets your business right now
-
3
Get Activated™ Install the framework. Make the shift.
-
4
Join Collective Wisdom Our implementation ecosystem.
How do I choose the right question for my first authority node?
Choose the question your ideal client asks most often before they become a client — the one that comes up on every discovery call, in every initial email, in every comment on your content. That question is already validated demand. You know the answer. You know how to say it clearly. That is your first node.
The question selection framework
High-value node questions have three qualities:
- Specific — not "how do I get clients" but "how do I get my first consulting client without a referral network"
- Query-phrased — written the way a person would type it into ChatGPT, not as a topic heading
- Answerable in depth — you have enough to say to fill a substantive page (300–600 words), not just a sentence
- The question you answer on most first calls
- The most common question in your intake form or DMs
- The most-repeated comment on your content ("I always wonder about...")
- The question a new client asks before they understand your framework
Where to find your first question
How long should an authority node be?
An authority node should be as long as it takes to answer the question fully — typically 400 to 800 words for the main content, plus structured elements (H3 subheadings, bullets, tables). There is no minimum for AI citation value; a precisely structured 400-word node will be cited far more often than a loosely written 2,000-word post that buries the answer.
The right length for each section
Opening direct answer block: 40–60 words. Complete sentence. No heading above it. Stands alone.
H3 sections with supporting detail: Each section 100–200 words. Bullets, tables, and numbered lists welcome.
Total page target: 400–800 words for a focused node. More is acceptable if it adds genuine depth — not if it pads a thin answer.
When longer is appropriate
Some questions legitimately require more space: comparative questions needing a table, or multi-step implementation questions needing a numbered process. Length is earned by the question, not imposed for perceived authority.
The test
Read your node aloud. If you can feel yourself repeating points or circling the answer rather than deepening it, cut. The goal is density, not length.
What is the right structure for an authority node?
The structure of an authority node follows a strict sequence: H1 (the full question), extractable answer block (40–60 word prose, no heading above it), then H3-organized supporting sections with detail, examples, or tables. This sequence is not aesthetic — it is functional. AI systems extract based on position and structure.
The canonical node structure
```
H1: Full query as a question
[40–60 word direct answer — NO heading above this paragraph]
A complete, standalone answer to the question. Plain prose. Citable.
H3 Subheading
Supporting detail, examples, step-by-step breakdown.
Another H3 Subheading
More depth, comparison table, common mistakes.
Another H3 Subheading
Implementation steps or next-action guidance.
```
What kills the structure
- Heading above the answer block: Any H2 or H3 before the direct answer pushes the extractable content down the page. Remove it.
- Intro paragraph before the answer: "In this article, we'll explore..." is not an answer. Delete it.
- The answer buried in bullet three: AI systems extract prose paragraphs, not bullet list items. The direct answer must be prose.
- No H3 subheadings: Unstructured body text with no subheadings signals low organization to AI crawlers.
How do I add citations to an authority node?
Use inline markdown-style citations in your node body: hyperlink the source text directly to the URL rather than using numbered footnotes. For example: write "according to Search Engine Journal, answer engine optimization..." rather than "according to Search Engine Journal [1]." This format is more legible to both AI systems and readers.
Citation best practices for authority nodes
Only cite real, verified sources. Do not link to sources you have not read. Do not fabricate URLs. If you cannot find a reliable source for a claim, either find one before publishing or reframe the claim as your professional observation.
Prefer primary sources. Research institutions, university studies, platform documentation, and original research reports carry more authority signal than aggregator articles citing other articles.
Cite in the body, not just the footer. In-text citations where the source is hyperlinked in the relevant sentence carry more weight than a bibliography at the bottom of the page.
Two to three citations per node is sufficient. You are not writing an academic paper. One strong citation for a key factual claim is better than five weak ones for general statements. Quality of sourcing matters more than quantity.
How do I know if my authority node is working?
A working authority node is one that appears in AI system answers when someone asks the question it was written for. Test it by querying ChatGPT, Perplexity, and Google AI Overviews with the exact H1 question of your node, four to eight weeks after publishing. If your site is cited or your answer is paraphrased, the node is working. If not, the issue is usually structure, not quality.
The diagnostic checklist
If a node is not being cited after six to eight weeks:
Check structure first:
- Does the page open with a direct answer block — no intro paragraph before it?
- Is the H1 a full question matching the query you are targeting?
- Are there H3 subheadings organizing the detail?
Check schema and indexing:
- Is Article schema implemented on the page?
- Is the page indexed? (Search Google: site:yourdomain.com/your-node-slug)
Check the answer:
- Is the opening 40–60 words genuinely standalone?
- Is there a more specific question you could be targeting?
The most common fix: move the answer earlier and remove any introductory text above it.
My first authority node took me two hours to write and three revisions to get the structure right. The expertise was not the problem — I knew the answer. The problem was that everything I had been trained to do in content marketing told me to warm the reader up first. Build context. Earn the answer. That instinct is exactly wrong for AEO. AI systems do not need warming up. They need the answer in the first paragraph or they look elsewhere.
Once I understood that the opening paragraph was the citation target, everything changed. I stopped writing for scroll behavior and started writing for extraction. The irony is that the same structure that AI systems extract is also the most useful structure for the reader — lead with the answer, then go deep. It turns out that what AI systems want and what busy, sophisticated readers want are identical. Nobody wants to hunt for the answer.
The first node you write will feel underpowered. Fifty words of direct answer followed by three H3 sections feels sparse compared to the sprawling blog posts you have been writing for years. Publish it anyway. Check whether it gets cited in four to six weeks. The first time you see your exact words quoted in a ChatGPT response to the question you wrote for, every instinct you had about 'more is more' in content will dissolve permanently.
Choose the question your ideal client asks most often before they become a client — the one that comes up on every discovery call, in every initial email, in every comment on your content. That question is already validated demand. You know the answer. You know how to say it clearly. That is your first node.
The question selection framework
High-value node questions have three qualities:
- Specific — not "how do I get clients" but "how do I get my first consulting client without a referral network"
- Query-phrased — written the way a person would type it into ChatGPT, not as a topic heading
- Answerable in depth — you have enough to say to fill a substantive page (300–600 words), not just a sentence
- The question you answer on most first calls
- The most common question in your intake form or DMs
- The most-repeated comment on your content ("I always wonder about...")
- The question a new client asks before they understand your framework
Where to find your first question
An authority node should be as long as it takes to answer the question fully — typically 400 to 800 words for the main content, plus structured elements (H3 subheadings, bullets, tables). There is no minimum for AI citation value; a precisely structured 400-word node will be cited far more often than a loosely written 2,000-word post that buries the answer.
The right length for each section
Opening direct answer block: 40–60 words. Complete sentence. No heading above it. Stands alone.
H3 sections with supporting detail: Each section 100–200 words. Bullets, tables, and numbered lists welcome.
Total page target: 400–800 words for a focused node. More is acceptable if it adds genuine depth — not if it pads a thin answer.
When longer is appropriate
Some questions legitimately require more space: comparative questions needing a table, or multi-step implementation questions needing a numbered process. Length is earned by the question, not imposed for perceived authority.
The test
Read your node aloud. If you can feel yourself repeating points or circling the answer rather than deepening it, cut. The goal is density, not length.
The structure of an authority node follows a strict sequence: H1 (the full question), extractable answer block (40–60 word prose, no heading above it), then H3-organized supporting sections with detail, examples, or tables. This sequence is not aesthetic — it is functional. AI systems extract based on position and structure.
The canonical node structure
```
H1: Full query as a question
[40–60 word direct answer — NO heading above this paragraph]
A complete, standalone answer to the question. Plain prose. Citable.
H3 Subheading
Supporting detail, examples, step-by-step breakdown.
Another H3 Subheading
More depth, comparison table, common mistakes.
Another H3 Subheading
Implementation steps or next-action guidance.
```
What kills the structure
- Heading above the answer block: Any H2 or H3 before the direct answer pushes the extractable content down the page. Remove it.
- Intro paragraph before the answer: "In this article, we'll explore..." is not an answer. Delete it.
- The answer buried in bullet three: AI systems extract prose paragraphs, not bullet list items. The direct answer must be prose.
- No H3 subheadings: Unstructured body text with no subheadings signals low organization to AI crawlers.
Use inline markdown-style citations in your node body: hyperlink the source text directly to the URL rather than using numbered footnotes. For example: write "according to Search Engine Journal, answer engine optimization..." rather than "according to Search Engine Journal [1]." This format is more legible to both AI systems and readers.
Citation best practices for authority nodes
Only cite real, verified sources. Do not link to sources you have not read. Do not fabricate URLs. If you cannot find a reliable source for a claim, either find one before publishing or reframe the claim as your professional observation.
Prefer primary sources. Research institutions, university studies, platform documentation, and original research reports carry more authority signal than aggregator articles citing other articles.
Cite in the body, not just the footer. In-text citations where the source is hyperlinked in the relevant sentence carry more weight than a bibliography at the bottom of the page.
Two to three citations per node is sufficient. You are not writing an academic paper. One strong citation for a key factual claim is better than five weak ones for general statements. Quality of sourcing matters more than quantity.
A working authority node is one that appears in AI system answers when someone asks the question it was written for. Test it by querying ChatGPT, Perplexity, and Google AI Overviews with the exact H1 question of your node, four to eight weeks after publishing. If your site is cited or your answer is paraphrased, the node is working. If not, the issue is usually structure, not quality.
The diagnostic checklist
If a node is not being cited after six to eight weeks:
Check structure first:
- Does the page open with a direct answer block — no intro paragraph before it?
- Is the H1 a full question matching the query you are targeting?
- Are there H3 subheadings organizing the detail?
Check schema and indexing:
- Is Article schema implemented on the page?
- Is the page indexed? (Search Google: site:yourdomain.com/your-node-slug)
Check the answer:
- Is the opening 40–60 words genuinely standalone?
- Is there a more specific question you could be targeting?
The most common fix: move the answer earlier and remove any introductory text above it.
Write from the depth of your actual experience, not from credentials. An authority node derives its value from the specificity and accuracy of its answer — which comes from firsthand expertise, not degrees or certifications. If you have helped clients solve this problem repeatedly, you have the authority to write the node. What you should not do is write about adjacent topics you do not know deeply just to fill cluster slots. Thin authority nodes with generic answers are worse than no node — they signal low-quality content across your whole domain.
Start with one node written well. Your first node will teach you more about the format than any amount of planning — you will discover what an extractable answer actually feels like to write, where your instinct to add context before the answer comes from, and how to structure depth without losing focus. Once you have written three to five nodes, batch production becomes efficient. Before that, it creates the risk of baking in structural mistakes across an entire cluster. Write, publish, test, then scale.
An authority node is written for a single, specific query and structured for AI extraction. A blog post is typically written for a topic, structured for human reading, and optimized for SEO ranking. The structural difference is meaningful: a blog post can explore a topic broadly, start with context, use narrative flow, and cover multiple angles. An authority node answers one question, opens with the direct answer, and organizes everything else as supporting depth. The same underlying content can be restructured from blog format into node format — and when it is, its AI discovery performance typically improves significantly.
You grow by making your expertise easy to find when people are actively searching — not by performing on social media.
Visibility is being seen. Discoverability is being found by the right person at the right moment. They require completely different strategies.
The most common reason content doesn't get found is that it's organized around topics rather than questions. Here's how to fix it.