yotoplay.com — AI Site Grade

Analysis

Yoto's AI-Visibility Audit

The site has no AI-specific bot rules in its robots.txt and no llms.txt — yet every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receives a 200 with full HTML content identical to browser delivery, served from Netlify with no UA-based blocking. The technical gate is wide open, but the content structure is not optimized for AI consumption.

Crawler Access

All 11 tested bot UAs return identical byte size (437,620) and status 200 on the homepage. No Cloudflare, no WAF challenge, no JS-only shell. The robots.txt uses a single User-agent: * rule that allows / and disallows only admin/ecommerce paths (/account/, /checkout/, /cart/, /blogs/, /pages/). No AI crawler is named or restricted. The llms.txt returns a 404 — the site has no AI-friendly content map. The all-players comparison page is a JS shell (14 words extracted), meaning AI crawlers see almost nothing on that page despite it being in the sitemap.

Cold-Knowledge Gap

The LLM prior knows Yoto was founded in 2015 by Ben Drury and Filip Denker, raised over $20M, and is often compared to Toniebox. The actual site says nothing about founding year, funding, or Toniebox. The "Our Story" page mentions "two dads with a shared background in the music industry" and Maria Montessori influence but omits the 2015 founding date, the London origin, and any funding milestones. The site claims "22 billion minutes listened in 2025" — a striking growth metric — but the cold LLM knowledge has no awareness of this figure. The audio-content-and-ai page is a strong, transparent AI-use policy (human-made by design, AI only where it adds value) that no external AI knowledge currently references.

Schema Posture

Product pages (/yoto-player, /yoto-mini) carry valid Product schema with gtin13, sku, offers (price, currency, availability). However, the homepage, "Our Story," "Why Yoto," and the press page have zero JSON-LD. The homepage has no Organization, WebSite, or Product schema despite being the primary entry point for AI crawlers. The FAQ sections on product pages are rendered as plain text headings — not marked up with FAQPage schema, so AI engines cannot extract structured Q&A pairs.

External Signals

The DNS TXT records reveal OpenAI domain verification (openai-domain-verification=dv-8svBk1BNHJ9QstnuEJoiRB8c) and two Anthropic domain verifications (anthropic-domain-verification-3b291c and anthropic-domain-verification-g6c0dv), confirming Yoto has proactively verified its domain with both OpenAI and Anthropic for API/retrieval use. The site links to Trustpilot reviews and Instagram but has no structured review markup. The press page is thin (119 words) and the press kit PDF is dated March 2026 — current, but the page itself offers almost no narrative for AI engines to cite.

Regional Fragmentation

The bare domain yotoplay.com immediately 302-redirects to uk.yotoplay.com. The US site lives at us.yotoplay.com with its own robots.txt and sitemap. Both share identical AI-access posture (no bot blocks). AI crawlers hitting the root domain land on the UK site by default, which may confuse geographic relevance for US-focused queries. The UK and US homepages have different canonical URLs but near-identical content — a potential duplicate-content signal for search crawlers.

Findings

1. No llms.txt file for AI content discovery Medium

   The site returns a 404 for llms.txt, providing no AI-friendly content map for crawlers to efficiently discover key pages.

   What to change: Create an llms.txt file listing the most important pages (homepage, product pages, Our Story, press, audio-content-and-ai) with brief descriptions.

2. All-players comparison page renders as JS shell High

   The /all-players page returns only 14 words of content to crawlers, meaning AI bots see an empty shell instead of the product comparison table.

   What to change: Implement server-side rendering or pre-rendering for the /all-players page so that static HTML content is available to crawlers.

3. Homepage lacks Organization and WebSite schema High

   The homepage has zero JSON-LD markup, missing Organization, WebSite, and Product schema that would help AI engines understand the brand and its offerings.

   What to change: Add Organization, WebSite, and Product JSON-LD schema to the homepage with brand name, logo, description, and product references.

4. Product FAQ sections lack FAQPage schema Medium

   FAQ sections on product pages are rendered as plain text headings, not marked up with FAQPage schema, preventing AI engines from extracting structured Q&A pairs.

   What to change: Add FAQPage JSON-LD schema to product pages, marking up each question and answer pair.

5. Our Story page omits founding year and funding details Medium

   The 'Our Story' page mentions 'two dads' and Montessori but omits the 2015 founding year, London origin, and over $20M in funding, which LLMs already know from external sources.

   What to change: Add the founding year (2015), location (London), and funding milestones to the Our Story page to align with existing LLM knowledge.

6. 22 billion minutes listened not referenced in LLM knowledge Medium

   The site prominently claims '22 billion minutes listened in 2025', but this striking growth metric is absent from LLM prior knowledge, representing a missed opportunity for AI citation.

   What to change: Ensure the 22 billion minutes figure is prominently placed in crawlable text on the homepage and Our Story page, and consider adding it to llms.txt.

7. Press page offers minimal narrative for AI citation Low

   The press page contains only 119 words and a press kit PDF link, providing little structured narrative for AI engines to cite in responses about Yoto.

   What to change: Expand the press page with key milestones, quotes, and a timeline to give AI engines more substantive content to reference.

8. Bare domain redirects to UK site, US site separate Low

   The root domain yotoplay.com redirects to uk.yotoplay.com, while the US site lives at us.yotoplay.com with near-identical content, potentially confusing AI crawlers on geographic relevance and creating duplicate content signals.

   What to change: Consider using hreflang tags or a single international site with language/region selectors to clarify geographic targeting to crawlers.

9. Trustpilot reviews not marked up with Review schema Medium

   The site links to Trustpilot but does not include structured Review or AggregateRating schema on product pages, missing an opportunity to surface social proof in AI responses.

   What to change: Add AggregateRating and Review JSON-LD schema to product pages, pulling in Trustpilot ratings and review counts.

What's working

• All major AI crawlers receive full HTML content — Every tested AI bot (GPTBot, ClaudeBot, PerplexityBot, etc.) gets a 200 with identical HTML to browser delivery, with no UA-based blocking or JS-only shells on most pages.
• Domain verified with OpenAI and Anthropic for API retrieval — DNS TXT records show verification tokens for OpenAI and two for Anthropic, indicating proactive steps to enable retrieval-augmented generation (RAG) access.
• Product pages have valid Product schema with GTIN and offers — The /yoto-player and /yoto-mini pages include Product JSON-LD with gtin13, sku, price, currency, and availability, enabling AI engines to extract structured product data.
• Audio Content and AI page explains AI use transparently — The /audio-content-and-ai page clearly states that content is human-made by design and AI is used only where it adds value, providing a trustworthy narrative for AI engines.
• Robots.txt allows all AI crawlers to access key pages — The robots.txt uses a single User-agent: * rule that allows / and only disallows admin/ecommerce paths, so AI crawlers are not blocked from any public content.
• Sitemap available with 80 URLs — The UK site has a sitemap at /sitemap.xml containing 80 URLs, helping crawlers discover content efficiently.