Rapporto del sito: 1 pagina misurata. Valutazione complessiva: Buono.
Punteggio del sito · stripe.com
Combina l'origine e 1 pagina misurata. Il report qui sotto dettaglia soltanto la pagina di origine.
Porta i risultati a chi può risolverli. Copia un riepilogo pronto per Slack, Teams o la prossima riunione.
Questo rapporto è pubblico. Il team può aprirlo senza un account.
C'è sostanza che un agente possa leggere?
Homepage does not serve Markdown via content negotiation
Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
No <link rel="alternate" type="text/markdown"> fallback found on the homepage
If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
28/212 buttons or links have no accessible name
An agent addresses a control by its name: it presses button "Search", not the button at 412×88. Give each one visible text, an aria-label, or an image with alt text.
Method note: this reads markup, not a rendered accessibility tree
Server-rendered content detected (1885 words, 12863 chars of visible text)
Low text-to-markup ratio (2.0%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Semantic landmarks present (main, section, header, footer, nav)
2 <h1> headings found (recommend exactly 1)
Use a single <h1> per page to clearly mark the primary topic. Demote secondary headings to <h2>+.
35/35 <img> tags have alt attributes
1 JSON-LD block(s) found
@context references schema.org
@graph array present (multi-entity structured data)
Key types found: Person, Organization, WebSite
No BreadcrumbList found
Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
No author declared in structured data
An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
12 sameAs link(s) tie your entity to external identifiers
Organization carries disambiguating detail (registration, legal address or contact point)
No dateModified or datePublished in structured data
Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.
3 structured-data value(s) do not appear in the visible text
Google’s one explicit requirement for structured data and AI features is that it match what a reader sees. Markup describing a page that is not there is the oldest form of spam, and it is now graded by systems that quote it. Note this compares the static HTML, so text rendered by script will read as missing here too.
<title> length 54 chars: "Stripe | Financial Infrastructure to Grow Your Revenue"
Meta description length 149 chars
Canonical URL: https://stripe.com/
<html lang="en-US">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1, viewport-fit=cover"
Un agente riesce a recuperarla?
Response compressed with gzip
No ETag or Last-Modified header — conditional requests unsupported
Send an ETag or Last-Modified header so crawlers can revalidate with If-None-Match / If-Modified-Since and receive a cheap 304 Not Modified instead of the full body.
Homepage is on the large side (637.4 KB decompressed)
Consider trimming inlined payloads to reduce crawl cost.
Roughly 3,216 tokens of content in 162,907 tokens of response (98% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 38ms
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=63072000
HSTS includes subdomains
HSTS preload-eligible
All 10 core AI crawler user-agents receive the same page as a regular client
Homepage is indexable
No directive restricts how AI assistants may use this page
Missing pages return 404
Homepage answers without a redirect
HEAD requests are supported
Content-Type: text/html with charset
Un agente trova ciò che pubblichi?
No AI meta tags (ai:*) found
Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
No rel="alternate" link to llms.txt in HTML
Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
No rel="alternate" link to the Agent Card in HTML
Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
No rel="me" identity links found
Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
OpenGraph required tags present (og:title, og:description, og:url, og:type)
OpenGraph recommended tags missing: og:site_name
Add these for richer previews: og:site_name.
Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
/robots.txt exists
No core AI crawlers explicitly configured
Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
Sitemap directive present
No Content-Signal directive found (optional)
Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
5/7 security headers present
No Link header for AI discovery (llms.txt, Agent Card)
Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
No machine-readable discovery relations beyond llms.txt and the Agent Card
Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
/llms.txt exists
/llms.txt Content-Type OK (text/plain)
H1 heading: "Stripe"
Blockquote description present
30 section heading(s) found
288 link(s) found
/llms-full.txt not found (optional but recommended)
Create a /llms-full.txt with expanded content — full documentation, API details, and comprehensive site information for AI agents.
/llms.txt is 64 KB
An index this large competes with the content it points at for context budget. Keep llms.txt to a map of links and move the prose into llms-full.txt or the pages themselves.
No rel="describedby" link to llms.txt
llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
1 duplicate link(s) in llms.txt
Each URL should appear once. Duplicates spend an agent’s budget re-reading what it already has.
15 sampled link(s) resolve
No per-page Markdown mirror found
llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
Consumer note: llms.txt is read by coding agents, not by search
Sitemap located: https://stripe.com/sitemap/sitemap.xml
Content-Type is XML (application/xml)
Sitemap-index references 9 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 3330 URL(s) across 3 child(ren)
Che cosa può chiamare un agente?
/.well-known/agent-card.json not found
This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
API surface present but no machine-readable description found
The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
No agent resource catalog found
A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
Site sells something but publishes no agent-readable commerce profile
Publish a Universal Commerce Protocol profile at /.well-known/ucp so an agent can find your catalog, cart and checkout without a human. Note that the alternatives are not discoverable by design: the OpenAI and Stripe Agentic Commerce Protocol defines no manifest, and AP2 advertises itself through an A2A card extension.
Agent Skills index published at /.well-known/skills/index.json
Skills index declares no $schema
Add "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json" so a consumer knows which revision this is.
8 skill(s) listed
No skill declares a content digest
A digest lets an agent verify it installed the skill you published, and notice when it changes. Add "digest": "sha256:…" to each entry.
No skill entry carries a url
Each entry needs a url pointing at its SKILL.md or archive, or an agent cannot install it.
No MCP server — MCP discovery does not apply to this site
No forms and no WebMCP code — nothing here for an agent to invoke as a tool
Nothing on this site requires authorization — auth discovery does not apply
Quali diritti d'uso sono dichiarati?
No RSL license discovery found
Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
No machine-readable usage policy declared
State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
/.well-known/security.txt exists
Required field "Contact" present
Required field "Expires" present
Expires date is in the future (2026-12-31)
4/5 optional fields present
Dai al team rapporti completi, correzioni prioritarie e monitoraggio per mantenere i miglioramenti dopo ogni rilascio.