Skip to main content

Generative Engine Optimization

How Perplexity Picks Local Business Recommendations (Reverse-Engineered)

Perplexity does not rank sources the way ChatGPT does, and treating them as the same target wastes effort. We ran 50 local queries across three verticals, logged every citation, and mapped the patterns that actually predict who gets recommended.

GEO / AI SearchAugust 31, 202611 min read1980 words

How Perplexity Is Actually Built

Perplexity is not a single model with an opinion. It is a retrieval pipeline wrapped around a router, and understanding that pipeline explains most of what follows in this article. When you ask a question, Perplexity does not just query one search index and summarize the top results the way a wrapper around ChatGPT Search might. It runs a query-planning step (frequently branching one question into several sub-searches), fetches a wider set of candidate pages than it will end up citing, scores them, and hands a filtered set to a language model — commonly its own Sonar models, tuned specifically for answering from retrieved sources rather than from parametric memory.

The default experience most people use is Copilot mode (called Search on the free tier), which asks clarifying questions and shows its source list openly, right next to the answer, rather than burying citations in footnotes. That transparency is useful for our purposes: it means you can audit exactly which sources Perplexity leaned on for a given query, which is a big part of how the testing behind this article was possible.

The other structural piece worth knowing is Comet, Perplexity's browser, which changes retrieval behavior further for users who have it. Comet can browse live pages directly rather than relying solely on a cached index, which in our testing produced citations of pages so recent that a standard search-index crawl could not plausibly have picked them up yet. If your business publishes something today, a Comet session can theoretically surface it today — a much tighter loop than the days-to-weeks lag typical of index-based retrieval.

What We Tested: 50 Local Queries Across 3 Verticals

To move past guesswork, we ran 50 local-intent queries through Perplexity in Copilot mode across three verticals with different content maturity levels: home services (HVAC, plumbing, roofing), medical and dental (dentists, med spas), and legal (personal injury and family law attorneys), spread across the mid-size metros we work in most. Queries ranged from broad ("best HVAC company in Tampa") to specific ("emergency plumber that answers calls after 10pm in Austin") to comparison-style ("difference between two dental implant clinics in Naples").

For every query we logged the full citation list Perplexity displayed, not just the businesses named in the prose answer, and recorded seven attributes for each cited source: publish date, last-modified date if visible, presence and density of schema markup, whether the page named a single clear business entity or covered several, how many other domains were cited alongside it, how deep the page went on the specific topic asked (a full page versus a passing mention), and whether the source was cited elsewhere in our dataset (a rough proxy for third-party corroboration).

This is a directional study, not a controlled experiment against Perplexity's actual scoring code, which is not public. But running the same structured logging across 50 queries and three fairly different verticals is enough to separate consistent patterns from noise, and it is the same method we use to validate GEO recommendations before we put them in front of clients.

A methodology note worth flagging: verticals behaved differently in scale, not in kind. Legal queries pulled from a noticeably smaller pool of qualifying sources than home services, since fewer attorney sites publish deep, frequently updated content, which meant a single well-optimized page could swing a legal query's citation list more than an equivalent change could in the more crowded home-services set. The six signals below held across all three verticals, but if you operate in a thinner content category, expect individual fixes to move your citation rate faster than the averages here suggest.

Six Source-Selection Signals We Observed

Across the dataset, six attributes correlated most consistently with a source being cited, in roughly descending order of how reliably they predicted inclusion. None of these is a confirmed weight from Perplexity's own documentation — they are patterns, but they were consistent enough across all three verticals that we now treat them as our working model.

  • Fresh publication or update date. Sources published or visibly updated within the prior 12 months accounted for the large majority of citations in our log, and a page with a current-year date visible in the byline or schema was cited noticeably more often than an undated one covering the same topic equally well.
  • Structured data density. Pages with LocalBusiness, FAQPage or Article schema present, and consistent with the visible page content, were cited more often than schema-free pages of comparable quality. Denser, internally consistent markup outperformed sparse or single-field schema.
  • Entity clarity. Pages that clearly named one business, one address and one set of services were preferred over roundup or comparison pages covering several. When a roundup was cited, Perplexity tended to cite it once for the general question and cite individual business pages separately for specific follow-up questions about one of the businesses named in it.
  • Source diversity in the answer itself. Perplexity rarely leaned on a single domain for an answer, even when one source covered the topic well. Answers typically pulled from three to six distinct domains, which means being one of several good sources on a topic matters more here than being the single best one, unlike a ChatGPT answer that will sometimes lean on one strong source.
  • On-topic depth. A page dedicated to the exact question asked (a service-specific page, not a general homepage) outperformed a broader page that mentioned the topic in passing, even when the broader page belonged to a more established domain.
  • External citation and corroboration. Sources that other cited sources also referenced, linked to, or agreed with factually were favored over an isolated source making an uncorroborated claim, particularly for anything price- or credential-related.

How This Differs From ChatGPT

If you have already optimized for ChatGPT citations, most of that work transfers, but the emphasis shifts in two directions that matter enough to change how you prioritize.

Perplexity rewards freshness more aggressively. In side-by-side testing on overlapping queries, ChatGPT would still cite a well-established, authoritative source from two or three years ago if nothing newer covered the topic as well. Perplexity was noticeably more willing to drop an older, more authoritative page in favor of a thinner but more recently published one, especially on queries with any time-sensitive framing ("best," "top," "2026"). If your content strategy has been "publish once, let authority accumulate," Perplexity is the engine that punishes that approach first.

ChatGPT, by contrast, weights authority and third-party trust more heavily relative to recency. A well-established local business with strong directory presence and press mentions but a stale website tended to still surface in ChatGPT answers; the same business scored worse in our Perplexity log unless something on the page had a recent date attached. The practical read: ChatGPT forgives a dated page if the entity behind it is well-established; Perplexity does not extend the same grace period.

The other consistent difference is citation count and diversity. ChatGPT answers in our broader tracking tend to name fewer sources per answer and will sometimes concentrate on one. Perplexity spreads citations across more domains by default, which is good news for smaller or newer businesses: you do not need to be the single best answer, you need to be a credible, current, on-topic option among several.

Tactics That Push You Into Perplexity's Citation Set

Given those signals, five tactics moved the needle most in our follow-up testing, where we made specific changes to client and test pages and re-ran the same query set 30 to 45 days later.

  • Publish and update dates in visible text and in schema, kept in sync. A page that shows "Updated September 2026" in the byline and carries a matching dateModified in Article or LocalBusiness schema outperformed pages with only one or the other.
  • An llms.txt file at your domain root. This is early and not universally honored yet, but Perplexity is among the more consistent respecters of it in our testing, and it costs almost nothing to add: a plain-text file pointing AI crawlers to your most important, most current pages.
  • Canonical entity signals that resolve to a single, unambiguous business. Consistent LocalBusiness schema with a stable @id, NAP that matches across your site and directories, and a single canonical URL per location all reduce the chance Perplexity treats you as an ambiguous or duplicate entity and skips you in favor of a cleaner competitor.
  • Wikipedia or Wikidata presence for named entities where it is achievable (typically larger, longer-established local businesses or their founders). Perplexity leans on knowledge-graph-style entity resolution more visibly than ChatGPT does in our testing, and a Wikidata entry gives it a clean anchor to confirm who you are.
  • Dedicated, deep pages per service and per location rather than one page trying to cover everything. Given how strongly on-topic depth predicted citation in our data, splitting a broad "services" page into individual pages per service consistently improved citation rate for the specific-query segment of our test set within the 30-to-45-day window.

How to Test Your Own Visibility in Perplexity

Run this monthly with Copilot mode, using your own site's exact sources so you can tell whether you are cited or just mentioned in the answer text without a source link.

  • Broad-intent: "best [service] in [city]" — tests whether you place at all among the diverse source set for a competitive query.
  • Specific-intent: "[specific service] that [specific qualifier, e.g., open on weekends] in [city]" — tests whether your deep, specific pages are winning on-topic depth.
  • Comparison-intent: "difference between [your business] and [a named competitor]" — tests whether Perplexity can resolve you as a clear, distinct entity with enough on-page substance to compare.
  • Direct-freshness check: ask the same broad-intent query again 30 days after publishing an updated or new page, and compare the citation list. A newly cited domain that was not there last month is the clearest signal a specific change worked.

Perplexity Pages: Being the Source vs. Being the Article

One more distinction worth understanding: Perplexity Pages lets any user (including you) publish a shareable, AI-generated research page on a topic, which itself can rank in Google and get indexed. This creates two separate ways to show up in the Perplexity ecosystem, and they are not the same play.

Being cited as a source means your own website page is one of the domains Perplexity pulled from when answering a user's query — this is what the rest of this article is about, and it is the higher-value outcome because it puts your business directly in front of someone actively deciding. Being the subject of, or publishing, a Perplexity Page means a piece of AI-generated content about your topic exists on Perplexity's own domain, which can itself accumulate visibility in Google search results over time, functioning more like a distribution channel than a citation.

For most local businesses, the source-citation path matters far more day to day, since it captures people mid-decision inside Perplexity itself. Perplexity Pages are worth a small amount of experimentation (publishing a well-sourced page on a topic where you are the best available source can itself become something later Perplexity queries cite), but should not distract from the core work: making your own site the clear, current, well-structured answer that the retrieval pipeline finds first.

One caution from the legal-vertical portion of our test set: a competitor's Perplexity Page summarizing "top personal injury attorneys" in a metro we tested was itself getting cited as a secondary source in follow-up queries, ahead of some of the individual firm websites it referenced. That is a reminder that a well-built Perplexity Page on your topic, even one you did not publish, can insert itself into the citation chain between a user and your own site. Checking whether one already exists for your core service and city terms takes five minutes and tells you whether you are competing against a page as well as against other businesses.

Frequently asked questions

How does Perplexity decide which local businesses to recommend?

Based on our testing across 50 local queries, Perplexity favors sources with a recent publish or update date, dense and consistent structured data, clear single-entity focus, on-topic depth (a dedicated page beats a passing mention), and corroboration from other cited sources. It is not a single published algorithm, so this is a pattern observed through structured testing, not confirmed weighting.

How is Perplexity different from ChatGPT for local business visibility?

Perplexity rewards freshness more aggressively and will drop an older, more authoritative source for a newer, thinner one on time-sensitive queries. ChatGPT weights established authority and third-party trust more heavily and tends to forgive a stale page if the business behind it is well-established. Perplexity also cites more distinct domains per answer, so being one of several credible sources matters more than being the single best one.

What is llms.txt and does it help with Perplexity?

llms.txt is a plain-text file at your domain root that points AI crawlers to your most important, current pages, similar in spirit to robots.txt. Adoption is not universal, but Perplexity was among the more consistent respecters of it in our testing, and adding it costs almost nothing.

Does having a Wikipedia or Wikidata page help you get cited in Perplexity?

It can, particularly for entity resolution. Perplexity appeared to lean on knowledge-graph-style signals for confirming who a business is more visibly than ChatGPT did in our tests, and a Wikidata entry gives it a clean, unambiguous anchor. This is realistically achievable mainly for larger or longer-established local businesses, not every small operator.

What is Perplexity Comet and does it change how citations work?

Comet is Perplexity's browser, and it can fetch live pages directly rather than relying solely on a cached search index for users who have it. In our testing this produced citations of pages published so recently that a standard index crawl could not have picked them up yet, which tightens the gap between publishing something and it becoming citable.

Should I focus on Perplexity Pages or getting cited as a source?

Getting cited as a source on your own website matters more for most local businesses, since it puts you directly in front of someone using Perplexity to decide. Perplexity Pages (AI-generated pages hosted on Perplexity's own domain) function more like a secondary distribution channel and are worth limited experimentation, but should not come before making your own site the clear, current, well-structured answer.

Can Local Visibility AI help my business get cited in Perplexity?

Yes. Our AI Visibility service applies the same testing methodology described in this article to your specific business and market, then implements the schema, freshness, and entity-clarity fixes that moved the needle in our own citation testing. See our AI Visibility service page for details.

Not sure how AI sees your business?

Get your 55-page Pro Audit for $19 — delivered in 48 hours. Shows exactly where you stand in ChatGPT, Perplexity, Google AI Overviews and the Local Pack.

Related services, industries, cities and resources from Local Visibility AI.