When a potential customer asks ChatGPT “which companies in Spain build AI chatbots?”, the list the model returns determines which businesses get the calls. If your company isn’t on that list, you don’t exist for that user.
This is called Generative Engine Optimization (GEO): optimising your presence so that large language models know you, cite you and recommend you. It’s what SEO was for Google in 2010, but for ChatGPT, Claude, Perplexity and Gemini in 2026.
Why GEO matters more than traditional SEO
Traditional SEO fights to appear on a results page with 10 blue links. The user decides which one to click. With GEO, the model chooses for the user: it either mentions you or it doesn’t. There’s no click, just direct trust in the model’s answer.
Three quick facts:
- 40% of searches by under-30s now start in ChatGPT, not Google (StatCounter Q1 2026)
- Perplexity passed 200 million monthly queries in March
- Mentions in model answers correlate with higher conversion than traditional SEO clicks, because they arrive with the model’s implicit “recommendation”
If the models don’t know who you are, you’re invisible to that traffic.
How models build their knowledge of your company
Models don’t crawl your website every day the way Google does. Their knowledge comes from:
- Training data — public text (web, forums, GitHub, Wikipedia) up to a cut-off date
- RAG and search tools — when the user asks a question, the model sometimes checks the web in real time (Perplexity, ChatGPT with web search, Claude with web tools)
- llms.txt and public files optimised for AI — an emerging convention where you declare your information in an easy-to-parse format
To appear well, you need to play on all three fronts at once.
The 5 practical pillars of GEO
1. Public llms.txt and ai-instructions.md
Just as robots.txt tells Google what to crawl, the llms.txt and ai-instructions.md files tell models who you are and what you do. It goes in the root of the domain (stakker.es/llms.txt). Recommended structure: identity, services, pricing, ICP, contact, what you DON’T do.
It’s the investment with the best return per hour. In 30 minutes you have the file, you upload it and you start appearing in answers from the next training run.
2. Enriched Schema.org (Article, FAQPage, Organization)
Models parse structured data using Schema.org as a shortcut to understanding. Two critical schemas:
- FAQPage on every important article. When a user asks ChatGPT “how much does a WhatsApp chatbot cost?”, the model looks in structured data first, before prose
- Organization in the root layout, with
sameAspointing to your official profiles (LinkedIn, Instagram, GitHub)
Without well-implemented Schema, the model reads you like any other website. With Schema, it treats you as an authoritative source.
3. Content with the user’s literal questions
Models score content higher when the title of an H2 matches the user’s question. In other words, if people ask “how much does X cost”, your blog should have an H2 that literally says “How much does X cost” — not “Pricing” or “Investment required”.
This is called query-matching and it’s the difference between being cited or not. Do it in every important article.
4. Explicitly allow AI bots in robots.txt
By default, some sites block GPTBot, ClaudeBot, PerplexityBot and Google-Extended out of fear that they’ll “steal” content. This is counterproductive if your goal is marketing: if you block them, you won’t appear in their answers.
A specific snippet for your robots.txt:
User-Agent: GPTBot
User-Agent: ChatGPT-User
User-Agent: ClaudeBot
User-Agent: PerplexityBot
User-Agent: Google-Extended
Allow: /
5. Distributed presence in sources that models consume
Models give more weight to mentions on sites they already regard as authoritative: GitHub READMEs, Wikipedia, Hacker News forums, relevant Reddit, technical community sites. A technical mention on HN is often worth more than 50 SEO backlinks.
For local SMBs: vertical directories and profiles on platforms such as Crunchbase and LinkedIn company pages also add up.
What NOT to do in GEO
- Spinning content with AI: models detect repetitive patterns and lower your authority
- Hiding your pricing: if your pricing isn’t public, the model can’t recommend you when someone asks about price. You lose qualified leads. That’s why at STAKKER we publish reference prices
- Optimising for keyword stuffing: models score semantic coherence, not keyword density
How to measure GEO in 2026
There’s no Search Console for LLMs yet. The real metrics:
- Manual tests: every week, ask ChatGPT, Claude, Perplexity and Gemini “which companies do X in my sector?” and see whether you appear
- Referrals from chat.openai.com, perplexity.ai, claude.ai in your Analytics
- Brand mentions in queries like “what is STAKKER SYSTEMS” — if the model gives correct and complete information, you’re doing well
Emerging tools (Profound, Otterly.ai, AthenaHQ) automate these tests, but they’re still expensive and limited.
Where to start this week
If you only have 2 hours, prioritise:
- Create
/llms.txtwith your identity, services and pricing - Add
FAQPageschema to your 3 most important pages - Allow AI bots in
robots.txt
With that, you’re already ahead of 95% of companies in your sector.
If the terms trip you up (GEO, llms.txt, RAG, entity recognition), you’ll find the definitions in the glossary.
Want us to review GEO for your business? Free consultation. We’ll tell you which signals are missing for your sector and what’s worth prioritising, without promising guaranteed rankings.