How does AlsoAsked work?

You enter a query, choose a country and language, and it builds a People also ask tree from Google. You can expand nodes to see deeper follow ups. Save what fits your page, ignore what belongs on separate posts.

Is AnswerThePublic a good SEO tool?

It is useful for turning one seed into many question and preposition angles. Use it to plan sections and comparisons. Pair it with your own Search Console data to decide which questions matter for your site.

What are the limitations of AnswerThePublic?

It shows autocomplete suggestions, not your traffic or rankings. It does not show how questions relate in click paths like People also ask does. Always read the live SERP before you finalise an outline.

What are some good alternatives to AnswerThePublic?

AlsoAsked is a strong complement because it maps PAA depth. You can also type queries directly, expand the PAA box yourself, and note autocomplete by hand. If you want volumes and audits, look to full suites, but for questions these two and the free path cover most needs.

Should I add every People also ask question I find?

No. Keep only the questions that match your page’s promise. Turn big branches into their own posts and link them. This avoids thin duplicates and keeps each page focused.

How do I know if my added questions worked?

Track the target page in Google Search Console. If you see new question queries with impressions but no clicks, tighten the snippet and place the answer higher. If impressions and clicks rise, keep the structure and build the next post in the cluster.

AnswerThePublic vs AlsoAsked

You want questions that real people ask. AnswerThePublic pulls autocomplete around your term. AlsoAsked expands People also ask into trees. Use both to plan one topic well and fill the gaps your page misses.

By Théophile Louvart, founder of Porteur · Updated 14 September 2026 · Markdown

What each tool is built for

AnswerThePublic draws autocomplete suggestions from search engines into wheels of questions, prepositions and comparisons. It is part of NP Digital.

AlsoAsked maps the People also ask box into a branching tree, several levels deep, by country and language. It shows how questions relate on the results page.

Autocomplete wheels vs People also ask trees

Autocomplete exposes how users tend to finish a seed, like “email deliverability” into “email deliverability best practices” or “email deliverability vs inbox placement”. It is breadth around stems.

People also ask shows question chains that searchers click through on the results page. It reveals follow ups like “What affects email deliverability”, then “Is a dedicated IP worth it”, then “How long to warm an IP”. It is depth along intent paths.

When to choose AnswerThePublic or AlsoAsked

Use this when	AnswerThePublic	AlsoAsked
You are starting a topic and want the lay of the land	Good: wide set of question and preposition variants around one seed	Okay: first PAA level suggests follow ups, less breadth
You are structuring H2s and comparison angles	Good: comparisons and prepositions surface “X vs Y”, “for”, “with” groups	Limited: PAA rarely shows pure “vs” unless the SERP does
You are writing an FAQ for a page already ranking	Okay: gives raw questions to consider	Strong: reveals the next-click questions people open from the SERP
You want related follow-on posts in a cluster	Good for parallel stems to turn into separate posts	Good for sequenced how-tos that link together
You need language and country filters	Supported across engines and locales, autocomplete based	Supported by country and language on Google PAA
You need to see relationships between questions	Weak: presented as grouped lists and wheels	Strong: visual tree shows parent-child links

Plan one guide and its FAQ with both

Pick one intent. Example: “email deliverability”. Your goal: one guide at /guides/email-deliverability with an embedded FAQ. You will map H2s from autocomplete and FAQs from PAA.

Scope sections with AnswerThePublic
Enter “email deliverability”. Note clusters in questions, prepositions and comparisons. Draft H2s like “What is email deliverability”, “How to improve”, “Dedicated IP vs shared IP”, “For SaaS”, “With Gmail”. Remove fluff, group overlaps.
Map follow ups with AlsoAsked
Enter the same term. Expand the tree two levels. Collect PAA questions that are within your page’s promise. These become FAQ entries or inline QAs under the right H2.
Decide what is one page vs spin-out posts
If a branch like “DMARC” explodes, give it its own page at /guides/dmarc and link it. Keep core deliverability questions in the main guide.
Write, then place FAQs where readers hesitate
Do not dump an FAQ footer only. Put “How long to warm an IP” under your IP section. Keep a concise FAQ block for disjoint questions readers might scan.
Check coverage against Search Console later
After shipping, watch queries on /guides/email-deliverability in Search Console. Add missing PAA questions that send impressions but no clicks.

A fixed page reads like this: H1 sets the promise, H2s cover the stems from autocomplete, each section answers its PAA subquestions in short QAs, and an FAQ ties loose ends.

The free path without tools

You can do this with your browser. It is slower but free. You will sample autocomplete and expand the People also ask box by hand.

Autocomplete sampling
In Google, type your seed, stop before Enter, and cycle letters or words, like “email deliverability a…”, “for…”, “with…”, “vs…”. Note recurring phrases.
People also ask expansion
Search the seed. Click to open a PAA question. Each click spawns more. Open questions that match your topic. Capture two to three levels deep.
Sense check intent
Open top results. If the SERP is product-heavy or news-heavy, your guide may not fit. Pick a seed with stable informational intent.
Outline and write
Turn the stems into H2s. Place PAA questions where readers will want them. Cut what is off-topic for your page’s promise.

Use Keywords Everywhere if you want rough volumes on page as you browse. Use Google Trends to see if interest is seasonal. These help you pick order, not whether to cover a question at all.

Why impressions rise without clicks

When you add many QAs, you gain impressions on long tails. Clicks lag until your snippet wins trust or grabs a rich result. That is normal on new pages.

Fix snippets first. Tighten the title and meta description. Match the exact phrasing of the question in the subheading. Link to the answer from the top with jump links.

How to avoid thin or duplicate questions

Do not split near-duplicates across pages. Keep “How to improve email deliverability” and “How to increase deliverability” on one page.
Answer each question once on a canonical page, then link to it. Avoid pasting the same QA on several pages.
If a PAA question is off-scope for your page, skip it. Leave it for a separate post you can rank for.
Keep answers short, then link to depth. A paragraph, a list, then a link to the detailed guide.

If two of your pages start to show for the same question, link them, then decide which is the keeper and reinforce it. Retire or fold the other later.

Worked example: plan a pricing guide and its FAQ

Site: yourproduct.com. Target page: /pricing. Seed: “pricing for project management software”. You want to rank the pricing page and answer buying questions.

AnswerThePublic for stems
Find “pricing tiers”, “per user vs per project”, “for nonprofits”, “with annual discount”, “cost calculator”. These map to H2s or links to subpages like /pricing/calculator.
AlsoAsked for buyer PAA
Surface PAA like “Is project management software worth it for small teams”, “What features are must-have”, “How to estimate seats”. Put these under the right H2s and in a short FAQ.
Ship and measure
In Search Console, filter to /pricing. Watch terms like “yourproduct pricing” and “project management software cost”. Add missing questions that show impressions without clicks.

A fixed /pricing page shows clear tiers, answers common PAA buyer doubts in-line, and links to deeper guides like /guides/roi with proof for hesitant readers.

Limits to keep in mind

Both tools reflect Google’s suggestions and PAA as of the crawl time. The live SERP shifts by location and time.
Autocomplete and PAA do not give you your own site’s clicks. Use Google Search Console for that.
Volumes in plugins and trend tools guide priority, not truth. For small queries, judgement matters more.
Trees and wheels are inputs. You still need to read the results page and match search intent.

Side by side

AnswerThePublic

answerthepublic.com

Turning one seed into grouped autocomplete suggestions as questions, prepositions and comparisons.

Good at

Finding breadth of phrases around a topic
Surfacing comparison and modifier angles
Quickly scoping H2 candidates for a guide

Choose it when You want wide coverage ideas around a seed and to plan sections and comparisons for one page.

Not for Measuring your own clicks or ranking changes, or showing SERP click-path relationships.

AlsoAsked

alsoasked.com

Mapping Google’s People also ask questions into expandable trees by locale.

Good at

Revealing follow-up questions along an intent path
Placing FAQs where readers hesitate
Deciding what becomes a subheading vs a separate post

Choose it when You want to see how questions branch from the SERP and fill in-page FAQs with the right depth.

Not for Broad modifier discovery like “for”, “with”, “vs” across many stems, or any analytics on your site.

Start with AnswerThePublic when you need breadth to outline a guide and spot comparison and modifier angles. Use AlsoAsked when you need depth to answer the next-click questions readers have on the results page and to place FAQs with intent. For a single topic, run both, merge overlaps, then cut anything off-promise. Check your target page in Google Search Console after shipping to decide which questions to keep expanding.

Questions

Check my site, free

Paste your target URL and topic, then run the free check to see three question gaps from rivals and searches around it in about thirty seconds.

Free check, no card
Read-only, your own accounts
Readable by your agent