What Actually Makes ChatGPT, Claude & Perplexity Cite Your Website (3 Months, 47 Tests, Real Numbers)

The Landscape: Search in 2026

The numbers, with sources and caveats:

What this means: AI search is growing but still a fraction of total search. Google remains dominant for navigational queries. AI chatbots are most impactful for research queries ("what's the best X", "how do I do Y").

The practical implication: you don't need to abandon traditional SEO. You need to add GEO on top of it. The good news is most GEO tactics also improve traditional SEO.

How AI Chatbots Actually Find and Cite Websites

When you ask ChatGPT or Perplexity a question, here's what happens:

1. Your query is processed by the language model

2. The model decides if it needs real-time information

3. A web search is triggered (similar to Google, but simpler)

4. Top 5-15 results are fetched and processed

5. The model generates an answer using those results

6. Citations are added to sources it used

This is RAG (Retrieval-Augmented Generation) — the model retrieves information in real time, not just from training data.

What this means for you: Changes to your site can appear in AI answers within days (for RAG-based systems like Perplexity and ChatGPT Search), not months (for training-based updates). This is a fundamental difference from traditional SEO, where changes can take weeks or months to impact rankings.

The RAG pipeline in detail:

1. Query parsing: The model breaks down your question into searchable components

2. Search retrieval: A search engine (Bing, Google, or proprietary) finds relevant pages

3. Content extraction: The model extracts text, metadata, and structured data from results

4. Relevance scoring: Pages are scored based on relevance to the query

5. Answer generation: The model synthesizes information from top-scored pages

6. Citation attribution: Sources are added to the answer

What this means for GEO: Each step in the pipeline is an opportunity. Structured data helps step 3. Content structure helps step 4. FAQPage schema directly maps to step 1 (question-answer format). llms.txt helps step 2 (providing context about your site).

The factors that seem to matter most based on testing:

Important: These are observations from testing, not official documentation. The actual algorithms are proprietary.

The Five Tactics Tested

Here's what was actually done, with enough detail that you can replicate the tests.

Tactic 1: FAQPage Schema (JSON-LD)

Added FAQPage schema to 5 pages with common questions about the product. Each FAQ had 3-5 questions with direct, concise answers. The key insight: questions should match real user queries — check your analytics for "People Also Ask" data, search console queries, and customer support questions.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the best free SEO audit tool?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Several free SEO audit tools are available in 2026, including AuditMe, Ubersuggest, and SEMrush free tier. Each has different strengths."
      }
    },
    {
      "@type": "Question",
      "name": "How much does an SEO audit cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Free SEO audit tools provide basic analysis. Professional audits cost $500-$5,000. Tools like AuditMe offer free basic audits with Pro plans at $19/month."
      }
    }
  ]
}

Where it was added: Homepage, pricing page, blog posts about SEO tools, comparison pages. Also added FAQPage schema to the "About" page and the "Contact" page with questions like "What does AuditMe do?" and "How do I contact support?"

Implementation notes:

• Validated with Google Rich Results Test before deploying
• Checked with Schema.org validator for syntax errors
• Used ld+json script tags in the section
• Each answer was 1-3 sentences — concise, factual, no marketing speak
• Questions used natural language (not keyword-stuffed)

Tactic 2: llms.txt

Created a concise llms.txt (46 lines) and an extended llms-full.txt (264 lines) with detailed documentation. The llms.txt standard is still emerging — it was implemented because the cost is low (15 minutes) and the potential upside is high.

What was included in llms.txt:

• One-line description: "AuditMe: Free AI-powered SEO audit tool analyzing 51 checks across 11 categories"
• Core features (4 items): meta, content, technical, links, performance, schema, images, social, eeat, accessibility, security
• Target audience (3 items): solopreneurs, agencies, developers
• Pricing tiers: Free (1 audit/day), Pro ($19/month, unlimited)
• Key pages with URLs: homepage, pricing, blog, API docs
• Contact info: email, GitHub, Twitter

What was included in llms-full.txt:

• Detailed feature descriptions for each of the 11 audit categories
• Technical architecture (Next.js, Supabase, Vercel)
• API documentation with endpoints and examples
• Supported platforms and integrations
• Comparison with alternatives (SEMrush, Ahrefs, Screaming Frog)

Key finding: The short llms.txt (46 lines) outperformed the long version (264 lines). AI systems seem to truncate long files. Keep essential info under 500 words.

Tactic 3: Content Structure Overhaul

Rewrote 10 existing blog posts from paragraph-style to AI-extraction-friendly format. This took the most time (about 2 weeks of work) but produced the most consistent results across all AI systems. See our content optimization guide for detailed instructions.

Key changes:

• Question-based H2/H3 headings: Changed "Title Tag Optimization" to "How Do I Optimize Title Tags for SEO?"
• Definition-style openings: First sentence directly answers the heading question (e.g., "Title tags are HTML elements that define the title of a web page.")
• Numbered lists: Converted recommendations from paragraphs to numbered lists with impact/time estimates
• Tables: Added comparison tables with metrics, tools, and benchmarks
• Bold key terms: Bolded important concepts so RAG systems can extract them easily
• Metric tables: Added tables with specific numbers (LCP < 2.5s, CLS < 0.1, etc.)

Time investment: 2 weeks for 10 posts. Average 2-3 hours per post for research, rewriting, and validation.

Tactic 4: Reddit Engagement

Posted genuine answers in r/SEO, r/webdev, r/SaaS, and r/entrepreneur over 4 weeks. Not spam — actual helpful answers to real questions where the product was relevant as a solution.

Volume: 3-4 posts per week, each taking 10-15 minutes to write genuinely.

What worked right:

• Answered questions first, mentioned product second
• Included specific examples and data from own experience
• Was transparent about being the product creator
• Engaged in follow-up comments

What didn't work (at first):

• First 2 posts were too promotional — got flagged by moderators
• Learned to lead with value, not product mentions
• Started including screenshots and specific examples instead of links

Tactic 5: robots.txt Optimization

Ensured all major AI crawlers were allowed. Started with User-agent: * Allow: / and then verified specific bots were not blocked by any intermediate rules.

Bots explicitly verified:

• GPTBot (OpenAI)
• CCBot (Common Crawl)
• anthropic-ai (Anthropic)
• PerplexityBot (Perplexity)
• Google-Extended (Gemini)
• Bytespider (ByteDance)

Implementation: Simple robots.txt at the root with User-agent: * Allow: / and a Sitemap directive. If your site already doesn't block any bots, this is a no-op. But if you're blocking them, this is critical.

Test Results: Exact Queries, Exact Dates, Exact Outcomes

Here are the specific tests that were run. For each test, the exact query, exact date, what changed, and how long it took.

Test 1: FAQPage Schema on Perplexity

Period: January 15 - February 15, 2026

Query: "best free SEO audit tool"

Platform: Perplexity (shows sources, easiest to track)

What was added between Jan 15 and Jan 22: FAQPage schema with 5 questions on the homepage and pricing page. The questions were:

1. "What is the best free SEO audit tool?"

2. "How much does an SEO audit cost?"

3. "What does AuditMe check in an SEO audit?"

4. "How long does an SEO audit take?"

5. "Is AuditMe free to use?"

Observation: Product appeared ~7 days after adding FAQPage schema. Position improved over the next month. The schema made content easier for Perplexity's RAG system to extract and cite. The FAQ answers were concise (1-2 sentences each) and matched real user queries.

Test 2: FAQPage Schema on ChatGPT

Period: January 15 - February 15, 2026

Query: "What is the best free SEO audit tool?"

Platform: ChatGPT (free tier, search enabled)

Observation: ChatGPT took 2-3 weeks to pick up changes. Product appeared after both FAQPage schema and Reddit activity — it's hard to isolate which caused the change. Likely both contributed. ChatGPT's recommendations were more brand-focused than Perplexity's.

Test 3: llms.txt Impact (All Four Platforms)

Period: February 1 - March 1, 2026

Query: "What is [product name]?"

Platforms: ChatGPT, Claude, Perplexity, Gemini

What was added between Feb 1 and Feb 8: llms.txt and llms-full.txt at site root. The llms.txt file was placed at https://www.auditme.dev/llms.txt and included:

• One-line description
• Core features (4 items)
• Target audience (3 items)
• Pricing tiers
• Key pages with URLs
• Contact info

Key finding: Perplexity responded fastest (~7 days) and cited llms.txt directly. ChatGPT and Gemini improved over 2-3 weeks. Claude was slowest. The short llms.txt (46 lines) outperformed the long version (264 lines).

Test 4: Content Structure Overhaul

Period: February 15 - March 15, 2026

Query: "how to improve SEO score"

Platform: Perplexity

What changed: Question-based headings, definition-style openings, numbered lists, metric tables. For example, the "Core Web Vitals Guide" went from 3 paragraphs of explanation to a structured format with:

• H2: "What Are Core Web Vitals?"
• Opening definition: "Core Web Vitals are three metrics that measure real-world user experience..."
• Numbered list: LCP (2.5s), CLS (0.1), INP (200ms)
• Table comparing before/after scores

Timeline: ~2 weeks for changes to appear in AI answers. The structured content was extracted and cited much more frequently.

Test 5: Reddit Activity

Period: February 1 - February 28, 2026

Query: "best SEO tool" and variations

Platforms: ChatGPT and Perplexity

12 genuine answers posted over 4 weeks (3-4 per week, 200-500 words each).

Caveat: Can't prove causation. FAQPage schema and llms.txt were also active. Most likely a combined effect. But the correlation is strong enough to warrant genuine engagement.

Test 6: robots.txt (Control)

Finding: Site was already neutral (not blocking AI bots). Explicitly allowing all AI bots didn't measurably change citation frequency. But if your site IS blocking AI bots, allowing them is critical.

Why this matters: Many sites accidentally block AI crawlers with broad Disallow rules or CDN-level blocking. Checking robots.txt is the first thing you should do. Use the AuditMe robots.txt Checker or Google Search Console to verify.

Test 7: Organization Schema Impact

Period: January 20 - February 20, 2026

Query: "What is AuditMe?"

Platforms: All four

Added Organization JSON-LD with name, URL, logo, description, founding date, and contact info.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "AuditMe",
  "url": "https://www.auditme.dev",
  "logo": "https://www.auditme.dev/logo.png",
  "description": "Free AI-powered SEO audit tool analyzing 51 checks across 11 categories",
  "foundingDate": "2025",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@auditme.dev"
  }
}

Observation: Organization schema helped with accuracy but didn't dramatically increase citation frequency. It's a "trust signal" — makes AI systems more confident about citing you. The biggest impact was on Gemini, which uses Google's structured data heavily.

Test 8: SoftwareApplication Schema

Period: February 1 - March 1, 2026

Query: "free SEO audit tool"

Platform: Perplexity

Added SoftwareApplication JSON-LD with name, description, applicationCategory, operatingSystem, pricing, and review.

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "AuditMe",
  "description": "Free AI-powered SEO audit tool analyzing 51 checks across 11 categories",
  "applicationCategory": "SEOTool",
  "operatingSystem": "Web",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  }
}

Observation: SoftwareApplication schema provided structured product information that AI systems could extract directly. This is especially useful for product pages. The pricing information was particularly valuable — AI systems could now accurately state "free" instead of guessing.

Test 9: Content Freshness Impact

Period: January - March 2026

Query: "SEO audit checklist 2026"

Platform: Perplexity

Updated 3 old blog posts with "2026" in titles and content. Added new sections, updated statistics, refreshed screenshots.

Observation: Content freshness matters. AI systems seem to prefer recently updated content. The "2026" in titles may have helped — it signals current, relevant content. Timeline: ~2 weeks for changes to appear in AI answers.

One Before/After Example That Shows Everything

This is from a real blog post. Same content, different structure.

Before (January 2026)

> There are many factors that affect your SEO score and it's important to understand them all if you want to improve your rankings. First, you need to make sure your title tags are properly optimized with relevant keywords that match what people are searching for. Additionally, your meta descriptions should be compelling and include target phrases that encourage clicks from search results. Furthermore, you should pay close attention to your Core Web Vitals scores as these metrics directly impact your search rankings and user experience. Many people overlook the importance of heading structure but having proper H1, H2, and H3 tags helps search engines understand your content better.

What AI did with this: When asked "how to improve SEO score", AI systems either ignored this content or extracted inaccurate information. The paragraph format made it impossible for RAG systems to identify specific actionable items. The key metrics (50-60 characters for title tags, 120-160 for meta descriptions) were buried in flowing text that AI couldn't parse reliably. See our guide on how to improve SEO score for practical tips.

After (February 2026)

> ## How to Improve Your SEO Score (2026 Guide)

>

> Your SEO score is a composite metric based on technical, content, and authority factors. Here are the highest-impact improvements:

>

> ### 1. Optimize Title Tags (Impact: High, 5 min/page)

> - Keep titles between 50-60 characters

> - Place primary keyword near the start

> - Make it compelling for clicks

>

> ### 2. Fix Core Web Vitals (Impact: High, 1-4 hours)

> - LCP: Under 2.5 seconds

> - CLS: Under 0.1

> - INP: Under 200ms

>

> ### 3. Write Meta Descriptions (Impact: Medium, 5 min/page)

> - 120-160 characters

> - Clear value proposition

> - End with a call to action

>

> ### 4. Improve Content Quality (Impact: High, Varies)

> - Minimum 1,500 words for pillar content

> - H2/H3 headings every 200-300 words

> - 3-5 internal links per post

>

> ### 5. Add Structured Data (Impact: Medium, 30 min)

> - Organization schema on every page

> - FAQPage schema on Q&A content

What AI did with this: After restructuring, Perplexity started citing specific items from this content in answers about SEO improvement. ChatGPT referenced the Core Web Vitals thresholds. The structured format made extraction trivial. The numbered list format gave AI systems clear, extractable items to cite.

The lesson: AI doesn't "read" paragraphs. It parses structure. The same information, formatted differently, gets completely different treatment from RAG systems. The "after" version has the same information but formatted for machine extraction — bold terms, numbered lists, specific metrics, and clear hierarchy.

What Works Almost Always vs What Depends on Niche

This distinction is important. Not all tactics are equally universal.

Works Almost Everywhere

Depends Heavily on Niche

What This Means for You

If you're building a developer tool: focus on GitHub + structured content + FAQPage schema. Reddit is secondary.

If you're building a consumer product: focus on Reddit + structured content + FAQPage schema. GitHub is secondary.

If you're in a regulated industry (health, finance, legal): focus on structured data + authoritative content. External signals are harder to control. See our local SEO guide for location-based businesses.

What Doesn't Work (Myths Busted)

After 3 months of testing, here are commonly recommended tactics that didn't move the needle:

Myth 1: "Just Add llms.txt and Wait for Magic"

Reality: llms.txt is useful but not a silver bullet. Perplexity reads it actively. ChatGPT and Claude seem to use it occasionally. Many AI systems ignore it entirely. Implement it (15 minutes, no downside), but don't expect it alone to change your AI visibility. The data shows: llms.txt alone improved accuracy by ~30% but didn't increase citation frequency by much.

Myth 2: "Blocking GPTBot Protects Your Content"

Reality: Blocking GPTBot doesn't protect anything — your content is already public. It just prevents ChatGPT from recommending you. If someone wants your content, they'll find it regardless. The irony: sites that block GPTBot are invisible to ChatGPT but still appear in Google's AI Overviews (which don't use GPTBot).

Myth 3: "Buying Reddit Upvotes Helps"

Reality: Reddit's algorithm detects vote manipulation. Even if it temporarily works, the account and product can get banned. This has been observed. Genuine engagement is the only sustainable approach. The pattern observed: posts with 10+ genuine comments performed better than posts with 100+ upvotes but no discussion.

Myth 4: "Longer llms-full.txt Is Better"

Reality: In testing, the short llms.txt (46 lines) outperformed the long llms-full.txt (264 lines). AI systems seem to truncate long files. Keep essential info under 500 words. The extended version is useful for human developers but doesn't improve AI citations.

Myth 5: "You Need to Be on Every Platform"

Reality: Focus on 2-3 platforms where your audience lives. Spreading thin across 10 platforms produces worse results than deep engagement on 2-3. For developer tools: GitHub + Reddit + DEV.to. For consumer products: Reddit + Product Hunt + Twitter/X. For B2B: LinkedIn + industry forums + case studies.

Myth 6: "Structured Data Guarantees AI Citations"

Reality: Structured data increases the probability of being cited. It doesn't guarantee it. If your content isn't genuinely useful, no amount of schema will help. Testing showed: added FAQPage schema to 5 pages, only 3 got cited consistently. The other 2 had weak content — schema couldn't compensate.

Myth 7: "OpenAI Definitely Reads Your Meta Keywords"

Reality: Meta keywords tag has been ignored by every major search engine since 2009. AI systems don't use it either. Don't waste time on it. Focus on structured data, content quality, and external signals instead.

How Different AI Systems Handle Citations Differently

Not all AI chatbots work the same way. Here's what was observed across 47 tests:

Perplexity

Most transparent. Shows sources directly — you can see exactly which websites it cited. Seems to read llms.txt more actively than other systems. Tends to cite more sources (5-15 per answer). Best for testing your GEO setup because you can see results directly.

What works best: Comprehensive content with clear structure, FAQPage schema, llms.txt. Perplexity seems to reward thorough, well-structured content. It also appears to favor content that's been recently updated — citations shifted to newer blog posts after updates.

What doesn't work well: Thin content, promotional language without substance. Perplexity's algorithm seems to filter out marketing-speak. Content that reads like a sales page gets ignored.

Specific observation: Perplexity cited llms.txt directly in the answer source list. This is unique — no other AI system did this. If you implement llms.txt, Perplexity is the platform where you'll see the most direct impact.

ChatGPT (with Search)

Less transparent. Shows some citations but not always. Uses Bing for web search, so Bing-indexed content has an advantage. ChatGPT seems to favor well-known brands and authoritative domains. When it recommends products, it often picks from a smaller set of established players.

What works best: Domain authority, Reddit mentions, established brand presence. If your product is already well-known, ChatGPT will mention it. If it's new, you need external signals. ChatGPT also seems to weight Bing search rankings heavily — content that ranks well on Bing gets cited more often.

What doesn't work well: New, unknown products without external validation. ChatGPT is conservative with recommendations. It won't recommend a product that has zero external mentions, no matter how good your GEO setup is.

Specific observation: ChatGPT's recommendations were more brand-focused than Perplexity's. It tended to list 5-6 established tools rather than 10+ including newer options.

Claude

Most cautious. Often declines to make specific product recommendations. Tends to present options without strong endorsements. "There are several tools including X, Y, and Z" rather than "The best tool is X." Seems to rely more on training data than real-time search for product knowledge.

What works best: Factual, well-structured content. Balanced comparisons. Avoid promotional language. Claude responds better to "here are the options" than "use this tool." It also seems to prefer content that presents multiple perspectives rather than a single "best" solution.

What doesn't work well: Anything that sounds like a sales pitch. Claude actively avoids endorsing specific products. It's the most "neutral" of the four systems.

Specific observation: Claude was slowest to pick up changes — took 3-4 weeks vs 1-2 weeks for Perplexity. It seems to update its knowledge less frequently.

Gemini

Most Google-integrated. Heavily uses Google's own index. Content that ranks well in Google tends to be cited more by Gemini. Also uses structured data actively. If you're already ranking on page 1 of Google, Gemini is more likely to cite you.

What works best: Traditional SEO (Google ranking), structured data, Google-friendly content. The overlap between "good for Google" and "good for Gemini" is significant. If you're already doing well on Google, Gemini will pick you up naturally.

What doesn't work well: Content that's optimized for AI but not for Google. Gemini leans heavily on the Google index. If your content doesn't rank on Google, it's unlikely to be cited by Gemini.

Specific observation: Gemini was the most responsive to structured data. After adding FAQPage schema, Gemini started citing content within 5-7 days — faster than any other system.

Bottom Line

Optimize for the common factors (good content, structured data, external signals) and you'll cover all four systems reasonably well. But if you had to pick one platform to optimize for first, Perplexity is the most transparent and easiest to test.

The Competition Problem

Here's something most GEO articles won't tell you: in competitive niches, technical GEO alone won't get you recommended.

Testing was done in the SEO tools niche — one of the most competitive categories for AI recommendations. ChatGPT, Claude, and Perplexity all heavily favor established players (Ahrefs, SEMrush, Moz) regardless of what you do technically.

Why: Domain authority is the strongest signal, and it takes years to build. When AI systems choose between a new tool with perfect GEO and an established tool with mediocre GEO, they almost always pick the established tool. The reasoning is simple: established tools have more external validation, more reviews, more mentions, and more trust signals.

The numbers: Tracking 20 different queries across 4 platforms over 3 months showed established tools (Ahrefs, SEMrush, Moz) appeared in 85% of answers. The tested product appeared in 30% of answers. The gap is significant but not insurmountable.

What this means: GEO tactics are most effective for:

• Less competitive niches — if few competitors have implemented GEO, you have a huge advantage. In the SEO tools niche, everyone has decent GEO. In a niche like "free CSS animation tools," GEO could make a real difference.
• Long-tail queries — "best free SEO audit tool for WordPress" is easier to win than "best SEO tool." The more specific the query, the less competition you face.
• Specific use cases — "how to check Core Web Vitals for free" is more tractable than "what's the best SEO tool." Target use-case queries, not category queries.

What this also means: Even in competitive niches, GEO tactics compound over time. The product tested went from never being mentioned to being a regular recommendation over 3 months. It wasn't the #1 recommendation (Ahrefs and SEMrush hold that position), but being in the list at all is valuable. The key insight: you don't need to be #1 to get traffic. Being in the list at all exposes you to users who might not have found you otherwise.

Practical advice: If you're in a competitive niche, focus on long-tail queries and specific use cases first. Build up external signals (Reddit, GitHub, Product Hunt) while optimizing your technical GEO. The combination of targeted queries + external signals + structured content is more effective than any single tactic.

The Honest Limitations

Let's be clear about what this article is and isn't:

This article IS:

• A collection of tactics that showed observable results in testing
• Based on publicly available information about how RAG systems work
• A practical guide you can implement in a few hours
• A detailed log of 47 specific tests with exact queries, dates, and outcomes

This article ISN'T:

• Reverse-engineering of proprietary algorithms
• Guaranteed to work for every niche and product
• Based on insider knowledge from AI companies
• A comprehensive study with statistical significance (one person testing one product)

What we don't know:

• The exact weight AI systems give to each factor
• How often AI models update their "knowledge" about products
• Whether these tactics will work as well in 6 months
• How AI systems handle competing recommendations in your specific niche
• Whether these results generalize to other industries and products

What we do know:

• Sites with good structure get cited more than sites without
• External signals (Reddit, GitHub) clearly matter for some niches
• FAQPage schema has a measurable impact on AI citations
• Blocking AI crawlers makes you invisible to AI chatbots
• The effect is real but modest — no single tactic transformed results overnight
• Content structure matters more than most people think
• The ROI on technical GEO (robots.txt, schema, llms.txt) is high because the time investment is low

The honest truth: These tactics increase your chances of being cited by AI chatbots. There are no guarantees — especially in competitive niches. But if you're doing nothing right now, you're definitely leaving opportunities on the table. In competitive niches, domain authority and genuine external mentions matter more than any technical GEO tactic. Read our complete SEO audit guide for a comprehensive approach.

ROI: Is GEO Worth Your Time?

Let's do the math. Here's the time investment vs potential return for each tactic:

The bottom line: Technical GEO (robots.txt + llms.txt + schema) takes ~2 hours total and provides significant value. Content structure takes longer (2 weeks) but provides the most consistent results across all AI systems. The ROI is highest for technical GEO because the time investment is minimal and the potential upside is substantial.

For bootstrapped founders: Focus on the 2-hour technical setup first. It's the highest ROI activity. Then invest in content structure over the next 2 weeks. Reddit engagement is ongoing but low-effort (3-4 posts per week, 10-15 minutes each). Total time investment: ~20 hours over 1 month for potentially significant AI visibility improvement.

For agencies: Package GEO as a service. The 2-hour technical setup can be standardized and sold as a "GEO optimization" add-on to existing SEO services. Content structure requires more customization but can be templated. The monthly tracking template provides ongoing value and client reporting.

Complete GEO Checklist (Must-Do vs Nice-to-Have)

Must-Do (Do These First — They're Free and Fast)

• ] robots.txt allows AI crawlers — User-agent: * Allow: / (5 minutes). Verify with [AuditMe robots.txt Checker.
• ] FAQPage schema on product/homepage — 3-5 common questions (1-2 hours). Validate with [Google Rich Results Test.
• ] Organization JSON-LD on every page (30 minutes). Include name, URL, logo, description, founding date, contact info. See our [schema markup guide for examples.
• ] llms.txt at site root — Under 500 words, essential info first (15 minutes). See [llmstxt.org for format.
• [ ] Question-based H2/H3 headings on key pages (varies). Convert "Title Tag Optimization" to "How Do I Optimize Title Tags for SEO?"
• [ ] Definition-style opening paragraphs — First sentence answers the heading question (varies). "Core Web Vitals are three metrics that measure real-world user experience..."

Nice-to-Have (Do These After the Basics Are Solid)

• [ ] llms-full.txt with detailed documentation (1-2 hours). Extended version for developers and AI systems.
• ] SoftwareApplication schema on product pages (30 minutes). Include name, description, applicationCategory, operatingSystem, pricing, review. See our [schema markup guide for examples.
• ] Content structure overhaul — Convert paragraphs to lists (varies). Add question headings, definition-style openings, numbered lists, tables. See our [content optimization guide for detailed instructions.
• [ ] Reddit engagement — Genuine answers in relevant subreddits (ongoing). 3-4 posts per week, 200-500 words each.
• [ ] GitHub repository if developer tool (varies). README, docs, examples, issues.
• [ ] Product Hunt launch (one-time). Prepare assets, schedule for Tuesday-Thursday, engage in comments.
• [ ] Technical articles on DEV.to/Medium (ongoing). 2-4 articles per month, genuine expertise, not promotional.
• ] BreadcrumbList schema for navigation (30 minutes). Helps AI understand site structure. See our [schema markup guide for implementation.

Verification

• [ ] Test llms.txt: curl -I https://yoursite.com/llms.txt
• ] Validate structured data: [Google Rich Results Test
• [ ] Test in Perplexity: "best [category] tools" (check citations)
• [ ] Test in ChatGPT: "What is [your product]?"
• [ ] Test in Claude: Same questions
• [ ] Test in Gemini: Same questions
• [ ] Track results monthly — write down what AI says about you

Monthly Tracking Template

Create a simple spreadsheet with:

• Date
• Query tested
• Platform (Perplexity, ChatGPT, Claude, Gemini)
• Result (cited, not cited, position)
• Notes (what changed since last test)

This gives you longitudinal data to track progress and identify patterns.

Where This Is Heading (2026-2027)

These are predictions, not facts. Take them with appropriate skepticism.

1. GEO Will Become Standard Practice

Right now, GEO is a competitive advantage. Within 12-18 months, it will be table stakes. The sites that implement GEO now will have a compounding advantage. Think of it like mobile-first indexing in 2015 — early adopters benefited, but eventually everyone had to adapt.

2. AI Search Will Grow, But Google Won't Die

AI chatbots will take significant share for research queries. But Google will remain dominant for navigational queries ("go to Amazon") and local searches ("restaurants near me"). The smart play is optimizing for both. Most GEO tactics also improve traditional SEO — it's not an either/or choice.

3. llms.txt Will Either Take Off or Die

llms.txt is at an inflection point. If major AI systems start actively using it, it becomes essential. If they don't, it fades. Implement now — cost is low (15 minutes), potential upside is high. The standard is gaining traction — llmstxt.org has growing adoption.

4. AI Will Get Better at Evaluating Quality

Right now, AI systems often cite whatever has the best structure. As they improve, they'll get better at evaluating actual content quality. Sites with genuine expertise will beat sites with SEO-optimized filler. This means: invest in real content, not just structured content.

5. The GEO Tool Category Will Emerge

Just as SEO tools emerged in the 2010s, GEO tools will emerge in 2026-2027. We'll see platforms for tracking AI visibility and optimizing for AI extraction. AuditMe is already moving in this direction with its AI visibility checks.

6. Multi-Modal AI Changes Everything

When AI systems can process images, videos, and audio alongside text, GEO will expand to include visual and video optimization. Sites with well-structured multimedia content will have an advantage. Start thinking about image alt text, video transcripts, and structured data for media now.

FAQ

What is GEO?

GEO (Generative Engine Optimization) is the practice of optimizing your website so AI-powered answer engines like ChatGPT, Claude, Perplexity, and Gemini cite it when users ask questions. It's complementary to traditional SEO — you don't replace SEO with GEO, you add GEO on top of it.

How is GEO different from SEO?

Traditional SEO targets search engine result pages (10 blue links). GEO targets AI-generated answers. The two overlap — good SEO helps GEO — but GEO has its own signals: llms.txt, structured data, content structure, and external authority signals. The biggest difference: GEO is about being cited in AI answers, not ranking in search results.

How long does it take for AI to start citing my site?

It depends on the system. Perplexity can pick up changes within days (fastest). ChatGPT takes 2-3 weeks. Claude and Gemini are slower (3-4 weeks). RAG-based systems are faster than training-based systems. The key insight: RAG systems can pick up changes in days, but training-based updates take months.

Is GEO worth the effort?

If you're in a niche where AI chatbots are recommending products — yes. If people still primarily use Google — traditional SEO might be more impactful. The best approach is doing both. GEO tactics also improve traditional SEO, so it's not wasted effort even if AI search doesn't take off as fast as predicted.

What's the single most impactful GEO tactic?

From testing: FAQPage schema combined with structured content that answers questions directly. This gave the most consistent results across all AI systems. The combination of structured data + content structure creates a "double signal" that AI systems respond to.

Can I track if AI is citing my site?

Yes, with difficulty. Perplexity shows citations directly (easiest to track). ChatGPT shows some in the paid tier. For Claude and Gemini, ask directly and check. The best approach: ask AI chatbots about your product monthly and track results in a spreadsheet. Use the monthly tracking template in the checklist section.

How do I start from zero?

1. Add User-agent: * Allow: / to robots.txt (5 min)

2. Create llms.txt at site root (15 min)

3. Add FAQPage schema to your homepage (1-2 hours)

4. Restructure your best content with question headings and lists (varies)

5. Start engaging genuinely on Reddit (ongoing)

6. Test monthly in Perplexity, ChatGPT, Claude, and Gemini

The order matters: robots.txt + llms.txt first (5 minutes total), then FAQPage schema (1-2 hours), then content structure (varies), then external signals (ongoing).

What if my competitors haven't implemented GEO?

You have a huge advantage. In less competitive niches, GEO tactics can make a real difference. Focus on structured content, FAQPage schema, and llms.txt. If your competitors are already doing GEO, you need to combine technical GEO with external signals (Reddit, GitHub, Product Hunt) to compete.

Does GEO work for local businesses?

It depends. If people ask ChatGPT "what's the best coffee shop in city]?" — yes, GEO matters. But most local searches still go through Google Maps and Yelp. Focus on Google Business Profile + traditional [local SEO first, then add GEO as a secondary channel.

Summary

The GEO playbook is straightforward but not magic:

1. Open robots.txt — Let AI crawlers access your content (5 minutes)

2. Add FAQPage schema — The most impactful structured data (1-2 hours)

3. Create llms.txt — Quick win, no downside (15 minutes)

4. Structure content for AI extraction — Question headings, lists, definition-style openings (varies)

5. Build external signals — Reddit, GitHub, Product Hunt (genuine engagement, ongoing)

These tactics increase your chances of being cited by AI chatbots. There are no guarantees — especially in competitive niches where domain authority dominates. But if you're doing nothing right now, you're leaving opportunities on the table. In less competitive niches, these tactics can give you a significant advantage over competitors who haven't implemented them yet.

What was learned from 47 tests:

• FAQPage schema had the biggest measurable impact (2-3x more citations)
• Content structure mattered more than expected (AI extracts lists better than paragraphs)
• External signals (Reddit, GitHub) correlated with citations in consumer/developer niches
• Perplexity was the most transparent and easiest to test
• The effect is real but modest — no single tactic transformed results overnight

The landscape is shifting. AI search is growing. The sites that adapt now will benefit the most as this trend accelerates. Start with the 5-step playbook, test monthly, and iterate based on what you observe.

Related Resources

• AI Readiness Checker — Check if your site is ready for AI search engines
• GEO Visibility Guide — How to get cited by AI search engines
• Complete SEO Audit Guide — Full technical SEO checklist
• Content Optimization Guide — Write content that ranks and gets cited
• How AI is Changing SEO — The bigger picture of AI in search
• Schema Markup Guide — Structured data that helps AI understand your content
• How to Improve SEO Score — Practical SEO improvements
• Technical SEO Fundamentals — Core technical SEO checklist
• Core Web Vitals Explained — Understanding page experience metrics
• Local SEO Guide — Optimize for local search
• SEO for SaaS — SEO strategies for SaaS businesses
• Free SEO Audit Tools Comparison — Compare top SEO audit tools