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

We're a vertical SaaS in AI-powered contract review with 45+ help articles ranked #1 for 'how to extract [specific clause type] using [our platform]' queries. When we check Gemini's citations, it pulls from generic legal tech blogs and LexisNexis instead—even though we have schema.org/HowTo + schema.org/DefinedTerm markup for proprietary clause taxonomy, higher organic rankings, and confirmed 2–3x weekly crawls. We've also tested adding schema.org/VideoObject to embedded extraction demos. The puzzle: our organic authority is undeniable, but Gemini seems to treat vendor-owned legal SaaS content as inherently less trustworthy than 'neutral' legal reference sources. Before we assume this is deliberate trust-based deprioritization, what's the diagnostic test to isolate whether Gemini is (A) silently failing to parse our DefinedTerm schema for clause types, (B) weighting pre-training data over current crawl signals, or (C) applying a trust heuristic that deprioritizes all vendor-owned legal content regardless of topical authority?

Asked by Lena B.
Test (A) by comparing Gemini citations for identical queries against your organic rank position—if it consistently cites lower-ranked sources, schema parsing likely isn't the blocker. For (B) vs (C), run a variant test: add schema.org/DefinedTerm markup to a neutral legal blog you control or partner with, then check if Gemini shifts attribution. If it does, you've isolated a trust heuristic; if not, it's training data recency. Most likely here: Gemini's legal vertical is pre-trained on curated 'neutral' sources (LexisNexis, bar associations) and treats vendor content as promotional, regardless of schema signals.