miniclip.com — AI Site Grade

Analysis

Miniclip serves all AI crawlers the same Nuxt SSR shell — but the homepage and game pages deliver under 30 words of visible text to every bot, while the /llms.txt URL returns the full homepage HTML instead of an AI-friendly content map.

Crawler Access

All 11 tested AI crawler UAs (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider, Perplexity-User) receive a 200 status with identical byte payloads (~143KB) served from AWS CloudFront + AmazonS3. No UA-based blocking exists. The robots.txt is a single line — User-Agent: * Allow: / — with zero AI-bot-specific rules. The /llms.txt path returns the full homepage HTML (143KB), not a structured text file, meaning the site has no AI-friendly content map. The site uses Nuxt SSR (server-side rendering), so AI crawlers receive rendered HTML, not an empty JS shell — but the rendered text is extremely thin.

Content & Schema

The homepage delivers 26 words of visible text ("Play our most popular games now!", "We are Miniclip", acquisition announcements). The /games page delivers 11 words. The /games/8-ball-pool page delivers 106 words but mostly navigation boilerplate. The only pages with substantive text are /our-story (203 words, describing "10 billion downloads" and "400 million monthly players"), /publishing (365 words with DAU and download stats), and the /minigames/ sub-pages which contain 19,000+ words of loot-box probability tables. Every page carries the same minimal WebSite schema — no VideoGame, MobileApplication, Organization, FAQPage, or SoftwareApplication schema exists anywhere. No FAQ, comparison, or structured answer-format signals are present on the main pages.

Cold-Knowledge Gap

The LLM knows Miniclip as a browser-casual-games pioneer founded in 2001, acquired by Tencent in 2015, and famous for 8 Ball Pool, Agar.io, and Subway Surfers. It also recalls criticism over aggressive monetization (in-app purchases). The site itself never mentions the Tencent acquisition anywhere — not on /our-story, not on the homepage. The site positions itself as a mobile-game publisher ("one of the largest mobile publishers in the world") with 10 billion downloads and 70M DAU across its network, but the LLM's prior knowledge is anchored to the browser-gaming era. The site's /our-story page claims 10 billion downloads (the LLM knows "over 4 billion" for Subway Surfers alone), and the /publishing page claims 70 million DAU — data points the cold model does not have.

External Signals

External search returned zero results for Miniclip-related queries — the site has minimal indexed external press coverage accessible via search. The DNS records reveal an anthropic-domain-verification TXT record, confirming the brand has proactively verified its domain with Anthropic for Claude crawler access. Other TXT records show integrations with Atlassian, Dropbox, LucidLink, Miro, OneTrust, SAP SuccessFactors, and Unity — a broad enterprise SaaS stack. The site's content-security-policy headers allow connections to Datadog for analytics. The Wayback Machine shows a snapshot exists, confirming the site has been live for years.

Surprising Findings

The /minigames/8ballpool page contains 110,000+ characters of loot-box probability tables (cue names, rarity tiers, drop rates) — this is the most content-rich page on the domain by far, yet it carries no schema markup and is buried under a /minigames/ path with thin meta descriptions. The /games/webview page returns zero words of visible text — an empty shell. The sitemap includes a /404 URL. The copyright footer reads "2000 - 2026" (three years ahead), suggesting automated year-rolling. The site has two URL patterns for the same games (/minigames/8ballpool and /pages/minigames/8ballpool) with different content — a canonicalization risk.

Findings

1. Homepage and game pages deliver under 30 words of visible text to AI crawlers High

   The homepage delivers 26 words of visible text, the /games page delivers 11 words, and the /games/8-ball-pool page delivers 106 words mostly navigation boilerplate. This severely limits the semantic content available for AI crawlers to index and understand.

   What to change: Add substantive descriptive content to the homepage and game listing pages, such as game descriptions, categories, and featured titles, to provide AI crawlers with rich text to index.

2. /llms.txt returns full homepage HTML instead of an AI-friendly content map High

   The /llms.txt URL returns the full homepage HTML (143KB) rather than a structured text file listing important URLs and content summaries. This means the site has no AI-friendly content map, missing an opportunity to guide AI crawlers to key pages.

   What to change: Replace the /llms.txt endpoint with a proper text file that lists important URLs (e.g., /our-story, /publishing, top game pages) with brief descriptions, following the llms.txt standard.

3. No VideoGame, MobileApplication, or Organization schema on any page High

   Every page carries only minimal WebSite schema. There is no VideoGame, MobileApplication, Organization, FAQPage, or SoftwareApplication schema anywhere, despite the site being a major game publisher with multiple popular games. This prevents AI crawlers from understanding the site's offerings and structure.

   What to change: Add VideoGame schema to game pages, Organization schema to the homepage and /our-story, and MobileApplication schema for mobile game titles. Consider FAQPage schema for common questions.

4. Tencent acquisition not mentioned anywhere on the site Medium

   The site never mentions the Tencent acquisition (2015) on the homepage, /our-story, or /publishing pages. The LLM's prior knowledge includes this fact, but the site's own content omits it, creating a mismatch that could reduce trust in AI-generated summaries.

   What to change: Add a mention of the Tencent acquisition to the /our-story page or the company description on the homepage to align with external knowledge.

5. Two URL patterns for the same game content create canonicalization risk Medium

   The site has two URL patterns for the same games: /minigames/8ballpool and /pages/minigames/8ballpool, with different content. This can confuse AI crawlers and dilute indexing signals.

   What to change: Implement canonical tags to point to the preferred URL pattern, or consolidate content under a single URL structure.

6. /games/webview page returns zero words of visible text Medium

   The /games/webview page returns 0 words of visible text, appearing as an empty shell. This is a broken page that wastes crawl budget and provides no value to AI crawlers.

   What to change: Either remove the page or add meaningful content; if it's intended for internal use, block it via robots.txt or noindex.

7. Sitemap includes a /404 URL Low

   The sitemap contains a /404 URL, which is a broken page that should not be indexed. This wastes crawl budget and signals poor site maintenance.

   What to change: Remove the /404 URL from the sitemap and ensure only valid, indexable pages are included.

8. Copyright footer reads '2000 - 2026', three years ahead Low

   The copyright footer displays '2000 - 2026', which is three years in the future. This appears to be an automated year-rolling error that could reduce trust.

   What to change: Update the copyright year to the current year or use dynamic JavaScript to display the correct year.

9. Robots.txt has no AI-bot-specific rules Low

   The robots.txt file contains only a single line allowing all user agents, with no specific rules for AI crawlers like GPTBot or ClaudeBot. While this allows access, it misses the opportunity to guide AI crawlers to important pages or away from low-value ones.

   What to change: Consider adding specific rules for AI crawlers, such as allowing access to key pages and disallowing low-value paths like /minigames/ (which contains loot-box tables) if not desired.

10. Content-rich /minigames/ pages lack schema markup Medium

    The /minigames/8ballpool page contains 110,000+ characters of loot-box probability tables, making it the most content-rich page on the domain, yet it carries no schema markup. This content is invisible to AI crawlers in a structured way.

    What to change: Add appropriate schema markup (e.g., WebPage, or custom schema for game items) to these pages to help AI crawlers understand the structured data.

What's working

• All 11 tested AI crawlers receive 200 status with no blocking — All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) are allowed access with a 200 status, and the robots.txt permits all user agents. This ensures no artificial barriers to AI visibility.
• Nuxt SSR delivers rendered HTML to AI crawlers — The site uses Nuxt server-side rendering, so AI crawlers receive fully rendered HTML rather than an empty JavaScript shell. This is a strong foundation for content accessibility.
• Anthropic domain verification TXT record present — The DNS records include an anthropic-domain-verification TXT record, indicating proactive verification with Anthropic for Claude crawler access, which can improve crawling trust.
• /our-story and /publishing pages contain substantive text with key metrics — The /our-story page (203 words) and /publishing page (365 words) provide meaningful content about the company, including 10 billion downloads, 400 million monthly players, and 70 million DAU. These pages are valuable for AI crawlers to understand the brand.
• Sitemap is accessible and contains 65 URLs — The sitemap is available at /sitemap.xml and contains 65 URLs, helping crawlers discover pages efficiently.
• Content delivered via AWS CloudFront CDN for fast global access — The site uses AWS CloudFront and Amazon S3 for content delivery, ensuring fast load times for crawlers worldwide.