# Preparación para AI de paypal.com
> Medido en la página de inicio. Calificación general: Bueno.
Puntuación 71/100, nota Bueno. Medido 2026-09-04T22:32:09.294+00:00, motor ax-audit@4.1.0.
## Comprobaciones
### Contenido — 80/100
#### Content Negotiation — 0/100
- **FAIL** Homepage does not serve Markdown via content negotiation
Got text/html (HTTP 200) for "Accept: text/markdown"
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.
https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No fallback found on the homepage
If you cannot enable content negotiation, advertise a Markdown version with so agents can discover it.
https://axrush.com/guides/content-negotiation#no-alternate
#### Operabilidad para agentes — 95/100
- **PASS** 52/52 interactive elements have an accessible name
- **WARN** 1/1 iframes have no title
An untitled frame is an opaque region. A title tells an agent whether it is worth entering.
https://axrush.com/guides/agent-operability#iframe-no-title
- **PASS** Method note: this reads markup, not a rendered accessibility tree
Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.
#### Structured Data — 90/100
- **PASS** 4 JSON-LD block(s) found
- **PASS** @context references schema.org
- **WARN** No @graph array (single-entity only)
Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
https://axrush.com/guides/structured-data#no-graph
- **PASS** Key types found: WebSite, WebPage
- **WARN** No BreadcrumbList found
Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
https://axrush.com/guides/structured-data#no-breadcrumb
- **WARN** 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.
https://axrush.com/guides/structured-data#no-author
- **WARN** No sameAs links
sameAs is what turns a name into an entity. Link your Organization or Person to Wikidata, LinkedIn, GitHub or Crunchbase so a model can connect this page to what it already knows.
https://axrush.com/guides/structured-data#no-same-as
- **WARN** 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.
https://axrush.com/guides/structured-data#no-dates
- **PASS** Structured-data headings appear in the visible text
#### HTML Rendering — 85/100
- **PASS** Server-rendered content detected (403 words, 2610 chars of visible text)
- **WARN** Low text-to-markup ratio (1.3%)
Recommended minimum: 5%
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
https://axrush.com/guides/html-rendering#low-ratio
- **PASS** Semantic landmarks present (section, header, footer, nav)
- **WARN** 2
headings found (recommend exactly 1)
Use a single
per page to clearly mark the primary topic. Demote secondary headings to
+.
https://axrush.com/guides/html-rendering#multiple-h1
- **PASS** 2/2 tags have alt attributes
#### SEO Basics — 100/100
- **PASS** length 66 chars: "Envíe y solicite pagos, compre, administre pagos y más | PayPal UY"
- **PASS** Meta description length 151 chars
- **PASS** Canonical URL: https://www.paypal.com/uy/home
- **PASS** <html lang="es-UY">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1, shrink-to-fit=no"
### Acceso — 93/100
#### TLS / HTTPS — 100/100
- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=31536000
- **PASS** HSTS includes subdomains
- **PASS** HSTS preload-eligible
#### Agent Access — 100/100
- **PASS** All 10 core AI crawler user-agents receive the same page as a regular client
#### Directivas de IA — 100/100
- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page
#### Higiene HTTP — 70/100
- **WARN** A missing page redirects (301) instead of returning 404
Location: https://www.paypal.com/ax-audit-probe-oh1hdxg9
A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
https://axrush.com/guides/http-hygiene#soft-404-redirect
- **WARN** Homepage takes 2 redirects to answer
301 → https://www.paypal.com/
302 → https://www.paypal.com/uy/home
Every hop is a round trip the agent pays for, and some clients cap redirects well below a browser. Collapse the chain: point the first URL straight at the final one.
https://axrush.com/guides/http-hygiene#redirect-chain
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset
#### Crawl Efficiency — 70/100
- **PASS** Response compressed with Brotli (br)
- **WARN** 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.
https://axrush.com/guides/crawl-efficiency#no-validators
- **PASS** Homepage size is reasonable (195.8 KB decompressed)
- **WARN** Roughly 653 tokens of content in 49,238 tokens of response (99% markup)
Estimated at four characters per token.
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 1268ms
### Descubrimiento — 75/100
#### LLMs.txt — 90/100
- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/plain)
- **PASS** H1 heading: "PayPal"
- **WARN** No blockquote description found ("> ...")
Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
https://axrush.com/guides/llms-txt#missing-blockquote
- **PASS** 7 section heading(s) found
- **PASS** 151 link(s) found
- **WARN** /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.
https://axrush.com/guides/llms-txt#missing-full
- **WARN** 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.
https://axrush.com/guides/llms-txt#no-describedby
- **FAIL** 1/15 sampled llms.txt link(s) are broken
https://www.paypal.com/us/shopping-selection (HTTP 404)
An index of dead links wastes exactly the budget it was meant to save, and an agent has no way to tell a moved page from a removed one. Revalidate llms.txt when you move pages.
https://axrush.com/guides/llms-txt#broken-links
- **WARN** No per-page Markdown mirror found
Tried /index.md and /index.html.md.
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.
https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.
#### Robots.txt — 60/100
- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
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.
https://axrush.com/guides/robots-txt#no-core-crawlers
- **PASS** Sitemap directive present
- **WARN** 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.
https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
https://axrush.com/guides/robots-txt#low-coverage
#### Meta Tags — 51/100
- **WARN** 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">.
https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** 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">
https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** 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">
https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** 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">.
https://axrush.com/guides/meta-tags#no-rel-me
- **PASS** OpenGraph required tags present (og:title, og:description, og:url, og:type)
- **WARN** OpenGraph recommended tags missing: og:site_name
Add these for richer previews: og:site_name.
https://axrush.com/guides/meta-tags#og-recommended-missing
- **PASS** Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
#### Sitemap — 100/100
- **PASS** Sitemap located: https://www.paypal.com/paypal-sitemap-index.xml
- **PASS** Content-Type is XML (text/xml)
- **PASS** Sitemap-index references 1213 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 1768 URL(s) across 3 child(ren)
#### HTTP Headers — 85/100
- **PASS** 5/7 security headers present
- **WARN** 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"
https://axrush.com/guides/http-headers#no-link-header
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
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.
https://axrush.com/guides/http-headers#discovery-relations
### Protocolos — 0/100
#### Agent Card (A2A) — 0/100
- **FAIL** /.well-known/agent-card.json not found
Site is agent-facing (an API surface (navigation into an API or developer area)). Also tried the pre-0.3 path /.well-known/agent.json. IANA-registered well-known URI.
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/
https://axrush.com/guides/agent-card#not-found
#### OpenAPI Spec — 0/100
- **FAIL** API surface present but no machine-readable description found
Evidence of an API: navigation into an API or developer area. Checked /.well-known/api-catalog, Link and <link> rel="service-desc", and /.well-known/openapi.json, /openapi.json, /openapi.yaml, /.well-known/openapi.yaml, /api/openapi.json, /v1/openapi.json, /swagger.json, /api-docs, /asyncapi.json, /arazzo.json
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.
https://axrush.com/guides/api-discovery#not-found
#### MCP (Model Context Protocol) — N/D
- **PASS** No MCP server — MCP discovery does not apply to this site
A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.
#### Catálogo de IA — 0/100 (informa, no puntúa)
- **WARN** No agent resource catalog found
Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
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.
https://axrush.com/guides/ai-catalog#not-found
#### Habilidades de agente — 0/100
- **WARN** No Agent Skills published
Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
https://axrush.com/guides/agent-skills#not-found
#### WebMCP — N/D
- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool
#### Descubrimiento de comercio — 0/100 (informa, no puntúa)
- **WARN** Site sells something but publishes no agent-readable commerce profile
Commerce signals found: links to a cart or checkout. Checked /.well-known/ucp, /.well-known/ucp.json.
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.
https://axrush.com/guides/commerce-discovery#not-found
#### Descubrimiento de autenticación — N/D
- **PASS** Nothing on this site requires authorization — auth discovery does not apply
No API description, API catalog, MCP server card or commerce profile found.
### Política — 43/100
#### Security.txt — 75/100
- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **FAIL** Required field "Expires" missing (RFC 9116)
Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
https://axrush.com/guides/security-txt#missing-field
- **PASS** 3/5 optional fields present
#### RSL License — 0/100
- **FAIL** No RSL license discovery found
Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
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.
https://axrush.com/guides/rsl#not-found
#### Política de uso — 40/100
- **WARN** No machine-readable usage policy declared
Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
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.
https://axrush.com/guides/usage-policy#no-policy
---
Representación en Markdown de https://axrush.com/report/paypal.com