How Stripe Made Its Product Line Easy for AI Tools to Recommend

A modern business website usually has multiple products, multiple audiences, and a navigation structure that makes sense to a human after a few clicks. AI assistants do not click. They read a curated map of your site and decide which page best answers a user question, then either cite that page directly or pull from it in a generated response. The structure of that map matters, and Stripe is one of the more thoughtful examples of how to build it.

The Stripe Example

Stripe is a payments and financial infrastructure platform with a sprawling product line, including payments, billing, invoicing, marketplace tools, point-of-sale hardware, and lending products. Each one has its own help pages, its own audience, and its own use cases. To help AI assistants navigate that complexity, Stripe published a file called llms.txt at the root of its website.

llms.txt is a small markdown file that acts as a curated map of a site for AI assistants. It lists the most important pages, organized into clear sections, with a short description of each page so an AI tool can understand the structure of the site without having to read every page first. We covered the format and why a major AI lab itself shipped one in our piece on Anthropic’s llms.txt adoption.

In practice, a Stripe-style llms.txt looks something like this:

# Stripe

> Stripe is a financial infrastructure platform for businesses. Our products power payments, billing, invoicing, marketplaces, point-of-sale, and lending.

## Payments

- [Accept a payment](https://docs.stripe.com/payments/accept-a-payment): Build a checkout flow with Stripe Elements or Checkout.
- [Payment methods](https://docs.stripe.com/payments/payment-methods): Cards, wallets, bank debits, and local payment methods.

## Billing

- [Subscriptions overview](https://docs.stripe.com/billing/subscriptions/overview): Recurring billing, trials, proration, and tax.
- [Invoicing](https://docs.stripe.com/invoicing): Send one-off and recurring invoices.

## Connect (marketplaces)

- [Connect overview](https://docs.stripe.com/connect): Build a platform that pays out to sellers, service providers, or contractors.
- [Account types](https://docs.stripe.com/connect/accounts): Choose between Standard, Express, and Custom connected accounts.

## Terminal (in-person)

- [Terminal overview](https://docs.stripe.com/terminal): Accept in-person payments with Stripe-certified hardware.

What makes the Stripe version notable is the structure. Instead of listing every page in a flat list, the file is organized by product category. Payments documentation sits under one heading, billing under another, and the marketplace product gets its own section with links to setup guides, payment processing pages, and dashboard help. An AI assistant like ChatGPT or Claude fielding a question about Stripe’s marketplace tools lands in the right neighborhood before it pulls a single page.

Why That Structure Matters

The format itself is simple, with section headings and a list of links under each one. The choices about what to put under which heading carry real weight. Those choices are the closest thing a brand has to telling an AI system how to categorize its content.

For Stripe, organizing by product is the obvious move because their customer base spans use cases that have very little overlap. A developer building a marketplace on Stripe has nothing to do with a small business owner setting up a basic payment link. The structure of the file keeps those audiences separated in a way an AI tool can understand and route correctly.

The same logic applies to any business with more than one product, service, or audience. A multi-service marketing agency, a software platform with several modules, or a consulting firm with distinct practice areas all face the same problem Stripe solved. Without a clear structure in the file, an AI tool may pull the wrong page or stitch together content from sections that should not be combined. We saw a version of this problem in our work building a confidential document search platform, where careful structuring of source material was the difference between accurate and misleading retrieval.

How to Apply This to a Smaller Site

Most businesses do not have the documentation scale Stripe has, and that is fine. The lesson is the principle, not the volume. The file should be organized the way you want an AI tool to categorize you, with section headings that match the questions buyers actually ask.

A useful exercise is to write down the five or six most common questions a prospect or AI assistant would have about your business. The answers to those questions become the section headings. Under each heading, list the main page that answers that question, with a short description of what the page covers. The file is short by design, usually under one hundred links, and the discipline of choosing what to include is what makes it useful.

For service businesses with treatment menus or service categories, this structural choice is even more important. We walk through that pattern in our pieces on dental websites and med spa treatment pages.

Where This Fits in an AEO Strategy

Answer Engine Optimization, or AEO, is the broader practice of making sure your site is clear, citable, and machine readable for the AI tools that now generate answers for users. AEO sits alongside traditional SEO and Generative Engine Optimization (GEO) as the layers of modern search visibility. Structured data tells search engines about the entities on a single page. llms.txt tells AI tools about the structure of your site as a whole. Both layers reinforce each other, and both are part of an AEO strategy that focuses on whether your content is clear enough to be cited and recommended.

The Stripe case is useful because it makes the structural decisions visible. Most brands publish llms.txt files that are flat lists of links with no organizing principle, which is fine for a small site but loses value as the content scales. Stripe shows what the file looks like when it is treated as a real piece of information architecture rather than a checkbox.

Audit Your Information Architecture

If you have a multi-product or multi-service business, the way your site is structured for AI tools matters more than most brands realize. Get an AEO audit to see whether your site architecture, your structured data, and your llms.txt are giving AI systems a clear path to the pages that drive your revenue.