monzo.com — AI Site Grade

Analysis

Monzo.com AI-Visibility Audit

The homepage carries a single Organization JSON-LD schema block — but every other page on the site, including product pages, blog posts, and the about page, ships zero structured data. A site with 15+ million customers, multiple financial products (current accounts, savings, ISAs, investments, pensions, credit cards, insurance), and a blog publishing weekly engineering and research content has effectively no semantic markup for AI crawlers to consume beyond the homepage.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a full 200 response with identical byte size (227 KB) to a browser. No UA-based blocking exists. The site runs on AWS CloudFront behind Cloudflare DNS, with a strict CSP and HSTS preload. The robots.txt uses a single User-agent: * rule disallowing /docs/, /legal/files/, /blog/authors/, and referral paths, but no AI-bot-specific directives exist. The llms.txt returns a 404 — the site has no AI-friendly content map.

Content & Schema Posture

Only the homepage has structured data: a single Organization schema with name, founding date, address, and social links. The /current-account, /savings-isas, /investments, /pensions, /features/cashback, /features/monzo-payday, /security, /about, and every blog post all return zero JSON-LD. No Product, FAQPage, FinancialProduct, BankAccount, SavingsAccount, InvestmentFund, or Article schema exists anywhere. The /savings-isas and /features/travel pages are cookie-walled shells — they render only the cookie banner (83 words of visible text) and no product content to crawlers that don't accept marketing cookies. The /investments page has a rich FAQ section with 6+ Q&A pairs but no FAQPage schema. The /current-account/plans page has a detailed comparison table (Extra vs Perks vs Max) with pricing, features, and interest rates — all in plain HTML with no Comparison or Table schema.

Cold-Knowledge Gap

The LLM knows Monzo as a "UK-based digital bank (challenger bank)" with "over 9 million users," "Pots," "fee-free foreign spending," and a founding date of 2015. The site itself claims 15+ million customers — a 60% gap the model is behind on. The model knows nothing about Monzo's pension consolidation product, investment platform (BlackRock iShares funds, themed funds), cashback program, Double Payday promotion, Billsback feature, or the Extra/Perks/Max subscription tiers. The model also references a "US scaled-back" narrative that the site's active US sitemap (/us-sitemap.xml with 2026-dated URLs) contradicts.

External Signals

The homepage links to Trustpilot and Which? (recommended 2 years in a row). DNS TXT records show verification tokens for OpenAI, Anthropic, and Cursor — Monzo has proactively verified its domain with at least three AI/LLM providers, yet has no llms.txt and no per-page schema to feed those verified crawlers structured content. The blog (last published May 2026) is active with engineering, data science, and research posts, but none carry Article or BlogPosting schema.

Surprising Findings

The /sitemap.xml path returns a 404 — the actual sitemap index lives at /sitemap-index.xml (which works), but the conventional path is broken. The UK sitemap contains thousands of URLs (1.3 MB XML) with hreflang annotations for 6 locales, yet the site has no canonical sitemap discovery path. The US sitemap still lists blog posts from 2019-2021 (Monzo's abandoned US expansion) with priority: 0.5 — stale content that AI crawlers will index as current. The /about page (264 words) is thinner than the cookie banner on some product pages.

Findings

1. Zero structured data on product, blog, and about pages High

   Only the homepage carries an Organization schema. All other pages, including current account, savings, investments, pensions, blog posts, and about page, have no JSON-LD markup. AI crawlers cannot semantically understand product details, FAQs, articles, or financial products.

   What to change: Add appropriate JSON-LD schema (Product, FinancialProduct, FAQPage, Article, BlogPosting) to every page type.

2. llms.txt returns 404 Medium

   The site has no llms.txt file, which is a recommended AI-friendly content map. This makes it harder for AI crawlers to discover and understand the site's content structure.

   What to change: Create an llms.txt file listing key pages and their descriptions.

3. Savings and travel pages are cookie-walled shells High

   The /savings-isas and /features/travel pages render only a cookie banner (83 words) to crawlers that do not accept marketing cookies. Product content is invisible to AI crawlers.

   What to change: Serve essential product content without requiring cookie consent, or use progressive enhancement to show content after consent.

4. Conventional /sitemap.xml returns 404 Medium

   The standard sitemap path /sitemap.xml returns a 404 error. The actual sitemap index lives at /sitemap-index.xml, but crawlers expecting the conventional path will find nothing.

   What to change: Redirect /sitemap.xml to /sitemap-index.xml or serve the sitemap index at the conventional path.

5. US sitemap contains stale blog posts from 2019-2021 Medium

   The US sitemap lists blog posts from Monzo's abandoned US expansion, with priority 0.5. AI crawlers may index these as current content, creating confusion about Monzo's market presence.

   What to change: Remove or noindex outdated US blog posts from the sitemap.

6. LLM knowledge of customer count is 60% behind actual Medium

   The LLM knows Monzo has 'over 9 million users', but the site claims 15+ million customers. This gap means AI-generated summaries will understate Monzo's scale.

   What to change: Ensure the homepage and about page prominently display the current customer count in structured data.

7. Investments FAQ section lacks FAQPage schema Medium

   The /investments page has a rich FAQ section with 6+ Q&A pairs, but no FAQPage schema is present. AI crawlers cannot extract these Q&As for use in search or voice assistants.

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

8. Blog posts lack Article or BlogPosting schema Medium

   The blog publishes weekly engineering and research content, but none of the posts carry Article or BlogPosting schema. AI crawlers cannot identify authors, publish dates, or article structure.

   What to change: Add Article or BlogPosting schema to all blog posts.

9. About page is very thin (264 words) Low

   The /about page contains only 264 words, which is less content than the cookie banner on some product pages. This limits the information AI crawlers can gather about Monzo's mission, history, and team.

   What to change: Expand the about page with more detailed content about the company's history, values, and leadership.

10. Robots.txt has no AI-bot-specific directives Low

    The robots.txt uses a single User-agent: * rule and does not explicitly allow or disallow AI crawlers like GPTBot, ClaudeBot, or PerplexityBot. While they are not blocked, the lack of explicit directives may cause some crawlers to be cautious.

    What to change: Add explicit allow directives for major AI crawlers to ensure optimal crawling.

What's working

• Homepage has Organization schema with key details — The homepage includes a single Organization JSON-LD block with name, founding date, address, and social links, providing basic entity information to AI crawlers.
• All major AI crawlers receive full 200 responses — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others all get a full 200 response with identical content to a browser. No UA-based blocking exists.
• Domain verified with OpenAI, Anthropic, and Cursor — DNS TXT records show verification tokens for OpenAI, Anthropic, and Cursor, indicating proactive domain verification with major AI/LLM providers.
• Active blog with engineering and research posts — The blog publishes weekly content on engineering, data science, and research, which can be valuable for AI crawlers if properly structured.
• Links to Trustpilot and Which? recommendations — The homepage links to Trustpilot and Which? (recommended 2 years in a row), providing external trust signals that AI crawlers can use to assess credibility.
• UK sitemap has hreflang annotations for 6 locales — The UK sitemap contains thousands of URLs with hreflang annotations for 6 locales, helping AI crawlers understand language and regional targeting.
• Plans page has detailed comparison table in plain HTML — The /current-account/plans page includes a comparison table with pricing, features, and interest rates for Extra, Perks, and Max plans, all in plain HTML that crawlers can parse.
• Strict CSP and HSTS preload in place — The site uses a strict Content Security Policy and HSTS preload, which are good security practices that also signal trustworthiness to AI crawlers.