We Ran stripe.com Through Our 18 AI-Readiness Checks. It Scored 95.
Published · 4 min read
On 15 October 2026 we pointed our free scanner at stripe.com. It runs the same 18 deterministic checks on every site: whether AI crawlers are allowed in, whether the page can be discovered and parsed, and whether its content is structured so an engine could quote it. Stripe scored 95 out of 100, grade A.
You can re-run it yourself: aaivisibility.com/results/stripe.com. Scores change when sites change, so the page you open may show a newer scan than this post.
What the score is, and what it isn’t
The score measures technical readiness: can an AI engine reach, read and quote the page? It does not measure how often ChatGPT, Claude, Perplexity or Gemini actually cite stripe.com. That needs repeated sampling of real answers, reported with a sample size and a confidence interval, and we did not sample Stripe for this post.
The result, category by category
| Category | Points | What it covers |
|---|---|---|
| AI Crawler Access | 30 / 30 | All 22 AI crawlers we track are allowed by robots.txt |
| Machine Discovery | 12 / 15 | llms.txt present, sitemap declared in robots.txt, no feed found |
| Structured Data | 16 / 16 | Valid JSON-LD with Organization and WebSite, Open Graph, canonical |
| Content Citability | 23 / 25 | Title and meta description in range, 5 H2s, lists, about 1,900 words; two H1s |
| Technical Trust | 10 / 10 | HTTPS, HTTP 200, fast response |
That adds up to 91 of 96 points. Article/FAQ schema was marked not applicable (a home page with no FAQ-style headings isn’t expected to carry it), so its 4 points left the denominator, and 91 of 96 is reported as 95.
The two findings
1. Two H1 tags (warning, 2 of 4 points). The check wants exactly one H1 that says what the page is. Two H1s are valid HTML; they just give a parser two candidates for “the main heading”. The fix is to keep one H1 and turn the other into an H2.
2. No RSS or Atom feed found (fail, 0 of 3 points). The scanner found no feed linked from the home page. A feed is a conventional way to announce new articles to tools that poll for them; our own fix text calls it optional. For a site that publishes articles, adding one is usually a small change.
What Stripe does well
- Every AI crawler is allowed. That category is 30 of the 100 points, and one blanket robots.txt rule can lose all of it.
- It publishes an llms.txt, a proposed convention for a plain-text map of a site for language-model tools. Some tools read it; Google states its Search does not use it, and we score it as a convention, not a requirement.
- Its Organization schema is present and parses cleanly, alongside Open Graph tags and a canonical URL.
What we would not conclude
- Not that Stripe is “visible in AI”. Readiness is a precondition, not an outcome.
- Not that 95 beats anyone. We publish no study of other payment companies.
- Not that the two findings cost Stripe anything measurable. We have no evidence either way.
Disclosure: we use Stripe for checkout. Stripe did not review this post and is not affiliated with Aura AI Visibility. Stripe is a trademark of its owner, used here only to identify the site we scanned.