TL;DR: To show up in AI answers, a site first has to be a normal, indexable site that doesn’t block the right crawlers. Google says you need no special files or markup for AI Overviews or AI Mode. OpenAI says ChatGPT search uses its OAI-SearchBot crawler. Every WebZum site covers those basics. It also adds llms.txt, ai.txt and schema markup. Those extras are cheap and harmless, but no AI company has promised to use them.
What Actually Decides If AI Can Find You
Here is what the companies themselves say.
Google. AI Overviews and AI Mode pull from normal Google Search. A page must be “indexed and eligible to be shown in Google Search with a snippet.” Google also says: “You don’t need to create new machine readable files, AI text files, or markup to appear in these features” (Google Search Central).
OpenAI. OpenAI runs several crawlers, and they do different jobs (OpenAI crawler docs):
| Crawler | What it does | If you block it |
|---|---|---|
OAI-SearchBot |
Finds sites for ChatGPT search | Your site won’t show in ChatGPT search answers |
GPTBot |
Collects pages that may train OpenAI models | Your content isn’t used for training. Search is not affected |
ChatGPT-User |
Visits a page when a ChatGPT user asks it to | It’s user-triggered, so robots.txt may not apply |
So the checklist, in order:
- Don’t block search crawlers in robots.txt (Googlebot, Bingbot, OAI-SearchBot, PerplexityBot).
- Get indexed. Check that Google can find your pages.
- Keep your Google Business Profile complete. Name, address, phone, hours.
- Have a clear page for each service with the facts written out in plain text.
- Collect reviews.
None of those five need llms.txt. Everything below is extra.
What We Build: Basics Plus Extras
Every WebZum site is a set of plain, fast HTML pages with real text that any crawler can read. On top of that, every site gets these files:
/llms.txt → AI-friendly business summary
/llms-full.txt → Extended context for deeper queries
/ai.txt → AI agent permissions and guidelines
/robots.txt → Explicit AI crawler access rules
+ FAQ Schema → Structured Q&A in JSON-LD
+ HowTo Schema → Step-by-step process markup
+ LocalBusiness → Schema.org entity data
No setup required. The files are built from the same business facts as the site.
1. llms.txt — The AI-Readable Business Card
The llms.txt proposal is a plain Markdown file that sums up a site for AI tools. It’s a community proposal, not a standard. Google says it doesn’t need one, and no major AI company has said its search uses it.
We generate it from the business research we’ve already collected:
export function generateLlmsTxt(data: LlmsTxtData): string {
const { businessResearch, websiteStrategy, websiteUrl, pages } = data;
let content = `# ${businessResearch.businessName}\n\n`;
content += `> ${businessResearch.businessName} is a ${businessResearch.businessType}`;
if (businessResearch.location) {
content += ` located in ${businessResearch.location}`;
}
// Services
if (businessResearch.services?.length) {
content += `\n\n## Services\n`;
businessResearch.services.forEach(s => content += `- ${s}\n`);
}
// Service areas (critical for local AI queries)
if (businessResearch.serviceAreas?.length) {
content += `\n\n## Service Areas\nWe serve: ${areas.join(', ')}\n`;
}
// Contact info, reviews, hours...
return content;
}
Why we include it anyway: it costs nothing, it doesn’t hurt, and any tool or agent that does read it gets a clean summary of services, areas, hours and contact info. We don’t claim it ranks you anywhere.
We also generate llms-full.txt with extended context—company history, competitive positioning, industry trends—for AI systems that want deeper understanding.
2. ai.txt — Permissions for AI Agents
The ai.txt proposal lets a business say what AI agents may do with its info. Like llms.txt, it’s a proposal. No AI company has committed to honoring it. Here’s what ours says:
export function generateAiTxt(data: AiTxtData): string {
return `
Business-Name: ${data.businessResearch.businessName}
Business-Type: ${data.businessResearch.businessType}
Location: ${data.businessResearch.location}
Canonical-URL: ${data.websiteUrl}
# Permissions
Allow-Recommendations: yes
Allow-Actions: no
Allow-Information-Sharing: yes
Allow-Citation: yes
Allow-Training: yes
# Contact Preferences
Preferred-Contact-Method: ${preferredMethod}
Phone: ${phone}
Business-Hours: ${hours}
# Restrictions
Do-Not: Make price commitments without verification
Do-Not: Impersonate business employees
Do-Not: Share non-public information
`.trim();
}
The key permission: Allow-Recommendations: yes tells AI systems “Yes, recommend this business when relevant.” Allow-Actions: no means “Don’t try to book appointments or place orders on the user’s behalf.”
Treat it as a stated preference, not a rule anyone has to follow.
3. robots.txt — Welcoming AI Crawlers
This is the file that matters most on this list. A robots.txt that blocks OAI-SearchBot keeps a site out of ChatGPT search answers. Some sites do this by accident, through a copied template or a security setting. We list the main AI crawlers by name and allow them:
// We support 15+ AI crawler user-agents
const AI_CRAWLERS = [
'GPTBot', 'ChatGPT-User', 'OAI-SearchBot', // OpenAI
'Claude-Web', 'ClaudeBot', 'anthropic-ai', // Anthropic
'PerplexityBot', // Perplexity
'Google-Extended', // Google AI
'YouBot', // You.com
'cohere-ai', // Cohere
'Applebot-Extended', // Apple Intelligence
'meta-externalagent', // Meta AI
'Amazonbot', // Amazon/Alexa
'AI2Bot', // Allen AI
];
// Each gets explicit access to AEO files
crawlers.forEach(crawler => {
rules += `User-agent: ${crawler}\nAllow: /\n`;
rules += `Allow: /llms.txt\nAllow: /llms-full.txt\nAllow: /ai.txt\n\n`;
});
One honest note: allowing GPTBot means your pages may be used to train OpenAI models. Blocking it would not hurt ChatGPT search. We allow it by default because most small businesses want to be known, not hidden. We also block a few heavy SEO crawlers that bring a small business no customers.
4. FAQ Schema
FAQ schema puts questions and answers in a format machines can read. Google says no special schema is needed for its AI features, so this is not a ticket in. It just states the facts clearly:
export function generateFaqSchema(data: FaqSchemaData): object {
const faqs = [];
// Auto-generate from business data
if (data.services?.length) {
faqs.push({
question: `What services does ${data.businessName} offer?`,
answer: `${data.businessName} offers: ${data.services.join(', ')}.`
});
}
// Industry-specific FAQs
if (isHomeServices(data.businessType)) {
faqs.push(
{ question: 'Do you offer free estimates?', answer: '...' },
{ question: 'Are you licensed and insured?', answer: '...' },
{ question: 'Do you handle emergency calls?', answer: '...' }
);
}
return {
'@context': 'https://schema.org',
'@type': 'FAQPage',
'mainEntity': faqs.map(faq => ({
'@type': 'Question',
'name': faq.question,
'acceptedAnswer': { '@type': 'Answer', 'text': faq.answer }
}))
};
}
We write different FAQs for restaurants, home services, healthcare, beauty, retail, fitness and professional services. A plumber’s customers ask different things than a salon’s. The same answers also appear as plain text on the page, which is what people and crawlers actually read.
5. Entity Disambiguation with Schema.org
Many businesses share a name. sameAs links in Schema.org markup point from your site to your other profiles:
{
"@type": "Plumber",
"name": "Just Plumbing San Diego",
"sameAs": [
"https://www.facebook.com/justplumbingsd",
"https://www.yelp.com/biz/just-plumbing-san-diego",
"https://www.google.com/maps/place/..."
]
}
This helps tie your site to the same business on Facebook, Yelp and Google Maps. The profiles still have to exist and match. Your Google Business Profile matters more than any markup.
The Assembly Pipeline
All of this happens automatically during our website generation assembly step:
// During website assembly (assembly-step.ts)
const llmsTxt = generateLlmsTxt({ businessResearch, websiteStrategy, websiteUrl, pages });
await storage.writeText('llms.txt', llmsTxt);
const llmsFullTxt = generateLlmsFullTxt({ businessResearch, websiteStrategy, websiteUrl, pages });
await storage.writeText('llms-full.txt', llmsFullTxt);
const aiTxt = generateAiTxt({ businessResearch, websiteUrl, allowRecommendations: true });
await storage.writeText('ai.txt', aiTxt);
const robotsTxt = generateRobotsTxt({ businessResearch, websiteUrl });
await storage.writeText('robots.txt', robotsTxt);
// Schema markup goes inline in each HTML page
const faqSchema = generateFaqSchema({ businessResearch });
const localBusinessSchema = generateLocalBusinessSchema({ businessResearch });
Zero configuration. Every site gets the same setup.
What We Don’t Claim
We can’t promise any AI tool will mention your business. No one can. AI answers depend on things a website builder doesn’t control, like reviews, your Google Business Profile, and how many other sites mention you. Be careful with any vendor who sells “AI visibility” as a file you install.
What we can do is make sure your site isn’t the thing holding you back.
How Does Your Business Score?
We built a free tool that checks a business on 6 areas: AI Discoverability, Structured Data, Entity Clarity, Content Answerability, Trust & Authority, and Voice Readiness. It’s our own checklist, not a Google or OpenAI score. Use it to spot gaps, like missing hours or a blocked crawler.
Try It
Visit any WebZum-generated site and check:
/robots.txt— which crawlers are allowed/llms.txt— plain-text business summary/ai.txt— stated AI permissions- View source →
<script type="application/ld+json">— structured data
FAQ
How do I make my website discoverable by ChatGPT and Perplexity?
Start with the basics. Don’t block OAI-SearchBot or PerplexityBot in robots.txt, make sure your pages are indexed, keep your Google Business Profile complete, and write your services and contact info as plain text on the page. Every WebZum site covers the website parts automatically.
Do I need an llms.txt file to show up in ChatGPT?
No. OpenAI’s docs point to OAI-SearchBot access, not llms.txt. Google says no special files are needed for its AI features. WebZum adds llms.txt because it’s free and harmless, not because anything requires it.
What is ai.txt?
A proposed file that states what AI agents may do with your business information. No AI company has committed to honoring it. It sits alongside llms.txt, which describes the business itself.
Does my robots.txt block AI crawlers?
It might. Look for OAI-SearchBot, PerplexityBot or a blanket Disallow: / in your robots.txt. Blocking GPTBot only stops OpenAI model training; it doesn’t hide you from ChatGPT search. WebZum’s robots.txt allows the main AI crawlers.
How do AI systems tell apart businesses with the same name?
Through entity disambiguation. Schema.org markup with sameAs links connects your site to your other profiles. Matching name, address and phone across your site and Google Business Profile matters just as much.
How can I check my site’s AEO score?
Use the free AEO Score tool. It checks a site on 6 areas using our own checklist. It’s a way to find gaps, not an official score from Google or any AI company.
Need a site that gets the basics right? Build your free website — or check your current site for gaps first.