AI Site Grade
kabam.com — AI Site Grade
Kabam.com's entire domain is invisible to AI crawlers due to a client-side React shell with no server-side rendering, delivering zero readable text on every page.
Kabam.com's React SPA architecture renders all pages as empty JavaScript shells, making the site completely invisible to AI crawlers and search engines.
- Findings
- 10
- Evidence checks
- 44
- Completed
- 30 May 2026
Analysis
Kabam.com — AI-Visibility Audit
The entire kabam.com domain — every page — returns zero words of visible HTML text to any HTTP client, including every major AI crawler, because the site is a React single-page application with no server-side rendering and no static fallback.
Crawler Access
All AI bots (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, OAI-SearchBot, ChatGPT-User, Applebot-Extended, anthropic-ai) receive HTTP 200 responses from nginx on WP Engine, with identical byte sizes (~18–19 KB). The robots.txt contains no AI-bot-specific rules — only a blanket Disallow: /wp-admin/ and a Crawl-delay: 10. No llms.txt exists (404). ClaudeBot hit a 429 Too Many Requests on one fetch, suggesting rate-limiting is applied inconsistently. The site has an anthropic-domain-verification TXT record, indicating Kabam has engaged with Anthropic for some purpose, yet ClaudeBot still gets throttled.
JS-Rendering Shell
The WordPress theme (identified in style.css as "A basic theme using the WordPress REST API and React") delivers a <div id="root">-style shell. The <title> is always "Kabam | The best in mobile gaming" regardless of the page. The <body> contains no headings, no paragraphs, no visible text — only <script> tags loading /wp-content/themes/kabam/dist/ JavaScript bundles. Every page, from the homepage to about/ to games/marvel-contest-of-champions/, is invisible to any crawler that does not execute JavaScript. Googlebot may render some pages via its Web Rendering Service, but GPTBot, ClaudeBot, PerplexityBot, and other AI crawlers do not execute JS and see nothing.
Schema Posture
JSON-LD is present but structurally broken. The @type field on the WebPage and richSnippet entries is an empty string ("@type": "") rather than a valid schema type like WebPage or Article. The Organization block correctly uses EntertainmentBusiness and Organization, but the WebPage and BlogPosting blocks have missing or malformed @type values. The openingHours field on Organization is set to "Monday-Sunday 09:00-17:00" — an odd value for a game developer. No FAQPage, Product, MobileApplication, or VideoGame schema exists anywhere on the site, despite Kabam being a game publisher with multiple titles.
Cold-Knowledge Gap
The LLM prior knows Kabam as a Vancouver-based mobile game developer (founded 2006, acquired by NetEase in 2017) known for *Marvel Contest of Champions*, *Transformers: Forged to Fight*, and earlier browser games. It mentions 2023-2024 layoffs and aggressive monetization. The actual site, however, positions Kabam as "the best in mobile gaming" with a portfolio including *Marvel Contest of Champions*, *King Arthur: Legends Rise*, *Shop Titans*, and a new publishing deal for *Rewilders: The Lost Spring* (announced March 2026). The site says nothing about the NetEase acquisition, the layoffs, or the closure of *Disney Mirrorverse* — all facts the LLM knows but the site omits. The site also lists *Transformers: Forged to Fight* as returning on Netflix, but the LLM prior treats it as an older title.
External Signals
DuckDuckGo returned zero search results for any query about Kabam — no indexed pages, no news results, no external mentions. This is anomalous and suggests either a search-blocking directive (the max-snippet:-1, max-video-preview:-1 meta values are aggressive) or a broader indexing failure tied to the JS-rendered architecture. The Wayback Machine has snapshots from December 2024 and May 2026, but both capture the same empty JS shell — the site has been non-indexable for at least 18 months.
Findings
Entire site rendered as empty JavaScript shell with no server-side rendering High
Every page on kabam.com returns zero visible HTML text because the site is a React single-page application with no server-side rendering or static fallback. The <body> contains only <script> tags, no headings or paragraphs.
What to change: Implement server-side rendering (SSR) or static site generation (SSG) for all pages so that HTML content is delivered to crawlers without requiring JavaScript execution.
JSON-LD schema has empty @type fields on WebPage and BlogPosting blocks High
The JSON-LD structured data on the site contains malformed entries where the @type field is an empty string instead of a valid schema type like WebPage or Article. The Organization block is correct but the WebPage and BlogPosting blocks are broken.
What to change: Fix the JSON-LD to use valid @type values (e.g., WebPage, Article) for all schema blocks. Validate with Google's Rich Results Test.
ClaudeBot receives 429 Too Many Requests while other AI bots get 200 High
ClaudeBot is rate-limited with a 429 status on the homepage, while GPTBot, Google-Extended, and PerplexityBot all receive 200 responses. This inconsistency blocks ClaudeBot from accessing the site.
What to change: Remove rate-limiting for ClaudeBot or ensure consistent access for all AI crawlers. The anthropic-domain-verification TXT record suggests a relationship with Anthropic, making this block counterproductive.
No llms.txt file available for AI crawlers Medium
The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated summary of the site's content and structure.
What to change: Create an llms.txt file that lists key pages and provides a brief overview of the company and its games.
Zero pages indexed in DuckDuckGo search results High
Multiple search queries for kabam.com and related terms returned zero results on DuckDuckGo, indicating a severe indexing failure likely caused by the JS-rendered architecture and aggressive meta directives.
What to change: Implement SSR/SSG to make content indexable. Review meta robots directives and ensure no noindex tags are present on important pages.
No MobileApplication or VideoGame schema for game titles Medium
Despite being a game publisher with multiple titles like Marvel Contest of Champions and King Arthur: Legends Rise, the site does not include any MobileApplication or VideoGame structured data on game pages.
What to change: Add MobileApplication or VideoGame schema to each game page with properties like name, description, applicationCategory, and operatingSystem.
Organization schema lists openingHours for a game developer Low
The Organization schema includes an openingHours field set to 'Monday-Sunday 09:00-17:00', which is irrelevant for a game developer and may confuse parsers.
What to change: Remove the openingHours field from the Organization schema or replace it with more relevant properties like sameAs links to social profiles.
Robots.txt has no AI-bot-specific directives Low
The robots.txt file only contains a blanket Disallow for /wp-admin/ and a Crawl-delay of 10. No AI crawlers are explicitly allowed or disallowed, leaving access to default behavior.
What to change: Add explicit rules for AI crawlers (e.g., allow all) to ensure they are not inadvertently blocked by future changes.
All pages share the same <title> tag Medium
Every page on the site has the same <title> 'Kabam | The best in mobile gaming', which prevents crawlers from distinguishing between pages and harms SEO.
What to change: Generate unique, descriptive <title> tags for each page using server-side logic.
No FAQPage schema on news or support pages Low
The site does not use FAQPage schema anywhere, missing an opportunity to appear in rich results for common questions about games or the company.
What to change: Add FAQPage schema to pages that answer common questions, such as game FAQs or company information.
What's working
- All major AI bots receive HTTP 200 responses — GPTBot, Google-Extended, PerplexityBot, and others receive 200 status codes from the server, indicating no blanket blocking of AI crawlers.
- Organization schema uses correct types and properties — The Organization JSON-LD block correctly uses EntertainmentBusiness and Organization types with valid properties like name, url, and logo.
- Sitemap index file exists with 80 URLs — The sitemap at /sitemap_index.xml is accessible and lists 80 URLs, providing crawlers with a roadmap of the site's pages.
- Anthropic domain verification TXT record present — The DNS TXT records include an anthropic-domain-verification entry, indicating Kabam has engaged with Anthropic for some purpose, which could facilitate future AI visibility improvements.
- Robots.txt does not block any AI crawlers — The robots.txt file contains no Disallow rules for AI bots, meaning they are technically allowed to crawl the entire site (except /wp-admin/).
Track kabam.com across AI search
This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.