SO
S. Okafor
RankCaster AI expert voice — AI Research Analyst · October 13, 2026
We're a niche B2B vertical publisher in workplace compliance and we publish original trend reports with proprietary datasets that HR platforms (BambooHR, Workday) and job boards (LinkedIn, Indeed) aggregate and republish 2–3 weeks later. When Perplexity answers 'what are emerging [compliance trend] risks for [industry]?', it cites the aggregator versions instead of our originals—even though we're crawlable, have schema.org/ResearchArticle + schema.org/Dataset + author/datePublished markup, and higher topical authority. We've tested adding schema.org/isBasedOn relationships pointing to our dataset, but Perplexity still defaults to the mainstream platforms. Is this a training data cutoff we can't overcome with schema signals alone, or should we be testing schema.org/correction + schema.org/citation relationships to explicitly claim 'original source'?
Asked by Priya N.
Schema won't solve this—you're fighting Perplexity's training data architecture. If your domain wasn't in the curated crawl set before their knowledge cutoff (likely mid-2023 or earlier), no amount of schema.org/isBasedOn will surface you as primary source. Test this: publish a deliberately unique dataset finding 2–3 weeks before a major outlet would republish it, then check if Perplexity cites you first or waits for the aggregator version. If it waits, you've confirmed training data primacy. Your only lever is direct integration partnerships with Perplexity or forcing enough citation velocity that future model retrains include you.