AEO and answer engines

How to Structure FAQ Answer Blocks on Small Business Service Pages for Answer Engines

FAQ schema no longer wins snippets for small businesses. The first 40 to 60 words under each real customer question decide whether an answer engine quotes the page.

Man drawing an email automation workflow strategy on a whiteboard
Photo by Campaign_Creators

A heating engineer's service page can carry flawless FAQPage markup and still never get quoted anywhere. The markup gets the attention, but the first sentence under each question does the work. Since August 2023, Google has shown FAQ rich results only for well-known, authoritative government and health sites. A plumber's or florist's FAQ schema no longer earns the expandable snippet under the listing.

Answer engines still lift short answers that make sense on their own from clearly structured pages. An answer engine is any search tool that writes a reply to a question and cites the pages it drew from, such as Google's AI Overviews. The small businesses that get quoted have rebuilt each service page around five questions real customers asked. Each one is answered in 40 to 60 plain words that still make sense out of context.

This guide shows you how to write FAQ answer blocks for answer engines on small business service pages, one page at a time. Each step gives you the action, what you should see and the mistake to avoid. We've written it for agency owners, freelancers and owners who edit their own sites.

By the end, each service page answers five real customer questions in blocks an answer engine can lift whole

You'll finish with one rebuilt service page. It will have five question headings, five standalone answers, FAQPage markup that matches the visible text and a simple log for checking whether the page is being picked up. Start with the service that earns your client the most, then repeat the method on the next page once the first one is live.

The timing is real. Google's AI Overviews reached US searchers in mid-May 2024, and this week clients are ringing their agencies to ask what it means for their calls. This method gives you a concrete piece of work to show them in place of a theory.

Before you start, get these four things lined up.

  • Read access to the client's enquiry inbox, contact form submissions and any call notes from the last three months
  • Their reviews, from wherever customers leave them
  • Edit access to the website, including the ability to add a script block to a single page
  • Access to the site's Google Search Console property

What this method will not do

Be straight with your client from the first conversation. Nothing here guarantees a citation. FAQ rich results are gone for commercial sites like theirs, and no amount of markup brings them back. Answer engines pick their sources in ways nobody outside them can fully see, and the same question asked twice can cite different pages. Schema doesn't move rankings either.

What the method does is make the page the easiest one on the web to quote for those five questions. It also makes the page more useful to the people reading it, which pays off even if no machine ever quotes it.

Step 1: Take the five questions from the client's inbox, not from a keyword tool

Sort the last three months of enquiries into one document. Go through contact form submissions, quote requests, emails, call notes and reviews. Copy out every question someone asked before they paid, in their exact words, spelling and all. Ignore the questions from existing customers about invoices or rebooking. Those belong somewhere else.

The questions that decide a sale fall into a small set of groups. Expect to see cost range, how long the job takes, whether the business covers the customer's area, what's included in the price and what happens if something goes wrong. A dog groomer's inbox fills up with "Do you do nervous dogs?" A heating engineer gets "Will you tell me if it fails the safety check?" Both are the "what happens if" question in that trade's words.

What you should see: the same five or six questions repeating, often with nearly identical wording. That repetition is your shortlist. If the client has no FAQ page today, this is still where the questions come from. The inbox already holds the FAQ, it just hasn't been written up yet. Phone-heavy businesses can jot down questions from calls for a fortnight to fill the gaps.

The mistake: copying the "People also ask" boxes word for word. You get the same questions as every competitor and none of your client's own detail. Use those boxes, and the keyword intent map you already keep for the client, to check the wording of the questions you found, never to replace them.

Step 2: Write each heading as the question in the customer's own words

Turn every shortlisted question into a heading written as a full question. Give the FAQ section an H2, such as "Questions about boiler servicing in Leeds", then make each question an H3 beneath it. Keep the customer's wording where it's clear, and add the place name where location matters to the answer.

Weak FAQ headings next to strong ones for a Leeds heating engineer
Weak headingStrong heading
Boiler Service Leeds FAQHow much does a boiler service cost in Leeds?
PricingWhat's included in an annual boiler service?
Fast and friendlyHow soon can you service my boiler?
Coverage and calloutsDo you cover Horsforth and Pudsey, and is there a call-out charge?

What you should see: headings that make sense read aloud as a search query. Read each one out. If it sounds like something a customer would type or say to their phone, it's right.

The mistake: clever headings like "Fast and friendly" that answer nothing, or stuffed ones like "Boiler Service Leeds FAQ" written for a crawler. The last row of the table above is also wrong, because it asks two questions in one heading. Split it. One question per heading, never two. An answer engine lifts one answer for one question, and a doubled heading gives it a block that half-fits both.

Step 3: Answer in the first 40 to 60 words so the block stands alone

Write the first sentence as the direct answer. That's a yes, a no, a number, a price range or a timeframe. Follow it with one or two sentences that qualify it, then stop. Those 40 to 60 words are the part an AI Overview is most likely to quote, so they need to carry the whole answer without the heading, the page or the business name around them.

Here's the test. Copy the answer, paste it into a blank note with no heading above it and read it cold. Does it still say what the service is, roughly where, and the answer? If it leans on "we", "this" or "as above" without saying who or what, rewrite it.

Here's a before and after for Daniel, a gas engineer who services boilers across north Leeds. His original answer to "How much does a boiler service cost in Leeds?" read like this.

Great question. Every boiler is different and lots of factors come into play, so it really depends on your system. Give us a ring and we'll talk you through everything and find the right option for you.

Daniel's original answer, 39 words, no number in it

Lift that block out of the page and it says nothing. There's no price, no service and no place. Here's the rewrite.

A standard annual gas boiler service in Leeds costs £80 to £95 with us, including the flue gas analysis and a written service record. Older or back boilers take longer and cost up to £120. We quote the exact price when you book, before we arrive.

Daniel's rewritten answer, 47 words

It opens with the figure. It names the service and the city, says what changes the price and what the customer gets. Pasted anywhere, it still works. That's the block an answer engine can lift whole.

What you should see: five answers, each with its direct answer in the first sentence and a total of 40 to 60 words before any extra detail starts.

The mistakes: opening with "Great question" or "It depends", or burying the answer under the third sentence. Writing "we" with no business or place named anywhere in the block counts too, and so does pushing every question towards "call us". The call to action belongs at the end of the page. The answer block is there to answer.

Answer templates for the five questions most service businesses get

Use these as starting patterns and fill them with the client's real figures and towns. Never put a number in a template that the business can't stand behind on the phone.

  • Cost: A [service] in [town] costs [low] to [high]. The price depends on [factor one] and [factor two]. We confirm the exact price [when, such as at booking or after a free survey].
  • Timing: A [service] takes [duration] for a [typical job]. We can usually start within [lead time] of booking. [Larger job type] takes [longer duration].
  • Service area: Yes, [business] covers [town list] and anywhere within [distance] of [base town]. Outside that area we charge [travel fee or rule] or refer you to [alternative].
  • What's included: Every [service] includes [item one], [item two] and [item three]. [Common extra] isn't included and costs [amount or range] if you need it.
  • Aftercare or guarantee: If [problem] happens within [period] of the job, we [what the business does] at no charge. After that, [what happens next].

Step 4: Follow the short answer with detail only this business can give

Add one short paragraph under each direct answer, packed with first-hand specifics. Name the towns covered, the typical turnaround this month, the things that change the price and a named step in the process. For Daniel, that paragraph says he's booking services about eight working days out in June, covers Horsforth, Pudsey, Headingley and Roundhay, and sends a photo of the flue reading with every service record.

That detail is the reason a source gets cited over a national directory. A directory can tell a searcher that boiler services cost a certain amount on average. It can't say who covers Roundhay this month or what goes in the service record. As our piece on local business visibility under generative search explains, answer engines favour pages that add facts nobody else has published. The short answer makes the block quotable, and the specifics make this page the one worth quoting.

What you should see: a paragraph under each answer that a competitor across town couldn't paste onto their site without lying.

The mistake: generic filler like "we pride ourselves on quality and customer service" that any business could have written, or a sales pitch dressed up as detail. A useful check is to swap the client's name for a competitor's. If the paragraph still reads as true, it's filler. Cut it and write something only your client knows.

Step 5: Put the blocks in visible HTML on the service page itself

Place the FAQ section on the page for that service, after the main service description and before the final call to action. Daniel's boiler servicing page runs in this order. First what the service is, then what a visit looks like, then the five questions, then the booking button. A reader who scrolls past the description with a doubt meets the answer before they meet the button.

Keep the questions off a single sitewide FAQ page. A central page mixes boiler servicing with power flushing and landlord certificates, so no single block sits next to the service it describes. An answer engine reading the boiler servicing page should find the boiler servicing answers right there. A general FAQ page is fine for questions about payment or opening hours, but service questions belong on service pages.

Accordions are fine. Search engines read collapsed text as long as it's in the page HTML when the page loads. To check, open the page, right-click and choose View Page Source, then search for the first few words of an answer. If you find them, the accordion is safe. If you don't, the text is being fetched by script after a click, and a crawler that never clicks never sees it.

What you should see: all five questions and answers present in the page source, under the service description, on the page for that one service.

The mistakes come in three kinds. Answers loaded by script after a click, as above. Answers set inside images or designed graphics, which no answer engine quotes because there's no text to lift. And the same five blocks pasted onto every service and location page. That last one is the most tempting, because it saves an afternoon.

Step 6: Add FAQPage markup that matches the visible text word for word

Add a JSON-LD script block to the service page with one entry for each question and its full visible answer. Copy the text straight from the page. Don't summarise it, shorten it or tidy it up for the markup. Here's Daniel's first question, marked up.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a boiler service cost in Leeds?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A standard annual gas boiler service in Leeds costs £80 to £95 with us, including the flue gas analysis and a written service record. Older or back boilers take longer and cost up to £120. We quote the exact price when you book, before we arrive."
      }
    }
  ]
}
</script>

Add the other four questions as further objects inside the mainEntity list, separated by commas. Include the detail paragraph from Step 4 in the answer text too if it sits under the same heading on the page, so the markup and the visible block hold the same words.

Here's why you're doing this when the snippet is gone. In August 2023 Google limited FAQ rich results to well-known, authoritative government and health sites. Your client's page won't get the expandable questions under its listing, whatever the markup says. The markup now does a quieter job. It labels each question and answer pair for machines, so there's no guessing about where one answer ends and the next begins. That's the honest case for adding it, and it's the one to give a client who asks whether FAQ schema is still worth it. It's cheap, it describes the content clearly, and it doesn't move rankings on its own. Our piece on how generative engine optimization differs from traditional SEO covers why clear structure matters more to answer engines than to the old blue links.

What you should see: a script block whose question names match the visible headings exactly and whose answer text matches the visible answers exactly.

The mistakes: marking up questions that aren't on the page, letting the marked-up wording drift from the visible answer after a later edit, and putting the FAQPage block in the site template so it fires on every page. Each one gives machines a description that doesn't match what people see, which is the opposite of the point.

Step 7: Validate the page and ask for it to be recrawled

Run the live URL through Google's Rich Results Test, then through the Schema Markup Validator at schema.org. The first checks the markup the way Google reads it. The second checks it against the schema vocabulary and catches structural slips the first one sometimes glosses over, such as a missing acceptedAnswer. Fix every error both tools report, then test again.

Once both come back clean, open Search Console, paste the URL into URL Inspection and choose Request Indexing. That asks Google to recrawl the page rather than waiting for its next routine visit.

What you should see: the Rich Results Test detects valid FAQ items, the validator shows your five questions with no errors, and no rich result preview appears. The missing preview is expected. It's the August 2023 change at work, not a fault in your code.

The mistake: reading the missing preview as a failure and rewriting markup that was already correct. Valid items detected means the job is done. Stop there and leave the page alone while it's recrawled.

Check whether it worked after four to six weeks, and what to change if it did not

Give the page four to six weeks after the recrawl before you judge it. Then check two places, Search Console and the search results themselves.

In Search Console, open the Performance report, filter by the page URL and look at the Queries tab. Add a query filter for question words such as how, what, does and can, one at a time. Compare impressions and clicks for the four weeks before the change with the four weeks after. Rising impressions on question queries tell you the page is being shown for the questions you wrote it around.

Then search the five questions by hand, from the client's area if you can, or with the town in the query if you can't. Note whether an AI Overview appears, and if it does, which sources it cites. Click the source links to see whether your client's page is among them. Run the checks on the same day each week, because the same question asked twice can cite different pages.

Keep a simple log in a spreadsheet with one row per question per check. Use columns for the date, the question, whether an AI Overview appeared, the sources cited, whether the client's page was one of them, and the page's question-query impressions that week. After six weeks you'll have something to show the client that's better than a feeling.

If nothing moved, work through these in order. Each one is a fix we'd try before concluding the method doesn't suit the page.

  1. Check URL Inspection again to confirm Google indexed the new version, not the old one.
  2. Reread each first sentence cold. If it doesn't give a number, a yes or no, or a timeframe in its opening words, rewrite it.
  3. Check whether AI Overviews appear for those questions at all. If none do, the page is competing for ordinary results on those queries, and the rising impressions are the result to report.
  4. Look at the pages that were cited and note what they give that your client's page doesn't, usually a firmer figure or a named local detail.
  5. Swap the weakest question for the next one on your inbox shortlist and log it as a fresh test.

Explain the results to the client in their terms. The page now answers the five things customers ask before they ring, and the log shows how often search tools are picking it up. Calls from people who already know the price range are calls that book.

Reuse the same answers in the client's email so the work pays twice

Send the five answers again as a welcome sequence. Someone who joins the client's list through a quote form or a newsletter signup gets one email per question across their first fortnight. Each email carries the short 40 to 60 word answer and a link to the full version on the service page. The email answers the question, and the click takes the reader to the page with the booking button on it.

Ask for replies at the end of each email. A line such as "Anything we haven't answered? Reply and ask" brings in new questions in the customer's own words, and those questions feed the next round of blocks. The inbox you started from in Step 1 keeps refilling itself.

SendTo's agency partners run campaigns, sequences, landing pages and websites for their clients under their own agency brand. That means the service page and the welcome sequence can live in one platform the client sees as your product, so an edited answer gets updated on the page and in the email together. Our SendTo review for agencies walks through how that looks from the client's side.

Start this week with one page. Pull the five questions from the inbox, write the first sentences, mark them up, validate the page and start the log. Then do the next service.

Know agency owners who'd sell email marketing to their own clients? Refer them to SendTo and you earn 20% of the partner subscription each agency pays us, every month they pay it, paid monthly by PayPal. It never comes out of what their own clients pay them.

Join the SendTo affiliate programme

Frequently asked questions

Is FAQ schema still worth adding if Google stopped showing FAQ rich results for my site?

Yes, as long as it matches the visible text word for word. It won't bring back the expandable snippet, and it won't move rankings. The visible answers do the real work, and the markup just labels them clearly.

How long should an answer be for an AI Overview to quote it?

Aim for 40 to 60 words, with the direct answer in the first sentence: a yes, a no, a range or a timeframe. Paste it into a blank note and read it cold. If it still names the service, the place and the answer, it's ready.

Where do I find the right questions if the client has no FAQ page today?

Check their inbox. Pull three months of contact forms, quote requests, emails, call notes and reviews, and copy out every question asked before someone paid. If the business runs mostly on the phone, log the questions callers ask for a fortnight.

Should FAQs sit on one central FAQ page or on each service page?

Put them on each service page, in visible HTML. Every page answers the five questions buyers of that service ask, so the answer sits right next to the thing it's about. A single catch-all page waters that down.

What do I write when the honest answer is it depends, like pricing?

Give the range and the factors that move it. A range with two named factors is quotable. A line like it depends on your system gives an answer engine nothing to lift, and it gives your customer no reason to ring.

How many questions should go on a service page before it turns into clutter?

Stop at five, and never go past seven. Beyond that the answers start to overlap and the page stops being a clear source for any of them. Keep one question per heading, too, because a doubled question gives you an answer that only half fits either one.

How long before the changes show up?

Validate the page, ask for a recrawl in Search Console and check again after four to six weeks using your log. Nothing guarantees a citation. The same question asked twice can cite different pages, so judge it on the pattern over time, not a single check.

How do I explain this work to a client who just wants more calls?

Keep it simple. You're rewriting the page so it answers the five things customers ask before they ring, in words a search tool can quote. People who get those answers up front ring ready to book.

Everything this blog teaches, on a platform with your name on it.

Email campaigns, websites, landing pages and print for your clients, made from a short brief and sent under your brand. Create your account and look around with a sample workspace loaded.

No contract · Cancel any time · Explore everything before you pay