Checked 9/4/2026 · https://stripe.com/gb
No hard blockers, but 1 points weaken AI discoverability.
Nothing has changed since the last scan of this URL.
AI crawler matrix
For each bot: what your robots.txt allows — and what your server actually returns to the bot's user agent. Rows highlighted in red: robots allows it, but the server blocks it (usually a WAF or bot-protection rule).
| Bot | Operator | robots.txt | Server response |
|---|---|---|---|
| GPTBot | OpenAI | allowed (via User-agent: *) | 200 + content |
| OAI-SearchBot | OpenAI | allowed (via User-agent: *) | 200 + content |
| ChatGPT-User | OpenAI | allowed (via User-agent: *) | 200 + content |
| ClaudeBot | Anthropic | allowed (via User-agent: *) | 200 + content |
| Claude-SearchBot | Anthropic | allowed (via User-agent: *) | 200 + content |
| Claude-User | Anthropic | allowed (via User-agent: *) | 200 + content |
| PerplexityBot | Perplexity | allowed (via User-agent: *) | 200 + content |
| Perplexity-User | Perplexity | allowed (via User-agent: *) | 200 + content |
| Google-Extended | Google (Gemini-Training) | allowed (via User-agent: *) | — |
| Googlebot | Google (KI-Übersichten) | allowed (via User-agent: *) | 200 + content |
| CCBot | Common Crawl (Trainingsdaten vieler LLMs) | allowed (via User-agent: *) | 200 + content |
| Bytespider | ByteDance (Doubao) | allowed (via User-agent: *) | 200 + content |
| Amazonbot | Amazon (Alexa/Rufus) | allowed (via User-agent: *) | 200 + content |
| Applebot-Extended | Apple (Intelligence-Training) | allowed (via User-agent: *) | — |
| Meta-ExternalAgent | Meta (Llama/Meta AI) | allowed (via User-agent: *) | 200 + content |
How is the score calculated?
| Not exactly one H1 heading | -5 |
| No author or authorship signal | -4 |
| No visible or marked-up date | -3 |
| No FAQ or HowTo markup | -2 |
| Result | 86 / 100 |
Structure & machine understanding
Not exactly one H1 heading
The page has 2 H1 headings. A single, unambiguous H1 tells humans and machines what the page is primarily about.
This is what you should do: Set exactly one H1 that names the page's main topic. Everything below starts at H2.
No FAQ or HowTo markup
Question-and-answer and step-by-step content is harder for AI systems to recognise as directly citable answers without FAQPage or HowTo markup.
This is what you should do: Where the page answers real questions or gives instructions, mark it up as FAQPage or HowTo (no markup without visibly matching content).
Trust and entity signals (E-E-A-T)
No author or authorship signal
No author is recognisable (neither meta tag, rel=author nor JSON-LD Person). For "experience" and "expertise" in the E-E-A-T sense, named, traceable authorship matters.
This is what you should do: For editorial content, name an author and link an author page; also mark them up as JSON-LD "Person".
No visible or marked-up date
No publication or modification date is recognisable (neither <time>, article:published_time nor datePublished in the JSON-LD). For many questions, AI systems prefer current sources.
This is what you should do: For content with a time reference, show a date visibly and mark up datePublished / dateModified in the JSON-LD.
OK (9)
- llms.txt present and plausibly structured.
- The main content is in the HTML without JavaScript.
- Structured data (JSON-LD) is present. — WebSite, Organization
- The organisation is marked up as JSON-LD.
- A canonical URL is set.
- The sitemap is reachable.
- The page title has a sensible length.
- Fast server response time.
- No noindex — the page may be indexed.
Next steps
- Not exactly one H1 heading. Set exactly one H1 that names the page's main topic. Everything below starts at H2.
- No author or authorship signal. For editorial content, name an author and link an author page; also mark them up as JSON-LD "Person".
- No visible or marked-up date. For content with a time reference, show a date visibly and mark up datePublished / dateModified in the JSON-LD.
Weekly re-scan with an email alert on every change. In preparation — add your address.
Method & limits
Checked 9/4/2026. citeglass fetches stripe.com and its related files (robots.txt, llms.txt, sitemap.xml) over HTTP — once as a normal browser, once per AI crawler user agent. No JavaScript is executed. Time to first byte: 341 ms.
What this is not: No rank or citation tracking, no statement about whether a model actually names you, and no check of content loaded via JavaScript. A snapshot from the perspective of one server IP.