wonderbly.com — AI Site Grade

Analysis

Wonderbly: AI-Visibility Audit

The site's product pages — the core content AI crawlers need most — all return 404s, making the entire catalog invisible to every AI engine despite perfect bot access on the homepage.

Crawler Access

All eleven AI bots tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User, Browser) receive a 200 with identical 384KB payload from the homepage. No UA-based blocking exists. The robots.txt has a single User-agent: * rule blocking checkout, account, cart, and preview paths — standard e-commerce hygiene — but no AI-bot-specific directives whatsoever. The site runs on Heroku behind Fastly CDN (151.101.x.x), with AWS Route53 DNS and Google Workspace mail. An anthropic-domain-verification TXT record confirms active ClaudeBot relationship management. An llms.txt exists at 80KB — unusually comprehensive, listing 30+ localized homepages, metadata, and priority page guidance. This is an advanced AI-readiness signal.

Cold-Knowledge Gap

The LLM knows Wonderbly as a personalized children's book company founded in London in 2012, originally named "Lost My Name," with the original bestseller "The Little Boy/Girl Who Lost Their Name." It mentions the viral social growth and a strong reputation. The site itself tells a different story: it now heavily promotes adult books (newspaper-themed, astrology, pets, poetry, sports), Father's Day gifts, and claims 10 million customers (the LLM says 8 million). The LLM has no knowledge of the Penguin Random House acquisition (June 2025, per Wikipedia), the expanded adult range, or the "Your Life in Newspaper Headlines" product. The site's own press page still says "over 9 million" — a stale figure that contradicts the homepage's "10 million."

Schema Posture

Every page carries the same minimal Organization schema: name, URL, sameAs links to Facebook/Pinterest/Twitter/Instagram. No Product schema, no Book schema, no FAQPage schema despite FAQ sections on multiple pages. No BreadcrumbList, no ItemList on collection pages, no Review schema despite Trustpilot integration. The blog subdomain has richer schema (WebSite, WebPage, BreadcrumbList, Organization with LinkedIn/YouTube/Wikipedia) — the main site does not. This is a critical missed signal: AI engines crawling product discovery pages get zero structured data about what is actually for sale.

Content Architecture Problem

The most surprising finding: every product page under /personalized-products/ returns a 404. The sitemap lists URLs like https://www.wonderbly.com/personalized-products/the-little-boy-who-lost-his-name and https://www.wonderbly.com/personalized-products/your-life-in-newspaper-headlines — all dead. The site appears to use a JavaScript-rendered product configurator (the homepage links to /personalized-products/.../create/start paths), meaning the actual product detail pages are inaccessible to crawlers without JS execution. Category pages (/personalized-books/kids/collections/lost-my-name) do render with text, but they are thin (164 words) and lack individual product data. An AI crawler cannot learn about specific book titles, prices, descriptions, or personalization options from this site.

External Signals

Wikipedia confirms the Penguin Random House acquisition closed June 2025 — a major signal the site itself does not prominently feature. The blog subdomain (WordPress) has richer SEO infrastructure and links to the main store, but the main site's blog links are buried in footers. Trustpilot is referenced but no review schema is implemented. The press page is thin and outdated, still referencing "over 9 million" books sold. No recent press coverage surfaced in search results.

Findings

1. All product pages under /personalized-products/ return 404 to AI crawlers High

   Every product detail page listed in the sitemap under /personalized-products/ returns a 404 HTTP status. This includes core titles like 'The Little Boy Who Lost His Name' and 'Your Life in Newspaper Headlines'. AI crawlers cannot access any individual product information.

   What to change: Restore server-side rendered product detail pages at the /personalized-products/ URLs or implement a fallback that serves static content to crawlers.

2. No Product or Book schema on any page High

   Every page audited carries only minimal Organization schema. No Product, Book, FAQPage, BreadcrumbList, or ItemList schema is present, despite FAQ sections and product collections existing on the site.

   What to change: Add Product or Book structured data to all product pages, and FAQPage schema to pages with FAQ content.

3. Press page uses outdated customer count Medium

   The press page states 'over 9 million' books sold, while the homepage claims '10 million customers'. This inconsistency undermines credibility for AI engines that may cite either figure.

   What to change: Update the press page to match the current customer count of 10 million.

4. LLM knowledge lacks adult book range and acquisition Medium

   The LLM knows Wonderbly only as a children's book company, missing the expanded adult product line (newspaper-themed, astrology, pets) and the Penguin Random House acquisition. This limits AI-generated recommendations.

   What to change: Prominently feature the adult book range and acquisition news on the homepage and press page, and ensure these are indexed by AI crawlers.

5. Category pages are text-thin for AI crawlers Medium

   Collection pages like /personalized-books/kids/collections/lost-my-name contain only 164 words of text, providing minimal context about the products. AI crawlers cannot extract detailed product information from these pages.

   What to change: Expand category page content with descriptive text, product summaries, and structured data to provide richer context for AI crawlers.

6. Trustpilot reviews not marked up with Review schema Medium

   The site integrates Trustpilot reviews but does not implement Review structured data. AI crawlers cannot extract review content for product pages.

   What to change: Add Review schema markup to product pages, pulling data from Trustpilot.

7. Blog links are buried in footer, limiting crawl depth Low

   The blog subdomain has richer SEO infrastructure but links from the main site are only in the footer. This reduces the blog's visibility to AI crawlers.

   What to change: Add prominent blog links in the main navigation or on key landing pages.

What's working

• Comprehensive llms.txt file at 80KB — The site hosts an unusually detailed llms.txt file listing 30+ localized homepages, metadata, and priority page guidance, signaling advanced AI-readiness.
• All 11 tested AI bots receive 200 on homepage — Every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, etc.) gets a 200 response from the homepage with no UA-based blocking.
• Anthropic domain verification TXT record present — The DNS TXT records include an anthropic-domain-verification entry, indicating active relationship management with ClaudeBot.
• Robots.txt blocks only checkout, account, cart, and preview paths — The robots.txt uses a single User-agent: * rule to block non-content paths, which is standard e-commerce hygiene and does not block AI bots from content.
• Wikipedia page confirms Penguin Random House acquisition — Wikipedia has a detailed page confirming the June 2025 acquisition by Penguin Random House, a strong external signal that the site itself does not yet leverage.
• Blog subdomain has richer schema than main site — The blog subdomain implements WebSite, WebPage, BreadcrumbList, and Organization schema with additional social links, providing a better structured data foundation.