A small-business FAQ page of short question and answer pairs being read by a search engine and an AI assistant.
An FAQ page is already shaped like the answer an AI assistant needs to give.

Most small-business websites have an FAQ page. Very few of them get quoted. The usual reason is not the topic. It is the shape of the writing.

This is the AEO part of xEO. AEO means Answer Engine Optimisation: helping your pages answer direct questions clearly, so search engines, AI assistants and voice search can use them.

A simple test: copy one of your answers into a message, on its own, with no heading and no page around it. If it still makes sense to a stranger, a machine can quote it too.

Why do AI assistants like FAQ pages?

Because an FAQ page is already the shape of what they produce: a question, then a short answer.

When someone asks ChatGPT, Gemini or Copilot a question, the tool does not return a list of ten links. It returns one answer, built from a few sources. It has to find a passage that answers the question and can be lifted out cleanly.

A long service page makes that hard. The useful sentence is buried in paragraph six, mixed in with a description of your team. An FAQ entry hands the machine the pairing directly.

What makes an FAQ answer quotable?

Seven things. None of them are technical tricks, and all of them make the page easier for people to read as well.

1. Use the questions customers actually ask

Not the questions you wish they asked. Most FAQ pages answer things like "Why choose us?" Nobody types that into anything.

Real questions are practical and slightly awkward: "Do you charge for a quote?", "How soon can someone come out?", "Do you work in Papakura?" Write the question in the customer's words, not in polished marketing English.

2. Put the answer in the first sentence

Do not build up to it. Systems that summarise a page read the sentence sitting closest to the question first, and often stop there.

Start with "Yes", "No", "About two weeks" or "From USD 99 per year". Add the detail afterwards, in the sentences that follow.

3. Keep each answer to about 40 to 60 words

That is long enough to be genuinely useful, and short enough to be quoted whole.

Under about 25 words, an answer usually leaves out the detail that makes it worth quoting. Over about 80 words, a machine has to cut it, and it will not always cut it where you would have.

4. Make every answer stand on its own

Remove "as mentioned above", "this depends on the package described earlier" and "see the section below". An FAQ answer is nearly always read out of order.

Repeat the noun instead of using "it". "Our callout fee is USD 60" survives being pulled out of the page. "It is USD 60" does not.

5. Be specific enough to be checked

"We are usually quite quick" tells a machine nothing it can repeat. "We reply to enquiries within one working day, Monday to Friday" is a fact.

Prices, hours, service areas, turnaround times, what is included and what is not. These are the sentences that get quoted, because they are the ones a customer was actually asking about.

6. One question, one answer

Do not stack three topics under one heading. If your answer contains the word "also" twice, it is probably two questions wearing one coat.

Split it. Two clear entries have two chances of matching what someone asks. One crowded entry usually matches nothing well.

7. Add FAQPage structured data

Structured data is a small block of code in the page that repeats your questions and answers in a format machines read directly. It removes the guesswork about which text is the question and which is the answer.

The visible text and the structured data must match. If they disagree, you are telling two different stories about the same business. Adding this correctly across a site is part of an xEO optimisation pass.

Where should the FAQ go on my site?

Next to the thing it is about. Three or four questions at the bottom of each service page usually work better than one long page holding forty questions.

The reason is context. An answer about drain-clearing prices, sitting on your drain-clearing page, is clearly about that service. The same answer on a general FAQ page, between a question about parking and one about invoices, is harder for a machine to attach to anything.

A single FAQ page still helps for questions that cover the whole business: payment methods, service area, opening hours, insurance. Keep both, and do not repeat the same answer in both places.

If your site is old enough that adding sections to each page is a fight, it is often cheaper to start again. A new website with xEO included has this structure built in from the first day.

How do I find the right questions to answer?

You already have them. They are in the places customers contact you.

  • Your last twenty enquiry emails. Write down every question that appears twice.
  • The questions you answer on the phone before anyone books.
  • The follow-up questions people ask after you send a quote.
  • Your reviews, which often say what worried someone before they hired you.
  • Google's "People also ask" box for your main service and location.
  • An AI assistant: ask it what people usually want to know before hiring your kind of business.

The first two sources are the best ones. A question a real customer asked you last week is worth more than ten guessed from a keyword tool.

What should I avoid?

  • Answers that dodge. "Please contact us for pricing" is not an answer, and it will not be quoted.
  • Sales language. "We pride ourselves on our unrivalled service" contains no fact a machine can use.
  • The same FAQ block copied onto every page. Duplicated content weakens all the copies.
  • Questions with no search behind them. If nobody asks it, answering it adds nothing.
  • Structured data that says something the page does not. That is a trust problem, not a shortcut.

How do I know if it is working?

Check three things, and give it a few weeks before you judge.

First, ask an AI assistant one of your own questions and read the answer closely. If the wording resembles yours, your page is being used. Our 10-minute ChatGPT test walks through this properly.

Second, look in Google Search Console for question-shaped queries reaching those pages. Third, and most useful, notice whether customers stop asking you the same thing in every first email. That means the page answered it first.

Be patient with the timing. Pages are usually recrawled within days to a few weeks, but a clear change in enquiries takes longer than that to see.

When the questions keep coming anyway

A good FAQ page removes the repeated questions from your inbox. It does not remove all of them, because some customers want a person to confirm the answer.

If the same five questions still arrive every week, that is a different job with a different fix. A custom AI agent can answer them from the same facts, at 9pm, and pass anything unusual to you. Write the FAQ page first — it becomes the material the agent works from.

FAQ page questions

How many questions should an FAQ page have?

Between six and twelve for a whole-business FAQ page, and three or four at the bottom of each service page. Quality matters more than quantity. Ten questions real customers ask will do more for you than forty invented to fill space.

Does FAQ structured data still show rich results in Google?

Usually not. Since August 2023, Google has shown FAQ rich results mainly for well-known government and health websites, so most small businesses will not see the dropdown in search results. The markup is still worth adding, because it tells every machine which text answers which question.

Should I use the same FAQ block on every page?

No. Repeating an identical block across pages gives search engines several near-identical pages to choose between, and none of them looks like the best answer. Write questions that belong to each page, and keep general questions on one FAQ page.

What if the honest answer is "it depends"?

Say what it depends on, with numbers. "Most kitchen jobs take two to three days, longer if we are replacing the flooring underneath" is quotable. "It depends on the job" is not. Give the usual case first, then the exception.

Is a good FAQ page enough to get into AI answers?

No, but it is one of the fastest improvements you can make. AI systems also need clear service pages, consistent business details and mentions elsewhere on the web. The FAQ page is where the plain facts live, so it is a sensible place to start.

Not sure which questions are worth adding? Send us your website. We will read it the way an AI assistant does and tell you which answers are missing, starting with an xEO optimisation audit.