July 12, 2026 · Italo Campilii

How to Get Your Brand Cited by ChatGPT, Perplexity, and Claude: A Practical GEO Checklist

Your customers stopped asking Google and started asking ChatGPT, and most brands are invisible in the answer. Ranking on page one of Google no longer guarantees you exist in an AI-generated response. This is the checklist I actually run across the five brands whose infrastructure I operate — over 500 GEO-optimized articles live, published by scheduled agents, built to be citable by machines as much as readable by people.

This is not theory. Every item below is something I've implemented, broken, and fixed in production.

GEO is not SEO with a new name

Traditional SEO optimizes for a ranked list of links. Generative Engine Optimization (GEO) optimizes for being quoted inside an answer. The mechanics overlap — crawlability, structure, authority — but the failure modes are different. An AI engine that can't fetch your page doesn't show you lower; it shows you never. An answer engine that can't lift a clean, self-contained passage from your article will paraphrase your competitor instead.

The shift in mindset: stop asking "what position am I?" and start asking "can a language model retrieve, parse, and attribute my content?"

Step 1: Let the AI crawlers in

The single most common GEO failure I see is self-inflicted: robots.txt or a bot-protection layer silently blocking the crawlers that feed AI engines. Many CDN and firewall defaults block "AI bots" wholesale — which means you've opted out of the answer layer without knowing it.

Explicitly allow, at minimum:

Then verify with your server logs or your CDN's bot analytics that these crawlers are actually getting 200 responses, not challenge pages. When I audited my own properties, I found bot-management rules blocking AI crawlers on a site I assumed was open. Assume nothing; read the logs.

Step 2: Ship an llms.txt

llms.txt is a plain-markdown file at your domain root that gives language models a curated map of your site: who you are, what you do, and links to your most important pages with one-line descriptions. Think of it as a sitemap written for a reader with no patience.

Keep it honest and short: your positioning in two sentences, then your cornerstone pages grouped by topic. It costs twenty minutes and it's the cheapest "here's how to understand my brand" signal you can hand to a retrieval system.

Step 3: Structured data that machines can trust

Schema markup (JSON-LD) is how you tell engines what a thing is instead of hoping they infer it. My baseline stack on every content site:

Validate it. Broken schema is worse than none, because it signals sloppiness on the exact channel where you're claiming precision.

Step 4: Entity consistency everywhere

AI engines resolve entities, not just keywords. If your brand is "Acme Labs" on your site, "Acme Labs Inc." on LinkedIn, and "AcmeLabsHQ" on a directory, you've split your identity into three weak entities instead of one strong one.

Lock down one canonical name, one description, one founder story — and repeat them verbatim across your site footer, About page, schema, social profiles, and directory listings. Consistency is what lets a model say "I know who this is" with enough confidence to cite you.

Step 5: Write passages worth lifting

Answer engines quote at the passage level, not the page level. Every important claim should live in a self-contained block that makes sense with zero surrounding context:

Read your own article and ask: if a model grabbed any single paragraph, would it stand alone and would it credit me? If not, rewrite.

Step 6: Feed Bing, because Bing feeds the machines

Underrated fact: Bing's index powers Copilot and portions of ChatGPT's browsing. Sites that ignore Bing Webmaster Tools are ignoring a direct pipe into two major answer engines.

Register every property in Bing Webmaster Tools, submit sitemaps, and fix whatever its crawler flags. It takes an hour per site and it's leverage most competitors skip.

Step 7: IndexNow for instant discovery

IndexNow lets you push URLs to Bing (and other participating engines) the moment they publish, instead of waiting for a crawl. I wired IndexNow pings into my publishing pipelines so that when a scheduled agent ships a post at 3 a.m., the URL is submitted within the same run — no human, no delay. If your CMS or build pipeline can make an HTTP request, you can implement this in an afternoon.

The full checklist, in order

  1. Audit robots.txt and CDN/firewall rules; explicitly allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot
  2. Verify in server logs that AI crawlers get real 200 responses
  3. Publish llms.txt at the domain root with your positioning and cornerstone pages
  4. Add JSON-LD schema: Organization, Article, FAQPage, Product, Person — and validate it
  5. Enforce one canonical brand name, description, and story across site, schema, and every external profile
  6. Restructure key articles into self-contained, answer-first passages with question-shaped headings
  7. Add an FAQ block to every substantial post
  8. Register all properties in Bing Webmaster Tools and submit sitemaps
  9. Wire IndexNow into your publish pipeline so new URLs are pushed automatically
  10. Re-test monthly — ask ChatGPT, Perplexity, and Claude questions your customers would ask, and log whether you're cited

Item 10 is the one people skip. GEO parameters shift constantly; the engines change how they retrieve and attribute. Treat it as an operating loop, not a launch task.

How I run this at scale

I don't do any of this by hand anymore. The checklist above is encoded into the agent workflows that publish for my brands — the same approach I describe in how I run five brands' infrastructure solo and in the 500-post SEO/GEO blog engine. Schema generation, internal linking, FAQ blocks, and IndexNow pings happen inside the pipeline, on a schedule, while I sleep. The checklist is the standard; the agents are the enforcement.

FAQ

How long does it take to get cited by AI engines?

Discovery can happen within days once crawlers have access and IndexNow is wired in, but consistent citation typically builds over weeks to months as engines accumulate confidence in your entity. The access and structure fixes are fast; authority compounds slowly.

Does llms.txt actually matter yet?

Adoption by engines is uneven, but the cost is near zero and the downside is none. It also forces you to articulate your entity clearly — which improves every other item on this list. I ship it on every property as a default.

Should I block AI crawlers to protect my content instead?

That's a legitimate business decision, but understand the trade: blocking GPTBot or ClaudeBot removes you from the answer layer where a growing share of buying research now happens. For most brands trying to be found, visibility is worth more than exclusivity.

— Italo Campilii. If you're building something that needs this kind of operator, get in touch.