There is a saying in business that resonates deeply with anyone building developer tools: the cobbler's children have no shoes. AuraCite is a Generative Engine Optimization (GEO) platform that helps brands track and improve how AI engines perceive, mention, and cite them. But when we launched in early 2026, we faced an uncomfortable truth: no AI engine knew who we were.
We were selling AI visibility tracking to brands while still needing a stronger public entity foundation ourselves. This is the story of how we used our own product and public-channel work to measure that gap, what we learned along the way, and the actionable framework you can apply to your own brand today.
1. The Challenge: Starting from Zero
Generative Engine Optimization is a new discipline. The term itself became widely adopted only in late 2025, following research from Princeton, Georgia Tech, and the Allen Institute that demonstrated how AI-generated answers were reshaping user behavior. Traditional search engines still process billions of queries daily, but a growing segment of users now turn to ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews as their primary discovery tools. When someone asks an AI engine "What is the best tool for tracking AI brand visibility?" the answer it generates determines which products get discovered — and which remain invisible.
AuraCite launched into this emerging category with strong technology but no brand presence. We had built a platform that monitors brand mentions across configured AI engines, calculates visibility scores, tracks citations, and provides actionable recommendations. The engineering was solid. The product worked. But when we asked ChatGPT, Perplexity, or Claude about GEO tools — silence. AuraCite did not appear in any AI-generated answer.
This was not surprising. AI language models are trained on web data, and they build their "knowledge" from content that exists across the internet — documentation, articles, forum discussions, social media mentions, product directories, and review sites. A brand that has no presence across these surfaces simply does not exist in the model's world. Having a great product is necessary but insufficient. If no indexable content describes your product in a way AI engines can extract and cite, you are invisible.
The irony was motivating. We had built the tools to measure exactly this problem. Now we needed to use the same workflow on our own brand. The question was practical: could AuraCite turn a weak public entity footprint into a measurable AI visibility program, and which actions would produce repeatable signals?
We set up AuraCite to track itself. We configured monitoring for key queries that our potential customers would ask AI engines — queries like "best GEO tools," "AI visibility tracking platform," "generative engine optimization software," and "how to monitor brand mentions in ChatGPT." We established a weekly measurement cadence, and we documented everything. This case study is the result.
2. The Approach: Technical Optimizations and Content Strategy
Our approach combined two parallel tracks: technical infrastructure that makes it easy for AI engines to discover, understand, and extract information about AuraCite, and content strategy that creates the informational surface area AI engines need to form opinions about a brand. Both are necessary. Technical optimization without content gives AI engines nothing to cite. Content without technical optimization makes it harder for AI engines to find and parse what you have published.
2.1 Schema.org JSON-LD Across All Pages
Structured data is not new to traditional SEO, but its role in GEO is fundamentally different. In traditional SEO, Schema.org markup helps search engines generate rich snippets — star ratings, FAQ dropdowns, recipe cards. In GEO, structured data helps AI engines understand the entity relationships and factual claims on a page. When an AI engine encounters a page with proper Organization, SoftwareApplication, and Product schema, it can extract machine-readable facts: what the product does, who built it, what it costs, what features it offers. This reduces the ambiguity that language models otherwise have to resolve through inference.
We implemented comprehensive JSON-LD schema across every public-facing page. Our landing page carries Organization and SoftwareApplication types with detailed feature lists, pricing information in EUR, and provider metadata. Every blog article uses Article schema with author information, word count, publication date, and topic keywords. Our comparison pages use structured data to describe alternative products and their relationship to AuraCite. Our FAQ sections are marked up with FAQPage schema so the question-answer pairs are machine-parseable. This was not a small effort — implementing structured data correctly across dozens of pages required careful attention to the Schema.org specification and validation against Google's Rich Results Test.
2.2 AI Crawler Discovery: llms.txt and robots.txt
The llms.txt file is a relatively new convention that provides a structured manifest of your website's content specifically for AI crawlers. Think of it as a human-readable sitemap that tells AI engines: here is what this site contains, organized by topic, with descriptions of each page and direct links. While there is no guarantee that every AI engine reads llms.txt, the convention is gaining adoption and represents a low-effort, high-potential-upside optimization.
Our llms.txt includes every public page with a one-sentence description: tools, guides, comparison articles, pricing, blog posts, and author information. We update it every time we publish new content, ensuring AI engines always have a current index of everything available on our site.
Equally important is the robots.txt file. Many websites inadvertently block AI crawlers. We explicitly allow GPTBot, ClaudeBot, PerplexityBot, GoogleOther, and other AI-specific user agents in our robots.txt. This is a simple configuration change that many brands overlook — if your robots.txt blocks AI crawlers, your content is invisible to them regardless of how good it is.
2.3 Island Test-Compliant Content
The Island Test is a content quality principle specific to GEO. It asks: can any single paragraph on your page stand on its own as a complete, useful answer to a question? AI engines do not read entire articles the way humans do. They extract individual passages — sometimes a single sentence, sometimes a paragraph — and present those passages as answers to user queries. If your paragraphs rely on context from surrounding text to make sense, AI engines cannot effectively use them.
We rewrote significant portions of our content to pass the Island Test. Every paragraph on our product pages, guides, and blog posts is self-contained. Each one states a complete fact, explains a concept fully, or provides an actionable recommendation — without requiring the reader to have read anything above or below it. This was the most labor-intensive optimization we undertook, but it directly determines whether AI engines can cite your content effectively.
2.4 E-E-A-T and Author Credibility
Google's E-E-A-T framework — Experience, Expertise, Authoritativeness, Trustworthiness — has become a core quality signal for AI engines beyond Google. Content attributed to credible, identifiable authors with demonstrated expertise ranks higher in AI-generated recommendations than anonymous or thinly attributed content. We created a detailed author page for our founder with professional background, LinkedIn profile links, and topic expertise areas. Every article is explicitly attributed to a named author with a link to their profile.
2.5 Comprehensive Content Pillars
Thin content does not perform in GEO. AI engines favor comprehensive, in-depth resources over brief listicles or surface-level overviews. Our primary content pillar is a 5,800+ word definitive guide to Generative Engine Optimization that covers the concept, methodology, tools, and implementation strategies in exhaustive detail. This single piece of content serves as the anchor for our entire GEO strategy — it targets the highest-value queries and provides the depth that AI engines associate with authoritative sources.
Around this pillar, we built supporting content: detailed tool comparisons against established competitors, a GEO vs. SEO guide that addresses the most common confusion point for newcomers, multilingual content in German and Arabic to reach non-English audiences, and technical articles on our MCP integration that target the developer community specifically. Each piece of content is substantial — typically 1,800 to 3,000 words — and optimized for the Island Test.
2.6 Community and Social Signals
AI engines can consider the breadth of a brand's presence across the web, not just its own website. Product directories, social profiles, developer repositories, community discussions, videos, and credible third-party mentions can all contribute to the signal surface that AI engines use to assess brand legitimacy and category relevance. AuraCite only claims and maintains channels when the profile is legally clean, useful, and relevant; we avoid spam-style seeding and unsupported directory sprawl.
2.7 MCP Integration as a Differentiator
AuraCite uses MCP-ready workflow support for authorized integrations as a technical positioning theme. MCP is a relevant topic in the AI developer community, and our technical content about GEO-focused MCP-ready workflows can support attention and backlinks in developer circles when the claims stay tied to released capabilities. This technical content performs well because it sits at the intersection of two high-interest topics: AI analytics and AI development infrastructure.
3. The Measurement: Tracking Ourselves with Our Own Tool
Using AuraCite to track AuraCite gave us an unusual advantage: we experienced our own product exactly as our customers do. Every friction point, every insight gap, every moment of delight — we felt it firsthand. This meta-measurement approach generated product improvements alongside the GEO data we were collecting.
Queries We Monitored
We configured AuraCite to track a set of high-value queries that represent the searches our potential customers would perform. These included category-level queries like "best GEO tools 2026" and "generative engine optimization platform," problem-aware queries like "how to track AI brand mentions" and "AI visibility monitoring tool," and brand-adjacent queries like "AI SEO analytics" and "ChatGPT brand monitoring." Each query was tracked across all configured AI engines in our monitoring network.
AI Engines Tracked
| AI Engine | Type | Crawl Behavior |
|---|---|---|
| ChatGPT (GPT-4o) | Conversational AI | GPTBot active crawler + browsing |
| Claude (Anthropic) | Conversational AI | ClaudeBot crawler + knowledge cutoff |
| Perplexity | AI search engine | Real-time web search + synthesis |
| Gemini (Google) | Conversational AI | Google index + AI Overviews |
| Bing Copilot | AI-assisted search | Bing index + GPT-4 synthesis |
| SearchGPT | AI search | Web search + citation model |
| You.com | AI search engine | Web search + multi-model synthesis |
Metrics
AuraCite tracks four primary metrics for brand visibility. Brand Strength Score is a composite score (0–100) that reflects how prominently a brand appears across all tracked AI engines and queries. Mention count tracks the raw number of times an AI engine references the brand by name in its responses. Citation count measures how often AI engines link to or cite the brand's own content as a source. Sentiment captures whether the brand is described positively, neutrally, or negatively when mentioned. We measured all four metrics at a weekly cadence, capturing a snapshot every Monday morning.
4. The Results: An Ongoing Journey
Honesty is a core principle of this case study. We are at week four of an eight-week campaign. We are not claiming victory — we are sharing a trajectory. The results are directional, and the journey is ongoing. Here is what we have observed so far.
Week-by-Week Trajectory
Week 1: Technical Foundation (Baseline = Zero)
Deployed Schema.org JSON-LD, llms.txt, updated robots.txt. Published the definitive GEO guide (5,800+ words). Baseline measurement: no AI engine mentioned AuraCite for any tracked query. Brand Strength Score: 0.
Week 2: First Signs of Life
Real-time and search-backed engines were the first places we reviewed for early awareness because they can surface newly published content faster than engines that depend more heavily on periodic training updates. Early citations were treated as directional signals and rechecked before drawing conclusions.
Week 3: Content Momentum Building
Published four additional blog posts and comparison articles. SearchGPT began mentioning AuraCite in response to tool-comparison queries, citing our comparison pages as sources. Community signals from LinkedIn and initial directory listings started creating the multi-source presence that AI engines look for when validating a brand's legitimacy.
Week 4: Measurable Progress (Current)
The monitoring loop moved from anecdotal checks to structured measurement across configured engines. Where mentions appear, we review the exact answer context, cited URLs, competitor set, and whether the same signal repeats. Engines that rely more heavily on training data may reflect public changes more slowly than search-backed systems.
Which Optimizations Showed the Fastest Impact?
Schema.org markup improved the quality of the entity foundation because it gave crawlers and AI systems machine-readable context about AuraCite, the founder, the product category, and individual pages. We treat schema as a discovery and disambiguation layer, not as a guaranteed ranking lever.
The llms.txt file reduced crawler friction by listing public pages in a structured, human-readable format. We cannot prove that every AI engine reads the file, so we use it as a low-friction context manifest rather than as a guaranteed discovery mechanism.
Comprehensive content gives engines more usable context than thin content. In our checks, deeper guides provided clearer passages, definitions, and source material for AI answers than short generic posts. The practical lesson is to prioritize distinct, well-structured resources that can stand alone as sources.
What Got Cited vs. What Didn't
| Content Type | Cited by AI Engines? | Notes |
|---|---|---|
| Definitive GEO guide (5,800 words) | Observed in early checks | Depth, structure, and clear definitions made the page more useful as a source |
| Tool comparisons (2,000+ words) | Observed in early checks | Useful for specific comparison and feature-context prompts |
| MCP integration article (1,800 words) | Observed in early checks | Niche audience; useful when the prompt explicitly touches MCP or developer workflows |
| GEO vs. SEO guide (2,400 words) | Observed in early checks | Useful for explaining the SEO/GEO distinction |
| Short blog posts (<1,200 words) | Not yet | Need more depth or time |
| Product landing page | Not directly | Referenced but not cited as a source |
"We are at the beginning of this journey, and here is what we are seeing so far: clear entity facts, structured data, credible sources, and useful content make AI visibility easier to measure and improve. Sustainable AI visibility is built through repeated checks, not one-off claims."
5. Lessons Learned
What Worked
Comprehensive content can perform better than thin content. In this campaign, our longest, most detailed articles were the first to be cited by AI engines. The 5,800-word GEO guide was cited before any shorter piece. AI engines often look for authoritative sources, and depth can be one signal of authority. If you are choosing between writing five 500-word posts or one 2,500-word comprehensive guide, test the comprehensive guide first.
Schema.org markup creates a cleaner measurement foundation. Implementing proper JSON-LD structured data across public pages improves disambiguation and makes content easier to parse. It is a practical foundation layer, but its impact still has to be checked in live results.
The Island Test is critical for citations. AI engines extract individual passages from pages for use in their answers. If those passages require surrounding context to make sense, the AI engine will skip them in favor of self-contained passages from other sources. Writing Island Test-compliant content — where every paragraph stands alone as a useful answer — directly determines whether your content gets cited or ignored.
Multi-source presence matters more than any single channel. AI engines triangulate brand legitimacy across multiple web sources. Having content on your own site is necessary but not sufficient. Directory listings, social media presence, community participation, and third-party coverage all contribute to the signal surface that helps AI engines decide to recommend a brand.
What Didn't Work
Just having a great product is not enough. Our dashboard, analytics capabilities, and MCP integration are genuinely differentiated in the GEO tools market. None of that mattered for AI visibility. AI engines cannot discover or evaluate a product they have never encountered in their training data or web searches. Product quality is a retention advantage, not a discovery advantage.
Traditional SEO does not translate directly to GEO. Our initial content was optimized for traditional search engines: keyword density, meta descriptions, header tags, internal linking. While these practices are not harmful, they are insufficient for GEO. AI engines weigh different signals: content depth, structured data, citation patterns, author credibility, and entity clarity. Optimizing for Google's top 10 blue links and optimizing for ChatGPT's recommended answer require overlapping but distinct strategies.
Generic content in a new category gets ignored. Our early attempts at short, general-purpose blog posts about AI and marketing generated zero AI engine interest. The content was correct but unremarkable — it said nothing that hundreds of other marketing blogs had not already said. AI engines have access to millions of pages on any given topic. To be cited, you need to say something unique, with original data or a distinctive perspective.
What Surprised Us
The speed difference between AI engines matters. Search-backed or real-time systems can reflect newly published pages faster than systems that rely more heavily on periodic training updates. Your GEO strategy should account for different engine timelines and verify changes through repeated measurement.
Structured data mattered more than we expected. We implemented Schema.org primarily as a best practice, without strong expectations about its impact. The results surprised us. Pages with comprehensive JSON-LD schema were discovered and cited faster than pages with identical content quality but no structured data. The machine-readable context that schema provides appears to reduce the friction for AI engines to extract and use information from a page.
Author credibility is an important trust signal. Content attributed to identifiable authors with relevant experience is easier for readers, crawlers, and AI systems to evaluate than anonymous or thinly attributed content. Creating a detailed author page helps connect expertise, brand, and topic coverage.
6. Your 8-Step GEO Framework
Based on everything we learned tracking our own AI visibility, here is the actionable framework you can apply to your brand today. These steps are ordered by implementation priority — start at the top and work down.
Implement Schema.org JSON-LD
Add comprehensive structured data to every public-facing page. Use Organization, Product, SoftwareApplication, Article, FAQPage, and HowTo types as appropriate. Validate with Google's Rich Results Test and treat schema as a practical disambiguation layer for AI discoverability.
Create llms.txt and Configure robots.txt
Publish an llms.txt file at your site root that lists all public pages with descriptions. Ensure your robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, and other AI-specific crawlers. These are low-effort changes that remove friction from AI content discovery.
Write Island Test-Compliant Content
Review every paragraph on your key pages. Each paragraph should make sense independently — a complete fact, concept, or recommendation that does not require surrounding context. AI engines extract passages individually; if yours need context, they will not be cited.
Build Comprehensive Pillar Content (2,000+ Words)
Create at least one definitive resource on your core topic. Aim for 2,000 words minimum — our best-performing content was 5,800 words. Cover the topic exhaustively with original insights, practical examples, and structured sections. Depth signals authority to AI engines.
Establish Author Credibility (E-E-A-T)
Create detailed author pages with professional background, expertise areas, and social profile links. Attribute all content to named authors. AI engines increasingly favor content from identifiable experts over anonymous or brand-only attribution.
Monitor Across Multiple AI Engines
Do not optimize for a single engine. Track your brand across ChatGPT, Perplexity, Claude, Gemini, Bing Copilot, and other engines simultaneously. Each engine has different behaviors, update cadences, and content preferences. What works on Perplexity may not work on ChatGPT.
Iterate Based on Data
GEO is not a one-time optimization — it is an ongoing process. Measure weekly, identify which content is getting cited, double down on what works, and revise what does not. Use the data to inform your content calendar, not assumptions.
Diversify Content Formats and Channels
Claim and maintain the channels that make sense for your company: your own website, public profiles, developer repositories, selective industry publications, product directories, and social platforms. AI engines assess brand legitimacy across the web, but low-quality seeding can damage trust.
Want a practical starting point? AuraCite's free AI Readiness Mini-Audit gives you a zero-provider-cost website readiness score, evidence, test prompts and starter snippets without signup. For DACH teams comparing tools, see the German GEO tool comparison for ChatGPT visibility.
What's Next
This case study covers the early phase of AuraCite's own AI visibility program. We will publish follow-up results when the data is sufficiently verified and useful for readers. The next phase focuses on entity consistency, proof assets, public education, selective distribution, and repeatable measurement.
The next public proof asset is the AI Visibility Audit Sample + B2B AI Visibility Mini Index, a cautious sample report showing how AuraCite evaluates AI-answer mentions, official-domain citations, Google AI Overview presence, and source gaps across a public B2B software sample set.
The core lesson from these first checks is clear: AI visibility is measurable and improvable, but it takes deliberate strategy and consistent execution. There are no shortcuts. A brand needs clear entity facts, credible sources, structured public pages, and a measurement loop that shows whether the work is actually changing AI answers.
We built AuraCite because we believe every brand deserves to understand how AI systems describe it. Tracking our own visibility keeps the product grounded in the same problem our customers face.
Ready to start tracking your AI visibility? Try the free AI Brand Check →