lovevery.com — AI Site Grade

Analysis

Lovevery AI-Visibility Audit

The main commerce site (lovevery.com) and the blog (blog.lovevery.com) operate as two entirely separate technical estates with no shared AI-visibility strategy — the blog has rich Article schema and a large content corpus, while the commerce site has zero structured data on any page examined.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive 200 status with full content on the homepage. The robots.txt at lovevery.com contains no AI-bot-specific rules; the wildcard * blocklist covers only Shopify admin/cart/checkout paths, leaving all product and content pages open. The blog subdomain's robots.txt blocks AhrefsBot but allows all other crawlers. The site runs on Vercel (Next.js) behind a standard edge cache. No WAF-based UA blocking was detected. The llms.txt returns a 404 — the site has no AI-friendly content manifest.

Schema Posture

The commerce domain (lovevery.com) has zero JSON-LD schema on the homepage, the Play Kits landing page, the About page, the Reviews page, or the individual product page (The Looker Play Kit). No Product, Organization, FAQPage, BreadcrumbList, or Review schema exists anywhere on the main site. The blog subdomain (blog.lovevery.com, a separate WordPress installation) does include Article, WebPage, BreadcrumbList, and WebSite schema with proper datePublished, author, and keywords — but this schema lives on a subdomain that is not linked via schema or sitemap from the main domain. The blog's sitemap_index.xml contains 10 sub-sitemaps with ~714 URLs; the main site's sitemap.xml lists 136 URLs. These are two disconnected content graphs.

Cold-Knowledge Gap

A frontier LLM queried cold about Lovevery correctly identifies the brand as a subscription-based Montessori-inspired play kit company (founded 2015 by Jessica Rolph and Roderick Morris) and notes the pricing criticism and shipping delays. However, the model's prior is thin: it knows nothing about the expert advisory board (Dr. Gillian Starkey, Dr. William Staso, Dr. Ariel Kalil, Jody Malterre, and 10+ others), the podcast ("My New Life"), the Preloved resale marketplace, the Reading Skill Set and Math Skill Set product lines, the Real Life Play Kitchen, or the Book Bundle add-on. These are all prominently featured on the live site but absent from the model's cold knowledge — a gap that structured data and an llms.txt could close.

Content Fragmentation

The blog contains 700+ research-backed articles with citations, expert quotes, and developmental guidance — a strong corpus for AI citation. But the blog is on a separate subdomain with its own sitemap, its own schema graph, and no Organization or WebSite schema linking it back to the parent brand. The main site's footer links to blog.lovevery.com as an external link, not an internal one. An AI engine crawling the commerce site would find no indication that a deep content library exists. The blog's Article schema includes author ("Team Lovevery") and keywords but no mentions or about linking to specific products — a missed opportunity for product-to-content entity association.

Findings

1. Zero JSON-LD schema on all commerce pages High

   The homepage, product pages, About page, and Reviews page on lovevery.com contain no structured data (Product, Organization, FAQPage, BreadcrumbList, or Review schema). This prevents AI crawlers from understanding page content and entity relationships.

   What to change: Add JSON-LD schema for Product, Organization, FAQPage, BreadcrumbList, and Review to all relevant commerce pages.

2. No llms.txt file for AI-friendly content manifest Medium

   The llms.txt endpoint returns a 404, meaning there is no AI-friendly content manifest to guide crawlers to key resources.

   What to change: Create an llms.txt file listing key pages and resources for AI crawlers.

3. Blog subdomain disconnected from main site in AI graph High

   The blog at blog.lovevery.com has rich Article schema but is not linked via schema or sitemap from the main domain. No Organization or WebSite schema connects the two, so AI crawlers treat them as separate entities.

   What to change: Add Organization schema on both domains linking to each other, and include blog URLs in the main sitemap.

4. Key products and features missing from LLM cold knowledge Medium

   A frontier LLM queried cold about Lovevery knows nothing about the expert advisory board, podcast, Preloved marketplace, Reading Skill Set, Math Skill Set, Real Life Play Kitchen, or Book Bundle — all present on the live site.

   What to change: Add structured data (Product, Organization) and create an llms.txt to surface these assets to AI crawlers.

5. Blog Article schema lacks product mentions or about links Medium

   The blog's Article schema includes author and keywords but no mentions or about properties linking to specific Lovevery products, missing an opportunity for entity association.

   What to change: Add mentions or about properties in Article schema to reference relevant products.

6. No AI-specific rules in robots.txt Low

   The robots.txt at lovevery.com has no rules for AI crawlers like GPTBot or ClaudeBot, relying on default allow. While not blocking, this misses an opportunity to guide crawlers to important pages.

   What to change: Add explicit allow rules for AI crawlers and consider a crawl-delay directive.

7. Blog robots.txt blocks AhrefsBot Low

   The blog's robots.txt blocks AhrefsBot, which may limit backlink analysis and AI visibility indirectly.

   What to change: Remove the AhrefsBot block unless there is a specific reason.

What's working

• All major AI crawlers allowed and served full content — The homepage returns 200 with full content for all tested AI crawlers, and robots.txt does not block any AI bots.
• Blog has rich Article schema with dates, author, keywords — The blog subdomain includes Article, WebPage, BreadcrumbList, and WebSite schema with proper metadata, aiding AI understanding.
• 700+ research-backed articles on blog — The blog contains over 700 articles with citations and expert quotes, providing a strong content base for AI citation.
• Blog sitemap_index.xml with 10 sub-sitemaps — The blog's sitemap is well-organized with multiple sub-sitemaps covering ~714 URLs, aiding crawler discovery.
• Main site sitemap.xml with 136 URLs — The commerce site has a sitemap listing 136 URLs, providing a crawl path for search engines.
• Fast hosting on Vercel edge network — The site runs on Vercel (Next.js) with edge caching, ensuring fast response times for crawlers.