Start with robots.txt, then check the layers in front of your site, because most blocks hide there.
1. Read robots.txt. Open yoursite.com/robots.txt and look for rules that name AI crawlers, or a blanket Disallow: / under User-agent: *. Each AI company documents its own crawler names, and they are separate bots for separate jobs: some collect training data, some build a search index, and some fetch a page live when a person asks a question. Blocking one does not block the others. Look the names up in the vendor's documentation instead of copying a list from a blog.
2. Test the real response. A robots.txt file that allows a bot means nothing if the server refuses it. Request a page with the full user agent string the vendor publishes and read the status code:
curl -I -A "<full user agent string from the vendor docs>" https://yoursite.com/
A 200 is good. A 403, a 429, or a challenge page means something is in the way. Some firewalls also check the visitor's IP range against the vendor's published list, so a plain curl can pass while the real bot fails.
3. Check your CDN and firewall. Bot protection at hosting and CDN providers often challenges unfamiliar automated traffic by default. Open the firewall event log and search for the user agents you care about.
4. Check rendering. Many crawlers do not run JavaScript. View the page source, not the browser inspector, and confirm your text is in the HTML.
5. Read your server logs. They show which bots actually visit and what each one gets back.
If everything is open and you still do not appear, the cause is almost always content or reputation. Access is the entry requirement, not the whole game.