rewardgateway.com — AI Site Grade

Analysis

The site's homepage and blog list pages carry zero JSON-LD schema, while individual blog posts carry BlogPosting and BreadcrumbList — but the most critical pages for AI discovery (homepage, solution pages, case study library, resource center) are entirely schema-bare.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai — receive a 200 status with full HTML content on the homepage. No UA-based blocking exists. The site runs on Cloudflare (A records point to AWS CloudFront IPs) with HubSpot as the CMS. The robots.txt is minimal: a single User-agent: * rule disallowing only /2018-homepage and its regional variants, plus HubSpot preview paths. No AI-bot-specific directives exist. /llms.txt returns 404. The sitemap.xml is present and contains ~3,788 URLs, but it is a single flat file rather than a sitemap index — unusual for a site of this scale.

Cold-Knowledge Gap

The LLM cold-knowledge prior is reasonably accurate on fundamentals: founded 2006 in London, acquired by Great Hill Partners in 2021, merged with Edenred in 2023, serves mid-to-large enterprises, clients include American Express and McDonald's. However, the prior mentions "AI-driven recognition features" and "integration challenges post-merger" — neither of which is substantiated anywhere on the live site. The homepage and solution pages make zero mention of AI in product features. The blog has one post about "risks and benefits of using AI in business" but it is generic, not product-specific. The cold knowledge also cites the acquisition as "undisclosed sum" — the press room confirms the figure was GBP 1.15 billion (approximately USD 1.4 billion), a material detail the model lacks.

Schema Posture

The homepage, solution pages, case study library, resource center, and blog listing pages all contain zero JSON-LD schema. Individual blog posts do carry BlogPosting and BreadcrumbList schema with publisher Organization markup referencing "Reward Gateway | Edenred" and a logo URL. But the Organization schema is never placed on the homepage or any top-level page, meaning AI crawlers have no structured way to confirm the company's name, founding date, logo, or social profiles from the site itself. The VideoObject schema on the solution page has an empty description field.

Content & Structure

The homepage delivers 591 words of visible text — adequate but not rich. The H1 is "Engage, motivate, and retain your people." No FAQ schema, no comparison tables, no structured data for the product modules listed (Recognition, Wellbeing, Discounts, Communications, Surveys). The blog is actively maintained with posts dated into 2025/2026, but the sitemap contains many URLs from 2015-2018 that redirect to the press releases listing page (individual press release permalinks are dead). The UK blog uses a different URL structure (/uk/blog) and references "EngagementOS" as a product name not found on the US site — a regional content fragmentation that may confuse crawlers.

External Signals

The DNS TXT records reveal integrations with HubSpot, Zendesk, Salesforce, Netsuite, Stripe, Zoom, Figma, Atlassian, OneTrust, and Docker — a complex vendor stack. The trust.rewardgateway.com subdomain returns 403 with a Cloudflare challenge ("Just a moment..."), blocking all crawlers from accessing security/compliance documentation. The case study library lists 80+ named clients including Accenture, Heineken, Marks & Spencer, AXA, and McDonald's — strong social proof that is not surfaced in any structured schema.

Findings

1. Homepage and top-level pages lack JSON-LD schema High

   The homepage, solution pages, case study library, resource center, and blog listing pages contain zero JSON-LD schema. Only individual blog posts have BlogPosting and BreadcrumbList schema. This prevents AI crawlers from confirming company identity, product offerings, and social proof in a structured way.

   What to change: Add Organization schema to the homepage and WebSite schema to all top-level pages. Include Product schema for the platform modules (Recognition, Wellbeing, etc.) on solution pages.

2. Cold knowledge includes unsubstantiated claims about AI features High

   LLM cold knowledge mentions 'AI-driven recognition features' and 'integration challenges post-merger', but the live site makes no mention of AI in product features. The only AI-related blog post is generic and not product-specific. This mismatch can lead to fabricated facts in AI-generated summaries.

   What to change: Add a dedicated page or section describing any AI capabilities in the product, or remove references to AI from the site if not applicable. Ensure product pages accurately reflect features.

3. Sitemap is a single flat file for ~3,788 URLs Medium

   The sitemap.xml contains approximately 3,788 URLs in a single file rather than using a sitemap index. For a site of this scale, this is unusual and may cause inefficient crawling or incomplete indexing by search engines and AI crawlers.

   What to change: Split the sitemap into multiple files (e.g., by content type or date) and use a sitemap index file to reference them.

4. /llms.txt returns 404 Medium

   The site does not provide an /llms.txt file, which is a recommended way to guide AI crawlers to the most important pages and provide structured context. This is a missed opportunity to influence AI-generated summaries.

   What to change: Create an /llms.txt file that lists key pages (homepage, solution pages, case studies, blog) and provides a brief description of the company and platform.

5. VideoObject schema on solution page has empty description Medium

   The solution page includes VideoObject schema but the description field is empty. This reduces the usefulness of the schema for AI crawlers and may lead to incomplete video metadata in search results.

   What to change: Populate the description field in VideoObject schema with a meaningful summary of the video content.

6. Regional content fragmentation between US and UK sites Medium

   The UK blog uses a different URL structure (/uk/blog) and references 'EngagementOS' as a product name not found on the US site. This inconsistency may confuse crawlers and dilute brand messaging across regions.

   What to change: Align product naming across regional sites or use hreflang annotations to clarify regional variations. Consider consolidating product names under a single brand.

7. Trust subdomain returns 403 with Cloudflare challenge Medium

   The trust.rewardgateway.com subdomain, which likely hosts security and compliance documentation, returns a 403 status with a Cloudflare challenge, blocking all crawlers. This prevents AI crawlers from accessing trust-related content that could enhance credibility.

   What to change: Allow crawler access to the trust subdomain by adjusting Cloudflare settings or providing a public summary page.

8. Sitemap contains many dead press release URLs from 2015-2018 Low

   The sitemap includes numerous press release permalinks from 2015-2018 that now redirect to the press releases listing page. These dead links waste crawl budget and may signal poor site maintenance to crawlers.

   What to change: Remove outdated press release URLs from the sitemap or set up proper 301 redirects to relevant current pages.

9. Blog posts lack FAQ schema for Q&A content Low

   Some blog posts contain question-and-answer sections but do not use FAQPage schema. This reduces the chance of appearing in rich results for common questions.

   What to change: Add FAQPage schema to blog posts that include Q&A sections.

10. Case study library lacks schema for client logos and testimonials Low

    The case study library lists 80+ named clients but does not use schema markup (e.g., Review, ClaimReview) to surface this social proof in structured form. AI crawlers cannot easily extract client names or testimonials.

    What to change: Add schema markup such as Review or ClaimReview to case study pages to highlight client names and outcomes.

What's working

• All major AI crawlers receive full HTML content — The homepage returns 200 status with full HTML content for all tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.). No UA-based blocking exists, ensuring AI crawlers can access the site's content.
• Blog is actively maintained with posts into 2025/2026 — The blog contains recent posts dated into 2025 and 2026, indicating fresh content that can attract crawlers and provide up-to-date information.
• Individual blog posts carry BlogPosting and BreadcrumbList schema — Each blog post includes BlogPosting and BreadcrumbList schema with publisher Organization markup, helping AI crawlers understand the content structure and authorship.
• Robots.txt allows all AI crawlers with minimal restrictions — The robots.txt file only disallows a few old homepage paths and HubSpot preview paths, allowing AI crawlers to access the vast majority of the site.
• Sitemap.xml is present and contains ~3,788 URLs — The sitemap is available and includes a large number of URLs, helping crawlers discover content efficiently.
• Case study library lists 80+ named clients including major brands — The case study library features well-known clients such as Accenture, Heineken, Marks & Spencer, AXA, and McDonald's, providing strong social proof that can enhance credibility in AI-generated summaries.
• Cold knowledge accurately captures company fundamentals — LLM cold knowledge correctly states the founding year (2006), location (London), acquisition by Great Hill Partners (2021), merger with Edenred (2023), and target market (mid-to-large enterprises).
• Press room discloses acquisition sum of GBP 1.15 billion — The press releases page includes the acquisition amount (GBP 1.15 billion), a detail that cold knowledge lacked. This information is available for crawlers to index.