Diagnosing which stage you are failing
Absence from AI answers has three very different causes and one shared symptom, so the first job is localization. If your server logs show no fetches from assistant crawlers, the failure is access. If fetches occur but your pages never appear as sources for queries they obviously answer, the failure is retrieval - usually rendering or chunk structure. If you appear as a source but are described without attribution, the failure is entity resolution.
Each diagnosis has a different fix and a different timeline. Access issues resolve within days of a configuration change. Retrieval issues resolve within weeks of a structural rewrite. Entity issues take months because they depend on third-party corroboration accumulating.
Running all three fixes simultaneously is fine, but reporting them together is not - a team that expects entity gains on an access-fix timeline will conclude the whole programme failed while it is actually working normally.
The compounding effect of corroboration
Models weight consistency across independent sources heavily, which makes the same claim appearing in five unrelated places worth far more than the same claim repeated on five of your own pages. This is the mechanism behind digital PR's outsized effect on AI visibility, and it operates even when the mentions carry no link at all.
Practical sources of corroboration are unglamorous and mostly free: accurate directory and marketplace listings, review platform profiles, conference and podcast appearances with proper attribution, documentation referenced by integration partners, and answers in communities where your category is discussed. Each one adds an independent confirmation of who you are and what you do.
Keep the description consistent across all of them. Five sources describing you five different ways can actively lower confidence, which is the opposite of the intended effect and a surprisingly common outcome when different teams own different profiles.