AEO · 8 min read
How to Rank in Google's People Also Ask Boxes
Summary
People Also Ask showed on 51.85% of searches. Here's how a site with no authority wins the whole question chain behind a service query.
By Hyder Shah, Founder & CEO · Published July 13, 2026 · Updated July 13, 2026
Position one is a single slot. A People Also Ask box is not. It regenerates every time a user taps a question, and each new answer comes from a different page. That is the only spot on a service-business SERP where a domain with no links and no history can get its name in front of a buyer this quarter instead of next year.
Most guides on this stop at 'use the question as an H2.' That is step four of seven, and it skips the mechanic that actually makes PAA worth an afternoon. Here is the whole thing.
What is the People Also Ask box, and why is it easier to win than position one?
People Also Ask is a Google SERP feature that lists questions related to your search, each expanding into a short answer sourced from one web page with a link to it. Semrush Sensor data from August 2024 put PAA boxes on 51.85% of all searches — more than half. It is one of the most common features on the results page.
The reason it is winnable: a PAA box shows three or four questions, and expanding any of them loads more. Ahrefs describes the supply as seemingly infinite — more questions load every time you click. So one SERP can surface a dozen source pages, not one. There is no winner-take-all math to lose.
It is also growing. seoClarity measured US PAA prevalence rising 34.7% on mobile and 37.5% on desktop between February 2024 and January 2025.
Do you need to rank in the top 10 to appear in PAA?
Effectively yes — but in the top 10 for the question, not for your head term. Ahrefs' analysis is blunt about it: most PAA answers come from one of the top ten rankings for the question itself, so unless you already rank there, your page is not an eligible answer source. Check it by searching the question in incognito and looking for your URL in the top 10.
That distinction is the entire opportunity. 'ac repair cost' is a bloodbath. 'how much does an emergency ac call cost at night' is a different SERP with a different, much weaker top 10 — often forums, a contractor blog from 2019, and a national aggregator. You are not competing with the money-term winners. You are competing with whoever bothered to answer the question.
So PAA work is not a shortcut around ranking. It is a shortcut around ranking for the expensive keyword. Our keyword research process for service businesses sorts long-tail questions by winnability for exactly this reason.
How does the accordion mechanic let one answer earn several more?
Two behaviors compound. First, expanding a PAA question loads more questions beneath it — the box grows as the user digs. Second, Ahrefs found that when the same question appears in PAA boxes across different queries, Google pulls the answer from the same source every time, and could not find a single exception while researching it.
Put those together and the payoff of one well-formed answer is not one impression. It is: every query whose PAA box contains that question, plus every deeper question your page also answers as the reader expands the chain.
That is why answering one question per page loses. You want a page that can be Google's source for six adjacent questions in the same chain — because they surface together, and they surface repeatedly.
How do you find the PAA chain for a service query?
Take 20 minutes and expand the box by hand — that is genuinely the highest-fidelity method, and it costs nothing. Search your money query in incognito, expand the first question, then expand every child question it spawns, three levels deep. Write down every question in the order Google surfaced it. You now have the chain.
Then check the current answer for each: who is the source, and what format did Google pull — a paragraph, a list, or a table? Ahrefs, Semrush, and seoClarity all say the same thing here, and it is the step people skip: if Google is showing a bulleted list for that question and you wrote a paragraph, you are not getting picked.
| Tool | What it gives you | Price | The catch |
| Google, incognito, expanded by hand | The real chain, in Google's order, with the current source and format | Free | 20 minutes per query, no export |
| AlsoAsked | A visual tree of PAA questions and their children | Free tier, paid plans above it | Shows the questions, not who currently owns the answer |
| Semrush Keyword Magic | Keywords filtered to those that trigger a PAA box, with volume | Paid | Volume on question keywords is often under 10 — judge by chain size, not volume |
| Search Console query report | Question-shaped queries your page already gets impressions for | Free | No PAA breakout — you are inferring, not measuring |
Ignore search volume on these. Ahrefs notes most PAA questions have low or no reported monthly volume — the value is in how many parent queries surface the question, not in the question's own volume.
How do you structure an H2 stack that catches a whole PAA chain?
One H2 per question in the chain, phrased the way Google phrased it, with a complete answer in the first 40 to 60 words underneath — no preamble, no throat-clearing, no 'before we get into that.' Google's own guidance for its answer surfaces is to make sure important content is available in textual form and that structured data matches the visible text.
The order matters too. Stack the H2s in the sequence the accordion surfaced them, because that sequence is Google's model of how the topic unfolds. A page that mirrors the chain reads as the natural source for the whole chain.
- Use the question verbatim as the H2 — Google matched a phrasing, so give it that phrasing.
- Answer in the first sentence, in a complete, standalone statement with a number or a bounded range in it.
- Match the format Google is currently showing for that question: paragraph, bulleted list, or table.
- Keep the answer block short. If it needs 400 words of context, put the context after the answer, not before.
- Add an FAQ block for the shorter questions in the chain that do not deserve their own H2.
This is the same discipline as passage-level optimization with an inverted pyramid: the extractable answer goes first, the supporting depth goes after. One page, written once, competes for the PAA box, the featured snippet, and the AI Overview on the same query.
How do you tell whether a PAA answer produced any traffic?
You cannot measure it cleanly, and anyone who tells you otherwise is selling something. Ahrefs states the problem plainly: Google does not show PAA interaction data in Search Console, and there is no other reliable source. There is no PAA filter, no PAA impression count, no PAA click column.
What you can do is triangulate. In Search Console, filter your page's queries to those containing 'how', 'what', 'why', 'does', or 'can', and watch impressions on that page after you publish the H2 stack. A jump in question-shaped impressions at an average position inside the top 10, with clicks lagging behind impressions, is the fingerprint of PAA visibility.
Treat that as a signal, not a number. Do not put it in a client report as 'PAA traffic.' It isn't.
Does a PAA appearance ever produce a booked call, or just impressions?
Mostly impressions — and the honest numbers are small. Backlinko's 2020 user-behavior study of 1,801 search sessions found that on average, only 3% of searchers interact with a People Also Ask box, though that varied widely by query, rising to 13.6% on one query type. Working from that 3% figure and its own stated assumptions, Ahrefs estimated that roughly 0.3% of searches with a PAA box end in a click on a source.
So no: PAA is not a lead channel. On a local SERP it is even less of one — the same 2020 Backlinko study found 42% of local searchers click a result inside the Google Maps pack, which is a long way from where the PAA box sits.
The real return is the second surface your answer paragraph unlocks. Ahrefs' study of 146 million SERPs found question queries trigger an AI Overview 57.9% of the time, and Semrush's December 2025 study of 10M+ keywords found that People Also Ask appears alongside 90.03% of AI Overviews. The same block of text — question heading, direct answer, one number — is what gets extracted by both. That is why PAA lives inside an AEO program rather than being a project of its own.
Our take: do not budget for 'PAA optimization.' Write question-shaped answers because that is how you get extracted anywhere, and treat PAA appearances as the free byproduct they are. The full method sits in our AEO guide.
How is PAA different from a featured snippet?
A featured snippet is one page winning one query at the top of the page; a PAA box is three or four questions — expanding to many more — each sourced from a different page, and each answer reused across every query where that question appears. Ahrefs notes featured snippets almost always sit first or second, while PAA boxes can appear in nearly any position, and sometimes not on page one at all.
| Feature | What it is | Slots per SERP | How hard to win | Reuse across queries |
| Featured snippet | One extracted answer to the query itself, at the top | 1 | Hard — you must beat everyone on the head query | None; it is query-specific |
| People Also Ask | Related questions, each with its own source | 3-4 visible, effectively unlimited on expansion | Moderate — top 10 for the question, not the head term | High; Google reuses the same source for the question everywhere it appears |
The verdict: for a fresh domain, PAA is the better first target. The featured snippet asks you to out-rank the whole first page. PAA asks you to be the best answer to one narrow question — and pays that answer out across every SERP where the question shows up.
If your site has content that ranks but never gets extracted, the fix is almost always structural — headings that describe instead of ask, and answers buried 300 words deep. That is what our SEO service rebuilds first. Get my free audit and we will show you which of your existing pages are one heading rewrite away from an answer box.
Where does this fit in your stack?
If you're running a US service business, the playbook in this post pairs with our full services lineup and applies cleanly across our supported industries and US locations. If you want help implementing it, book a free strategy call — we'll review your current setup and prioritize the next three moves.
For the deeper engagement details, see our GEO service. New to the terminology here? Our SEO & marketing glossary defines every acronym in this post.
What are the most common questions about this topic?
Common questions readers send us about this topic.
Do I need to rank on page one to appear in People Also Ask?
You need to rank in the top 10 for the specific question, not for your main keyword. Ahrefs found most PAA answers come from a page already in the top ten rankings for the question itself. Those are two different SERPs. You may sit at position 30 for 'roof replacement cost' and still rank top-5 for 'how long does a roof replacement take' — and that second SERP is where the PAA eligibility lives.
How do I get my content into a People Also Ask box?
Find the question chain by expanding the PAA box by hand, three levels deep. Give each question its own heading, worded exactly as Google worded it. Answer it in the first 40 to 60 words underneath, with no preamble. Match the format Google currently shows for that question — paragraph, bulleted list, or table. Then confirm you rank in the top 10 for the question, because without that you are not an eligible source.
How is People Also Ask different from a featured snippet?
A featured snippet answers the query itself, in one slot, at the top of the page. People Also Ask shows related questions — three or four at first, more as you expand — each answered by a different page. Ahrefs notes featured snippets usually appear first or second, while PAA boxes can appear in almost any position on the page. PAA also reuses your answer across every query where the same question surfaces.
How long should a PAA answer be?
Roughly 40 to 60 words for a paragraph answer, placed immediately under the question heading. Long enough to be a complete, standalone answer with a specific number or range in it; short enough that Google can lift it whole. Anything that needs more context should have the context placed after the answer, not in front of it. Bulleted answers should be four to six items with no filler line.
Can Search Console tell me if I'm appearing in PAA?
No. Ahrefs states directly that Google does not show PAA interaction data in Search Console, and no other reliable source exists. The closest proxy: filter your page's queries to question-shaped ones — how, what, why, does, can — and watch for a rise in impressions at an average position inside the top 10, with clicks lagging impressions. Treat that as a signal, not a measurement, and never report it as PAA traffic.
Do PAA boxes appear on local service searches?
Yes, but the local SERP is not where PAA earns its keep. Backlinko's 2020 study of 1,801 search sessions found 42% of local searchers click a result inside the Google Maps pack, which sits well above the PAA box. On a 'plumber near me' style query, your lead is in the map pack. PAA pays off on the research questions that come before it — cost, timing, and what-happens-if queries.
Does appearing in PAA actually send traffic?
Very little on its own. Backlinko's 2020 study found only 3% of searchers interact with a PAA box on average, rising to 13.6% on some queries. Using that figure and its own stated assumptions, Ahrefs estimated around 0.3% of searches with a PAA box result in a click on a source. Treat PAA as visibility and answer-surface practice, not as a traffic channel with a forecastable number attached.
How many PAA questions can one page win?
There is no published cap, and one page winning several questions is the normal outcome of a well-built question chain. Ahrefs points out that a page answering many common questions can be pulled as the source for multiple answers, and because Google reuses the same source for a question across queries, those impressions accumulate. Build one page per chain, not one page per question.
About the author
Hyder Shah
Founder & CEO, Foundgrove
Hyder Shah is the founder of Foundgrove, an SEO and GEO agency for US service businesses. See our editorial policy for how these guides are researched and reviewed.
Related reading
Other tactical pieces from the Foundgrove blog.
- AEO · 15 min read
Answer Engine Optimization (AEO): Complete 2026 Guide
Customers ask ChatGPT and Claude before Google. Here's the AEO playbook to get cited inside the AI assistants that now pick the winners.
Read the aeo playbook → - GEO · 11 min read
Passage-Level Optimization: The Inverted Pyramid for AI
AI engines extract 120-180 word chunks, not whole pages. Here's the inverted pyramid pattern that gets passages cited — with concrete examples.
Read the geo playbook → - SEO · 11 min read
Keyword Research for Service Businesses: The 2026 Playbook
Find high-converting, buyer-intent keywords for your service business. Mine low-volume local terms that bring customers instead of chasing vanity traffic.
Read the seo playbook → - AEO · 8 min read
Featured Snippets for Service Businesses: How to Win
You cannot win a featured snippet unless you already rank top-10. Here is how to find the queries where you are eligible and take the box.
Read the aeo playbook → - AEO · 9 min read
People Also Search For: What It Is and How to Use It
PASF fires when a searcher clicks your result and bounces back to Google. Read those chips as a diagnostic, not a keyword dump — here is how.
Read the aeo playbook → - AEO · 11 min read
SERP Features a Service Business Can Actually Win
A local service SERP stacks about nine features and you can win three of them. Here's the triage: content, money, Business Profile, or closed.
Read the aeo playbook →
Want help applying this to your business?
Book a free 30-minute call. We'll review your current acquisition stack and show you the three highest-leverage moves for your industry and state. Or read how our GEO service works.