paydo.com — AI Site Grade

Analysis

PayDo: Open to All AI Crawlers, Invisible to the Open Web

PayDo has an llms.txt file and grants every major AI crawler unfettered 200-level access with full content — yet the cold LLM knowledge about the brand is already more detailed and accurate than what most sites with far less technical openness achieve, revealing a striking asymmetry between technical AI-readiness and external discoverability.

Crawler Access

Every AI bot tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, anthropic-ai, ChatGPT-User, Perplexity-User — receives a 200 status with 192KB of identical content matching the browser baseline. No UA-based blocking, no Cloudflare challenge, no JS shell. The robots.txt contains zero AI-bot-specific directives; the wildcard * rule disallows standard WordPress admin paths and a handful of pricing pages (/pricing-for-checkout/, /personal-pricing/, /pricing-for-business/) but leaves the entire public site open. The site runs on Cloudflare (NS: charles.ns.cloudflare.com / roxy.ns.cloudflare.com) with AWS-hosted A records (15.197.64.52, 3.33.243.156) and HSTS enabled. No JS rendering risk — all pages serve full HTML content on first GET.

llms.txt and Sitemap Posture

PayDo is an outlier in having a functional, auto-generated llms.txt (88KB, generated by All in One SEO v4.9.5.1) that lists blog posts, the sitemap, and a site description. This is rare among EMIs. The sitemap.xml is a sitemap index with 14 sub-sitemaps covering posts, pages, careers, case studies, events, a glossary (242 URLs), news, and tags — indicating a large content footprint (hundreds of pages). The glossary sitemap alone contains ~200+ financial term definitions, which are strong answer-signal content for LLM retrieval.

Cold-Knowledge Gap

The cold LLM (no search) already knows PayDo is a UK FCA-regulated EMI (FRN 900594), offers multi-currency IBANs, virtual/physical cards, mass payouts, and serves SMEs, e-commerce, and freelancers. It even references Trustpilot reviews mentioning verification delays — a detail the site itself does not surface. The gap is not in what the model knows but in what the site fails to reinforce: the MFSA Malta licence (secured August 2025), the Canada FINTRAC registration, the stablecoin partnership with BVNK (May 2026), and the direct SEPA/SEPA Instant integration (November 2025) are all absent from the cold model's knowledge. These are recent, high-signal regulatory and product milestones that the site publishes as news articles but that have not yet propagated into the model's training data.

Schema and Content Signals

The homepage and all key pages carry Organization + WebPage + BreadcrumbList JSON-LD schema, but critically no Product, Service, or FAQPage schema despite the homepage containing an explicit FAQ section with Q&A pairs. The business page includes a comparison table (PayDo vs Traditional Bank vs Payment Platform) rendered as visible HTML text — a strong answer-signal format — but it is not marked up as a Table or Comparison schema. The max-snippet:0 robots meta tag on every page is a self-inflicted visibility constraint: it tells Google (and by extension Google-Extended) to show zero-character snippets in search results, reducing the brand's SERP real estate.

External Signals

External search results for PayDo are essentially absent. Searches for "PayDo reviews", "PayDo Trustpilot", "PayDo Reddit", and "PayDo fintech news" returned zero results from DuckDuckGo. The cold LLM references Trustpilot reviews, but no Trustpilot page surfaced in live search. The site's own news section lists partnerships (BVNK, InCore Bank, Gigadat, PlayerAuctions, Uplatform, Melbet, Difmark) and the MFSA licence — but none of these appear to have generated independent press coverage indexed by search engines. This creates a near-total external citation vacuum: an AI engine doing live retrieval would find almost nothing about PayDo outside paydo.com itself.

Findings

1. No Product or Service schema on key pages High

   The homepage and business pages lack Product, Service, or FAQPage JSON-LD schema despite containing FAQ sections and comparison tables that would benefit from structured markup.

   What to change: Add Product, Service, and FAQPage JSON-LD schema to the homepage and business pages, marking up the FAQ section and comparison table.

2. max-snippet:0 meta tag limits search snippets High

   Every page includes a robots meta tag with max-snippet:0, which tells Google to show zero-character snippets in search results, reducing SERP visibility.

   What to change: Remove the max-snippet:0 directive or change it to a larger value (e.g., max-snippet:-1) to allow snippets.

3. Near-zero external search results for PayDo High

   Searches for 'PayDo reviews', 'PayDo Trustpilot', 'PayDo Reddit', and 'PayDo fintech news' returned zero results on DuckDuckGo, indicating a lack of indexed third-party coverage.

   What to change: Invest in PR and link-building to generate independent press coverage and reviews on platforms like Trustpilot.

4. Recent regulatory and product milestones absent from cold LLM knowledge Medium

   The MFSA Malta licence, Canada FINTRAC registration, stablecoin partnership with BVNK, and SEPA/SEPA Instant integration are published as news articles but have not yet propagated into the cold LLM's training data.

   What to change: Ensure these milestones are featured prominently on the homepage and business pages, and consider submitting press releases to wire services to accelerate indexing.

5. Comparison table on business page lacks structured markup Medium

   The business page includes a comparison table (PayDo vs Traditional Bank vs Payment Platform) rendered as visible HTML text but not marked up with Table or Comparison schema.

   What to change: Add Table or Comparison schema to the comparison table to enhance AI and search engine understanding.

6. Robots.txt disallows several pricing pages Medium

   The robots.txt disallows /pricing-for-checkout/, /personal-pricing/, and /pricing-for-business/ for all crawlers, preventing AI bots from accessing pricing information.

   What to change: Remove the disallow rules for pricing pages or allow AI bots specifically to access them.

7. FAQ section on homepage not marked up as FAQPage Medium

   The homepage contains an explicit FAQ section with Q&A pairs, but no FAQPage JSON-LD schema is present.

   What to change: Add FAQPage schema to the FAQ section on the homepage.

8. llms.txt not optimized for AI consumption Low

   The llms.txt is auto-generated by All in One SEO and lists many URLs but lacks a curated summary or prioritized links for AI crawlers.

   What to change: Manually curate the llms.txt to highlight key pages (e.g., business, pricing, news) and provide a concise site description.

What's working

• All AI crawlers receive full HTML content with 200 status — Every major AI bot tested receives a 200 status with 192KB of identical HTML content, matching the browser baseline. No JS rendering or blocking is required.
• Functional llms.txt with extensive URL listing — PayDo has a rare, auto-generated llms.txt (88KB) that lists blog posts, sitemaps, and a site description, providing a direct signal for AI crawlers.
• Large content footprint with glossary and news sections — The sitemap index contains 14 sub-sitemaps covering hundreds of pages, including a glossary with ~200+ financial term definitions and a news section with recent milestones.
• Cold LLM already knows key brand details accurately — The cold LLM correctly identifies PayDo as a UK FCA-regulated EMI, its services (multi-currency IBANs, cards, mass payouts), and target customers (SMEs, e-commerce, freelancers).
• No JavaScript rendering required for content — All pages serve full HTML content on first GET, eliminating the risk of AI crawlers encountering empty JS shells.
• Organization and WebPage schema present on key pages — The homepage and key pages include Organization, WebPage, and BreadcrumbList JSON-LD schema, providing basic structured data.