Does FAQ Schema Still Help You Get Cited by AI?

A year ago, every SEO checklist said the same thing: add FAQ schema and watch your answers appear in Google and in AI answers. Then, in 2026, Google stopped showing FAQ rich results altogether. If you run a Melbourne service business and paid someone to add FAQ schema to every page, you are entitled to ask what it is doing now.

Short answer: FAQ schema no longer earns a rich result in Google, which stopped showing FAQ rich results in May 2026, and Google says no special schema is needed for AI Overviews. What still works is the FAQ content itself: real customer questions answered plainly on the page. Markup generated from that visible content is cheap and harmless, but it is not a citation switch.

What happened to FAQ rich results?

They are gone from Google Search. Google's Search documentation changelog records a deprecation notice in May 2026 saying the FAQ rich result would no longer appear in Google Search from 7 May 2026, and in June 2026 Google removed the FAQ rich result documentation entirely because the feature is no longer shown.

This was the end of a slow fade. Google had already limited FAQ rich results to well-known, authoritative government and health websites back in 2023, so most small businesses had not seen their FAQs expand under a search result for years.

None of this affects the questions and answers on your page. Only the special search result built from the markup has gone.

Does FAQ schema help you get cited by AI Overviews?

Not directly, by Google's own account. Its guide to optimising for generative AI features lists "overfocusing on structured data" among the things you do not need to worry about: structured data is not required for generative AI search, and there is no special schema.org markup you need to add. It still recommends structured data as part of overall SEO, and says markup should match the visible text on the page.

What gets a page used in an AI Overview is what gets it ranked: being indexed, being eligible for a snippet, and answering the question better than the alternatives. AI Overviews retrieve pages through Google's core ranking systems and often run several related searches to build one answer. A page with five well-answered customer questions matches more of those related searches than a page with none, whether or not the questions carry markup.

For ChatGPT, Perplexity and the other assistants, no vendor documents that FAQPage markup earns citations. They read pages. Some may read the markup too, but anyone promising that schema gets you into ChatGPT is selling a guess.

So is FAQ schema still worth adding?

Yes, if it costs you nothing to keep accurate. No, if it means maintaining a second copy of your answers by hand.

What people say FAQ schema does	Is it true in 2026?
Shows expandable FAQs under your Google result	No. Google stopped showing FAQ rich results in May 2026
Helps Google understand what the page contains	Yes. Google says it uses structured data to understand page content
Required to appear in AI Overviews	No. Google says no special schema is needed
Gets you cited by ChatGPT	Unproven. No assistant documents it
Safe if it says something the page does not	No. Google's policies say not to mark up content readers cannot see

Google's structured data guidelines are clear on that last row: do not mark up content that is not visible to readers, and do not use structured data to mislead. Markup that drifts out of sync with the page is worse than none.

The safest pattern is the one this blog uses: write the FAQ section once, on the page, and have the site generate the FAQPage markup from that visible section automatically. The two can never disagree, and nobody has to remember to update both.

Which questions belong in a service business FAQ?

The ones customers actually ask you, in the words they use. The value now sits almost entirely in the content, so the questions matter more than the code.

For a Melbourne electrician, good questions come straight from the inbox and the phone:

• "Do you work in Bayside on Saturdays?"
• "Can you replace an old switchboard in the same day?"
• "Do I need to be home for a smoke alarm check?"
• "What happens if you find old wiring during a job?"

Bad questions are the ones nobody asks: "Why are we Melbourne's most trusted electrician?" That is an ad wearing a question mark, and it gives neither a customer nor an AI summary anything to use.

Answer each in two to four sentences. Start with the direct answer ("Yes, Saturday mornings from 8am"), then the condition or detail. If the honest answer is a price range, give one and say what moves it. If it depends, say what it depends on.

How do you add FAQs and markup properly?

Six steps, and the first two are where the value is.

Caption: Steps one and two do the work for customers and AI. The markup is the last mile.

1. Collect real questions. Pull them from emails, chat logs, call notes and review comments over the last few months.
2. Write short answers. Two to four sentences, direct answer first.
3. Publish them visibly on the page each question belongs to. Switchboard questions on the switchboard page, not one giant FAQ page.
4. Generate the markup from that visible content, using your site or plugin, not by hand.
5. Validate it with the Schema Markup Validator at validator.schema.org, which checks schema.org markup in general now that Google no longer offers an FAQ rich result to test for.
6. Review quarterly. Prices, hours and service areas change. Old answers are worse than no answers.

For reference, generated FAQPage markup looks like this, and every word in it also appears on the page:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Do you work in Bayside on Saturdays?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. We take Saturday morning jobs in Brighton, Hampton, Sandringham and Black Rock from 8am to 1pm. Emergency callouts outside those hours are quoted separately."
    }
  }]
}

Should you use a plugin or a custom build?

On WordPress, SEO plugins such as Yoast and Rank Math include FAQ blocks that output the markup from the visible questions. If your FAQs are already in WordPress, use them. That is the right call for most small sites.

A custom build is worth it when the questions themselves are the problem. Most businesses have hundreds of real questions sitting in their inbox, their website chat and their booking notes, and nobody has time to read them. An AI integration can:

• read new enquiries from your inbox, web chat or booking system each week;
• group them into recurring questions and flag ones your site does not answer;
• draft a short answer from your approved information for you to edit and approve;
• publish the approved answer to the right page, with markup generated from it.

A person approves every answer before it goes live, because an FAQ is a public statement about your business. As an estimate, this kind of integration is $2,500 to $6,000 at a fixed price, built in two to three weeks, with hosting under $50 a month and AI usage usually at the low end of $20 to $200 a month. If the questions are mostly about bookings and availability, an AI receptionist may answer them better in the moment than any FAQ page.

For the bigger picture on what AI search rewards, see SEO vs GEO, and for where FAQs sit on a local page, how suburb landing pages get landscapers cited by AI.

Frequently asked questions

Should I remove FAQ schema that is already on my site?

Not if it matches the visible questions and answers on each page. It no longer produces a rich result in Google, but accurate markup does no harm. Remove or fix any markup that describes content readers cannot see, or answers that have since changed.

What about HowTo schema?

Google retired HowTo rich results in 2023, well before FAQ. The same logic applies: clear, well-structured instructions on the page are what help readers and AI answers, and the markup alone earns nothing visible in Google.

How many FAQs should a page have?

As many as customers genuinely ask about that page's topic, which is usually three to eight. Repeating the same five questions on every page adds nothing and makes the site harder to read.

Will a separate FAQ page work better than FAQs on each service page?

Usually not. A question answered on the page it belongs to gives that page more to rank and be quoted for. A single FAQ page can still work as an index that links out to the detailed answers.

Want your real customer questions on your site?

We will look at your enquiries, your current FAQs and how your pages read to AI search, then show you which questions are worth answering first. Book a free AI workflow audit. The audit fee comes off your first project.