AEO and answer engines

7 FAQ Page Mistakes That Keep Small Business Sites Out of Answer Engines

Answer engines quote one clear sentence, not a whole page. Seven FAQ habits stop small business sites being quoted, and each one has a five-minute test and a fix.

Empty interior of a modern hair salon with styling chairs and stations
Photo by sanctuarysalondayspa

Since mid-May 2024, Google has shown AI Overviews at the top of US search results. Chat assistants now answer questions like "which plumber near me does same-day repairs" with a short paragraph. Those answers are built from sentences lifted off real web pages. So a small business FAQ page has two outcomes. It supplies the sentence that gets quoted, or it gets skipped. Google pulled back some of the stranger answers in late May, after a few odd ones went round, but the mechanism didn't change. The engine finds a passage that settles the question and quotes it.

FAQ pages are usually written to reassure someone who's already on the site. They open with friendly lines, use brand language and end with "get in touch for details". That's fine for a reader who's already on the page. An answer engine gets nothing it can quote from it. FAQ page optimisation for answer engines is mostly rewriting the answers you already have, so each one opens with a plain fact that makes sense on its own.

Below are seven habits that keep FAQ pages out of AI answers. Each one comes with what it looks like, why it costs you and a test you can run in five minutes. Be clear on one thing first. Nobody controls what an answer engine quotes, and no fix guarantees you'll be included. These fixes improve your odds, and the tighter answers work well as email content too. If you want the wider picture on traffic, we covered what Google's AI Overviews rollout means for small business search traffic separately.

1. Answers that warm up before they answer get passed over

"Great question." "At Hargreaves Heating, we believe every customer deserves peace of mind." "We understand how stressful it is when your boiler breaks down." These openers feel polite. They also push the actual answer down to the third or fourth sentence, and sometimes there's no answer at all.

An extractor scans an answer for the first sentence that settles the question. If that sentence comes after 40 words of warm-up, a competitor's answer that opens with a plain yes or no gets picked instead. Answer engines aren't reading for tone. They want a sentence they can quote that's still true and complete once it's pulled out.

Before and after for a Leeds heating engineer

VersionAnswer to "Do you offer same-day boiler repairs?"
BeforeGreat question. At Hargreaves Heating we know a broken boiler is never convenient, which is why our friendly team always does everything we can to get to you as quickly as possible. Give us a call to discuss your needs.
AfterYes, Hargreaves Heating offers same-day boiler repairs within 20 miles of Leeds, booked before 11am. Calls after 11am are booked for the next morning. Our engineers carry common parts for Worcester, Vaillant and Ideal boilers, so many repairs are finished on the first visit.

The rewrite is barely longer. The difference is that its first sentence carries the whole answer, including the business, the service, the area and the condition. Everything after it is detail for the human reader.

2. Questions written in the owner's vocabulary miss how customers actually ask

"Our Service Guarantee." "Aftercare." "The Process." Those are labels the owner would use. No customer types them into a search box. A customer asks "What happens if the repair fails?" or "Do I have to pay again if the leak comes back?" A heading in the owner's language matches nothing anyone actually searches for.

This matters more now because people type and speak full questions, and answer engines match those questions against question-shaped text on the page. A heading phrased the way a customer asks gives the engine a clear pairing between their question and your answer. A label like "Aftercare" makes the engine work out what the section is for, and it often won't bother.

Where to find the questions your customers really ask

You don't have to guess. The exact wording is already sitting in places you can open this afternoon.

  • Enquiry emails and contact form submissions, especially the first line, where people state what they want in their own words.
  • Call notes or the questions whoever answers the phone hears every week.
  • Review text, where customers mention what they worried about before booking ("I wasn't sure if they'd do weekends").
  • The search queries report in Google Search Console, filtered for queries that start with how, what, can, do or is.
  • The related questions Google shows on the results page when you search for your own service and town.

Copy the phrasing as you find it, including the awkward bits. If a cafe's customers keep asking "can I bring my dog in", don't tidy that into "What is your pet policy?" Use their words for the heading and put your formal term in the answer if you need it. A salon can do the same with "how long does a balayage take" and still mention "freehand colour technique" in the second sentence.

3. Answers loaded only when someone clicks a tab may never be read

Some FAQ accordions and tabs don't contain their answers at all. The answer text is fetched with JavaScript when a visitor clicks. Others are third-party widgets embedded in an iframe, so the questions and answers live on the widget provider's domain, not yours. Both look perfect in a browser.

A crawler sees something different. If the answer text isn't in the HTML your server sends, the crawler may index a list of questions with nothing under them. Google does render JavaScript, but rendering happens in a later queue and isn't guaranteed for every page. Plenty of other crawlers read the raw HTML and run no scripts at all. Iframe content is worse, because any credit for those answers goes to the widget's domain, not your site.

The five-minute source test

Open the FAQ page, then view the page source. Use Ctrl+U on Windows or Option+Command+U in Chrome on a Mac. Don't use right-click and Inspect. Inspect shows the page after scripts have run, so it will always show the text and tell you nothing. In the source view, search for a distinctive phrase from the middle of one answer, such as "booked before 11am". If it's there, crawlers can read it. If only the question appears, or you find an iframe tag pointing to another domain, the answers need to move into the page itself. On most website builders that means swapping the widget for the builder's own accordion block and pasting the answers in.

4. Answers that lean on the page around them fall apart when quoted alone

"As mentioned above, this is included." "It usually takes two weeks." "This package covers everything you need." "We're based here." Read on the page, with the heading and the paragraphs around them, these make sense. Read on their own, they don't.

That's exactly how an answer engine uses them. It lifts one passage out of your page and puts it into an answer next to text from other sites. Anything the passage relied on, like the heading, the earlier paragraph or the page title, gets left behind. "It usually takes two weeks" turns into a sentence about nothing. The engine passes over it and picks an answer that names its subject.

Paste the answer into a blank document

This is the standalone test. Copy one answer, without its question, into an empty document. Show it to someone who has never heard of the business. If they can't tell who is speaking, what service it's about and where it applies, rewrite it. An accountant's "It's included in this package" becomes "Patel and Co's sole trader package includes the self assessment tax return and one call with an accountant before the 31 January deadline." Name the business, the service and the area once in each answer. You don't need them in every sentence, which reads as stuffing.

The same test settles the question of whether FAQs belong on one page or on each service page. Put each service-specific answer on the page for that service, where the surrounding context backs it up. Keep a short central FAQ for general questions like opening hours, payment and parking. The answers need to stand alone wherever they sit, because engines quote them out of context either way. We set out the layout in detail in how to structure FAQ answer blocks on small business service pages, including how a heading and answer pair should look in the page code.

5. Marketing copy gives an answer engine nothing it can state as fact

"Competitive prices." "Fast turnaround." "Serving Leeds and the wider area." "A friendly, professional team." Every one of these is true in the owner's head, and none of them can be checked. An answer engine asked "how much does a boiler service cost in Leeds" or "which salon in Harrogate does Sunday appointments" needs a sentence that states something. A claim about your prices doesn't tell anyone what you charge.

Answer engines lean towards passages with checkable specifics like a number, a day, a town or an inclusion, and they tend to skip adjectives. A vague answer gets skipped. The engine quotes whoever wrote the plain fact instead, which could be a competitor, a directory listing or a comparison site.

Swap the vague phrase for the fact behind it

Vague phraseQuotable fact to write instead
Competitive pricesThe starting price of your most-booked job, written as a 'from' price, plus what it includes
Fast turnaroundMost bookkeeping catch-ups are finished within 5 working days of receiving your bank statements.
Serving the wider areaWe cover Leeds, Wakefield, Harrogate and Otley, and charge a call-out fee beyond 20 miles.
Flexible opening timesThe salon is open 9am to 7pm Tuesday to Saturday and 10am to 4pm on Sundays.
Everything you needThe package includes the cut, wash and blow-dry. Toner and treatments are charged separately.

The test takes two minutes. Highlight every adjective in your answers. For each one, ask what number, place or inclusion sits behind it. If there's a real fact, write the fact and delete the adjective. If there isn't one, the sentence is filler and can go.

Publishing prices has a real trade-off

Owners have fair reasons not to publish prices. Every job is different, competitors can see them, and a price that's too low draws the wrong enquiries. You don't need to publish a full price list to get quoted. A 'from' price, a typical range or a list of what changes the price (property size, access, parts) all give an engine something solid. A cafe can state its corkage policy without listing its menu. An accountant can say a sole trader return is a fixed fee agreed before work starts, and name what's included. Keep the exact figures on the service page, where you'll update them, and link to it from the FAQ.

6. FAQ markup that doesn't match the visible page does more harm than no markup

FAQPage structured data is the code that labels each question and answer for machines. It goes wrong in three ways. The wording in the markup differs from the wording on the page. The markup holds answers that aren't on the page at all. Or a plugin stamps the same FAQ markup onto every page of the site, so the about page, the contact page and every blog post all claim the same twelve questions.

First, expectations. Since August 2023, Google has shown FAQ rich results, the dropdown questions under a search listing, mainly for well-known government and health sites. Almost no small business will get those dropdowns, whatever its markup says. So does FAQ schema still matter? A little. Markup still helps machines read which text is a question and which is its answer. But it only helps when it matches what a visitor sees. Markup that disagrees with the page is a mixed signal, and Google's guidelines say structured data must reflect the visible content.

The match test

Run the FAQ page through Google's Rich Results Test or the Schema Markup Validator and copy out the questions and answers it finds. Put them side by side with the visible page. Every marked-up question should appear on the page word for word, with the same answer. Then test a page that has no FAQ, like your contact page. If FAQ markup shows up there, a plugin is copying it site-wide, so switch that setting off. If you can't keep the markup in step with the page, remove it. A page with no markup and clear answers beats a page with markup that contradicts itself.

7. Stale or contradictory answers teach answer engines not to trust the page

The FAQ says you close at 5pm. Your business profile says 5.30pm. The contact page says you cover "all of West Yorkshire" and the FAQ lists four towns. The price in the FAQ went up in January and nobody changed it. Each mistake looks small. Put together, they leave the engine unsure which version is true.

When sources disagree, the engine has to pick one, and your page isn't guaranteed to win. It may quote a directory that happens to be current, or a competitor whose facts line up everywhere. A wrong answer also costs you directly. The customer who turns up at 5.15pm to a locked door won't book again.

A quarterly five-fact check

Once a quarter, put five facts in a simple spreadsheet and check each one in three places: the FAQ, the service pages and your listings (business profile, directories, social bios).

  1. Opening hours, including bank holidays and seasonal changes
  2. Prices or 'from' prices for your top three services
  3. Service area, named town by town
  4. Booking lead time, such as same day, next week or a six-week waiting list
  5. How to contact or book, including the phone number, form and any online booking link

Where the three disagree, fix the source you control first, then the listings. The whole thing takes about twenty minutes for a small business. If you look after clients, add it to your regular account check-in. It fits naturally into a mid-year account review, because it gives the client something concrete they can see fixed.

Fixing these mistakes also gives you a year of email content

An FAQ answer that opens with a plain fact, names the business and stands on its own is already a short email. "You asked, we answered" works as a monthly feature. Take one real question from the inbox, give the 50-word answer and add one link to book. Pick five or six of the answers and you have a welcome sequence that covers what every new subscriber wants to know, like hours, area, prices and how booking works, before they ask.

This is where we come in for agencies. In SendTo, the AI designer turns a campaign brief into finished HTML email in seconds, so pasting in a reworked FAQ answer with the client's brand preset gives you a ready draft. The built-in reviewer then checks the subject line, links and structure before launch. That matters with FAQ content, because a stale link or a broken booking URL is easy to carry over from the page. For more ways to reuse writing, see how to turn one client blog post into a month of emails.

If you only have an afternoon, fix hidden text first, then first sentences

There are seven fixes, but they aren't worth the same. Do them in order of impact for the effort, so the first hour makes the biggest difference.

  1. Step 1: Run the source test from mistake 3. If the answers aren't in the page HTML, nothing else on this list matters, because the crawler can't read them.
  2. Step 2: Rewrite each first sentence so it answers in 15 to 25 words, and run the standalone test on each one (mistakes 1 and 4). This is the biggest change for answer engines, and it's quick.
  3. Step 3: Swap headings for the customer's own phrasing and replace adjectives with facts (mistakes 2 and 5). This takes longer because you have to dig out real questions and real figures.
  4. Step 4: Make the markup match the page and put the quarterly five-fact check in the calendar (mistakes 6 and 7). This is maintenance, and it keeps the earlier work accurate.

FAQ page optimisation for answer engines doesn't guarantee a quote. Nobody controls what these systems pick, and they're still changing month to month. What it does is turn a page written to reassure visitors into a set of sentences an engine can lift and trust. The same sentences rank for long questions and feed your newsletter.

For agencies, the seven checks make a tidy one-page audit. Run it on a prospect's site, show them the before and after for two answers, and offer the rewrite as a fixed-price job. The quarterly check then becomes a recurring line on the retainer, which sits well next to the ideas in packaging email marketing as a productised service.

Recommend SendTo to the agencies you work with and earn 20% of the partner subscription each referred agency pays SendTo, every month it pays. You never take a share of what that agency's own clients pay it. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal.

Join the SendTo affiliate programme

Frequently asked questions

Will an accordion or tabbed FAQ stop my answers being found?

Not if the answer text is already in the page HTML and only hidden with CSS. Collapsing text doesn't hide it from a crawler. Loading answers on click with JavaScript, or putting them in a third-party iframe, does. Check with view source (Ctrl+U), not Inspect.

How long should each FAQ answer be to get quoted?

Answer the question in the first 15 to 25 words, then add detail. Aim for 40 to 80 words in total. Quick check: cover everything after the first full stop. If what's left still answers the question, you're done.

Where do I find the exact questions my customers ask?

Start with enquiry emails, contact form first lines, call notes and review text. Then add Search Console queries starting with how, what, can, do or is, plus the related questions Google shows for your service and town. Copy their wording exactly, awkward bits included.

Should FAQs go on one central page or on each service page?

Both, split by topic. Put service-specific answers on that service's page, and keep a short central FAQ for general stuff like opening hours, payment and parking. Wherever they sit, every answer has to make sense on its own, because engines quote them out of context.

How often should I update my FAQ answers?

Run a check every quarter. Stale or contradictory answers teach answer engines not to trust the page, so compare the key facts in your FAQ, like prices, hours and service area, against what's true today and against the rest of your site.

Does adding FAQ markup make up for weak answers?

No. Markup that doesn't match the visible page does more harm than no markup at all. Get the visible answers right first, then make sure any markup repeats them word for word.

Which FAQ fix should I do first if I've only got an afternoon?

Fix hidden text first. If crawlers can't see your answers, better first sentences and customer phrasing are wasted. Once the text is in the page source, rewrite each answer so its first sentence settles the question.

Will these fixes guarantee my business gets quoted in AI answers?

No. Nobody controls what an answer engine quotes, and no fix guarantees you'll be included. These changes do improve your odds, and the tighter answers make good email content too.

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