yaspa.com — AI Site Grade

Analysis

The Yaspa site is fully open to every AI crawler with no restrictions, yet the cold-knowledge gap is severe — LLMs describe a UK-based open banking fintech processing £1B+, while the site itself is entirely US-focused, mentions zero transaction volume, and has zero external web presence detectable via search.

Crawler Access

All 11 AI bots tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Bytespider, Applebot-Extended, Perplexity-User, and browser baseline) receive identical 200 responses with full 538KB HTML from the homepage. No UA-based blocking, no JS shell, no Cloudflare challenge. The robots.txt is a bare Yoast default — User-agent: * with Disallow: (empty, meaning allow all) — and names zero AI bots explicitly. The llms.txt returns a 404 (WordPress 404 page). The site runs on LiteSpeed behind AWS DNS, with no security headers (no HSTS, no CSP, no X-Frame-Options).

Cold-Knowledge Gap

The LLM prior describes Yaspa as a UK-based fintech founded in 2019, processing over £1B in transactions by 2023, serving iGaming/financial services/e-commerce with "Pay by Bank" and "Payouts" products. The actual site tells a fundamentally different story: every page redirects to /us/, the product line is rebranded around ACH-guaranteed payments (not UK open banking), the homepage touts "36x faster than cards" and conversion-rate metrics, and the about page reveals the company was founded in 2017 as "Citizen" and rebranded to Yaspa in October 2023. The £1B volume figure, the UK FCA regulation mention, and the e-commerce vertical are entirely absent from the live site. The /uk/ path returns a 404.

Schema Posture

Every page carries Yoast-generated WebPage, WebSite, Organization, and BreadcrumbList schema. The Organization schema lists only a single sameAs link (LinkedIn) — no Twitter/X, no Crunchbase, no Wikipedia. No Product, FAQPage, HowTo, or SoftwareApplication schema exists anywhere on the product pages. The Intelligent Payments page, which describes AI-powered behavioral analysis and fraud detection, has zero schema describing the software product itself. The datePublished values are in the future (2026), suggesting the site was recently rebuilt or staged.

External Signals

DuckDuckGo web search returns zero indexed results for queries including "Yaspa", "Yaspa payments", "Yaspa fintech", "Yaspa open banking", and "Yaspa iGaming". The DNS TXT records show an anthropic-domain-verification token, confirming the brand has proactively registered with Anthropic for Claude access — yet the site has no llms.txt and no AI-specific crawl guidance. The site also has google-site-verification, apple-domain-verification, and atlassian-domain-verification tokens, indicating active platform registrations that have not translated into search visibility.

Content Architecture Surprises

The blog contains ~170+ articles spanning 2023-2026, including the rebrand announcement from Citizen to Yaspa (September 2023). However, the blog lives under two URL structures — /blog/ (UK-root) and /us/blog/ (US-root) — with overlapping content and no clear canonicalization between them. The site has dedicated pages for Skill-based-gaming (capital S) and prediction-markets alongside online-gaming, suggesting a deliberate US-market vertical strategy. No FAQ, comparison tables, or structured answer-format content exists on any page. The developer documentation at docs.yaspa.com is password-protected, meaning AI crawlers cannot access technical integration details.

Findings

1. Severe cold-knowledge gap between LLM prior and live site High

   LLMs describe Yaspa as a UK-based open banking fintech processing over £1B, but the live site is entirely US-focused, mentions no transaction volume, and lacks UK references. The /uk/ path returns a 404.

   What to change: Add UK-specific content or redirect /uk/ to a relevant page, and include key metrics (e.g., transaction volume) on the homepage to align with LLM knowledge.

2. Zero indexed pages in web search results High

   Multiple web searches for Yaspa and related terms returned zero results, indicating the site has no organic search presence despite having a sitemap and blog.

   What to change: Investigate indexing issues (e.g., noindex tags, canonical errors, or server configuration) and submit sitemap to search engines.

3. llms.txt returns 404 Medium

   The llms.txt file, which provides AI crawlers with guidance on content to use, is missing and returns a WordPress 404 page.

   What to change: Create an llms.txt file that lists key pages and summaries for AI crawlers.

4. robots.txt lacks AI-specific directives Low

   The robots.txt is a bare Yoast default with no explicit rules for AI bots, missing opportunities to guide crawler behavior.

   What to change: Add explicit directives for AI bots (e.g., GPTBot, ClaudeBot) to control crawl rate and access.

5. No Product or SoftwareApplication schema on product pages Medium

   Product pages like Intelligent Payments and Online Gaming lack structured data describing the software, missing opportunities for rich results.

   What to change: Add SoftwareApplication or Product schema to product pages with name, description, and application category.

6. Schema datePublished values set in the future Medium

   Multiple pages have datePublished values in 2026, which may confuse crawlers and affect freshness signals.

   What to change: Update datePublished to actual publication dates or remove if not applicable.

7. Organization schema lists only one sameAs link Low

   The Organization schema includes only a LinkedIn URL, missing other social profiles (Twitter, Crunchbase, Wikipedia) that help establish entity identity.

   What to change: Add additional sameAs URLs for Twitter/X, Crunchbase, and Wikipedia if available.

8. Developer documentation is password-protected Medium

   The docs.yaspa.com subdomain requires authentication, blocking AI crawlers from accessing technical integration details.

   What to change: Make at least a summary or public version of the documentation available without authentication.

9. No FAQ or comparison tables on any page Low

   The site lacks FAQPage schema or comparison tables that could generate rich results and answer common queries.

   What to change: Add FAQ sections to key pages with FAQPage schema, and consider comparison tables for product differentiation.

10. Missing security headers (HSTS, CSP, X-Frame-Options) Low

    The site lacks HSTS, CSP, and X-Frame-Options headers, which may affect trust signals for AI crawlers.

    What to change: Implement HSTS, CSP, and X-Frame-Options headers to improve security posture.

What's working

• All AI crawlers receive full HTML content — All 11 tested AI bots receive identical 200 responses with full HTML, no blocking or JS shells.
• Yoast-generated schema on every page — Every page includes WebPage, WebSite, Organization, and BreadcrumbList schema, providing basic structured data.
• Anthropic domain verification token present — DNS TXT records include an anthropic-domain-verification token, indicating proactive registration with Anthropic for Claude access.
• Blog contains rebrand announcement and 170+ articles — The blog includes the Citizen-to-Yaspa rebrand announcement and over 170 articles, providing historical context.
• Multiple platform verification tokens in DNS — DNS TXT records include google-site-verification, apple-domain-verification, and atlassian-domain-verification tokens, showing active platform registrations.