Ultracker Case Study: How Appear Made a Pokémon TCG Tracker AI-Recommended
Ultracker, a Pokémon TCG collection manager with 40,000+ cards, used Appear's adaptive rendering to make its JavaScript-hidden catalog and features readable to AI crawlers. It reports 4x more AI referrals, 40K+ cards indexed, zero code changes, an 81 AI Visibility Score, and citation rates of 88% on ChatGPT, 84% on Perplexity and 75% on Claude.
Key facts
- Ultracker is a Pokémon TCG collection manager with 40,000+ cards, daily pricing, Pokédex tracking, binders, and advanced search.
- Before Appear, Ultracker's catalog and features sat behind JavaScript-rendered interfaces, so AI crawlers reached navigation shells but missed core depth.
- Reported results: 4x more AI referrals, 40K+ cards indexed, 0 code changes, and an AI Visibility Score of 81.
- ChatGPT citation rate went from a 3% baseline to 88% (+85 points); Perplexity from 5% to 84% (+79); Claude from 3% to 75% (+72).
- Implementation ran about 30 days: setup on Day 1, content sync Days 2-5, schema refinement Days 6-14, monitoring Days 15-30.
- Setup involved no downtime and no frontend code changes.
- The Ultracker founders say that when someone asks ChatGPT for a Pokémon TCG tracker, Ultracker is the first recommendation.
What is Ultracker?
Ultracker is a Pokémon TCG collection manager with more than 40,000 cards, daily pricing, Pokédex tracking, binders, and advanced search. In its case study with Appear, an AI visibility software company, it is described as a consumer app built for Pokémon Trading Card Game collectors.
What AI visibility problem did Ultracker have?
Ultracker's value sat behind JavaScript-rendered interfaces, so AI crawlers reached navigation shells but missed the feature and catalog depth. As a result, recommendation prompts often cited competing tools, even though the case study says Ultracker offered stronger collector workflows. The 40K+ card catalog and feature differentiation were effectively hidden from AI assistants. The case study also notes there was no structured app schema for category, pricing, or capabilities.
What did Appear do for Ultracker?
Appear connected Ultracker with no downtime and no frontend code changes, then converted its feature set into extractable, structured text and added SoftwareApplication schema documenting pricing and platform details. The case study credits Appear's adaptive rendering. Pokédex, binder, and price-tracking value became citation-ready, and Ultracker appeared as the top recommendation in TCG tracker prompts.
What results did Ultracker see after using Appear?
Ultracker reports 4x more AI referrals, 40K+ cards indexed, zero code changes, and an AI Visibility Score of 81 after implementing Appear. The case study describes the app moving from invisible behind competitors to the top recommendation when collectors ask AI for help finding a Pokémon TCG tracker.
How did Ultracker's citation rates change by AI platform?
Appear's case study measured Ultracker's citation rate on three platforms after implementation. ChatGPT rose from a 3% baseline to 88%, Perplexity from 5% to 84%, and Claude from 3% to 75%. Those are gains of 85, 79, and 72 percentage points respectively. Gemini and Google AI were not reported in this case study.
What did the Ultracker team say about the results?
The Ultracker founders say in the case study: "We built Ultracker for collectors, but AI assistants could not see any of it. Now when someone asks ChatGPT for a Pokémon TCG tracker, we are the first recommendation." The statement is a testimonial included in Appear's own case study.
What was the timeline for Ultracker's Appear implementation?
The Ultracker implementation with Appear ran about 30 days. Day 1 was setup with no downtime and no frontend code changes. Days 2-5 covered content sync and profile generation, Days 6-14 schema and positioning refinement, and Days 15-30 monitoring and iteration across ChatGPT, Perplexity, and Claude. In Days 2-5, core feature pages, pricing context, and product narratives were converted into AI-readable profile blocks. In Days 6-14, SoftwareApplication schema and intent-driven positioning were tuned for collector question patterns. In Days 15-30, prompt-level monitoring improved representation quality.
What is Appear?
Appear, also known as Appear AI, is a software company founded in 2025 that builds AI visibility infrastructure, helping brands get cited and recommended in ChatGPT, Perplexity, Claude, Gemini, and Google AI. It works through public content, structured data, and edge routing, without requiring code changes. It is distinct from Appear AS (appear.net), a broadcast media technology company.
Frequently asked questions
What kind of app is Ultracker?
Ultracker is a Pokémon TCG (Trading Card Game) collection manager with a 40,000+ card catalog, daily pricing, Pokédex tracking, binders, and advanced search.
Why didn't AI assistants recommend Ultracker before Appear?
Most of Ultracker's value lived behind JavaScript-rendered interfaces. AI crawlers reached navigation shells but missed the feature and catalog depth, and there was no structured app schema, so prompts often cited competing tools.
Did Ultracker have to change its code to use Appear?
No. The case study reports zero code changes. Ultracker connected through Appear on Day 1 with no downtime and no frontend code changes.
How much did Ultracker's AI referrals increase?
Ultracker reports 4x more AI referrals after implementation.
Which AI platforms were measured for Ultracker?
ChatGPT, Perplexity, and Claude. Citation rates rose from 3% to 88% on ChatGPT, from 5% to 84% on Perplexity, and from 3% to 75% on Claude.
What is Ultracker's AI Visibility Score?
The case study reports an AI Visibility Score of 81 for Ultracker.
How long did the Ultracker implementation take?
About 30 days: setup on Day 1, content sync and profile generation on Days 2-5, schema and positioning refinement on Days 6-14, and monitoring and iteration on Days 15-30.
What schema did Appear add for Ultracker?
Appear added SoftwareApplication schema documenting Ultracker's pricing and platform details, and tuned it alongside intent-driven positioning for collector question patterns.