fnatic.com — AI Site Grade

Analysis

Fnatic.com: AI-Visibility Audit

The site has zero structured data across every page examined — no JSON-LD, no Product schema on product pages, no Organization schema on the homepage or about page, no Article schema on news posts — despite being a commerce-driven esports brand with a shop, team rosters, and a membership program.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a full 200 response with identical byte payload (194,541 bytes) as a browser. No UA-based blocking exists. The site runs on Vercel (Next.js) with Cloudflare DNS. The robots.txt is minimal: a single User-agent: * rule allowing / with four narrow disallows (/account/onboarding/*, /500, /gear/o, /moodboard/*). No AI-bot-specific directives exist. /llms.txt returns a 404 (rendered as a full Next.js 404 page). The sitemap is present and contains ~200 URLs including account pages, community pages, and product pages.

Content & Schema Posture

The homepage (254 words visible text) describes Fnatic as "the leading esports organisation in the west" with links to shop, partners, community, and plus. The about page (570 words) provides strong narrative: 20 years, $16M+ prize money, 30+ games, $55M raised, partnerships with Gucci, Red Bull, INZONE. The Valorant and League of Legends team pages list current rosters with player names and roles. The shop page lists products with prices. No page on the domain contains any JSON-LD schema — no Organization, Product, FAQPage, Article, BreadcrumbList, or WebSite schema. Product pages (e.g., the Base Hoodie at €94.99) have no Product schema despite having price, size, material, and availability data. The membership comparison page uses a table format with tier comparisons but has no Table or ProductGroup schema.

Cold-Knowledge Gap

The LLM knows Fnatic as a 2004-founded esports org with a record in CS 1.6 majors, the "Fnatic Bunker" training facility, and a Streak/Dash/React peripheral line. It also recalls 2023-2024 restructuring, layoffs, and the cutting of their Valorant roster — reputational signals the site itself never addresses. The site's Valorant page shows a current roster (Boaster, Alfajer, Kaajak, Crashies, Veqaj, Cyvoph) and a Boaster re-signing announcement from October 2025, directly contradicting the model's stale "roster cut" memory. The site also reveals that Fnatic Gear has been absorbed into Sony's INZONE brand (announced August 2025) — a major strategic pivot the cold model knows nothing about. The model still describes Fnatic Gear as an active product line, when the site now redirects hardware efforts to INZONE.

External Signals

The partners page lists 14+ case studies with BMW, AMD, Nike, Monster, Red Bull, and others. The news section shows active commercial momentum: IMG as global commercial agency (March 2025), GoGlobal partnership, DLSM as trading partner, Skinrave.gg collaboration, and the INZONE gear transition. The Red Bull "Fnatic Crew" creator collective launched November 2025. The most recent article (April 2026) introduces "STASHD," a digital collectibles platform built with Loot Labs. The site is actively publishing and commercially expanding, but none of this activity is surfaced to AI engines through structured data.

Additional Findings

The /gear page returns a 404 despite being listed in the sitemap and linked from the footer — a dead end for any crawler following that path. The homepage has no <h1> tag in the visible content (the h1 "Join the club" appears only in the newsletter signup section). News articles have no Article schema, no datePublished/dateModified metadata in structured form, and no author markup. The canonical tag is missing from most pages (homepage, about, esports pages, product pages), though some news articles have it. The site uses index,follow robots meta on all pages including the 404 page.

Findings

1. Zero JSON-LD schema on any page High

   No page on fnatic.com contains any JSON-LD structured data. The homepage, about page, shop, product pages, news articles, team rosters, and membership comparison all lack Organization, Product, Article, FAQPage, BreadcrumbList, or WebSite schema. This prevents AI crawlers from understanding the site's content and entities.

   What to change: Add JSON-LD schema for Organization on the homepage and about page, Product on product pages, Article on news pages, and FAQPage or Table schema on the membership comparison page.

2. /llms.txt returns 404 Medium

   The /llms.txt endpoint returns a full Next.js 404 page, meaning AI crawlers cannot discover a curated list of important URLs or context about the site.

   What to change: Create an /llms.txt file that lists key pages (homepage, about, shop, news, esports teams) and provides a brief description of the site.

3. /gear page returns 404 despite being in sitemap and footer High

   The /gear page, listed in the sitemap and linked from the footer, returns a 404 error. This creates a dead end for crawlers and users.

   What to change: Either restore the /gear page with content or remove it from the sitemap and footer links.

4. Homepage lacks a visible H1 heading Medium

   The homepage has no visible H1 tag; the only H1 is 'Join the club' inside the newsletter signup section, which is not a descriptive page title. This harms semantic structure and accessibility.

   What to change: Add a descriptive H1 heading to the homepage, such as 'Fnatic: Leading Esports Organization'.

5. Canonical tags missing from most pages Medium

   The homepage, about page, esports pages, and product pages lack canonical tags, which can lead to duplicate content issues and confuse crawlers about the preferred URL.

   What to change: Add self-referencing canonical tags to all pages.

6. News articles lack Article schema and date metadata High

   News articles have no Article schema, no structured datePublished or dateModified, and no author markup. This prevents AI crawlers from surfacing news content in rich results or knowledge panels.

   What to change: Add Article schema with datePublished, dateModified, headline, and author fields to all news articles.

7. Product pages lack Product schema High

   Product pages like the Base Hoodie have price, size, material, and availability data but no Product schema, preventing AI crawlers from understanding product details and potentially surfacing them in shopping results.

   What to change: Add Product schema with name, description, price, currency, availability, and size fields to all product pages.

8. No Organization schema on homepage or about page Medium

   The homepage and about page contain rich company information (founded 2004, $16M+ prize money, 30+ games, $55M raised, partnerships) but no Organization schema, missing an opportunity for knowledge panel enrichment.

   What to change: Add Organization schema with name, founding date, description, logo, and social links to the homepage and about page.

9. Site content contradicts stale LLM knowledge about roster cuts and gear line High

   The LLM's cold knowledge recalls 2023-2024 restructuring, layoffs, and Valorant roster cuts, and still describes Fnatic Gear as an active product line. The site's current Valorant roster and the INZONE gear transition (August 2025) are not surfaced to AI crawlers via schema or /llms.txt, so AI models may serve outdated information.

   What to change: Add structured data (Organization, Article, Product) and update /llms.txt to highlight the current roster and INZONE partnership, ensuring AI crawlers index the latest information.

10. No BreadcrumbList schema on any page Low

    No page uses BreadcrumbList schema, which helps crawlers understand site hierarchy and can appear in search results.

    What to change: Add BreadcrumbList schema to all pages, especially shop, news, and esports sections.

11. Membership comparison page lacks FAQ or Table schema Medium

    The membership page uses a table to compare tiers but has no FAQPage or Table schema, making the comparison data invisible to AI crawlers.

    What to change: Add FAQPage schema for each tier's features or Table schema to represent the comparison data.

12. robots.txt has no AI-bot-specific rules Low

    The robots.txt allows all AI crawlers with only four narrow disallows. While not blocking, it misses the opportunity to guide AI crawlers to important pages or away from low-value ones.

    What to change: Consider adding specific directives for AI crawlers, such as allowing key sections (news, esports, shop) and disallowing account or admin paths.

What's working

• All major AI crawlers receive full access — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others all receive a 200 response with identical content as a browser. No UA-based blocking exists, ensuring crawlers can access the site.
• Sitemap is present with ~200 URLs — The sitemap contains approximately 200 URLs covering key sections including shop, news, esports teams, and community pages, helping crawlers discover content.
• Active news section with recent commercial partnerships — The news section shows ongoing commercial activity: IMG agency partnership (March 2025), Red Bull Fnatic Crew (November 2025), INZONE gear transition (August 2025), and STASHD digital collectibles (April 2026). This demonstrates a vibrant brand with fresh content.
• About page provides rich company narrative — The about page contains 570 words detailing 20 years of history, $16M+ prize money, 30+ games, $55M raised, and partnerships with Gucci, Red Bull, and INZONE. This is strong content for AI crawlers if structured.
• Esports team pages list current rosters with player details — Valorant and League of Legends team pages list current players with names and roles, providing valuable entity data that could be enhanced with schema.
• Partners page lists 14+ brand case studies — The partners page showcases collaborations with BMW, AMD, Nike, Monster, Red Bull, and others, demonstrating strong external signals and brand authority.
• Membership program with clear tier comparison — The membership page offers a tiered program (likely free and paid) with a comparison table, providing monetization and community engagement data that could be structured.