FAQ blocks: one section, two search engines

If one content pattern pays twice, it is the humble FAQ block. Classic search likes it because question headings match real queries. AI assistants like it because each pair is a pre-packaged answer they can lift. You write five short paragraphs and feed both systems.

Choosing the questions

Use the ones customers actually send you. Your inbox, your quote requests, and your phone calls are the source material. For a service business the universal five are: how much does it cost, how long does it take, what area do you serve, what exactly is included, and how do we start. Add the objection you hear most, "can I do this myself", "do you work with my platform", and you have a section worth ranking.

Writing answers that get lifted

• Answer in the first sentence, in two to four sentences total.
• Use numbers wherever they exist: prices, ranges, durations.
• Write self-contained answers. "As mentioned above" dies the moment the answer is quoted out of context.

Make it machine-readable

Pair the visible section with FAQPage JSON-LD listing the same questions and answers. The markup must mirror what is on the page, not extend it. On WordPress, most SEO plugins have an FAQ block that outputs both at once; on static sites it is a dozen lines of JSON in the head.

Placement

Put FAQs on the pages where the questions arise: pricing questions on service pages, shipping questions on product pages. One giant FAQ page collects orphaned answers nobody finds. Three to six per page is plenty.

Our scan checks crawled pages for FAQ blocks and for FAQPage schema as part of the AI visibility score, because in AI answers, the site that already phrased the question tends to be the site that gets quoted.

Quick answers

Do FAQ sections still help SEO?

Yes. Question headings match how people search, FAQPage schema makes the pairs machine-readable, and the same content is prime material for AI assistant answers.

Where should FAQs live: one big page or per page?

Per page. Three to six questions on each money page beat one orphaned FAQ page, because the answers sit in the context where both humans and crawlers need them.