Overview

You were cited in an AI answer last month, and now you are not. Or a competitor has started appearing where you used to. This is one of the most common and most fixable problems in AI search, and you can win back lost citations as long as you approach it methodically instead of rewriting everything at once.

This playbook gives you a 30-day plan. Week one is diagnosis, week two is page fixes, week three is supporting signals, and week four is measurement. You can run it for a single important prompt or a whole topic.

Before you start

Gather three things so you are working from evidence rather than hunches.

  • The prompts that lost citations: the exact questions, the engines, and the dates when you lost the citation.
  • The page that used to be cited: the URL, and ideally what it looked like back then.
  • Who replaced you: the domains and pages now cited for the same prompts.

If you track prompts daily, this history already exists. If not, start tracking now and work from today’s answers.

Tip: Pick no more than five prompts for your first run. A tight scope makes it easier to see what worked.

Week 1: diagnose

Resist the urge to edit yet. The first week is about finding the cause, because the right fix depends on it.

Day 1 to 2: check access

Work through the boring causes first.

  1. Is the page still live and returning a normal response, with no accidental redirect or error?
  2. Do robots.txt rules or firewall settings block the AI crawlers?
  3. Is the content present in the HTML, or does it depend on scripts that crawlers may not run?
  4. Did the page move, get a new URL or lose its canonical tag?

If you find a technical cause, fix it and skip to measurement. Many lost citations are just this.

Day 3 to 4: compare with the winner

Open the page that replaced you and compare it with yours, side by side. Ask what it does better.

  • Does it answer the question in the first paragraph?
  • Is it newer, with a visible update date?
  • Does it include specifics you lack, such as numbers, steps or a comparison?
  • Is it structured with clear headings, lists or a short FAQ?
  • Does it come from a source type the engine seems to prefer, such as a review site or documentation?

Day 5 to 7: check the wider picture

Look beyond the single page. Did your whole site lose visibility, or only this topic? Did several engines drop you, or one? A drop in one engine points to that engine’s behavior. A drop everywhere points to your content or access. Also check whether an answer is now describing you inaccurately, which can be a separate issue.

Week 2: fix the page

Now make focused changes to the page, guided by the diagnosis. Fewer, deliberate edits are easier to evaluate than a total rewrite.

  • Lead with the answer. Put a clear, self-contained answer in the first paragraph, then support it.
  • Add the missing specifics. Fill the gaps the winner covers: real figures, steps, examples, definitions and honest comparisons.
  • Cover the fan-outs. Add sections for the narrower questions AI engines tend to split your topic into, such as pricing, alternatives and pitfalls.
  • Add a short FAQ with markup. Use FAQPage schema where questions are genuine and the answers are on the page.
  • Refresh the facts. Update stale statements and show the revision date.
  • Tidy the structure. Descriptive headings, short paragraphs and lists make passages easier to quote.

When you are done, make sure the page is indexed quickly. Resubmitting the URL and using IndexNow where supported can speed discovery.

Week 3: strengthen supporting signals

A single page rarely wins alone. Use the third week to reinforce it.

  1. Link internally. Point relevant pages at the updated one with descriptive anchor text.
  2. Fix inconsistent descriptions. Make sure your brand, product names and key facts match across your site, profiles and directories.
  3. Earn corroboration. Where engines cite third-party sources for your topic, such as review sites, industry lists or community threads, make sure you are accurately represented there.
  4. Publish a missing page. If the diagnosis showed that no page of yours answers a fan-out question, write it now.
  5. Correct wrong claims. If an answer says something false about you, fix the source it is likely drawing from, then re-check.

Week 4: measure and decide

AI answers move slowly and noisily, so judge your work over a window, not a day. Re-run the same prompts on the same engines and compare with your week-one notes.

  • Won back: keep the page fresh and add it to your regular review.
  • Partial improvement: you may be cited in some engines but not others. Investigate the holdouts separately.
  • No change: go back to the diagnosis. The cause may be outside the page, such as a stronger competitor source or a type of source the engine prefers.

Check follow-ups at several points, for instance after one, two and four weeks, rather than once. Look at whether competitors moved too, so you do not credit or blame your change for a broader shift.

Keep it from happening again

  • Set alerts for lost citations so you hear about drops in days, not months.
  • Put your top pages on a refresh schedule.
  • Keep AI crawler access under review after site or plugin changes.
  • Track a stable set of prompts so you can see regressions.

How aeoora helps

aeoora watches for exactly this situation. It flags lost citations and competitors gaining ground as signals, scores them into prioritized actions, and includes a Win back lost citations skill that drafts the page changes for you to approve. After you ship a fix, it checks back after 7, 14 and 30 days so you know whether it worked.

You can try it on your own prompts with a 2-day free trial, compare plans on the pricing page, or browse the docs to see how the Action Center works.

Written by

AI search research

Share this article