How to get found by ChatGPT, Perplexity and Google AI: the lipp.dev case A developer relaunched the personal site lipp.dev as a static Astro build designed to be read and cited by AI assistants, explicitly allowing named AI crawlers such as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot in robots.txt while still blocking /api/. The work also included disabling Cloudflare email obfuscation so addresses appear in raw HTML, submitting to Bing and IndexNow, and adding structured data and consistent author identity; the developer reports no citation results yet, only that Google had indexed about 38 pages and Bing 2 the day after launch. Originally published on lipp.dev https://lipp.dev/en/guides/get-found-by-ai/ . My site has been live for one day. This is what I did so AI assistants can read it, find it and cite it: every step is in the site's code, and you can check it. In short. AI assistants that search the web cite pages they can read , that they find in an index Google's, Bing's or their own and whose author they can identify. On lipp.dev I worked on those three things: AI crawlers welcomed by name and HTML that reads without JavaScript; Bing, IndexNow and the sitemap; structured data and the same identity everywhere. No tricks: technical SEO done with care. The new lipp.dev went live on 18 November 2026 . I am writing this the day after, so I have no results to show you yet: no charts, no "+300% citations". I'll tell you what I did and why, with links to the official documentation. The starting point, measured on 19 November: Google had indexed about 38 pages of the site, Bing only 2. I'll measure the results over the coming weeks and update this guide with the real numbers, even if they're disappointing. When an assistant searches the web to answer you, it reads pages that someone has already discovered and put into an index. There are three main routes: OAI-SearchBot . OpenAI says sites that opt out of it are not shown in ChatGPT search answers PerplexityBot to surface and link sites in its results, and Perplexity-User when a user asks a question In practice, a site with solid SEO basics already has a head start. The work "for AI" is mostly: don't block anyone, get indexed beyond Google, and be clear about who you are. Many sites block AI bots without knowing it, through copied rules or a CDN setting. In my robots.txt I listed them one by one, so the intent is unambiguous: User-agent: Allow: / Disallow: /api/ AI crawlers, named explicitly so the intent is unambiguous User-agent: GPTBot User-agent: OAI-SearchBot User-agent: ChatGPT-User User-agent: ClaudeBot User-agent: Claude-SearchBot User-agent: Claude-User User-agent: PerplexityBot User-agent: Perplexity-User User-agent: Google-Extended User-agent: Applebot-Extended Allow: / Disallow: /api/ Sitemap: https://lipp.dev/sitemap-index.xml A useful distinction: GPTBot is for model training, OAI-SearchBot for search. You can block the first, allow the second, and still appear in ChatGPT search. Likewise Google-Extended is about Gemini and doesn't touch Google Search: Google says it affects neither inclusion nor ranking Google's crawlers https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers . I let them all in: for a freelancer who wants to be known, being read pays off. It's a choice, not a requirement. lipp.dev is built with Astro, as a static site: every page reaches the browser as complete HTML, with real text and real links