How do I find the right People Also Ask questions to target?

Find the real questions in Google's own People Also Ask box, in AI chat follow-up prompts, and in your own support tickets and search console data. Write the question in the exact words a searcher would use, then answer it directly in the first sentence.

Does Google still show a rich result for FAQ schema?

Google restricted it in August 2023 to well-known, authoritative government and health websites, then deprecated the feature entirely, stopping it from appearing in Search starting May 7, 2026. Most business sites will not see the visual FAQ snippet in Google anymore.

Is FAQPage schema still worth using if the rich result is gone?

Yes. Google has said unused structured data causes no problems, and FAQPage schema still gives AI crawlers and answer engines a clean, pre-labeled question and answer pair to extract, even without the Google rich result that used to display it.

What makes a PAA answer more likely to get cited?

Lead with the direct answer in plain language within the first sentence, keep the whole answer to 40 to 60 words, make it specific rather than vague, and ground every claim in something the surrounding article actually supports elsewhere on the page.

Where should PAA questions go on the page?

Place each question as its own heading directly above the paragraph that answers it, so the question and its proof sit together. A dedicated FAQ section near the end still works for shorter questions, as long as each answer stays grounded in the article.

How do I measure whether my PAA questions are getting cited?

Watch Search Console's performance report for the exact question phrasing, periodically search the question yourself logged out to check for a PAA appearance or AI citation, and filter GA4 for referral traffic from AI tools to confirm a citation is sending visits.

How to Write People Also Ask Questions That AI Will Cite

People Also Ask questions get cited when they sound like a real person asking and answer in the first sentence. Here is how to find the real questions, write answers AI can lift cleanly, and still use FAQ schema now that Google's rich result is gone.

Write People Also Ask questions the way people actually type or speak them, answer each one in 40 to 60 words right after the question, mark them up with FAQPage structured data, and place them near the content that proves the claim. That combination gets a question cited by AI answer engines.

At a glance

Start from real questions, pulled from Google's own People Also Ask box, "People also search for," and the follow-up prompts AI tools surface, not from guesses about what sounds good.
Phrase the question like a person, not a marketer. Match the words a real searcher types or speaks, including the awkward ones.
Answer first, in 40 to 60 words. The direct answer comes immediately after the question, with supporting detail after it, not before.
Mark it up with FAQPage schema. Google no longer shows a visual FAQ rich result for most sites, but the structured data still hands AI systems a clean, labeled question and answer pair.
Place questions near the proof. A PAA block answering a question your article does not actually support elsewhere on the page will not get cited by anything that checks.

Where Do You Find the Real Questions People Ask?

The biggest mistake in writing PAA-style questions is inventing them. Google's own People Also Ask feature already shows you the real, expanding list of follow-up questions searchers have around a topic, pulled from actual query data, not from a guess at what might rank. Before writing anything, search your target keyword yourself and record every PAA question that appears, then click into a few of them, since each click reveals a fresh set of follow-ups.

Do the same across the surfaces that matter now beyond classic Google search:

"People also search for" and related searches at the bottom of the results page, which surface adjacent phrasing and subtopics.
AI chat follow-up prompts. When you ask ChatGPT or Perplexity a question in your topic, look at the follow-up questions they suggest. These reflect how the same intent gets explored in a conversational interface, which is closer to how generative engine optimization actually gets evaluated.
Your own search console and support data. The exact phrasing customers use in support tickets, reviews, and site search is often a better source than any tool, because it is not filtered through a keyword tool's normalization.
Community sites. Forums and Q&A communities show the real words people use to ask a question when no one is optimizing the phrasing for search.

Collect more questions than you need, then keep only the ones your page can genuinely answer with specific, accurate information. A question you cannot answer well should not make the list just because it has search volume.

How Do You Phrase a Question the Way People Actually Ask It?

Real questions are rarely as tidy as a keyword list. People ask "how long does SEO take to work" and "do I need to redo my website for AI search," not "SEO timeline expectations" or "AI search website requirements." Write the question exactly as a person would say it out loud or type it into a search box, including the conversational framing.

A few patterns to keep:

Keep the question form. "What is X" and "how do I X" outperform a statement rephrased with a question mark stapled on.
Match the specificity of the real query. If people ask about a specific tool, price range, or timeframe, keep that detail in the question rather than generalizing it away.
Do not merge two questions into one. "What is X and how much does it cost" should usually be two separate questions with two separate direct answers, since that is how both PAA and AI answer engines structure a response.

How Do You Write an Answer AI Will Actually Cite?

The answer, not the question, is what gets lifted into a PAA snippet or an AI-generated response, so the first sentence has to do the work.

Lead with the direct answer in plain language, then follow with 20 to 40 more words of the specific detail, qualification, or number that makes the answer trustworthy rather than generic. Aim for a total of 40 to 60 words.

What separates a citable answer from a buried one:

No throat-clearing. Skip "That's a great question" or a paragraph of context before the answer arrives. Answer, then explain.
Specific over vague. "Most local SEO campaigns show measurable movement in 3 to 6 months" beats "it depends on several factors," even though the honest answer often does depend on several factors you can mention afterward.
Self-contained. The answer should make sense if it is the only sentence a reader or an AI system ever sees, since that is often exactly what happens.
Grounded in the page. Never write an FAQ answer that claims something the rest of the article does not actually support. An answer engine checking the surrounding content, or a human reader scrolling up, will catch the gap.

Do You Still Need FAQPage Schema If Google Doesn't Show the Rich Result Anymore?

Yes, and the history here matters. In August 2023, Google restricted the FAQ rich result so it would "only be shown for well-known, authoritative government and health websites," with the visual snippet no longer shown regularly for anyone else. Then, per Google's Search Central changelog, Google deprecated the feature entirely in May 2026, noting it would stop appearing in Search starting May 7, 2026, and later removed the FAQ rich result documentation altogether. For almost every business site, the FAQ rich result in classic Google search is gone.

That does not make FAQPage schema pointless. Google's own guidance when it first restricted the rich result noted that structured data sitting unused on a page "does not cause problems for Search." More importantly for GEO, the schema still gives any system reading your page, an AI crawler, an answer engine, a language model doing retrieval, a question and its answer pre-labeled and separated from your navigation, ads, and layout. You lose the visual snippet in Google. You keep the clean, machine-readable pair that makes extraction and citation easier everywhere else, including inside Google's own AI Overviews, which pull from indexed content rather than from the deprecated rich result feature.

Where Should PAA Questions Live on the Page?

Placement affects whether a question gets associated with the content that proves it. Put each question as its own heading, directly above the paragraph or list that answers it, rather than batching every question into an FAQ dump at the very bottom disconnected from the body. Within the body of a guide like this one, a question-shaped H2 or H3 followed immediately by the direct answer does double duty: it reads naturally and it is extractable.

A dedicated FAQ section near the end still earns its place, especially for the shorter, adjacent questions that do not warrant a full section of their own, as long as each answer is grounded in a claim the article already made above it. What does not work is writing a generic FAQ block as an afterthought, disconnected from the actual content, purely to tick a schema box.

How Do You Measure Whether It's Working?

Track PAA and AI citation the same way you would track any other content investment, not by vibes:

Search Console's performance report, filtered to the query, to see if impressions grow for the question phrasing you targeted, and whether you start appearing for the exact long-tail question itself.
Direct checks. Periodically search the target question yourself, logged out, and note whether your page appears in the PAA box, an AI Overview, or a cited source in ChatGPT or Perplexity.
Referral and direct traffic from AI tools, which shows up in GA4 once you know what to filter for, confirming that a citation is actually sending people, not just appearing.
Rich result and schema validity, checked in Search Console's enhancement reports, so a markup error does not quietly disqualify a page that would otherwise qualify.

This is slower to show results than a rankings report, since a citation inside an AI answer does not always leave a clean click trail, but the combination of Search Console data and periodic manual checks will tell you honestly whether the work is landing.

The Bottom Line

Writing a PAA question that gets cited is less about a format trick and more about discipline: find the question people actually ask, answer it in plain language up front, back it with schema even though the visual rich result is gone, and place it next to the content that proves it true. Our guide to answer engine optimization covers the wider practice this fits inside, getting named as a source when AI answers for your customers instead of a search engine.