How to recover a lost AI citation.
You were in the answer last month. You're not anymore. What happened? Citations churn with model updates and competitor moves, and without a forensic trail you are reduced to guessing — which means fixing the wrong thing, or fixing nothing.
Open the SKU's history in prompt runs: every refresh stores the verbatim answer per prompt per engine, so the drop has a date. Diff your PDP and the slot-winner's PDP across that date, attribute the cause — you, them, or the engine — and ship the matching recovery fix. Part of SKU-level tracking.
The slow way: archaeology without an archive
The manual problem is that the evidence no longer exists. Nobody screenshotted the answer when it was good, so you can't prove the SKU was cited, let alone when it stopped. You reconstruct from memory: "I'm pretty sure we were in there in April." You check the Wayback Machine for your own PDP, dig through theme deploy logs and app change histories, and ask the review-app vendor whether anything changed. For the competitor's side you have even less — their current page, no history.
Sometimes this works: a theme deploy on the suspected date with a missing JSON-LD block afterward is a smoking gun. More often the investigation produces a plausible story rather than a cause, the team ships a guess, and the prompt gets rerun for a few anxious weeks. Citation forensics without stored history is the worst version of the job — all of the pressure, none of the data.
The eCommerce Insights way
- Date the drop. The SKU's prompt-run history stores every verbatim answer per refresh. Scroll to where CITED becomes MISSED: the drop has a date and a before/after answer pair, not a vibe.
- Check your side first. The same history stores your PDP's factor scores per refresh. A schema factor that fell 30 points the day after a theme update is your answer. Common self-inflicted causes: theme deploys breaking JSON-LD, thinner copy rewrites, disconnected review feeds, robots.txt edits.
- Check their side. The answer history names who holds the slot now. Their PDP's observable changes around the drop date — rewrite, review jump, new third-party coverage — are in the watchlist record if you were tracking them, and recoverable from their current page if not.
- Attribute honestly. You, them, or the engine. If neither page changed, the engine retrained — it happens, and pretending otherwise wastes a sprint. The mechanism behind churn is covered in how AI engines pick which products to cite.
- Ship the matching fix and re-run. Self-inflicted: restore what broke. Competitor-driven: close their specific gap. Engine-driven: optimize for the new answer pattern rather than mourning the old one. Watch the same prompt weekly; slots lost to your own regressions typically return within two to six weeks of the fix (eCommerce Insights observations, early 2026).
What "good" looks like
The deeper win is preventive: with alerts on citation drops, this job starts the day the slot is lost instead of the month the revenue notices.
Ask AI about this job
Have your favorite AI engine apply this walkthrough to your situation.
Frequently asked questions
Why did my product disappear from the AI answer?
Can a lost citation always be recovered?
How do I know it's a real drop and not session variance?
What's the forensic trail eCommerce Insights actually keeps?
Does a recovered citation stick?
Every answer, archived. Every drop, dated.
Per-SKU, per-prompt history across six engines. 14-day trial.