The Blog Post Skeleton I Use on Every Site I Own

Quick read: Content structured for AI retrieval follows a recognizable pattern: a direct, factual opening paragraph before any brand voice, organized sections with descriptive H2 headings, a FAQ block using ### Question? H3 subheadings, and internal links connecting the piece to related content. Research on AI citation behavior — including an Ahrefs study tracking 1,885 pages — confirms that AI systems pull from visible HTML during retrieval, not from JSON-LD markup. Structure that makes answers easy to extract consistently outperforms structure that makes pages look polished.

Two posts on two different sites, same topic, similar word count, similar internal links. One gets cited by Perplexity when someone asks a related question. The other doesn't. The difference, in most cases, isn't the depth of the subject matter. It's the structure.

I've written enough posts across enough sites to have a working skeleton that I drop into every new piece before I write a single word. Not because the template is magical — it's not — but because it removes the structural barriers to AI citation before they have a chance to form. Once the structure is right, the actual writing determines whether the post is any good. Without the structure, the writing quality doesn't matter much.

Here's the skeleton.

The literal template

1. H1 title — keyword-forward, under 60 characters, slightly conversational

The title does two jobs: tells the reader what they're getting, and signals the topic to a machine reading the page. "Slightly conversational" matters here. A question-format or plain-English title tends to perform better in AI queries than a keyword-stuffed headline, because it more closely matches the language someone actually uses when asking an AI a question. "The Blog Post Skeleton I Use on Every Site I Own" beats "Blog Post Structure Best Practices 2026 Guide" — not because keywords don't matter, but because the conversational phrasing matches query intent more naturally.

2. Quick read blockquote — one neutral, factual, LLM-citable paragraph

This is the highest-leverage element in the whole skeleton, and the most counterintuitive one.

The Quick read goes before the hook, right after the front matter. It's written in neutral, factual language — no brand voice, no opinion, no humor. The standard I use: could a large language model paste this paragraph verbatim as the answer to a related question without needing to caveat or filter it? If yes, you've done it correctly.

This element exists because AI retrieval systems prefer content that can be cited cleanly. Brand voice signals opinion to a retrieval system; opinion is harder to cite reliably. The Quick read is the neutral, citation-friendly version of the post's core point. Everything outside it can be as personality-forward as the site warrants — but that one paragraph, written before the hook and before any brand voice, is what gets cited.

3. Opening hook — 2-4 sentences, specific, no preamble

The hook comes immediately after the Quick read. It's the first thing with voice — specific, no throat-clearing, no "in today's digital landscape" warm-up. A specific scenario, a counterintuitive claim, or a direct observation. You're writing for a reader who will leave in under five seconds if you don't earn their attention immediately.

4. H2 sections — what it is, why it matters, the mechanics, what won't help

The body sections follow a consistent internal logic: explain the thing plainly, connect it to the reader's actual situation, give the concrete mechanics, then name the anti-patterns. Each H2 heading should be descriptive enough that someone scanning only the headings can follow the argument. A page where the headings are vague gives AI retrieval systems nothing to anchor to.

The "what won't help" section is worth naming explicitly: it's not optional and it's not filler. It's where the post does the work of distinguishing accurate from common-but-wrong advice. Content that names anti-patterns gets cited more often because AI systems field "I've heard conflicting things about X" queries constantly — and a post that already handles the objection is ready to be extracted as the answer.

5. ## FAQ section — with ### Question? H3 headings

More on this below, but the structural rule is non-negotiable: use ### Question? format — not bold text, not H2 headings, not bullet points. This format is what the site's extractFaqs() function reads to auto-generate FAQPage JSON-LD from the visible content. And it's the format that AI retrieval systems recognize as a direct question-and-answer structure.

6. One soft CTA at the end

One. Not three scattered through the post. Not two with slightly different wording. One mention of the relevant service path, earned by the post having actually explained something useful, at the end. The CTA works because the post did something worth asking for; the pitch feels out of place when it's the actual point of the post.

Why the Quick read is the most important element

Here's the honest version of how AI citation works at the content level: a retrieval system doing a lookup pass is looking for content it can extract, attribute, and return as an answer. Long opinion pieces, content buried inside brand voice, and posts that take three paragraphs to state the core claim are harder to cite cleanly.

The Quick read is the paragraph written explicitly for that purpose. You're not writing it for a reader of your newsletter — you're writing it for a language model that needs a clean, attribution-friendly summary. Every other paragraph in the post can be as sardonic, specific, and personality-forward as you want. That one paragraph is the exception.

It's tempting to skip this element when a topic doesn't feel like it has a "neutral" version. Every topic does. The trick is to write the Quick read before you write the hook — while the factual version is still in your head and before the brand voice takes over. Once you're in the voice of a post, writing neutrally for that post becomes harder.

Why the FAQ format matters — and why bold isn't enough

The Ahrefs research on AI citations confirms what the structural logic implies: AI systems read visible HTML during retrieval, not JSON-LD in the document head. The FAQ section works precisely because it's visible, structured, and formatted as the thing AI systems are trying to produce — a question followed by a direct answer.

The ### Question? format matters for two reasons. First, it creates a semantic signal that this heading is a question, which maps to how AI queries arrive. A ## Section Heading tells the reader what this section covers; a ### What does this actually mean for my business? tells the retrieval system this is a question-answer pair. Second, in DBO's setup specifically, the extractFaqs() function reads H3-level headings within a ## FAQ section to auto-generate the schema. The markup is generated from the content structure; you can't generate it correctly from bold text or bullet points.

Bold text doesn't do this. It signals emphasis, not a question-answer relationship. If your FAQ section is formatted as bold questions followed by paragraphs, a retrieval system has to infer the Q&A structure. With ### Question? headings, it doesn't have to infer anything. For a deeper look at what the research says about FAQ markup, structured data, and what actually moves AI citations — including the full context of the Ahrefs study — the FAQ schema breakdown covers the numbers in detail.

What breaks the structure

Opening with context-setting. Any variant of "in today's digital landscape" or "this topic is more important than ever" is the fastest path to not being cited. There's nothing for a retrieval system to extract. Start with the thing itself.

Burying the answer. Retrieval systems read top-down. A post that takes four paragraphs to state what the post is about loses points before it says anything interesting. Lead with the answer; elaborate below it.

Putting the CTA before the value. The soft CTA at the end works because the post earned it. A pitch in the second paragraph — or worse, a pitch dressed as a FAQ answer — signals that the post is a funnel, not a resource. Retrieval systems aren't penalizing you explicitly for this, but readers are, and reader engagement is one of the signals that affects how content gets treated downstream.

Writing standalone posts with no internal links. A page with no internal links is structurally isolated — it tells search systems and AI crawlers nothing about what concept cluster it belongs to. Even two internal links, correctly targeted, change the page's structural position. The complete AEO guide covers why cluster architecture matters; the short version is that a connected post is treated as more authoritative than the same post on an island.

Using the same anchor text for every internal link. Varied anchor text sends more useful signals than "click here" repeated twelve times. "Complete AEO guide," "our AEO overview," and "the second search" all link to the same place — but each tells the system something slightly different about what the destination covers.

FAQ

Does the order of sections in this skeleton actually matter?

Yes. The Quick read before the hook matters because retrieval systems read top-down and prioritize content that appears early. The FAQ at the end matters because it clusters conversational queries after the substantive content establishes context. Mixing FAQ questions into the body copy, or putting them at the top of the page, sends mixed signals about what the page is primarily about.

Why is the Quick read written neutrally when the rest of the post has brand voice?

Brand voice reads as opinion to a retrieval system, and opinion is harder to attribute cleanly. A neutral, factual paragraph can be cited verbatim; an opinionated paragraph requires the AI to filter and paraphrase before using it. The Quick read is explicitly the non-opinionated version of the post's core claim — the citation-friendly excerpt, written before any brand voice sets in.

Can I use this skeleton on service pages, not just blog posts?

The structural principles transfer: lead with a direct answer (what the service is), use descriptive H2 headings, add a FAQ section at the bottom. Service pages have a different primary goal — explain and persuade rather than answer a question — so the body section structure tends to be more persuasive than educational. But the Quick read, FAQ format, and internal linking logic apply directly.

How many FAQ questions is the right number?

Five to seven is the practical range. Fewer than five and the section feels thin; more than seven and you're likely answering questions the reader doesn't have. The test: are these questions your actual customers ask — in the exact words they use — or are they questions that sounded reasonable when you wrote them? The former gets cited. The latter fills a page.

Does this skeleton replace good writing?

No. Structure removes the barriers to citation; content quality determines whether the citation is actually useful. A well-structured post full of thin or vague content still won't get cited consistently — the retrieval system extracts the structure and finds nothing worth returning. The skeleton is the necessary condition, not the sufficient one.

Is this different from general SEO advice about content structure?

Most SEO content advice is about topics and keywords. This is about the physical structure within a piece of content — the sequence of elements, the formatting choices, and the specific functions each part serves for AI retrieval. You can follow every keyword best practice and still produce content that AI systems can't cleanly extract, because the structure works against you. The skeleton addresses that layer specifically. For the broader optimization picture — entities, trust signals, crawlability, what ChatGPT and Perplexity actually look for — the AI search optimization guide covers the content factors that work alongside the skeleton.

---

The structure isn't the point of the post — the point of the post is the thing the post is actually about. But get the structure wrong, and the point of the post never reaches the people looking for it.

If you'd rather hand this off — the structure, the cluster logic, the ongoing maintenance that keeps a site's AI visibility from drifting — the Get Found on Google and AI path covers how we approach it as a managed operation.