AI Readiness analysis based on 11 scans, most recently 2026-04-13 03:21 UTC. Programmatic scoring across 5 categories.
A B at 76/100 is a strong foundation. The basics are in place — the site is readable, discoverable, and mostly parseable by a retrieval model. What's left is usually the last 10-20% that separates a site AI engines notice from one they actively cite. The breakdown below points at the exact categories where the easy gains still sit.
ZeroKit's rubric splits AI Readiness into 5 independent categories. A host scores points inside each category up to a fixed maximum, and the overall 0-100 score is the sum. The five cards below show where the stripe.com score came from.
Strong — 100%
Whether pages carry parseable JSON-LD blocks (Organization, WebSite, Article, FAQPage, SoftwareApplication, BreadcrumbList…). Structured data is the canonical way to tell both search engines and LLMs what a page IS, not just what it says.
Multiple schema types in play, covering the site's identity, its content, and its navigation. AI answer engines cite structured pages at disproportionately high rates.
Strong — 95%
Whether the site ships an llms.txt file at the root — the emerging convention for handing an LLM a curated site map with headings, summaries, and direct links to the parts of the site a reader should actually see.
A well-formed llms.txt (with H1, H2 sections, summary blockquote, and a reasonable link count) tells any LLM exactly what the site is about without scraping ten pages.
Partial — 73%
Whether the page is easy for a retrieval model to quote: does it use real headings, short paragraphs, named entities, clear fact statements, and server-rendered text (not JavaScript placeholders)?
Content is readable but occasionally buried in client-side rendering or generic boilerplate. Pre-render the hero and the top two sections of each page so the HTML source contains the quotable text.
Partial — 60%
Whether pages set the specific meta tags (noai, noimageai, robots, googlebot) that modern AI pipelines honour — and whether those directives are internally consistent with the robots.txt policy.
Meta directives are partially set. Audit the <head> across templates and ensure each public page carries <meta name="robots" content="index,follow"> at minimum.
Partial — 50%
Whether the site publishes an explicit allow/disallow list for the major AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, and friends) so training and live-retrieval agents know where they stand.
Robots.txt exists but misses some of the newer AI user-agents. A one-line addition for each of GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot covers 90% of the crawl volume.
These are the categories where stripe.com is already giving AI crawlers what they look for. Hold the line here; regressions in the working categories cost more than gains in the weak ones.
The biggest gains on this host live in the categories below. Each fix is independent — you do not need to finish one before starting the next — and each fix is a one-time piece of work that keeps paying out every time an AI crawler visits.
ZeroKit fetches the target URL once per scan with a standard browser User-Agent, then makes a small number of additional requests for the conventional files an AI crawler would look for: /robots.txt, /llms.txt, /sitemap.xml, and a handful of well-known meta endpoints. The returned HTML is parsed for JSON-LD blocks, OpenGraph, Twitter Cards, and AI-specific meta directives. Nothing private is stored — only the derived score and category breakdown.
The exact rubric and every signal we check is documented on the AI Readiness Checker page. This analysis is regenerated daily when fresh scan data lands in the database.
Analysis auto-generated from the most recent scan data for stripe.com. The narrative text is templated from the score distribution and does not imply manual review. For a human-reviewed audit, buy the full report above.