Outrings
Trust, privacy and content quality

How do I add an FAQ section that search engines actually use?

Real questions, visible answers, correct markup — in that order. Schema on questions nobody asked achieves nothing.

3 min read
Short answer

Write the questions people actually ask, answer each in one or two sentences of visible text, and mark it up with FAQPage schema. The markup must describe content that is genuinely on the page and visible — that is a hard requirement, not a guideline.

Find the real questions

The most common failure is inventing questions to fill a section. Sources for real ones:

  • Your support inbox and chat logs. The best source by a distance.
  • Sales calls — the objections that come up every time.
  • Search Console queries that land on the page but do not match its main subject.
  • "People also ask" boxes for your target query.
  • Asking an assistant your topic and noting the follow-up questions it raises.

A question nobody asks helps nobody, and dilutes the section around it.

Write the answers for extraction

  • One or two sentences of direct answer, then detail if needed.
  • Answer the question asked, not an adjacent easier one.
  • Include the specifics — numbers, names, limits.
  • Do not answer with a link. "See our pricing page" is not an answer.
  • Make each answer independent of the others.

The markup

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does delivery take?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Two to three working days to UK addresses, five to seven to the EU. Orders placed before 2pm ship the same day."
    }
  }]
}
</script>
Google's requirement is explicit: the question and answer must both be visible on the page. Content hidden behind a click is acceptable if it is in the HTML and can be revealed — an accordion is fine. Content that does not exist on the page at all is a violation, and the rich result gets removed along with, sometimes, others.

Accordions done properly

An accordion is good for scanning a long FAQ, and fine for search as long as the content is in the HTML rather than fetched on click. Two things to get right:

  • Use <details> and <summary>, or a button with aria-expanded controlling a region. Do not use a bare <div> with a click handler — keyboard users cannot reach it.
  • Content should be present in the DOM when the page loads. Loading it on click hides it from every crawler.

Where to put it

  • On the relevant page, not a separate FAQ page. Questions about delivery belong on the product page.
  • A central FAQ page is fine as well, for people who go looking.
  • Three to eight questions per page is usually right. Thirty questions on one page means most of them belong somewhere else.

What our audit reports about this

Every item below is measured directly, not inferred. Run it against your own site and the result names the exact rule or header responsible.

  • Whether question-and-answer structure is present in the page content.
  • Whether FAQPage schema exists, parses, and matches visible content.
  • Whether accordion content is present in the HTML rather than loaded on interaction.
  • Whether accordion controls are keyboard accessible and expose their state.

For agents and scripts, the same measurement is at /api/v1/faq?url=yoursite.com — see the API documentation.

Related questions

Do FAQ rich results still appear in Google?

Google narrowed FAQ rich results to a limited set of site types, so the visual dropdown is far less common than it was. The underlying structure still helps comprehension and extraction by answer engines, which is now the stronger reason to do it.

Can I mark up questions that are not visible?

No. Google requires the content to be present and visible on the page. Marking up hidden or non-existent content is a violation that can cost you rich results site-wide.

How many questions should I include?

As many as are genuinely asked, usually three to eight per page. Padding the list with invented questions dilutes the real ones and helps nobody.

Read next

All 50 guides · How every check works · API for agents