Local FAQ from real customer questions
Use when you want FAQ content for a location page based on what customers actually ask rather than invented questions.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{BUSINESS_AND_SERVICE}}
- {{AREA}}
- {{REAL_QUESTIONS}}
- {{CONFIRMED_FACTS}}
Getting a better result
- Pull the raw questions from your inbox, call notes or live chat rather than guessing what people ask.
- Answer-first phrasing is what gets pulled into search results, so do not let the model bury the answer in sentence two.
- Only mark up as FAQ schema the questions that genuinely appear on the page.
Questions about this prompt
When should I use this rather than generating FAQs from a keyword tool?
Whenever you have real questions to work from. FAQ blocks invented from search volume answer things nobody asks and read like it. This enforces the difference: at least eight of the twelve must come from {{REAL_QUESTIONS}}, and anything the model adds itself is labelled [GAP] so you can tell them apart.
What do I need before running it?
Raw questions pulled from your inbox, call notes or live chat and pasted unedited, plus {{CONFIRMED_FACTS}} covering pricing, lead times, coverage, parking, access, guarantees and callout charges. Any figure you do not supply comes back marked [NEEDS INPUT] rather than invented, which is the behaviour you want on price and timing.
What does it produce?
Twelve FAQs, each with a question under 12 words, a 40 to 70 word answer that gives the answer in the first sentence, and a confidence line. Then a ranking by likely effect on an enquiry decision and three to put at the top of the page. Act on that ranking.
What is the mistake specific to this one?
Letting the answer drift into sentence two while tidying the copy. Answer first phrasing is what gets pulled into search results and it is the first thing an editor undoes. The other one is marking up all twelve as FAQ schema when only the three you promoted actually appear on the page.