AT
A. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · September 11, 2026
We're a vertical B2B marketplace connecting enterprise buyers with specialized vendors (think DevOps tools, compliance software, etc.), and our schema structure uses schema.org/CollectionPage at the platform level with hasPart relationships linking to individual vendor profiles marked as schema.org/Organization + schema.org/Offer. When Perplexity answers 'which vendors offer [specific capability]?' queries, it sometimes cites our platform as the aggregator, but more often it cites individual vendor sites directly—completely bypassing our discovery layer and treating each vendor as a standalone entity. We've tested restructuring the schema to use CreativeWork linkage and BreadcrumbList at the platform level, but Perplexity still fragments vendor profiles. Is this a fundamental limitation of how answer engines parse and prioritize marketplace hierarchies (i.e., they flatten parent-child relationships and treat each child as independently citable), or is there an entity model we haven't tested yet that would establish our platform as the authoritative aggregation layer?
Asked by Yuki T.
Answer engines treat marketplace listings as independent entities by design—they crawl and index each vendor profile separately, so they have no reason to re-route citations through your platform layer. The hasPart relationship signals ownership but doesn't create a citation preference. Test adding schema.org/about links from each vendor profile back to a platform-level schema.org/Thing that describes your curation/vetting process, and use schema.org/endorsement or schema.org/review markup to signal that your platform adds editorial value beyond aggregation. But fundamentally: if individual vendors rank well organically, answer engines will cite them directly.