An FAQ section that search engines understand answers questions real customers ask, puts the direct answer in the first sentence, and shows every question and answer as text on the page. Where it helps, the same content is described with FAQPage structured data that matches the visible text word for word. Google now shows FAQ rich results only for a limited group of sites, so write the section for readers and answer engines first, and treat any rich result as a bonus.
#Start from questions customers actually ask
The best FAQ questions come from people who have already contacted you. Invented questions read like advertising, and nobody searches for them. Sources worth checking:
- Your inbox and contact form: the questions sales and support answer every week.
- Chat logs and call notes, including the exact words customers use.
- The search box on your own site, if it logs queries.
- Google Search Console, which shows the queries your pages already appear for.
- Reviews and comments, where people mention what confused them.
Keep the customer's wording in the question. If buyers ask "Can I pay by bank transfer?", do not rewrite it as "Which payment methods are supported?". Keep each FAQ on the page it belongs to: delivery questions on the delivery page, pricing questions next to prices. Review the list when something changes, and delete questions that no longer apply. An FAQ goes stale like any other content.
#Write answers that can be quoted
Search features and AI answer engines lift short passages out of a page. A passage is useful to them only if it makes sense on its own, so write each answer with the answer in its first sentence:
- Answer first. Start with "Yes", "No" or the fact itself, then give the conditions, then the details.
- Repeat the subject. Write "The plugin needs WordPress 6.0 or newer", not "It needs 6.0". The sentence may be read without the question above it.
- One question per item. Split compound questions so each answer stays short.
- Be specific. Name versions, conditions and steps. If the honest answer is "it depends", say what it depends on.
- Link to the full page when an answer needs more than a short paragraph, so the FAQ does not turn into a manual.
Avoid answers that only say "Contact us". They give a reader nothing to act on and give a search engine nothing to quote.
#FAQPage structured data that matches the page
Structured data is machine-readable markup, usually JSON-LD inside a <script type="application/ld+json"> tag, that tells search engines what a page contains. For an FAQ, schema.org defines the FAQPage type: a list of Question items, each with an acceptedAnswer of type Answer.
The rules that matter most:
- Mark up only visible content. Every question and answer in the JSON-LD must appear on the page with the same wording. Extra or hidden questions in the markup go against Google's guidelines.
- Use FAQPage only for questions the site answers itself. Pages where users post questions and answers, such as forums, use the
QAPagetype. - Generate the markup from the same data as the page. If the accordion and the JSON-LD both come from one list of questions in the CMS, they cannot drift apart when an editor changes an answer.
- Validate it. Google's Rich Results Test and the Schema Markup Validator show errors before you publish.
Google has limited FAQ rich results, the expandable questions under a search listing, to a small set of well-known, authoritative sites, mainly government and health sites. Most business sites will not get that display. The markup still describes the page clearly to any system that reads it, and it costs little when it is generated from data you already have. The rules have changed before, so check Google's current documentation on FAQ structured data before you plan around it.
#Accessible accordion markup
Most FAQ sections are accordions: the questions stay visible and each answer opens on request. Built badly, an accordion hides content from keyboard and screen reader users. Built well, it helps everyone. The usual pattern:
- Each question is a real
<button>inside a heading at the right level, so it can be reached with Tab and opened with Enter or Space. - The button carries
aria-expanded, set totrueorfalseas it opens and closes, andaria-controlspointing at the answer's id. - The answer panel can carry
role="region"witharia-labelledbypointing back at its button. - Focus styles stay visible. Do not remove the outline without a clear replacement.
The native <details> and <summary> elements give you a working disclosure with no JavaScript at all, which is a good choice for simple pages. Whichever you use, put the answer text in the HTML when the page loads. Answers fetched only after a click may never be read by crawlers, and they disappear if a script fails. Opening the first item by default helps when the first answer is the one most visitors need.
Keep the questions in one editable list. If you also want FAQPage markup, generate it in your template from that same list, so the page and the structured data always agree.
#How PN Scripts can help
PN Scripts can build an FAQ section like this for your site, matched to your theme, with the structured data generated from the same list of questions. Tell us about your site.
Comments
Comments
No comments yet. Ask a question or share what worked for you.
Leave a comment