AI search

Podcast episode one: put the answer first for AI search

Episode one of The Ledger, out loud. Priya and Maren explain why you should put the answer first, so AI search tools can find, trust and quote it.

Two microphones facing each other over a speech bubble with the answer first, a short block of text below a quote mark

In the first episode of The Ledger, out loud, Priya and Maren talk about one habit: putting the answer first. AI search tools build their replies from short passages on many pages. A passage that answers the question plainly, with its source in view, is far easier to quote than one that warms up for three paragraphs.

Episode one: put the answer first for AI search

Show notes: why the answer first matters #

What we cover in this episode:

  • Why a reply from an AI search tool is built from passages, not whole pages.
  • How to write an answer capsule: a short, plain answer right under a question heading.
  • Why a source and a named author make a passage safer to quote.
  • What to do with the rest of the post once you put the answer first.

Further listening and reading from our blog:

Chapters #

  1. Why we started a podcast about writing
  2. How an AI answer is put together
  3. The paragraph with the answer first
  4. Sources and names
  5. What the rest of the post is for
  6. One thing to try this week

The transcript #

Read the full transcript

Priya: Welcome to The Ledger, out loud. I'm Priya Raman, research editor at Larkspur Studio.

Maren: And I'm Maren Okafor, head of content. We're starting with the habit we ask every writer for: the answer first, everything else after.

Priya: Let's start with why it matters more now. When someone asks an AI search tool a question, the tool doesn't hand back one page. It reads many pages and builds a reply from short passages. Google's own features work like this too, such as the AI Overview at the top of some results.

Maren: So the unit that gets chosen is the passage, not the post.

Priya: Right. Often the tool splits one question into several smaller ones and searches for each. That is called query fan-out. Your page might be picked to answer just one of those small questions.

Maren: Which means each section has to stand on its own. If the answer to "how long should a meta description be" only makes sense after the three paragraphs above it, it is hard to lift out.

Priya: So what does a section with the answer first look like?

Maren: The heading asks the question in the reader's words. The first two or three sentences answer it plainly. No "great question", no history. Then the detail comes after: the reasons, the exceptions, the example.

Priya: How long is that first answer?

Maren: Our house rule is forty to sixty words. Long enough to be complete, short enough to quote whole. Khalid's linter checks it for us, so it never slips.

Priya: And it should make sense out of context. If you read only that paragraph, do you know what "it" refers to?

Maren: That's the test I use most. I copy the paragraph into a blank note. If it still answers the question, it's done. If it says "as we saw above", it's not.

Priya: Let's talk about sources. In my work on how these tools cite pages, the passages they quote tend to state a fact plainly and show where it came from.

Maren: Which is what a good editor asks for anyway.

Priya: Exactly. A number with a link to where it came from is easier to trust than a bare number. And a page with a named author, who has real experience of the subject, gives the reader a reason to believe it.

Maren: Google says much the same. Its guidance on AI features says the usual good practice applies, and there's no special trick. We link it in the notes.

Priya: So nobody needs a separate "AI version" of their post?

Maren: No. Write one good page. Make each section answer one question, plainly, with its source. That serves the skimmer, the search engine and the AI tool at once.

Priya: What about the rest of the post? If you put the answer first, why would anyone keep reading?

Maren: Because the answer is the start, not the whole job. Below it you give what a short reply can't: the worked example, the step-by-step, your own data, the edge cases. That is where you add something new, what we call information gain.

Priya: And that's often what gets a page cited over a dozen others saying the same thing.

Maren: If ten pages give the same answer, the one with a real example from real work has a reason to be chosen.

Priya: Any traps?

Maren: Two. First, writing the question heading and then not answering it. The heading promises, the paragraph dodges. Second, stuffing every section with the same keyword. It reads badly and helps no one.

Priya: And from my side: don't invent numbers to sound precise. If you don't have a source, say it's an example. A made-up figure is worse than none, because once it's quoted, it travels.

Maren: So, one thing to try this week?

Priya: Pick your best post. Find the three questions it answers. Under each heading, rewrite the first paragraph so it answers in a few plain sentences.

Maren: Then copy each one into a blank note and check it still makes sense alone.

Priya: That's it for episode one. Thanks for listening.

Maren: See you next time.

What to do after listening #

Pick one post and try the exercise from the end of the episode: the answer first under every question heading. Then read Google's own page on AI features and your website, which Maren mentions. It confirms that good pages need no special treatment to appear in AI search features.

How this page is marked up #

This page carries structured data for a podcast episode. It names the episode, its number, the show it belongs to and the audio file, so podcast apps and search engines can place it. Khalid writes it from the post's settings.

Signing up by email is not open on this site.

About the author

Priya Raman

Research editor at Larkspur Studio

Experience MSc in Statistics, runs the yearly Larkspur content benchmark

Priya turns questions about content into numbers you can trust. She designs the yearly Larkspur content benchmark, checks every statistic we publish against its source, and writes about measuring what content earns and how AI search chooses what to quote.

Reviewed by

Add us as a preferred source on Google

Numbers from 140 small business blogs, free to read.

Read the 2026 content benchmark

Posts that link here

Comments are not open on this site.