Prompting Perplexity

Perplexity is an answer engine from Perplexity AI. It differs from a general chat assistant in one important respect: it is built around searching the web and writing an answer with links to the pages it drew on. That design changes what a good prompt looks like.

With a chat assistant, you typically supply the material and ask for it to be transformed. With Perplexity, you are usually asking it to find the material. The wording of your question therefore does double duty. It tells the product what to write and it shapes what gets retrieved. A vague question should be expected to retrieve vague pages. A question that names the subject, the time frame, the geography and the kind of evidence you want gives the search step something to work with.

This is why the prompts on this site list Perplexity only for research-with-sources tasks, such as market research, literature scans and competitor analysis. For drafting or editing text you already have, the search step adds little.

The long structured prompts in this library still work here, but the parts that matter most are different. Role descriptions and tone instructions carry less weight than a tightly scoped question, explicit rules about acceptable sources, and an output format that keeps each claim next to its citation. Follow-up questions in the same thread are a normal part of the workflow: start broad enough to see what exists, then narrow.

Citations are a starting point for verification and should not be treated as proof. A linked page may not say exactly what the summary attributes to it, so open the sources behind anything you plan to rely on.

Product features, modes and plans change often and are not described in detail here. Consult Perplexity's own help and documentation for current specifics.

How to get better results

Write the question the way a careful researcher would scope it

Include the subject, the period you care about, the region or market, and the type of answer you need. 'Remote work trends' is a topic; a question about how hybrid policies at large employers in a named country have changed over the past two years is something a search can be run against. Specific terms in the question are the terms the retrieval step should be expected to use.

Say which sources you will accept

If you only want primary sources, official statistics, peer-reviewed papers or documentation from the vendor concerned, state that. If certain kinds of page should be excluded, such as forums or marketing copy, say so too. Treat this as a preference the product should try to honor and then confirm it did, by looking at what was actually cited.

Ask for claims and citations to stay together

Request an output format where each finding is followed by its source, for example a table with a claim column and a source column, or short bullets each ending in a citation. This makes it obvious when a statement has no support, and it lets you check the important ones quickly. Ask for uncertainty and disagreement between sources to be reported, not smoothed over.

Tell it what to do when evidence is thin

Add an explicit instruction for the case where little reliable information exists: say so, and list what could not be found. Without that instruction, any system that writes fluent text may fill a gap with a reasonable-sounding generalization. Do not ask it to supply links from memory; rely on the sources it attaches to the answer and open them yourself.

Research in passes, not in one giant prompt

A single request that covers market size, competitors, pricing and regulation tends to get shallow coverage of each. Ask one focused question, read the answer and its sources, then follow up within the same thread to go deeper on the part that matters. Where the product lets you save standing instructions or group related threads, use that for rules that apply to the whole project.

Where it fits

Well suited to

  • Questions about current or recent information where you need to see the sources
  • First-pass market, competitor and industry research
  • Finding primary documents, papers or official pages on a defined topic
  • Checking a specific factual claim against several published sources
  • Building a reading list before deeper manual research

Watch out for

  • A citation shows where to look, not that the summary is accurate; open and read the sources for anything important
  • Source quality varies, and a confident answer can rest on a weak or outdated page
  • Broad questions tend to produce generic summaries; narrow the scope if the answer is thin
  • It is not the right tool for rewriting or formatting text you already have
  • Information behind logins or paywalls may not be reachable, which can skew what is cited

Prompts that work with Perplexity

These prompts are expected to work with Perplexity based on their structure. Check each prompt page for its testing status; see how compatibility is labelled.

SEO

Research