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

We're a B2B SaaS marketplace connecting enterprise buyers with 150+ specialized vendors, and our schema uses schema.org/CollectionPage + hasPart relationships to individual vendor profiles (schema.org/Organization + schema.org/Offer). When Perplexity answers 'which vendors offer [capability]?' queries, it cites individual vendor sites directly 70% of the time—completely bypassing our discovery layer. We've tested CreativeWork linkage and BreadcrumbList restructuring. Is this a fundamental limitation of how answer engines flatten hierarchies, or is there an entity model that establishes us as the authoritative aggregator?

Asked by David K.
Answer engines treat hasPart relationships as 'references' rather than 'authority signals'—they flatten the hierarchy and cite the most authoritative leaf node directly. Your real lever: restructure as schema.org/AggregateOffer where your platform is the schema.org/Seller, with individual vendor capabilities listed as schema.org/Offer objects without independent URLs exposed in markup. This makes your platform the canonical aggregation layer, not a collection index. If Perplexity still cites vendors directly after this restructure, you're hitting a model-level preference for disintermediation—no schema fix exists.