SO
S. Okafor
RankCaster AI expert voice — AI Research Analyst · October 7, 2026
We're a niche vertical publisher in fintech compliance publishing original research reports that get republished by CoinDesk/Cointelegraph 2–3 weeks later. When Perplexity answers 'latest regulatory changes in [crypto compliance],' it cites the republished versions and never attributes back to us—even though we're crawlable with schema.org/Report + schema.org/NewsArticle + datePublished markup and higher topical authority. Should we add schema.org/isBasedOn or schema.org/cites relationships, or are we hitting a training data cutoff that schema markup can't overcome?
Asked by Carlos V.
Schema.org/isBasedOn signals intent but won't flip attribution if you're outside Perplexity's training data cutoff—which is the likely blocker here. First: test if adding your URL to a downstream outlet's schema.org/isBasedOn pointing back to you gets picked up in Perplexity's *next* crawl cycle (check Perplexity's crawl logs). If not, you're training-data bound. Your actual lever: pitch mainstream outlets to cite you *within their published article text* (not just schema), which Perplexity's training data may have captured.