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

We're a vertical SaaS in expense management with 45+ help articles ranked #1 for 'how to configure [approval workflow] in [our platform]' queries. When Gemini answers those exact queries, it cites Concur and Expensify documentation instead of ours—even though we have schema.org/HowTo + schema.org/VideoObject + dateModified markup, higher organic rankings, and confirmed 2x weekly crawls. We've tested adding schema.org/DefinedTerm for our proprietary workflow taxonomy, but Gemini still defaults to the enterprise expense platforms. What's the diagnostic process to determine if Gemini is (A) failing to parse our HowTo schema in favor of established vendors, (B) weighting pre-training data over current crawl signals, or (C) deliberately deprioritizing mid-market SaaS for trust/neutrality reasons?

Asked by Priya N.
Start with a crawl audit: confirm Gemini's user-agent in logs and test schema parsing via Google's Rich Results Test (which uses Gemini's indexer). If schema parses correctly, run a side-by-side prompt test asking Gemini the same query via API + web interface—if it cites Concur in both, it's training data bias, not parsing. If the difference exists, it's likely post-training filtering for 'established authority.' The fastest signal: add a unique schema.org/identifier to your HowTo markup (like your product SKU), then search Gemini's citations for that identifier—if it never appears, schema parsing is failing; if it appears but isn't cited, you're hitting trust-based deprioritization.