A good FAQ entry states the answer in its first sentence, uses the wording people actually type, and stays complete when read alone, without the page around it. Aim for 40 to 90 words per answer, with no marketing language. Add FAQPage markup only if the questions and answers are visible on the page, and don't expect it to produce a rich result in Google.

This article covers how to find the questions, how to write the answers, and what to do about markup.

Start with questions people really ask

Invented questions tend to be the ones you wish people asked: "Why is our platform the best choice?" Nobody searches for that. Pull questions from places where customers state them unprompted:

  • Search Console queries. Filter the Performance report for queries containing "how," "what," "can," "does," "why," "vs" or "cost." Real phrasing is already there.
  • Support tickets and chat logs. The first line of a ticket is usually the question in its natural form.
  • Sales call notes. Objections are questions in disguise: "Do you integrate with X?" "What happens if we cancel?"
  • Site search. Anything visitors type into your own search box and don't find is a gap.
  • Autocomplete and "People also ask" boxes. Use these to check wording, not to copy a list wholesale.

Keep the user's phrasing, including awkward phrasing, as long as it is clear. "Can I use this without a credit card?" is better than "Is a payment method required for registration?" Our keyword research guide covers reading intent behind a query if you need to decide whether a question deserves its own entry.

Cut any question that only you care about. If it didn't come from a query, a ticket or a call, it probably doesn't belong.

Write the answer first, then stop

The first sentence must be the answer. Context, caveats and links come after. If someone (or something) reads only that sentence, it should still be true and useful.

In our reading, this is also what makes an entry extractable: a block that depends on the paragraph above it ("As mentioned earlier...") can't be lifted out intact. We don't have vendor documentation describing how any AI engine selects FAQ text, so treat that as reasoning, not a documented behavior. The same pattern is useful for human readers who scan.

The same discipline applies at the top of a page; see how to write a quotable definition.

Before and after

The figures below are illustrative placeholders.

Before:

How long does shipping take? Great question! At Example Store, we know waiting for a package can be exciting. Shipping times depend on many factors, so read on to learn more about how we get your order to you.

This answers nothing. It is 33 words of preamble.

After:

How long does shipping take? Standard shipping takes 3–5 business days within the US. Orders placed before 2 p.m. ET ship the same day, and tracking is emailed when the label is created. Express shipping takes 1–2 business days and costs $15. Orders to Alaska, Hawaii and US territories add 2–3 days. International orders are covered under "International shipping" below.

The answer is in sentence one. Exceptions follow. The reader can stop at any sentence and still hold something accurate.

The 40-90 word target

This range is a working guideline, not a documented limit from any search engine or AI vendor. It exists because of two failure modes:

LengthProblem
Under 40 wordsUsually a bare "Yes" or "No" with no conditions, so it's often wrong in edge cases
40-90 wordsRoom for the answer, one or two conditions, and a pointer
Over 90 wordsProbably two questions. Split it, or move the detail to a full page and link

If an answer needs 300 words, it is an article. Write the short answer in the FAQ and link to the long one.

Standalone means no dependencies

Check each entry against this list:

  1. Name the subject. Write "Example Store's return window is 30 days," not "The window is 30 days."
  2. No back-references. Remove "as above," "see the previous question," "this."
  3. State units and conditions. "$15" is fine; "a small fee" is not.
  4. One question, one answer. No "and also" questions.
  5. No marketing language. Words like "industry-leading," "seamless," "best-in-class" and "we're passionate about" add length and no information.
  6. Say "no" when the answer is no. An entry that avoids a plain negative loses trust.

Structure on the page

Put the FAQ under a clear heading and make each question its own subheading, or a clearly separated bold line. A consistent pattern helps readers and parsers alike. See heading structure for how hierarchy is read.

Group questions by topic when you have more than about eight: shipping, billing, setup. Put the most-asked entries first.

Don't hide answers behind accordions that require JavaScript to render. If the answer isn't in the HTML a crawler receives, it is not reliably part of the page. Collapsed accordions that are present in the HTML are a separate matter, covered in the next section.

When to use FAQPage markup

FAQPage is the schema.org type for a page with several questions and their answers. The situation around it has changed, and the vendor facts matter here.

  • Google's 2023 update limited FAQ rich results to well-known, authoritative government and health sites. [2]
  • Google announced that the FAQ rich result would no longer appear in Google Search starting May 7, 2026. [1]
  • Google's documentation for the feature was removed in June 2026 because it is no longer shown in results. [6]
  • Google also says structured data that isn't used doesn't cause problems for Search, but has no visible effect there. [2]

So markup is not a way to get an expanded result in Google. Whether it is worth adding depends on what else you want it for: a consistent machine-readable description of the content, or other consumers of schema.org data. Our FAQPage schema article goes through that decision. The FAQ writing itself does not depend on it. Answer-first entries are worth writing with no markup at all.

The visible-answer requirement

If you do add markup, it must match what the user sees. Schema.org's FAQ guidance says to mark up only content that is visible to people visiting the page, not hidden elements. [4] Google's general structured data guidelines say content referred to by structured data should not be hidden from the user. [5]

In practice:

  • Every question and answer in the JSON-LD must appear on the page in the same words.
  • Don't put extra "SEO" questions only in the markup.
  • Don't mark up answers that sit behind a login or a paywall.
  • When you edit the visible text, edit the JSON-LD in the same commit.

A minimal example:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard shipping takes 3–5 business days within the US. Express shipping takes 1–2 business days and costs $15."
      }
    }
  ]
}

The text can be a shorter version of the visible answer only if it is not misleading. The safest choice is identical text.

Don't use QAPage for this

QAPage is for a page built around one question with user-submitted answers. Google's QAPage guidance says not to use it for FAQ pages or for pages with multiple questions on the same page. [3] A multi-question FAQ is FAQPage or no markup.

For the wider picture of which types matter, see schema markup for AI search.

What we don't know

No vendor document in our notes says that FAQ-formatted content is cited more often by AI engines, or that markup changes that. Don't plan around a claimed lift. The case for this format is plainer: readers get answers faster, and each entry holds up if quoted alone.

What to do next

  1. Pull 10 real questions from Search Console, support tickets and sales notes.
  2. Rewrite each answer so the first sentence is the answer, then trim to 40-90 words.
  3. Read each entry alone and remove anything that needs the page around it.
  4. Decide on FAQPage markup separately. If you add it, mirror the visible text exactly.
  5. Set a review date. Prices, limits and policies change, and a stale answer is worse than none.