Google 停止顯示 FAQ 豐富搜尋結果後，如何撰寫可供 AI 答案引用的網站 FAQ

For years the main reason to add an FAQ section was the dropdown it could earn in Google results. That reason has gone. The page itself still matters, though, because AI assistants and AI search features pull short, direct answers from pages, and a well-built FAQ is one of the easiest things on a site for them to lift.

This post covers what changed at Google, what still makes an FAQ worth writing, and the HTML pattern we use so each answer stands on its own.

Disclosure: Appie.run publishes this post. The AI FAQ Generator and Website FAQ Generator mentioned below are our free tools. Everything else here works with any CMS and no tool at all.

What Google changed (as read on 26 Oct 2026)

From Google's Search Central updates and Search Console Help:

FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google added a deprecation notice on 8 May.
On 15 June 2026 Google removed the FAQ structured data documentation, the FAQ report in Search Console and FAQ support in the Rich Results Test.
Search Console API support for FAQ appearance data was removed in August 2026.
Google says existing FAQPage markup can stay on your pages and causes no harm.
In the same June update Google noted that an llms.txt file isn't needed for Google Search.

So: no more SERP dropdown, no penalty for leftover markup, and no special file required. What's left is the content.

Why an FAQ is still worth writing

Nobody outside the AI companies can tell you exactly how each assistant picks its sources, and we won't pretend to. What you can control is whether your answer is easy to find, easy to extract and correct when pulled out of context. A question-and-answer block does all three if you write it properly:

The question matches the way people actually ask it.
The first sentence of the answer is the answer.
The answer makes sense without the paragraphs around it.

Those same properties help a human who lands on the page from a support link, so the work isn't wasted whichever way the traffic arrives.

Step 1: Collect real questions

Don't invent questions in a meeting. Pull them from places where customers already asked:

Support tickets and live chat transcripts
Sales call notes ("Does it work with...?", "What happens when...?")
Reddit and community threads in your category
Your site search logs

Group duplicates, then keep the 8 to 15 that come up most or block a purchase.

Step 2: Write answers that survive being quoted alone

A quick test for each answer: paste it into a blank doc with only the question above it. Does it still make sense?

Weak:

Yes, as mentioned above, it does, depending on your plan.

Better:

Yes. Team plans include SSO via SAML. The Starter plan does not.

Rules we follow:

Answer in the first sentence. Yes/no, a number, or a name.
Name the thing. Say "the Starter plan", not "this plan".
Keep it to 40 to 80 words for most answers. Link out for detail.
Date anything that changes. "As of 26 Oct 2026, the Starter plan costs $19/month." Prices and limits go stale, and a stale quoted answer is worse than none.
Only state what the page can back up. If the policy lives elsewhere, link to it rather than paraphrasing it loosely.

Step 3: Use plain, semantic HTML

You don't need a plugin. Headings for questions and paragraphs for answers are enough, and they render the same for every crawler:

<section id="faq" aria-labelledby="faq-title">
  <h2 id="faq-title">Frequently asked questions</h2>

  <h3 id="faq-sso">Does the Starter plan include SSO?</h3>
  <p>No. SSO via SAML is included on Team plans only. The Starter plan
     uses email and password sign-in. <a href="/pricing">Compare plans</a>.</p>

  <h3 id="faq-cancel">Can I cancel at any time?</h3>
  <p>Yes. You can cancel from the Billing page, and your plan stays active
     until the end of the current billing period.</p>
</section>

If you prefer collapsible answers, <details>/<summary> keeps the text in the HTML:

<details>
  <summary>Can I cancel at any time?</summary>
  <p>Yes. You can cancel from the Billing page, and your plan stays active
     until the end of the current billing period.</p>
</details>

Avoid loading answers only via JavaScript after a click. If the text isn't in the served HTML, some crawlers will never see it.

Give each question an id so you can link straight to it from support replies and docs.

Step 4: Keep or add FAQPage markup (optional)

Google no longer shows FAQ rich results, and it says leftover markup does no harm. Other consumers of schema.org data may still read it, so if it's already there, keep it in sync with the visible text. If you add it, mirror the on-page wording exactly:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I cancel at any time?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can cancel from the Billing page, and your plan stays active until the end of the current billing period."
      }
    }
  ]
}
</script>

The risk with markup is drift: someone updates the visible answer and forgets the JSON. If your FAQ comes from a CMS field, generate both from the same source.

Step 5: Put the FAQ where the question is asked

One giant /faq page is fine as an index, but the most useful placement is next to the thing in question: pricing questions on the pricing page, setup questions in the docs. A short block of 4 to 6 questions per page tends to stay accurate because the owner of that page sees it.

Step 6: Review it on a schedule

Add a "last reviewed" date and put a recurring reminder on someone's calendar. Every price, limit and integration claim in the FAQ should be checked against the product at least each quarter.

Getting a first draft faster

If you have the source material but not the time, two of our free browser tools can produce a draft for you to edit (both run a captcha check first):

AI FAQ Generator (appie.run/tools/ai-faq-generator): paste up to 2,000 characters of text, pick 1 to 10 FAQs, a language and a tone. The answers are grounded in the text you pasted, and it doesn't add policies or prices that aren't there.
Website FAQ Generator (appie.run/tools/website-faq-generator): give it up to 5 public URLs. It skips questions it can't answer from those pages instead of guessing.

Treat the output as a draft. Check every answer against Step 2's rules before it goes live.

Checklist

[ ] Questions come from real customer sources
[ ] Each answer starts with the answer
[ ] Each answer makes sense on its own
[ ] Prices and limits carry an "as of" date
[ ] Questions and answers are in the served HTML
[ ] Any FAQPage JSON-LD matches the visible text word for word
[ ] A review date is set

Google sources: Search Central blog and Search Console Help pages on FAQ rich results and structured data, read 26 Oct 2026.

RG, Founder, Appie.run