FAQPage Schema That Matches Your Visible FAQs

Why FAQs Still Belong on the Page

In 2023 Google stopped showing FAQ rich results for most sites. Many people read that as "FAQs are dead" and pulled them off their pages. That was a mistake. The rich result was a bonus. The FAQ itself was never about the rich result.

A good FAQ answers the questions that stop someone from calling. Do you work on my kind of car. How long will it take. Do I need to book. Each answer removes one reason to leave. That has not changed.

FAQs also help in places people forget. AI answer tools like to quote short, direct answers under a clear question. Search engines use the questions to learn what the page covers. And the questions add real words to a page, in the customer's own phrasing, that a template cannot fake.

So keep them. Keep the schema too. It costs nothing, it tells machines exactly where the questions are, and it is ready if Google widens the rich result again.

The Rule: Schema Must Match What People See

Google's rules for FAQPage are clear on one point. Every question and answer in the markup must be visible to the user on the page. The schema is a label for content that is there. It is not a place to put extra content.

Break that rule and you risk a manual action. Worse, you create two versions of the truth. The schema says one thing, the page says another, and an AI tool may quote the hidden one to a customer who then cannot find it on your site.

The safest rule is the strict one. The text in the schema should be the same text a visitor can read, word for word. Not a summary. Not a longer version. The same words.

Content inside a closed accordion counts as visible. A <details> tag that opens on tap is fine. Content hidden with CSS that never shows, or loaded only for bots, is not.

Write Questions Customers Actually Ask

Pull questions from real calls, texts and emails. Ask the person who answers the phone what they hear every week. Write the question in the customer's words, with sentence case and a question mark.

• Good: "Do you work on hybrids?"
• Good: "Can I wait while you do the oil change?"
• Bad: "Why is Example Auto the best choice for hybrid service?"
• Bad: "What are the benefits of regular maintenance?"

Answer in one to four plain sentences. Put the direct answer first. Yes, no, a time, a fact. Then add the one detail that matters. Do not stuff keywords into answers. Do not put a price in an answer unless it comes from the same place your quotes do.

The Visible FAQ Block

Here is a plain, accessible FAQ block. It uses <details> and <summary>, which open and close with no script and work with a keyboard and a screen reader.

<section id="faq">
  <h2>Questions We Get Every Week</h2>

  <details>
    <summary>Do you work on hybrids?</summary>
    <p>Yes. We service most hybrids, including brakes, cooling and the 12 volt
       battery. For the high voltage battery we test it first and tell you
       what we find before any work starts.</p>
  </details>

  <details>
    <summary>How long does a brake job take?</summary>
    <p>Most brake jobs take about two hours. If the rotors need replacing we
       call you with the price before we go ahead.</p>
  </details>
</section>

Keep the answer as plain text in a paragraph. Links and lists in an answer are allowed, but they make the match with the schema harder. Plain text is easiest to keep in sync.

The Matching JSON-LD

Put this in the head or at the end of the body. Each question's name is the summary text. Each text is the answer paragraph. Same words, same order.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you work on hybrids?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We service most hybrids, including brakes, cooling and the 12 volt battery. For the high voltage battery we test it first and tell you what we find before any work starts."
      }
    },
    {
      "@type": "Question",
      "name": "How long does a brake job take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most brake jobs take about two hours. If the rotors need replacing we call you with the price before we go ahead."
      }
    }
  ]
}
</script>

Use one FAQPage block per page. If a page has two FAQ sections, put all the questions in one mainEntity list. Test the page with Google's Rich Results Test and the Schema Markup Validator. Both should read it with no errors.

Where FAQs Belong on a Site

Put questions where the question comes up. A brake page gets brake questions. A city page gets questions about that town. The home page gets the few questions every new customer asks, such as hours, booking and payment.

A separate FAQ page is fine as a place to collect the general ones. It should not be the only place. Someone reading about brakes should not have to leave the page to learn how long the job takes.

Place the FAQ block near the end of the main content, before the footer. Give it a plain heading such as "Questions We Get Every Week". Link to it from the top of the page if the page is long, so a skimmer can jump straight there.

Do not repeat the same questions on every page. Each page should carry the questions that belong to its topic. A few shared ones, like how to book, are fine. A whole block copied site wide is not.

How FAQs Help With AI Answers

When someone asks an AI tool a question about a local service, the tool looks for a short, clear answer from a page it trusts. A question as a heading with a direct answer under it is the easiest thing for it to lift. That is exactly the shape of a good FAQ.

So write each answer so it makes sense alone. Do not start with "As we said above". Name the thing you are talking about. "Most brake jobs take about two hours" can be quoted anywhere. "It usually takes about two hours" cannot, because nobody knows what "it" is.

This is also why the schema has to match. If the tool quotes your schema and the page says something else, the customer who clicks through finds a different answer.

Build Both From One List

The way FAQs go wrong is drift. Someone fixes a typo in the visible answer. The schema keeps the old text. A month later a price changes on the page and the schema still quotes the old one. Nobody notices, because nobody reads JSON-LD.

Stop that at the source. Keep each page's questions in one list, in your page data. Have your template build the visible block and the JSON-LD from that same list. Then a change is one edit and both sides move together.

If you use a CMS, put the FAQs in a repeatable field and have the theme write both outputs. Never paste the JSON-LD by hand into a page.

What the Finishing Pieces Contain

You now have everything needed to add a matching FAQ to a page by hand. The finishing pieces make it safe across a whole site. They hold a small function that turns one list into both the visible block and the JSON-LD, a check script that reads your built pages and fails if any schema text is missing from the page, and the edge cases that break the match. Enter your email to open them. To see how FAQs fit into local pages, read city pages that rank.