In August 2023, Google restricted FAQ rich results to government and health websites. Most commercial sites lost their expandable FAQ snippets in SERPs. Many businesses abandoned FAQ schema entirely after that change.
That was the wrong move. Google has not said it ignores FAQ schema. It still parses it, still learns from it, and still uses it to understand content structure. FAQ schema still influences featured snippet eligibility, People Also Ask placement, voice search results, and AI Overview citations. Only about 12.4% of domains use any schema.org markup at all. The businesses that maintained their FAQ schema while competitors dropped theirs are now better positioned for AI-intermediated search.
How People Also Ask Works for Local Queries
Google’s PAA Selection Logic: Why Certain Questions Surface
People Also Ask boxes appear for the majority of Google searches, and local queries are no exception. The selection logic combines relevance to the original query, frequency of similar questions across searches, available content that provides clear answers, and user engagement patterns with which questions people actually click to expand.
For local queries like “best dentist in Macon,” PAA boxes might show: “How do I choose a good dentist?”, “What should I look for in a family dentist?”, “How much does a dental cleaning cost without insurance?”, “Are walk-in dentists any good?”
These questions represent the research path a potential customer follows. If your content answers these questions with the clarity and structure Google prefers, you appear in PAA boxes alongside or above competitors.
PAA Expansion Behavior: How Clicking Opens New Questions
When a user clicks to expand a PAA question, Google dynamically loads additional related questions below it. PAA is not a fixed list but an expanding tree of related queries.
Each expanded answer reveals new questions. A user who clicks “How much does a dental cleaning cost?” might see new questions about insurance coverage, payment plans, and cost comparisons. This expansion behavior means winning one PAA placement can lead to visibility across an entire cluster of related questions.
Local Queries That Consistently Trigger PAA Boxes
Certain local query patterns reliably generate PAA: “[service] near me” queries, “[service] in [city]” queries, “best [professional] in [city]” queries, “how much does [service] cost in [city]” queries, and “how to find a [professional] in [city]” queries.
Questions involving cost, quality evaluation, process explanation, and comparison reliably appear in PAA for local services. These are the questions you should prioritize in your content.
Reverse Engineering PAA for Your Market
Scraping PAA Results Across Your Target Keywords
Search each of your target keywords and record the PAA questions that appear. Click to expand each question and record the new questions that appear. Do this across your full keyword list to build a comprehensive map of PAA questions in your market.
Tools like Semrush, Ahrefs, and AlsoAsked.com automate this process. They scrape PAA results at scale and show which questions appear most frequently across your keyword set.
Manual collection works for small keyword sets under 50 terms. For larger sets, use tools to avoid spending days on manual scraping.
Categorizing Questions by Intent: Pre-Purchase, During, Post-Purchase
Organize your PAA questions into the buying cycle.
Pre-purchase questions: “How do I choose?”, “What should I look for?”, “How much does it cost?”, “What is the process?” These come from people evaluating options. Your answers should build trust and demonstrate expertise.
During-purchase questions: “What do I need to bring?”, “How long does it take?”, “What should I expect?” These come from people who have decided to use a service and want practical information.
Post-purchase questions: “How do I maintain?”, “When should I schedule the next?”, “What if something goes wrong?” These come from existing customers or people planning ahead.
Each category lives on a different page type. Pre-purchase answers belong on service pages. During-purchase answers fit on preparation or process pages. Post-purchase answers work on maintenance guides and follow-up pages.
Identifying PAA Gaps Your Competitors Haven’t Answered
Look at who currently wins each PAA placement. If the current source is a national site with a generic answer, a localized answer from a local business can win the spot. Google prefers locally relevant content for local queries.
If no competitor in your market has content directly answering a frequent PAA question, that gap is your opportunity. A well-structured answer to an uncontested PAA question can win the placement with relatively little competition.
Writing Answers That Win PAA Placement
Answer Length and Format That Google Prefers to Extract
Google’s PAA extraction favors concise, direct answers. The optimal format: a 40 to 60 word direct answer in the first paragraph, followed by supporting detail.
The first paragraph should answer the question as if someone asked you directly and you had one breath to respond. No preamble, no filler. Direct answer, immediately.
Bad: “When it comes to choosing a plumber, there are many factors to consider. The plumbing industry has evolved significantly over the past decade…”
Good: “Choose a plumber based on three factors: valid state license (verify at your state licensing board), reviews from customers in your specific neighborhood, and transparent pricing provided before work begins. Licensed plumbers carry insurance that protects your home if something goes wrong.”
Structuring Content so Google Can Pull Clean Snippets
Format each FAQ as a question heading (H2 or H3) followed by a concise answer paragraph. This structure maps directly to how Google extracts content for both PAA and featured snippets.
Use the exact question phrasing people use. “How much does a dental cleaning cost?” works better than “Dental Cleaning Pricing Information.” The heading should match the natural language query.
Keep answers self-contained. Each answer should make sense without reading the rest of the page. Google extracts individual Q&A pairs, not entire sections.
Matching Answer Tone to Query Intent (Transactional vs Informational)
Transactional queries (“how much,” “where to find,” “how to hire”) need direct, practical answers with numbers, steps, or recommendations. Informational queries (“what is,” “how does,” “why should”) need educational answers that explain concepts clearly.
Match the tone to the intent. A person asking “how much does roof repair cost in Atlanta” wants a price range and the factors that affect it. A person asking “what causes roof leaks” wants an explanation. Giving the first person an explanation and the second person a price range mismatches intent and loses the PAA placement.
FAQ Schema Implementation
FAQPage Schema Markup: Correct JSON-LD Structure
FAQPage schema uses JSON-LD format. Each question-answer pair is a separate entity within the mainEntity array:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much does a dental cleaning cost in Macon?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A dental cleaning in Macon costs between $75 and $200 without insurance, depending on whether it is a standard cleaning or a deep cleaning. Most insurance plans cover two cleanings per year at no out-of-pocket cost."
}
},
{
"@type": "Question",
"name": "Do you accept walk-in dental patients?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, we accept walk-in patients during regular business hours Monday through Friday. Wait times for walk-ins average 20 to 40 minutes. For shorter wait times, we recommend scheduling an appointment."
}
}
]
}The schema content must match the visible page content exactly. Do not put answers in schema that do not appear on the page.
Where to Place FAQ Sections on Local Service Pages
Place FAQs at the bottom of the service page they relate to, above the footer. A plumbing service page gets plumbing FAQs. A water heater page gets water heater FAQs.
Also create a central FAQ hub page that collects the most important questions across all services. This hybrid approach (distributed FAQs on service pages plus a central hub) provides both contextual relevance and a comprehensive resource.
The central hub page should link to the relevant service pages for deeper information. The service pages should not duplicate the full FAQ hub; they should contain only the questions most relevant to that specific service.
Combining FAQ Schema with Other Local Markup Without Conflicts
FAQPage schema and LocalBusiness schema coexist without conflict when placed on the same page. They describe different things: FAQPage describes the question-answer content, LocalBusiness describes the business entity.
Do not nest FAQPage schema inside LocalBusiness schema. They should be separate entities within the same JSON-LD script tag or in separate script tags on the same page.
This guide covers FAQPage schema only. LocalBusiness schema implementation is covered in the schema markup guide. Event schema is covered in the events guide. Keeping schema types in their respective implementation contexts prevents conflicts and simplifies maintenance.
Tracking PAA Wins and FAQ Rich Results
Monitoring PAA Presence with Rank Tracking Tools
Standard rank tracking tools show your position for a keyword. PAA tracking is different because you need to know whether your URL appears within the PAA box for a given query, not just where you rank in organic results.
Semrush, Ahrefs, and STAT track PAA appearances. Configure tracking for your target PAA keywords and monitor which URLs win the PAA placement. Track changes over time to understand whether your FAQ content strategy is gaining or losing PAA visibility.
Search Console Data: Filtering for FAQ Rich Result Impressions
Google Search Console’s Performance report can be filtered by search appearance type. If your FAQ schema generates any rich results (even limited ones for health or government categories), they appear here.
For non-government, non-health businesses, FAQ rich result impressions will be minimal after the 2023 restriction. Instead, focus on monitoring impressions and clicks for the specific URLs containing your FAQ content. Growth in impressions for those URLs indicates Google is recognizing and testing your FAQ content for relevant queries, even without the expandable rich result display.
Track query data for FAQ page URLs separately. The queries generating impressions should align with the questions you are targeting. If they do not, your question phrasing may not match how people actually search.
FAQ schema implementation in this guide uses FAQPage type only. LocalBusiness schema is covered separately. The August 2023 restriction on FAQ rich results for commercial sites remains in effect as of February 2026, but FAQ schema continues to influence featured snippets, voice search, and AI citations.