The four most common causes, in order of likelihood
A competitor published something new
Check whether a competitor recently earned new coverage, a comparison mention, or a review that an AI engine may now be citing instead of, or alongside, you.
The AI engine changed how it sources answers
Model and retrieval updates happen periodically and can shift which sources get preferred — not something you can fix directly, but worth ruling out before assuming the problem is your content.
Your entity data went inconsistent or stale
If your name, description, or details differ across the third-party sites an engine draws from, that inconsistency can quietly erode how confidently it cites you.
Your tracked query set shifted
If you changed your prompt list, competitor list, or date range between checks, part of an apparent drop can just be a different measurement, not a real change.
How to figure out which one is yours
- 1
Compare your drop against competitor movement, not just your own trend
If a competitor's mentions rose right as yours fell, that's a strong signal of what actually happened.
- 2
Re-run the exact same prompt set and date range you used before
A different prompt list or competitor set between checks can look like a drop when it's really just a different measurement.
- 3
Check whether your entity details are consistent across the web
Look at how your brand is named and described on the third-party sites AI engines already cite for your category.
- 4
Look for anything that changed in your own content around the same window
A page taken down, rewritten, or gone stale can explain a drop just as easily as anything external.
Why one drop isn't a verdict
AI-generated answers carry some inherent volatility — the same prompt run twice in the same week can return a slightly different mix of brands, even with nothing having changed. A single lower reading is a data point, not a trend.
The more reliable signal is a sustained move over several weeks of consistent tracking, not a single check that happened to catch a low point. Treat one drop as a prompt to look closer, not as confirmation something is broken.