Perplexity Related Questions Scraper avatar

Perplexity Related Questions Scraper

Under maintenance

Pricing

from $1.99 / 1,000 search results

Go to Apify Store
Perplexity Related Questions Scraper

Perplexity Related Questions Scraper

Under maintenance

Scrapes related/follow-up questions from Perplexity search results (perplexity.ai/search). Extracts follow-up questions that appear alongside AI answers.

Pricing

from $1.99 / 1,000 search results

Rating

0.0

(0)

Developer

Search API

Search API

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 days ago

Last modified

Share

Submit one or multiple questions through Perplexity's current search form and collect the follow-up or related questions rendered with each completed answer. Output includes stable question IDs, ranking and query-match context, the public result URL/thread ID, and useful parent-answer evidence such as excerpt length, word count, citation count, and reported source count.

Choose single or fair batch mode, current Perplexity search modes, question type, keyword filters, sort, global/per-query limits, concurrency, timeouts, and optional proxies. Legacy focusMode: "web" remains accepted as the current Search mode. Obsolete academic/social/YouTube/Reddit path modes are rejected because the current interface no longer exposes them as equivalent search modes.

Run locally with apify run --purge --input-file INPUT.json. Perplexity may show a Cloudflare challenge or an explicit sign-in wall depending on IP/session state. The Actor detects both and fails without solving CAPTCHAs or storing placeholders. If you are authorized to use an existing Perplexity session, store a Playwright cookie array in the secret environment variable PERPLEXITY_COOKIES_JSON; cookie names/values are never logged or written to the dataset. GOOGLE_SERP is incompatible with Perplexity browser traffic; use an authorized Residential or custom HTTPS proxy when appropriate.

The current public result page exposes questions in rendered DOM sections, not in a reliable public structured endpoint. Extraction therefore validates the initial status/content type, submits the visible form, waits for answer streaming to stabilize, then parses exact Follow-ups/Related surfaces with a bounded semantic fallback. Results are written atomically only after every requested query succeeds.