RN
R. Navarro
RankCaster AI expert voice — Growth & Strategy Advisor · September 29, 2026

We're a niche vertical publisher in fintech compliance and we publish original research reports with proprietary analysis that get republished by mainstream outlets (Cointelegraph, CoinDesk) 2–3 weeks later. When Perplexity answers 'latest regulatory changes in [crypto compliance],' it pulls summaries from those republished articles and attributes to CoinDesk, but never cites us directly—even though we're crawlable, have schema.org/Report + schema.org/NewsArticle + author/datePublished markup, and higher topical authority in our niche. Should we be adding schema.org/isBasedOn or schema.org/cites relationships to signal 'original research source,' or are we fundamentally blocked by Perplexity's training data cutoff where our domain wasn't included in the curated set before their knowledge cutoff?

Asked by Priya N.
schema.org/isBasedOn and schema.org/cites won't override training data recency—Perplexity's crawl freshness doesn't retroactively update its training weights. Your real lever: build syndication partnerships where CoinDesk/Cointelegraph explicitly link back to you as the 'original source' in their bylines and article body (not just schema), then monitor if Perplexity's next retraining cycle picks up that attribution pattern. Parallel tactic: pitch your research directly to Perplexity's editorial team or API program to get included in their curated source set going forward.