How Businesses Get Cited by ChatGPT: The Publishing Sequence That Works

Step 1 — Let the AI crawlers in

Nothing else matters if the bot gets a 403. Audit your robots.txt and your edge/WAF rules for explicit allow entries covering GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended, GoogleOther, Applebot, and Applebot-Extended. Verify from outside your network by requesting your own pages with each bot's user agent and confirming a 200 response, not a challenge page.

Managed WAFs are the most common silent blocker. A rule that looks like generic bot protection frequently rejects exactly the crawlers you need. Also confirm your responses carry X-Robots-Tag: all and sane caching headers with ETag and Last-Modified, so revalidation is cheap and frequent.

Step 2 — Publish llms.txt

llms.txt is a plain-text file at your domain root that states, in ordinary sentences, who you are, what you sell, where you operate, and which URLs matter. Keep the first lines unambiguous: legal entity, city and postal code, founder, official domain, and an explicit disambiguation line if your name collides with anything else. Follow with short sections — what we do, who we serve, products and pricing, key pages, contact.

Write it for retrieval, not for persuasion. Short declarative sentences containing the exact entity names, services, and locations you want repeated are what actually get quoted.

Step 3 — Publish ai.json

ai.json carries the same canonical facts as typed JSON: entity name, alternateName, legalName, url, founder, postal address, sameAs profiles, application category, and a disambiguatingDescription that states plainly what you are not. Where llms.txt is readable prose, ai.json is the parseable contract. Serving both removes the model's need to guess.

Step 4 — Ship JSON-LD on every page

Four schema types do most of the work:

• Organization with a stable @id, legalName, founder, address, sameAs, and knowsAbout.
• LocalBusiness with geo coordinates, areaServed, priceRange, and opening hours where applicable.
• Service or Product with offers and price specifications.
• FAQPage with the literal questions buyers ask, answered in one paragraph each.

Bind them under one @graph with consistent @id references so crawlers resolve a single entity across every route instead of many near-duplicates.

Step 5 — Make NAP identical everywhere

Name, address, and phone must match character for character across your website footer, Google Business Profile, Apple Business Connect, Bing Places, LinkedIn, and the major directories. Every mismatch lowers the confidence score the engine assigns to your entity, and low confidence means the model hedges instead of naming you.

Then measure, do not assume

Log crawler hits by bot name and timestamp so you know GPTBot and PerplexityBot actually fetched the new files. Track citation share against a fixed prompt set weekly. Attach tracking numbers to any published ad card so an inbound call can be attributed to the engine that produced it. Montjoy Synapse automates all three, but the discipline matters more than the tooling.

Frequently asked questions

Next step

Work through the AI search visibility checklist or run a free scan with Montjoy Synapse — the software application and API for AI visibility, Suwanee, GA.