xoxoday.com — AI Site Grade

Analysis

Xoxoday maintains an unusually mature AI-visibility posture — an explicit llms.txt with competitor lists, canonical guidance, and brand constraints — yet the cold LLM knowledge about the brand is stale, referencing a pre-rebrand identity and missing the core "Xoxoday Hub" unified platform narrative entirely.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, anthropic-ai — receives a full 200 response with the same 460KB payload as a browser. The robots.txt explicitly allows all of them on / while blocking only subdomain shells (marketplace.xoxoday.com, accounts.xoxoday.com, plumdemo.xoxoday.com) and tracking-parameter URLs. Bytespider is the sole bot blocked (403 from Cloudflare). The site runs on Cloudflare with HSTS and CSP (frame-ancestors 'self'), but no JS-rendering barrier: the homepage delivers ~1,600 words of visible text on a plain GET.

llms.txt Maturity

The /llms.txt file is a standout — last updated 2025-12-24, it includes a brand summary, canonical domain guidance per product, competitive landscape lists (e.g., Empuls vs. Achievers/Bonusly/Workhuman, Plum vs. Sendoso/Tremendous/Prezzee), explicit "brand is not" constraints (not a consumer cashback or gambling platform), and a brand usage note: never refer to the brand as "xoxo". This is rare depth for an llms.txt and signals deliberate AI-content strategy.

Cold-Knowledge Gap

The LLM's prior knowledge describes Xoxoday as having "products including Xoxoday Plum, Xoxoday Compass, and Xoxoday Empuls" — but Compass is not listed as a product on the site (it redirects to getcompass.ai and appears only in the llms.txt competitor section). The cold knowledge claims "over 1,000 enterprise clients" while the site says 5,000+ businesses. The model references "funding from Stellaris Venture Partners" — the site's timeline shows seed funding from Kshatriya Ventures (2013), strategic investment from Mahindra Holidays (2016), growth capital from Apis Partners (2022), and a Series C in 2025. The model also knows nothing about the Giift rebranding to Xoxoday (March 2025) or the unified Xoxoday Hub platform narrative.

Schema & Content Posture

The homepage carries a single Organization schema with an OfferCatalog listing five products (Plum, Empuls, Compass, Loyalife, Loopr). The /about-us page has richer schema: AboutPage with Organization including 11 named leaders, 7 office addresses (Bangalore, Redwood City, New York, Dubai, Doha, London, Jakarta), founding date, and slogan. However, product sub-pages (/plum, /empuls) carry zero JSON-LD schema — no Product, SoftwareApplication, or WebSite types. The blog (blog.xoxoday.com) has only a basic WebSite schema. No FAQ schema, no HowTo, no Article schema on individual blog posts detected.

External Signals & Surprising Finds

The newsroom reveals that Xoxoday was formerly known as Giift and rebranded globally in March 2025 after a $70M investment from Apis Partners — a critical fact entirely absent from the LLM's cold knowledge. The site lists 65 million users and 5,000+ customers including H&M, Capgemini, Nielsen, Freshworks, Xero, and Kennametal. The /youforia page offers a physical experiential gifting product (curated boxes with journals and gift cards) — a tangible product line not mentioned in any AI-facing content. The sitemap contains 2,353 URLs, indicating a large content surface, but the blog uses a separate subdomain (blog.xoxoday.com) on Ghost, creating a domain split that may dilute authority signals.

Findings

1. Cold LLM knowledge is stale, referencing pre-rebrand identity and missing unified platform narrative High

   The LLM's prior knowledge describes Xoxoday as having products including Compass, which is not listed on the site, and references outdated funding and client numbers. The Giift rebranding to Xoxoday (March 2025) and the unified Xoxoday Hub narrative are absent.

   What to change: Update the llms.txt with the current brand narrative, product list, and key facts (e.g., 5,000+ customers, 65 million users, Apis Partners investment).

2. Product sub-pages lack JSON-LD schema High

   The /plum and /empuls pages carry zero JSON-LD schema, missing opportunities for Product, SoftwareApplication, or WebSite types that would help AI crawlers understand the offerings.

   What to change: Add JSON-LD schema (Product, SoftwareApplication) to each product sub-page.

3. Blog on separate subdomain dilutes authority signals Medium

   The blog at blog.xoxoday.com runs on Ghost, creating a domain split that may dilute authority signals for AI crawlers and search engines.

   What to change: Consider moving the blog to a subdirectory (e.g., xoxoday.com/blog) to consolidate authority.

4. No FAQ, HowTo, or Article schema detected on blog or product pages Medium

   The site lacks FAQ schema, HowTo schema, and Article schema on blog posts, which are commonly used by AI crawlers to extract structured answers.

   What to change: Add FAQ schema to relevant pages and Article schema to blog posts.

5. Youforia experiential gifting product absent from AI-facing content Medium

   The /youforia page offers a physical experiential gifting product, but this product line is not mentioned in the llms.txt or any AI-facing content, limiting its discoverability by AI agents.

   What to change: Add Youforia to the llms.txt product list and include a brief description.

6. Bytespider crawler blocked by Cloudflare Low

   Bytespider (ByteDance's crawler) receives a 403 response, preventing its content from being indexed by ByteDance's AI products.

   What to change: Allow Bytespider access if the site wants visibility in ByteDance's AI ecosystem.

7. Compass product page redirects to external domain Medium

   The Compass product page redirects to getcompass.ai, and Compass is listed as a product in the homepage schema but not as a current offering on the site, causing confusion for AI crawlers.

   What to change: Update the homepage schema to remove Compass if it is no longer a product, or provide a proper landing page.

8. No llms-full.txt provided Low

   The site provides an llms.txt but no llms-full.txt, which could offer more detailed documentation for AI agents.

   What to change: Consider adding an llms-full.txt with comprehensive product documentation.

What's working

• Explicit llms.txt with brand constraints and competitive landscape — The /llms.txt file includes a brand summary, canonical domain guidance, competitive lists, and brand usage notes, demonstrating deliberate AI-content strategy.
• All major AI crawlers allowed with full HTML content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others receive a 200 response with the same 460KB payload as a browser, ensuring content is indexable.
• Rich Organization schema on /about-us with leadership and offices — The /about-us page includes detailed Organization schema with 11 named leaders, 7 office addresses, founding date, and slogan, providing structured data for AI crawlers.
• Homepage Organization schema with OfferCatalog listing five products — The homepage carries an Organization schema with an OfferCatalog listing five products, helping AI crawlers understand the product portfolio.
• Large content surface with 2,353 URLs in sitemap — The sitemap contains 2,353 URLs, indicating a substantial content surface for AI crawlers to index.
• Newsroom page with key brand facts and customer logos — The newsroom page lists 65 million users, 5,000+ customers including major brands, and details the Giift rebranding, providing authoritative content for AI crawlers.