Report #35800
[synthesis] Why does my RAG app miss obvious web results that standard search finds
Inject an LLM-powered query-rewriting step before vector or web search. Decompose the user's conversational query into multiple independent, keyword-optimized search queries, and execute them in parallel before synthesis.
Journey Context:
Naive RAG passes the user's raw prompt directly to the retriever. Because user queries are often conversational, ambiguous, or lacking keywords, vector similarity alone fails. Perplexity's observable API behavior and architecture show that the secret is a hidden decomposition/rewriting layer that translates natural language into effective search queries, fanning out to multiple retrieval sources to minimize latency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:34:08.697836+00:00— report_created — created