<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Luca Piacentini</title>
    <description>The latest articles on DEV Community by Luca Piacentini (@lipp).</description>
    <link>https://dev.to/lipp</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4019576%2F363a24d2-ae66-4001-b570-be23f3b7f222.png</url>
      <title>DEV Community: Luca Piacentini</title>
      <link>https://dev.to/lipp</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lipp"/>
    <language>en</language>
    <item>
      <title>How to get found by ChatGPT, Perplexity and Google AI: the lipp.dev case</title>
      <dc:creator>Luca Piacentini</dc:creator>
      <pubDate>Thu, 19 Nov 2026 20:02:52 +0000</pubDate>
      <link>https://dev.to/lipp/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lippdev-case-28fo</link>
      <guid>https://dev.to/lipp/how-to-get-found-by-chatgpt-perplexity-and-google-ai-the-lippdev-case-28fo</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://lipp.dev/en/guides/get-found-by-ai/" rel="noopener noreferrer"&gt;lipp.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;In short.&lt;/strong&gt; AI assistants that search the web cite pages they can &lt;strong&gt;read&lt;/strong&gt;, that they find in an &lt;strong&gt;index&lt;/strong&gt; (Google's, Bing's or their own) and whose &lt;strong&gt;author&lt;/strong&gt; 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.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  An honest note first
&lt;/h2&gt;

&lt;p&gt;The new lipp.dev went live on &lt;strong&gt;18 November 2026&lt;/strong&gt;. 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI answers come from
&lt;/h2&gt;

&lt;p&gt;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:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ChatGPT&lt;/strong&gt; has a search crawler, &lt;code&gt;OAI-SearchBot&lt;/code&gt;. OpenAI says sites that opt out of it are not shown in ChatGPT search answers (&lt;a href="https://developers.openai.com/api/docs/bots" rel="noopener noreferrer"&gt;OpenAI's crawler docs&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Perplexity&lt;/strong&gt; uses &lt;code&gt;PerplexityBot&lt;/code&gt; to surface and link sites in its results, and &lt;code&gt;Perplexity-User&lt;/code&gt; when a user asks a question (&lt;a href="https://docs.perplexity.ai/guides/bots" rel="noopener noreferrer"&gt;Perplexity's docs&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google&lt;/strong&gt; uses its usual index for AI Overviews and AI Mode. To appear as a source, a page only needs to be indexed and eligible for a snippet: no special files or markup required (&lt;a href="https://developers.google.com/search/docs/appearance/ai-features" rel="noopener noreferrer"&gt;Google Search Central&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copilot&lt;/strong&gt; and Bing's AI summaries are built on Bing (&lt;a href="https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview" rel="noopener noreferrer"&gt;Bing Webmaster blog&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Be readable
&lt;/h2&gt;

&lt;h3&gt;
  
  
  A robots.txt that welcomes AI crawlers by name
&lt;/h3&gt;

&lt;p&gt;Many sites block AI bots without knowing it, through copied rules or a CDN setting. In my &lt;code&gt;robots.txt&lt;/code&gt; I listed them one by one, so the intent is unambiguous:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;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
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A useful distinction: &lt;code&gt;GPTBot&lt;/code&gt; is for model training, &lt;code&gt;OAI-SearchBot&lt;/code&gt; for search. You can block the first, allow the second, and still appear in ChatGPT search. Likewise &lt;code&gt;Google-Extended&lt;/code&gt; is about Gemini and doesn't touch Google Search: Google says it affects neither inclusion nor ranking (&lt;a href="https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers" rel="noopener noreferrer"&gt;Google's crawlers&lt;/a&gt;). I let them all in: for a freelancer who wants to be known, being read pays off. It's a choice, not a requirement.&lt;/p&gt;

&lt;h3&gt;
  
  
  HTML that reads without JavaScript
&lt;/h3&gt;

&lt;p&gt;lipp.dev is built with Astro, as a static site: every page reaches the browser as complete HTML, with real text and real links (&lt;code&gt;&amp;lt;a href&amp;gt;&lt;/code&gt;). 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.&lt;/p&gt;

&lt;h3&gt;
  
  
  The email address in plain text
&lt;/h3&gt;

&lt;p&gt;The 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 (&lt;a href="https://developers.cloudflare.com/waf/tools/scrape-shield/email-address-obfuscation/" rel="noopener noreferrer"&gt;Cloudflare docs&lt;/a&gt;). People see no difference, but anything reading only the HTML finds a placeholder. I turned it off on 19 November: &lt;code&gt;hello@lipp.dev&lt;/code&gt; is now in the page source, exactly as people read it. The cost is a bit more spam.&lt;/p&gt;

&lt;h3&gt;
  
  
  Speed
&lt;/h3&gt;

&lt;p&gt;No 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).&lt;/p&gt;

&lt;h2&gt;
  
  
  Be findable (beyond Google too)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Sitemap, canonical and hreflang
&lt;/h3&gt;

&lt;p&gt;The sitemap is generated on every build. Every page has its canonical URL and the Italian/English pair declared with &lt;code&gt;hreflang&lt;/code&gt;, so no engine mixes up the two versions or takes them for duplicates.&lt;/p&gt;

&lt;h3&gt;
  
  
  IndexNow on every deploy
&lt;/h3&gt;

&lt;p&gt;IndexNow 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 (&lt;a href="https://www.indexnow.org/" rel="noopener noreferrer"&gt;indexnow.org&lt;/a&gt;). On lipp.dev a script runs after every production build, reads the sitemap and submits every URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// after the production build: every URL of the sitemap, in one call&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;urlList&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;xml&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;matchAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;loc&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&amp;lt;&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;\&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;loc&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;/&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'https://api.indexnow.org/indexnow'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'POST'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s1"&gt;'Content-Type'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'application/json; charset=utf-8'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;host&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'lipp.dev'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;KEY&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;keyLocation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`https://lipp.dev/${KEY}.txt`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;urlList&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The 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.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bing Webmaster Tools
&lt;/h3&gt;

&lt;p&gt;Most 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 (&lt;a href="https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview" rel="noopener noreferrer"&gt;Bing's announcement&lt;/a&gt;). 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.&lt;/p&gt;

&lt;p&gt;I also submitted the main pages to Brave Search.&lt;/p&gt;

&lt;h3&gt;
  
  
  llms.txt and llms-full.txt
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;llms.txt&lt;/code&gt; is a 2024 proposal by Jeremy Howard: a Markdown file at the site root that gives assistants a short, ordered map of the content (&lt;a href="https://llmstxt.org/" rel="noopener noreferrer"&gt;llmstxt.org&lt;/a&gt;). &lt;code&gt;llms-full.txt&lt;/code&gt; isn't part of the proposal: it's a later convention, the long version with all the useful text.&lt;/p&gt;

&lt;p&gt;On 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Be recognisable
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Structured data, linked together
&lt;/h3&gt;

&lt;p&gt;Every 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:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;ProfessionalService&lt;/code&gt; + &lt;code&gt;LocalBusiness&lt;/code&gt;: Lipp, with VAT number, area served (Rome, Lazio, Italy), opening hours, contacts, and in &lt;code&gt;sameAs&lt;/code&gt; the Google Maps listing and the LinkedIn page;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Person&lt;/code&gt;: Luca Piacentini, with the job title and the LinkedIn, GitHub and Instagram profiles;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Service&lt;/code&gt; on service pages, &lt;code&gt;FAQPage&lt;/code&gt; only where the questions are actually on the page, &lt;code&gt;BreadcrumbList&lt;/code&gt; everywhere;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;ProfilePage&lt;/code&gt; on the &lt;a href="https://lipp.dev/en/about/" rel="noopener noreferrer"&gt;About&lt;/a&gt; page, with the person as main entity: the format Google describes for pages of creators sharing first-hand perspectives (&lt;a href="https://developers.google.com/search/docs/appearance/structured-data/profile-page" rel="noopener noreferrer"&gt;Google's docs&lt;/a&gt;);&lt;/li&gt;
&lt;li&gt;on the guide itself, &lt;code&gt;TechArticle&lt;/code&gt; with me as the author.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Person"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://lipp.dev/#luca"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Luca Piacentini"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"jobTitle"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Web designer e sviluppatore freelance"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"worksFor"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://lipp.dev/#business"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"sameAs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"https://www.linkedin.com/in/lucapiacentini/"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"https://github.com/l-piacentini"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"…"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One rule I always keep: the structured data only says what the page also says.&lt;/p&gt;

&lt;h3&gt;
  
  
  The same identity everywhere
&lt;/h3&gt;

&lt;p&gt;On 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".&lt;/p&gt;

&lt;p&gt;Then 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.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pages that answer
&lt;/h3&gt;

&lt;p&gt;AI assistants quote concrete sentences: who you are, where you work, what you do, with what results. That's why there is an &lt;a href="https://lipp.dev/en/about/" rel="noopener noreferrer"&gt;About&lt;/a&gt; page with dates and background, an &lt;a href="https://lipp.dev/en/faq/" rel="noopener noreferrer"&gt;FAQ&lt;/a&gt; with direct answers, and project pages with measured results where there are some.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I didn't do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No separate page for bots: people and crawlers read the same HTML.&lt;/li&gt;
&lt;li&gt;No forced keywords and no copy-paste pages for each city: I work across Italy remotely and I say so, without cloning pages.&lt;/li&gt;
&lt;li&gt;No made-up reviews and no self-awarded star ratings in the structured data.&lt;/li&gt;
&lt;li&gt;No Wikidata entry written by me: without independent sources it would be a conflict of interest.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The checklist for your site
&lt;/h2&gt;

&lt;p&gt;You can check almost all of it yourself in an afternoon:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;code&gt;yoursite.com/robots.txt&lt;/code&gt;: there must be no &lt;code&gt;Disallow: /&lt;/code&gt; for &lt;code&gt;OAI-SearchBot&lt;/code&gt;, &lt;code&gt;PerplexityBot&lt;/code&gt; or everyone (&lt;code&gt;User-agent: *&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Check your CDN or firewall: some have settings that block AI bots regardless of robots.txt.&lt;/li&gt;
&lt;li&gt;View a page's source (not the inspector): the important text and links must already be there, without JavaScript.&lt;/li&gt;
&lt;li&gt;Search the source for your email address: if you find a placeholder, an anti-spam feature is hiding your contact from AI too.&lt;/li&gt;
&lt;li&gt;Register the site in Google Search Console &lt;strong&gt;and&lt;/strong&gt; Bing Webmaster Tools, and submit the sitemap to both.&lt;/li&gt;
&lt;li&gt;Turn on IndexNow: many CMSs and CDNs already have a setting or a plugin.&lt;/li&gt;
&lt;li&gt;Add the basic structured data: who you are (&lt;code&gt;Person&lt;/code&gt; or &lt;code&gt;Organization&lt;/code&gt;), the business, the services, and &lt;code&gt;sameAs&lt;/code&gt; pointing to your real profiles.&lt;/li&gt;
&lt;li&gt;Write one sentence that says who you are and what you do, and use it word for word on your site, Google Business, LinkedIn and directories.&lt;/li&gt;
&lt;li&gt;Make an "about" page with verifiable facts: since when you've worked, where, for whom, with what.&lt;/li&gt;
&lt;li&gt;Ask ChatGPT, Perplexity and Google AI Mode who you are and what you do, note the date, and ask again a few weeks later.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://lipp.dev/ &lt;span class="o"&gt;|&lt;/span&gt; grep -o &lt;span class="s1"&gt;'hello@lipp.dev'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; head -1
curl -s https://lipp.dev/robots.txt
curl -s https://lipp.dev/llms.txt &lt;span class="o"&gt;|&lt;/span&gt; head -20
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What I'll measure
&lt;/h2&gt;

&lt;p&gt;In 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 &lt;a href="https://lipp.dev/en/guides/get-found-by-ai/" rel="noopener noreferrer"&gt;the guide on lipp.dev&lt;/a&gt; with what I find.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you'd like me to do it
&lt;/h2&gt;

&lt;p&gt;If 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: &lt;a href="https://lipp.dev/en/#contatti" rel="noopener noreferrer"&gt;write to me&lt;/a&gt; or see &lt;a href="https://lipp.dev/en/services/stand-out/seo-geo-aeo/" rel="noopener noreferrer"&gt;the SEO, GEO &amp;amp; AEO service&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Written with the help of AI tools; every fact and link was checked by me.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>astro</category>
    </item>
  </channel>
</rss>
