{"slug": "how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case", "title": "How to get found by ChatGPT, Perplexity and Google AI: the lipp.dev case", "summary": "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.", "body_md": "*Originally published on [lipp.dev](https://lipp.dev/en/guides/get-found-by-ai/).*\n\nMy 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.\n\n**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.\n\nThe 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.\n\nThe 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.\n\nWhen 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:\n\n`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 (\nIn 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.\n\nMany 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:\n\n```\nUser-agent: *\nAllow: /\nDisallow: /api/\n\n# AI crawlers, named explicitly so the intent is unambiguous\nUser-agent: GPTBot\nUser-agent: OAI-SearchBot\nUser-agent: ChatGPT-User\nUser-agent: ClaudeBot\nUser-agent: Claude-SearchBot\nUser-agent: Claude-User\nUser-agent: PerplexityBot\nUser-agent: Perplexity-User\nUser-agent: Google-Extended\nUser-agent: Applebot-Extended\nAllow: /\nDisallow: /api/\n\nSitemap: https://lipp.dev/sitemap-index.xml\n```\n\nA 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.\n\nlipp.dev is built with Astro, as a static site: every page reaches the browser as complete HTML, with real text and real links (`<a href>`). React only wakes up in the contact form. I can't assume a crawler runs JavaScript, so everything that matters has to be in the HTML.\n\nThe site sits behind Cloudflare, which has an option that hides email addresses from spammers: it replaces the address in the HTML and rebuilds it with a script ([Cloudflare docs](https://developers.cloudflare.com/waf/tools/scrape-shield/email-address-obfuscation/)). People see no difference, but anything reading only the HTML finds a placeholder. I turned it off on 19 November: `hello@lipp.dev` is now in the page source, exactly as people read it. The cost is a bit more spam.\n\nNo AI asks for a minimum speed score, but Google lists page experience among the basics that also apply to its AI features. On lipp.dev: static pages on Cloudflare Pages, a single self-hosted typeface, WebP images. In internal tests on 12 November, mobile Lighthouse scored 100 on the home, service and project pages, and on 19 November the server answered in about 0.19 seconds (TTFB).\n\nThe sitemap is generated on every build. Every page has its canonical URL and the Italian/English pair declared with `hreflang`, so no engine mixes up the two versions or takes them for duplicates.\n\nIndexNow is a protocol that lets a site tell search engines a page is new or changed, instead of waiting for them to come by. Bing, Naver, Seznam, Yandex and Yep support it ([indexnow.org](https://www.indexnow.org/)). On lipp.dev a script runs after every production build, reads the sitemap and submits every URL:\n\n``` js\n// after the production build: every URL of the sitemap, in one call\nconst urlList = [...xml.matchAll(/<loc>([^<]+)<\\/loc>/g)].map((m) => m[1]);\nawait fetch('https://api.indexnow.org/indexnow', {\n  method: 'POST',\n  headers: { 'Content-Type': 'application/json; charset=utf-8' },\n  body: JSON.stringify({ host: 'lipp.dev', key: KEY, keyLocation: `https://lipp.dev/${KEY}.txt`, urlList }),\n});\n```\n\nThe key is public by design: it sits in a text file on the domain and proves the site is mine. If the call fails, the deploy goes on anyway.\n\nMost people only think of Google Search Console, which of course I set up. But Bing is the base of Copilot and Bing's AI summaries, and since February 2026 Bing Webmaster Tools has a report, still in preview, that shows how often your pages are cited in Copilot and Bing's summaries ([Bing's announcement](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview)). I verified the domain with a DNS record and submitted the sitemap. For ChatGPT, Bing's weight isn't documented: OpenAI runs its own crawler and doesn't publish how much other indexes count. I cover both routes, since it costs little.\n\nI also submitted the main pages to Brave Search.\n\n`llms.txt` is a 2024 proposal by Jeremy Howard: a Markdown file at the site root that gives assistants a short, ordered map of the content ([llmstxt.org](https://llmstxt.org/)). `llms-full.txt` isn't part of the proposal: it's a later convention, the long version with all the useful text.\n\nOn lipp.dev both are generated on every build from the same data as the pages (services, projects with their results, FAQ), so they can't say anything the site doesn't. I'm cautious about their weight: Google states plainly that its AI features need no such files, and no major engine has confirmed reading them systematically. I keep them because they cost nothing.\n\nEvery page of lipp.dev carries a JSON-LD graph with the same core nodes, joined by stable identifiers, so engines understand it is always the same business and the same person:\n\n`ProfessionalService` + `LocalBusiness`: Lipp, with VAT number, area served (Rome, Lazio, Italy), opening hours, contacts, and in `sameAs` the Google Maps listing and the LinkedIn page;`Person`: Luca Piacentini, with the job title and the LinkedIn, GitHub and Instagram profiles;`Service` on service pages, `FAQPage` only where the questions are actually on the page, `BreadcrumbList` everywhere;`ProfilePage` on the `TechArticle` with me as the author.\n\n```\n{\n  \"@type\": \"Person\",\n  \"@id\": \"https://lipp.dev/#luca\",\n  \"name\": \"Luca Piacentini\",\n  \"jobTitle\": \"Web designer e sviluppatore freelance\",\n  \"worksFor\": { \"@id\": \"https://lipp.dev/#business\" },\n  \"sameAs\": [\"https://www.linkedin.com/in/lucapiacentini/\", \"https://github.com/l-piacentini\", \"…\"]\n}\n```\n\nOne rule I always keep: the structured data only says what the page also says.\n\nOn 19 November I asked ChatGPT \"Who is Lipp?\". It described me well, but as an \"independent studio\": the words of my old site. AI assistants repeat what they find almost word for word. That same day I aligned the title, description, structured data and llms.txt on \"freelance web designer and developer\".\n\nThen the same sentence and the same details wherever I can be found: Google Business Profile, Bing Places (imported from Google), LinkedIn profile and page, GitHub, Instagram, AddLance, FreelanceDEV. \"Luca Piacentini\" is a name with plenty of namesakes, and \"Lipp\" alone is ambiguous: so name, brand and job always travel together.\n\nAI assistants quote concrete sentences: who you are, where you work, what you do, with what results. That's why there is an [About](https://lipp.dev/en/about/) page with dates and background, an [FAQ](https://lipp.dev/en/faq/) with direct answers, and project pages with measured results where there are some.\n\nYou can check almost all of it yourself in an afternoon:\n\n`yoursite.com/robots.txt`: there must be no `Disallow: /` for `User-agent: *`).` Organization`), the business, the services, and \n\n```\ncurl -s https://lipp.dev/ | grep -o 'hello@lipp.dev' | head -1\ncurl -s https://lipp.dev/robots.txt\ncurl -s https://lipp.dev/llms.txt | head -20\n```\n\nIn two weeks, and again in two to three months, I'll look at: indexed pages in Google Search Console and Bing Webmaster Tools, Bing's AI citations report, and the same questions asked to ChatGPT, Perplexity and Google AI Mode, with date and answer. I'll update [the guide on lipp.dev](https://lipp.dev/en/guides/get-found-by-ai/) with what I find.\n\nIf you have a site, new or in need of fixing, I can do this work for you too: technical audit, robots.txt, structured data, Bing and IndexNow, llms.txt, and the same identity across your site and profiles. I'm a freelancer based in Rome working with businesses all over Italy, and you always talk to me: [write to me](https://lipp.dev/en/#contatti) or see [the SEO, GEO & AEO service](https://lipp.dev/en/services/stand-out/seo-geo-aeo/).\n\n*Written with the help of AI tools; every fact and link was checked by me.*", "url": "https://wpnews.pro/news/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case", "canonical_source": "https://dev.to/lipp/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lippdev-case-28fo", "published_at": "2026-11-19 20:02:52+00:00", "updated_at": "2026-11-19 20:13:35.160490+00:00", "lang": "en", "topics": ["generative-engine-optimization", "ai-crawlers", "ai-search", "structured-data"], "entities": ["lipp.dev", "OpenAI", "ChatGPT", "Perplexity", "Google", "Cloudflare", "Astro", "Bing"], "also_reported_by": [], "takeaway": "Name each AI crawler explicitly in robots.txt (GPTBot for training, OAI-SearchBot for ChatGPT search, Google-Extended for Gemini) so you can block training while staying eligible for AI search answers.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case", "markdown": "https://wpnews.pro/news/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case.md", "text": "https://wpnews.pro/news/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case.txt", "jsonld": "https://wpnews.pro/news/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lipp-dev-case.jsonld"}}