Login walls and gated content: what AI agents can reach

An AI agent acting for a customer usually doesn't have that customer's password, and it can't create accounts or pay for subscriptions on a whim. Anything you put behind a login or a paywall is, for most agents, simply not there. That's often the right call. But many sites hide things that should be public, and lose recommendations because of it.

What agents can and can't reach

Different kinds of agent meet a login wall in different ways:

Kind of agent	Behind a login or paywall
AI assistants fetching a page for a question	Get the login page or the paywall, and answer from whatever is visible
AI search and training crawlers	Index only what's public, unless you choose to show them more
Browser agents carrying out a task	Usually stop and ask the person to sign in, or give up. Some can hand control back to the person for the sign-in step

So the question for each page is simple: if an agent can only see the public version, can it still answer the customer's question and move them forward?

What to keep public

These are the things agents are most often asked about. If they sit behind a login, the agent either says it doesn't know or quotes a competitor who shows them openly.

• Prices. "Sign in to see price" and "add to cart to see price" hide the one fact shoppers ask about most. If you can't show an exact price, show a starting price or a range. See machine-readable prices.
• Product information. Specifications, sizes, materials, compatibility and stock. A catalog that only appears after sign-in is invisible to agents.
• Policies. Shipping, returns, warranty and payment options. These decide many purchases, and agents quote them directly. See shipping, returns and FAQ pages AI assistants can quote.
• Plans and pricing for software. What each plan includes and costs, and whether there's a free trial. See agent readiness for software companies.
• Help content. Setup guides, FAQs and documentation. If your help center needs a login, assistants can't answer support questions about your product.
• Contact and location details. Opening hours, addresses and how to reach you.

Trade and wholesale businesses often hide everything, because prices vary by customer. Consider showing the catalog and list prices publicly, with a note that account holders get their own prices after signing in. The agent can then recommend you and send the buyer to log in for the final number.

What can stay behind the wall

Plenty of content belongs there: order history, saved addresses, account settings, customer-specific prices, members-only content and paid articles. The goal isn't to remove logins. It's to make sure the wall sits in front of private and paid things, not in front of the information a customer needs to decide.

Handing off to the person

When an agent does reach something that needs the customer, make the handoff smooth:

• Say what's needed in plain text. "Sign in to see your order history" is something an agent can relay. A login form with no explanation isn't.
• Return to the same place. After sign-in, send the person back to the page or cart they were on, with the cart intact, so the agent's work isn't lost.
• Don't require an account to buy. Guest checkout lets an agent finish a purchase without creating an account for someone. AgentScore checks for it in Shoppers can check out without an account, and our guide to guest checkout explains why it matters.
• Use proper status codes. Redirect to a login page, or return 401 or 403, rather than a 200 page that looks like content but isn't. Agents and crawlers can then tell "this needs a login" from "this page says nothing".
• Make sign-in forms agent-friendly. Labelled fields and standard autocomplete values help browser agents and password managers alike. See sign-up, booking and lead forms AI agents can finish.

Paywalls and structured data for publishers

Publishers face a specific version of this. You may want search engines to see the full article so they can rank it, while readers see a paywall. Showing crawlers different content from readers can look like cloaking. Google's documented answer is paywalled content structured data: you mark the article as not free, and point to the part that's behind the paywall.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "How trail running shoes are tested",
  "isAccessibleForFree": false,
  "hasPart": {
    "@type": "WebPageElement",
    "isAccessibleForFree": false,
    "cssSelector": ".paywalled-content"
  }
}
</script>

The cssSelector must match a class on the element that wraps the paid content. Google explains the details in its paywalled content guidelines, and the properties are defined at schema.org.

Two things to keep in mind:

• The markup describes access; it doesn't grant it. Whether you show full articles to any crawler, including AI search and training crawlers, is a business and licensing decision. Make it deliberately, per agent, and reflect it in robots.txt and your CDN rules.
• Give agents something to cite. A clear headline, a summary paragraph and the key facts above the paywall let assistants describe and link to your article even when they can't read it all. A paywall that hides everything, headline included, gets you nothing.

How to check your own site