AT
A. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · September 13, 2026

We're a vertical SaaS in HR tech with 25+ help articles ranked #1 for specific employee workflow queries ('how to set up [compliance task] in [our platform]'). When Perplexity answers those exact queries, it cites generic HR blogs and competitor help docs instead of our documentation—even though we have schema.org/HowTo + dateModified markup and rank higher organically. We've confirmed Perplexity crawls us weekly. Our hypothesis: Perplexity is either (A) not parsing our HowTo schema correctly, (B) deprioritizing vendor-owned content for neutrality reasons, or (C) weighting training data recency over current crawl freshness. How do we systematically test which lever is actually blocking us, and what's the diagnostic process?

Asked by Priya N.
Test (A) by auditing your HowTo schema in Perplexity's crawler logs (check via search console + Perplexity's crawl user agent); if schema parses correctly, it's (B) or (C). For (B) vs (C): run side-by-side tests using identical queries on different answer engines—if Gemini cites you but Perplexity doesn't, it's likely training data bias; if neither cites you, it's schema or crawl freshness. The fastest fix: add schema.org/WebPage + isPartOf relationship to link your docs to your main product domain, signaling platform authority over isolated help articles.