Generative Engine Optimization (GEO) means preparing content in such a way that AI systems like ChatGPT, Perplexity, or Google’s AI Mode use it as a source and cite it. The building blocks for this are no secret: clear answers, verifiable figures, structured data—and crawlers that are allowed to access the store.
At a Glance: The 5 GEO Building Blocks
- Question-based headings based on real user queries—the answer is in the first sentence.
- FAQ blocks and fact boxes with specific numbers and source citations.
- Structured data: Product, FAQPage, Organization, and Article with author.
- Crawler accessibility: Carefully configure robots.txt, bot blockers, and WAF rules.
- Consistent facts: Company name, location, product range, and USPs must be identical on all pages.
What is GEO—and how does it differ from SEO?
GEO complements traditional search engine optimization with a new goal: Instead of just ranking in a list of search results, the online store should be cited as a source and linked to in AI-generated answers. The fundamentals overlap significantly—clean technical SEO, good content, and structured data benefit both. The difference lies in the focus: AI systems extract answers; they don’t present ten blue links. Therefore, content that answers a question directly, verifiably, and in a machine-readable format is prioritized for citation.
How can I get cited in ChatGPT, Perplexity, and similar platforms?
By ensuring your content provides what an AI needs for a good answer: the direct answer in the first sentence under a question heading, data points with sources, lists and tables instead of continuous text, a recognizable author, and an update date. Equally important are clear company and product facts—name, location, product range—that remain consistent across all pages. Firsthand experience—measurements, product tests, practical knowledge of the product range—is among the factors that increase the likelihood of being cited.
What structured data does an online store need?
Four markup types cover the most important cases—in JSON-LD format—so that search engines and AI systems can unambiguously map the content:
| Markup | What it represents |
|---|---|
| Product | Price, availability, GTIN, reviews—the basis for shopping results and product mentions in AI responses. |
| FAQPage | Machine-readable question-answer pairs—the most quotable content format of all. |
| Organization | Who runs the store: name, location, logo, contact information—feeds company facts into knowledge systems. |
| Article with Author | Guides and news with attributable authorship and dates—a signal of trust and timeliness. |
Consistency is key: the markup, the visible page, and the merchant feed must match—discrepancies erode trust.
Do AI crawlers even reach my store?
This is the most commonly overlooked fundamental: Anyone who blocks AI bots across the board—via robots.txt, bot blockers, or WAF rules in the CDN—will not appear in AI responses. Many stores unknowingly block crawlers like GPTBot, ClaudeBot, or PerplexityBot because they’re caught up in a generic “bad bot” list. It makes sense to make a conscious decision: Allow response and search crawlers, and handle training crawlers separately based on content protection considerations. In addition, the llms.txt file is gaining traction—a file in the root directory that provides AI systems with curated entry points; our own llms.txt in live operation demonstrates what this looks like.
How do I measure whether GEO is effective?
Through two metrics: the frequency of citations in AI responses and referral traffic from AI services. For the former, there are tools like the Sistrix AI Check, which we featured in a separate news article; for the latter, simply check the referrers (chatgpt.com, perplexity.ai, etc.). Important for managing expectations: GEO is a nascent field with limited research (as of August 2026). These measures are among the factors that promote AI visibility—no reputable source can promise guaranteed results. The appeal lies in the fact that almost all GEO components are good SEO practices anyway.
What the XONIC Shop System offers in this regard
The technical GEO building blocks are included as standard in the XONIC Shop System: product pages feature structured product data, including a Google Merchant Feed; news and how-to articles are automatically tagged with NewsArticle JSON-LD and author profiles; and FAQ content is tagged with FAQPage microdata. The AI crawler control (since version 4.8.2) separates visibility from content protection: allow response crawlers, exclude training crawlers via robots.txt. In addition, there is AI knowledge export, which makes curated store content available in a machine-readable format. The feature overview provides an overview; the guide to Google tools describes the Google tools.
Frequently Asked Questions About GEO
Sources
Stephan Dunger
Stephan Dunger is one of the brains behind the XONIC store system. He has been developing the platform together with the team since 2012 - from the database to the interfaces to the checkout.
A passionate programmer, technical mind and consultant at the same time: with his in-depth knowledge of store systems and e-commerce, Stephan combines the depth of a developer with an eye for the big picture. Together with the XONIC team, he shapes the technical direction, consistently thinks about functions from the retailer's perspective and advises on customized solutions.
The result is software with a face: customers don't get an anonymous provider, but a direct line to the people who develop XONIC. Pragmatic, fast and at eye level.
