FAQ schema

Open your most important page and count the questions it answers in prose. Delivery times, what is included, whether you work weekends, how the pricing works. Most business pages answer five to ten questions without ever asking one.

FAQPage schema takes those answers and presents them as explicit question-and-answer pairs. That is exactly the shape an assistant wants, because it can lift a pair with no interpretation.

The markup

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you charge per user?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Fernway is one flat price per crew, regardless of how many people use it. A three-person crew and a nine-person crew pay the same."
      }
    },
    {
      "@type": "Question",
      "name": "Do you work with Xero?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Approved quotes sync to Xero as draft invoices, usually within a minute."
      }
    }
  ]
}
</script>

Rules that decide whether it works

The question and answer must both be visible on the page. Schema describes the page; it does not add to it. Marking up content that is not there is a policy violation and, more practically, gets your markup ignored.

Write the question the way a customer says it. "Do you charge per user?" not "Pricing model information". You are matching how the question will be asked in a chat box.

Answer in the first sentence. The first sentence should be complete on its own. Everything after it is supporting detail that may be trimmed.

Be specific. "No, one flat price per crew" gets quoted. "We have flexible pricing to suit your needs" does not.

Fifty words is plenty. Long answers get truncated at an arbitrary point, which is not a good look.

Where to put the visible version

A simple accordion is fine — but only if the answers are in the HTML on load, not fetched by a script when clicked. If your FAQ component lazy-loads, the crawler sees empty containers. The safest pattern is plain headings and paragraphs.

<h2>Do you charge per user?</h2>
<p>No. Fernway is one flat price per crew, regardless of how many
people use it. A three-person crew and a nine-person crew pay the same.</p>

How many

Three to eight per page. Beyond that you are usually better off giving the topic its own page, which gives you a URL that can be cited directly.

Common questions

Do FAQ rich results still appear in Google?

Google has significantly narrowed which sites get FAQ rich results in search. The schema remains useful for machine readability regardless of whether the visual rich result appears.

Can I put FAQ schema on every page?

You can, but only where the page genuinely contains those questions and answers. Duplicating the same FAQ block site-wide is a signal of low quality.

Does the visible FAQ need to be an accordion?

No, and plain headings with paragraphs are safer. If you do use an accordion, make sure the answer text is in the HTML on page load.