FAQ pages
Also called Frequently asked questions, FAQ section, Q&A page.
An FAQ page is a page of the questions customers actually ask, each followed by a short, direct answer. Done well, it saves phone time and gives Google and AI assistants plain sentences they can quote. Each question gets one clear answer, and each answer lives in one place.
Doug's Field Guide · Updated
What makes a good FAQ answer?
Start with the questions you hear most on the phone and at the door. For a plumber that is 'How much does a water heater cost to replace?', 'Do you charge to come out?', 'Can you come today?'. For a dentist it is insurance, new patient openings and what a cleaning costs.
Answer in the first sentence, then add a line or two of detail. 'Most tank water heater replacements run $1,400 to $2,200 installed. The price depends on size, fuel type and whether the venting needs changes.' That first sentence stands on its own. Google and AI assistants look for exactly that when they quote a page, which is the heart of AEO.
Give each question one answer. If the same question shows up on five pages with five slightly different answers, customers and search engines can't tell which is right. Put the full answer on the most relevant page, and link to it from the others.
Can you have too many FAQ pages?
Yes. Some sites generate hundreds of pages like 'How much does drain cleaning cost in [town]?' with the same answer and a different town name. Google's spam policies call that scaled content abuse: many pages made mainly to manipulate rankings, however they were produced. Pages made to rank for many similar searches are doorway abuse. Hundreds of thin, near identical FAQ pages fit both.
Most local businesses need one solid FAQ page, plus a few service-specific questions at the bottom of each service page. Add a question when customers start asking it, not to target a search phrase. If a question has a different answer in each town, like travel fees, put it on the area page for that town.
Does FAQ markup still get you anything in Google?
FAQPage schema markup used to make questions drop down under your Google result. Google limits FAQ rich results to a few government and health sites. The markup does no harm on a real FAQ page. The value now comes from the answers themselves, which can still appear in regular results, People Also Ask boxes and AI answers.
Keep the answers on the page as plain text. An answer inside an image or a PDF menu is harder for search engines and assistants to read and quote. Reread the page each quarter so prices, hours and policies stay current. An old price quoted back to a customer costs you more than a missing answer.
Build your FAQ from real questions
- Ask whoever answers your phone to write down every question customers ask for one week.
- Pick the ten most common and write a one sentence answer to each, then add one or two lines of detail.
- Include real numbers where you can: price ranges, hours, how soon you can come.
- Put the answers on one FAQ page, and add the three most relevant ones to the matching service page, linking back to the full FAQ.
How Doug does it
Doug answers your customers, so he sees the questions they actually ask. Each week he drafts FAQ answers from your own material, up to 3 a week. He publishes them to WordPress, Shopify, Webflow, a GitHub repo, or a site he hosts on your domain, and the sites he builds carry FAQPage markup.
Keep exploring
- People also askThe box of related questions in Google results, each with a short answer.
- Answer engine optimizationAEO, GEO, LLM SEO: getting named in AI answers on Google and in assistants.
- Schema markupA short block of code that tells search engines your name, address, hours and services.
- How Doug learns your businessYour website, files, and Q&A pairs become the only place his answers come from.
Sources
- Google Search Central: Spam policies for Google web search
- Google Search Central: Latest documentation updates
Written by Doug's team from these sources and our own work with local businesses. Search engines change their rules, so check the source before a big decision.
