How to Format a Blog Post for AI Search (Section by Section)

---

I love a good template. Always have. When I learned AEO best practices for blog posts, the thing that clicked for me wasn’t just the why. It was that the best practices are a structure. A repeatable, teachable, trainable-to-AI structure.

Once I understood how large language models actually decide what to recommend — and it turns out it’s less mysterious than you’d think — the whole question of “how do I write for AI search” simplified into something I could put in a doc and hand to Claude. That doc became a skill. That skill now formats every post on this site.

I’m going to be honest about something upfront: this site is new. I don’t have years of data showing you exactly how I rank for every keyword. What I do have is the methodology, the structure, and the AI Visibility Suite I built to audit content against these exact best practices. (That report exists because I wanted a way to run AI against content — mine and my clients’ — and benchmark it against what we know works. That’s also where I’d start if you want to know where your own posts stand right now.)

Here’s the structure, section by section.

---

Table of Contents

• Why structure is the thing AI is actually looking for
• Section 1: The H1 headline
• Section 2: The Quick Answer Box
• Section 3: The introduction
• Section 4: The Table of Contents
• Section 5: Body sections with question-based H2s
• Section 6: The FAQ section
• Section 7: The closing invitation
• The visual layer: images and alt text
• How I automated this with a Claude skill
• FAQ

---

Why is structure what AI search is actually looking for?

AI tools like ChatGPT, Claude, and Perplexity aren’t reading your blog posts the way a person does. They’re scanning for signals. Is there a clear question being answered here? Where is the answer? Who wrote this, and does the structure of this content suggest they actually know what they’re talking about?

The posts that get cited aren’t always the most beautifully written ones. They’re the ones that make all of that obvious. And what makes it obvious is a specific structure that signals: this is a question, and here is a direct, organized answer.

Once I understood that, the whole thing stopped feeling like a technical SEO puzzle and started feeling like a content design problem. Which is a much better problem, because content design is learnable, repeatable, and something you can train AI to help with.

---

Section 1: The H1 headline

Your H1 is the title of your post, and it needs to do one job above everything else: contain the question or keyword your ideal client is actually searching.

Not a clever headline or a brand-voice-y phrase — the actual thing they type into a search bar.

“How to format a blog post for AI search” is a keyword. “Why your blog isn’t showing up (and what to do about it)” is a headline. The first one is findable. The second one is not, at least not until you’ve built enough authority that people are searching for you specifically.

The test I use: if I read the headline cold, could I tell you exactly what question this post answers? If not, sharpen it.

You can still write in your voice. You just lead with the question first.

---

Section 2: The Quick Answer Box

Right after your title, before your introduction, before anything else: a short, direct answer to the question your post is about.

Two to four sentences in plain language in a complete thought, not teasing.

This is called a Quick Answer Box — and yes, labelling it matters. You want to actually use the words “Quick Answer” as a visible label at the top of the block. As for heading level: don’t use an H2 or H3 here. The Quick Answer Box sits outside your post’s heading hierarchy — it’s a styled callout, not a section. On this site it’s formatted as bold text inside a visually distinct block (you can see it at the top of the content strategy post). That treatment is intentional: it tells AI tools “this is a special extract” without disrupting the H2 structure that organizes the rest of the post. A plain paragraph with no label doesn’t do the same job. Here’s a deeper explanation of what it is and why it works.

The Quick Answer Box does two things. For the human reader, it confirms immediately that they’re in the right place. For AI tools, it’s a clean, extractable answer they can pull directly into a summary or citation. You’re making their job easy. They return the favour by citing you.

This is not the same as giving away too much too soon. You’re not giving away the whole post. You’re giving the answer upfront and spending the rest of the post making it useful and actionable. Think of it like a newspaper story — the facts in the first paragraph, the context and depth below.

---

Section 3: The introduction

Your introduction names the problem or situation the reader is in. No “In today’s digital landscape.” No warm-up. You’re already in the conversation.

A strong intro does three things:

• Tells the reader they’re in the right place
• Names the exact frustration or question they came in with
• Gives them a reason to keep reading

Personal stories, honest admissions, and specific context all work here. What doesn’t work is a paragraph of scene-setting before you get to anything useful. (I’ve written those. They’re easy to cut in editing and you should cut them.)

The intro is also where you drop your primary keyword naturally, since it should appear in the opening paragraph for both SEO and AEO purposes.

---

Section 4: The Table of Contents

A Table of Contents isn’t required in every post, but for longer ones it’s one of those small structural choices that does a lot of quiet work. For pillar pages and longer cluster posts (roughly 2,000+ words), a ToC gives readers a map of the post and lets them jump to the section they actually need. That behaviour — a reader clicking straight to a specific section — signals to Google that your content is organised and useful.

For AEO, the ToC also reinforces your heading structure. AI tools scanning your post see the same questions listed twice: once in the ToC and again as the actual H2s in the body. That repetition is a signal, not noise.

When to include it: Any post over 2,000 words, or any post with five or more distinct sections. Pillar pages always get one.

When to skip it: Short cluster posts (under 1,500 words) with three or four sections don’t need a ToC. It adds length without adding value, and readers can just scroll.

---

Section 5: Body sections with question-based H2s

Your H2s are the section headers that organize your post, and they’re also one of the main things AI scans when deciding what your post covers.

When your H2s are phrased as questions, they act as search query matches. AI tools see “How do I know if my blog post is formatted for AI search?” as a question being answered, and that section becomes a candidate to cite for anyone searching that exact thing.

You don’t need every H2 to be a question. But aim for at least two or three, especially at the points where you’re directly addressing something your reader is actively wondering. The ones that work best are phrased the way your ideal client would actually say it, not the way you’d phrase it in your own head.

Each section covers one complete, useful idea. If a section starts going in three directions, it belongs in two separate posts.

---

Section 6: The FAQ section

FAQs are having a moment — and honestly, they deserve it. A FAQ section at the end of your post is one of the most consistent signals AI tools look for, and most people still aren’t adding them. (Which means the ones who do stand out immediately.)

FAQ sections work for two reasons. First, they’re collections of direct question-and-answer pairs, which is the format AI is built to scan and extract from. Second, they let you cover the close variations of your primary keyword — the follow-up questions, the adjacent searches — all in one place.

A few dos and don’ts worth knowing:

	What to do	Why it matters
✅	Write FAQs as plain visible text — bold question, answer directly below	AI can only extract what’s visible on the page
✅	Link within FAQ answers	Helps AI connect related content on your site
✅	Add FAQ schema markup (when you’re ready)	Tells Google to pull your Q&As directly into search results — this is a phase two move and has its own learning curve. [LINK TO: future post on schema markup once published]
❌	Use an accordion or “click to reveal”	If the answer is hidden until someone clicks, AI tools may not read it at all
❌	Add nifty interactive features	Clever for design, bad for AEO — keep it simple

You already know the questions. They’re in your DMs, your client intake forms, the things people ask on discovery calls. Write those down and answer them in two to four sentences each. That’s a FAQ section.

For longer posts, aim for five to seven questions. For shorter cluster posts, three to five is enough. They don’t need to be comprehensive. They need to be real.

---

Section 7: The closing invitation

Your last section is not a summary. Your reader just read the post. They don’t need you to tell them what was in it.

What they need is one clear next step and a reason to take it. Sometimes that’s a question that invites them to reflect. Sometimes it’s a direct link to a resource. Usually it’s both.

The closing is also where your primary CTA lives — the one thing you want the reader to do after they finish. Keep it to one thing. Two CTAs split attention. One CTA drives action.

---

The visual layer: images and alt text

Here’s the thing most people don’t realize about images and AI search: AI can’t see your images. It reads the alt text.

Alt text is the short description you attach to every image in your CMS — the field most people skip, or fill in with something like “screenshot.” It’s one of those steps that feels tedious (I won’t pretend otherwise), but it’s another opportunity to be found. Don’t skip it.

Quick note: Alt text was built for accessibility first. It’s what screen readers use to describe images to people who are visually impaired — and that purpose should still be in your mind when you write it. Accessibility and AEO aren’t in conflict here though. AI tools read the exact same field to understand what your image is showing and how it connects to your content. Descriptive alt text serves both. Leave it blank and the image is invisible — to the people who need it most, and to the AI tools you’re trying to reach.

Your alt text needs to do two things:

• Describe what’s literally in the image
• Tie it to your topic

Take the image above as a live example.

Bad alt text: photo

Good alt text: cozy home office desk with plants and an open laptop, set up for writing blog posts

The bad version tells AI nothing. The good version describes what’s literally in the image and connects it to the topic. That’s the whole formula.

Alt text vs. caption: These are two different fields that do different jobs. Alt text is the invisible description AI and screen readers use — it never shows on the page. A caption is the visible text that appears below the image for your reader. If you’re using a stock photo (like one from Unsplash), the caption is the right place to credit the photographer: Photo by [Name] on Unsplash. That keeps your alt text clean and descriptive, and gives proper credit where it’s due.

File naming: The same logic applies before you upload. A file named screenshot-2026-06-26-at-8.49pm.png tells AI nothing. A file named blog-post-format-ai-search-quick-answer-box.png is readable as context before the image even loads. The format that works: primary-keyword-descriptor.png — all lowercase, hyphens not underscores.

Image quantity: One image per major section is the right density for a longer post. The practical test is whether the section is explaining something visual. If yes, it needs a screenshot. If it’s purely conceptual, it can stand alone.

Compress before you upload. Most website platforms resize images but don’t compress them efficiently. A slow-loading page affects crawl signals and how AI tools access your content. TinyPNG or Squoosh takes 30 seconds and keeps your images fast without sacrificing quality. Worth making it a habit.

---

How I automated this with a Claude skill

Here’s where it got interesting for me.

Once I had the structure mapped out, I started thinking about it the way I think about most repeatable processes: can I train AI to do this consistently, the same way every time, in my voice?

So I did. I uploaded my notes, my research, my own methodology and point of view into Claude, and Claude and I built a skill together — a set of instructions it follows every time I write a new post. The skill knows the exact sections that need to be included, how to structure them for AEO, and how to write in my voice instead of its own. (The Brand Voice Playbook is a big part of why that works — that process is here if you want to build your own.)

The result: I don’t start posts from a blank page anymore. Before any draft gets written, Claude interviews me. It asks me questions about the topic — my take, my experience, what I’ve noticed, what I’d tell a client — and I answer like I’m talking to a friend. My ideas, my stories, my point of view. Claude organizes my answers into a structured draft using my words, not its own. Then I review, edit to my liking, and publish.

This part matters to me. The ideas in my posts are mine. The methodology is mine. The skill just makes sure they come out organized and formatted correctly, every time. AI removes the friction. It doesn’t replace the thinking.

And it goes further than that. I use Claude in Cowork to automate the weekly prompting — Claude checks my content strategy in Notion, surfaces what to write next based on what’s mapped out, and kicks off the workflow automatically. Everything that can be automated is automated. The only thing I’m doing manually is the judgment call, the editing, and the final review.

I built the AI Visibility Suite partly to have a rigorous way to check that the posts coming out of this system are actually formatted right. It’s a full audit of your site and content against the AEO best practices we know AI looks for — scored, specific, and with a clear list of what to fix. If you want to know exactly where your content stands against these criteria, that’s the place to start.

---

FAQ

Do I need to use all of these sections in every post?
The Quick Answer Box, question-based H2s, and FAQ section should be in every post. The Table of Contents is covered in its own section above — short version: always for pillar pages and longer posts, optional for short cluster posts. The intro and closing are always there. Think of the structure as a non-negotiable checklist, not a flexible suggestion.

How long should a blog post be to show up in AI search?
Long enough to fully answer the question. For cluster posts (one specific question, one specific answer), 1,200 to 2,000 words is usually right. For pillar pages (broad topic, comprehensive coverage), 3,000 to 5,000 words. AI tools don’t reward length for its own sake — they reward completeness. A 900-word post that answers its question thoroughly can outperform a 3,000-word post that meanders.

Can I retrofit this structure onto posts I’ve already published?
Yes, and it’s worth doing on your highest-traffic posts first. Add a Quick Answer Box, rephrase two or three H2s as questions, add a FAQ section at the bottom. You don’t need to rewrite the whole post. The structure changes are the part that matters most for AI visibility.

Does this structure work for Google search as well?
Yes. The signals that help AI tools — direct answers, question-based structure, FAQ sections, clear authorship — align closely with what Google looks for in its AI Overviews and traditional results. Optimizing for AI search and for Google are increasingly the same work.

What’s the difference between AEO and SEO?
SEO (Search Engine Optimization) is about ranking in traditional Google search results. AEO (Answer Engine Optimization) is about being cited directly by AI tools that answer questions instead of returning a list of links. They share the same foundation — write clearly, answer real questions, publish consistently — but AEO puts more emphasis on direct answers, question-based structure, and named author credibility signals. You don’t need to build two separate strategies. One good content system satisfies both.

Do I need a paid tool to check if my posts are formatted correctly?
Not necessarily. The checklist in this post is enough to self-audit. If you want an outside eye and a scored report, the AI Visibility Suite is what I built to do exactly that — it runs your content against AEO best practices and tells you specifically what’s working and what to fix.

---

The structure isn’t the hard part. The hard part is writing the post consistently enough that the structure compounds. A well-formatted post published once doesn’t do much. A well-formatted post published every week for six months builds something.

Build the template once, train Claude on it, and trust the system to do what you built it to do.

Want to know how your existing content holds up against these criteria right now? The AI Visibility Suite audits your site against AEO best practices and gives you a scored report with the specific fixes that will move the needle. That’s where I’d start.