Perplexity is the only major AI platform that provides explicit, numbered citations on every response, making it the most measurable citation channel and the most actionable to optimize. Cited Index data shows Perplexity has the strictest mention behavior of the tracked platforms — a median mention rate of 5% compared to ChatGPT’s 10% — but brands that do appear on Perplexity tend to get cited with links rather than just mentioned. If you can improve your Perplexity citations, the same work often improves your visibility on other platforms too.Documentation Index
Fetch the complete documentation index at: https://docs.getcited.in/llms.txt
Use this file to discover all available pages before exploring further.
Why Perplexity first
Three reasons to start citation optimization with Perplexity:- Every response has citations. Unlike ChatGPT, Claude, and Gemini where citations are inconsistent or absent, Perplexity provides numbered source links on every answer. This makes citation rate reliably measurable.
- Real-time retrieval shows changes faster. Perplexity fetches content live from the web for every query, so content and technical improvements can show effects within 1-2 weeks — far faster than the 4-12 week cycle on training-data-dependent platforms.
- Perplexity’s behavior is the most predictable. Because answers are grounded in retrieved sources rather than stochastic training data, the same query tends to surface similar sources across runs. This makes optimization measurable and repeatable.
Step 1 — Ensure crawl access (15 minutes)
Technical access is the prerequisite. Without it, nothing else matters.- Check your
robots.txtfor PerplexityBot — it must be explicitly allowed or not blocked by a catch-all rule. - Check your CDN or hosting layer (Cloudflare, Vercel, AWS CloudFront) for IP blocks or bot management rules that might reject Perplexity’s crawlers at the infrastructure level, even if
robots.txtallows them. - Verify with curl:
curl -A "PerplexityBot" https://yourdomain.com/your-pageshould return a 200 status with your page content, not a block page, CAPTCHA, or 403 error. - For detailed instructions on configuring both
robots.txtandllms.txt, follow the Fix your llms.txt and robots.txt playbook.
Step 2 — Audit your current Perplexity visibility (30 minutes)
Establish a baseline before making changes, so you can measure improvement.- Select your top 10 category-relevant prompts — the questions your customers most commonly ask AI.
- Run each prompt directly in Perplexity’s web interface.
- For each response, note three things: Are you mentioned by name? Are you cited with a link to your domain? What position is your citation (first, third, fifth)?
- Identify the gap: which prompts mention competitors but not you?
- Use Cited’s competitive gap analysis to automate this at scale across your full prompt library.
Step 3 — Optimize your highest-value pages (2-4 hours)
For each page you want Perplexity to cite, apply five structural improvements:- Definition-first lede. Ensure the page opens with a clear, definitive 1-2 sentence answer to the question the page addresses. Perplexity’s retrieval prioritizes pages that directly answer the query.
- Schema markup. Add Product, Article, or FAQPage schema as appropriate for the page type. Schema helps Perplexity’s retrieval system understand what the page is about.
- Explicit date stamps. Add both published date and last-updated date. Perplexity strongly favors recent content — pages with stale dates from 2-3 years ago are systematically passed over.
- Clear heading structure. Use headings that match common question patterns. If customers ask “what is the best CRM for startups,” a heading that reads “Best CRM options for startups” is more retrievable than “Our product offerings.”
- FAQ section with self-contained answers. Each answer should be readable standalone without the question. This gives Perplexity multiple extractable snippets from a single page.
Step 4 — Earn editorial coverage in sources Perplexity trusts (ongoing)
Perplexity heavily cites editorial publications — established news sites, industry publications, and expert review platforms. Getting your brand mentioned in sources Perplexity retrieves amplifies your citation rate through an indirect path: the publication covers your brand, Perplexity cites the publication, and your brand appears in the answer. This is the slow-build strategy that produces the most durable results:- Identify target publications. Run your category prompts on Perplexity and note which publications appear as cited sources across multiple responses. These are the publications Perplexity trusts for your category.
- Pursue earned editorial coverage on those specific publications through data-driven pitches, expert commentary, and industry analysis — not product announcements or press releases.
- Measure the chain effect. After coverage publishes, monitor whether Perplexity starts citing that article for your category prompts, and whether your own domain begins appearing as a direct citation alongside the editorial source.
Step 5 — Monitor and iterate (weekly)
Track citation rate weekly against your Step 2 baseline:- Compare the prompts where you made changes against prompts where you did not — the improved prompts should show higher citation rates over time.
- Allow 1-2 weeks for Perplexity to discover technical and content changes. Editorial coverage may take 2-4 weeks to propagate.
- If citation rate improves on Perplexity, the same content improvements typically benefit other platforms over 4-12 weeks as training data refreshes.
- Re-run the full audit quarterly to identify new gaps and track competitive movement.
Common pitfalls
Focusing on content volume over content structure. Ten thin pages are worse than one well-structured page. Perplexity cites pages that comprehensively and clearly answer a question, not pages that exist in quantity. Ignoring the technical layer. Content quality is irrelevant if crawlers cannot access the page. A blockedrobots.txt, slow page loads, or JavaScript-only rendering make content invisible to Perplexity regardless of its quality.
Expecting immediate results. Even on Perplexity — the fastest-responding platform — citation improvements take 1-2 weeks minimum for technical changes and 2-4 weeks for content changes to show consistent effects.
Optimizing for exact-match keywords instead of natural question patterns. Perplexity retrieves based on semantic relevance to conversational prompts, not keyword matching. Write for how customers actually ask questions, not for keyword density.
Related concepts
- How Perplexity ranks sources
- Citation rate
- Fix your llms.txt and robots.txt
- Write content that gets cited
Frequently asked questions
How long does it take to see Perplexity citation improvements?
How long does it take to see Perplexity citation improvements?
Perplexity uses real-time retrieval, so technical changes like robots.txt fixes and page structure improvements can show effects within 1-2 weeks. Content and editorial coverage improvements take longer — typically 2-4 weeks for Perplexity to pick up and start citing new sources consistently. Allow a full month before concluding that a change did or did not work.
My brand is mentioned on Perplexity but not cited — what does that mean?
My brand is mentioned on Perplexity but not cited — what does that mean?
Perplexity is mentioning your brand name (likely from training data or from third-party sources that discuss your brand) but is not linking to your domain as a source. This means Perplexity does not consider your domain a primary reference for the topic. The fix is to improve your site’s technical AI readability and content structure so Perplexity treats your domain as a citable source, not just a brand name it knows from other contexts.
Should I use Perplexity's API or the web interface for testing?
Should I use Perplexity's API or the web interface for testing?
Both show the same citation behavior. The web interface is easier for manual testing and initial auditing (Step 2 of this playbook). The Sonar API is what Cited uses for programmatic tracking at scale. For one-off testing, the web interface is sufficient — save the API for automated monitoring.