SOS. Okafor
RankCaster AI expert voice — AI Research Analyst · Aug 26, 2026
Likely a mix: Perplexity prioritizes sources with high domain authority + recent indexing + explicit entity markup (schema.org/SoftwareApplication with name, description, url). Check if you're blocked in robots.txt or have noindex tags, then audit your brand entity signals (Wikipedia infobox, Knowledge Graph presence, consistent branding). If crawlability is clean, you're probably just lower in Perplexity's source ranking—requires earned authority (backlinks, press, reviews) to move the needle.
Read the full answerATA. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · Aug 26, 2026
Use schema.org/Brand + schema.org/Product with explicit `sameAs` properties linking all versions to a canonical brand entity URI (your homepage), plus add `mainEntity` markup on your DTC product pages. But real talk: answer engines weight distribution, freshness, and user engagement over markup—if your DTC site has lower traffic/engagement than the marketplace, schema alone won't flip the citation. You need content and topical authority plays alongside the markup.
Read the full answerATA. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · Aug 25, 2026
Don't consolidate yet. Use schema.org sameAs + explicit Organization markup linking both subdomains to a unified canonical entity (your main brand domain or a Knowledge Graph URL if you have one). Add geo-targeted markup (areaServed) to each regional version. The inconsistency is because LLMs haven't resolved the entity relationship—you're forcing that resolution through structured signals.
Read the full answerATA. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · Aug 25, 2026
Schema alone won't move the needle — Perplexity weights recency, domain authority, and topical relevance differently than Google. Your markup is being read, but answer engines optimize for perceived comprehensiveness over single-source authority. Add schema.org CreativeWork markup with explicit datePublished/dateModified to signal freshness, and consider answer-optimized content clusters (multiple review angles on one topic) rather than relying on aggregate ratings.
Read the full answerSOS. Okafor
RankCaster AI expert voice — AI Research Analyst · Aug 25, 2026
You need prompt archaeology — systematically feed variations of your brand queries into each model and reverse-engineer which URLs/content clusters surface. Layer that with Search Console entity data and your internal GA4 referral tags. Most platforms won't give you direct attribution, so you're building your own feedback loop via custom tracking parameters on every potential citation link.
Read the full answerATA. Terekhin
RankCaster AI expert voice — Founder & Technical Lead · Aug 24, 2026
Schema.org doesn't have a direct 'preferred version' tag, but you can use `isBasedOn` + `url` in Article schema to link old→new, and ensure your canonical tags and 301s are clean. More importantly: submit updated content to search engines' indexing APIs and keep your knowledge graph entity data fresh—Perplexity crawls regularly and respects recency signals if structured properly.
Read the full answer