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.