Rapport du site : 1 page mesurée. Note globale : Moyen.
Score du site · visa.com
Combine l'origine et 1 page mesurée. Le rapport ci-dessous détaille uniquement la page d'origine.
Transmettez les constats à ceux qui peuvent les résoudre. Copiez un résumé prêt pour Slack, Teams ou votre prochaine réunion.
Ce rapport est public. Votre équipe peut l’ouvrir sans compte.
Y a-t-il de la substance qu'un agent puisse lire ?
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.
Server-rendered content detected (195 words, 1403 chars of visible text)
Low text-to-markup ratio (3.3%)
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, header, footer)
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
Heavy JavaScript with no <noscript> fallback
Provide a <noscript> fallback that explains the site or links to a non-JS variant. This helps agents that disable JS.
Only 9/11 <img> tags have alt attributes
Add descriptive alt="" to every <img>. Agents use alt text to understand images they cannot process visually.
2 JSON-LD block(s) found
@context references schema.org
No @graph array (single-entity only)
Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
Key types found: 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.
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.
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.
<title> length 53 chars: "Donde sea que te encuentres, Visa está contigo | Visa"
Meta description is long (168 chars)
Trim to 70-160 characters; longer descriptions get truncated.
Canonical URL: https://www.visa.com.uy
<html lang="es">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1"
122 hreflang alternate(s) but no x-default
Add <link rel="alternate" hreflang="x-default" href="..."> as a fallback for unmatched locales.
13/13 interactive elements have an accessible name
11/11 images, frames or videos have no declared dimensions
Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.
Method note: this reads markup, not a rendered accessibility tree
Un agent peut-il seulement la récupérer ?
A missing page redirects (301) instead of returning 404
A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
Homepage takes 2 redirects to answer
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.
HEAD requests are supported
Content-Type: text/html with charset
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS includes subdomains
HSTS lacks the preload directive
Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
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
Response compressed with Brotli (br)
Cache validator present (Last-Modified)
Conditional request returns 304 Not Modified
Homepage size is reasonable (42.1 KB decompressed)
Roughly 351 tokens of content in 10,776 tokens of response (97% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 370ms
Un agent trouve-t-il ce que vous publiez ?
/llms.txt not found
Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
No sitemap found
Publish an XML sitemap at /sitemap.xml and reference it from robots.txt with: Sitemap: https://your-site.com/sitemap.xml
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">.
No OpenGraph meta tags found
Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.
No Twitter Card meta tags found
Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.
/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.
No Sitemap directive found
Add a Sitemap directive to your robots.txt: Sitemap: https://your-site.com/sitemap.xml
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.
6/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.
Qu'un agent peut-il appeler ?
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.
No agent-facing surface — an Agent Card does not apply to this site
No API surface — API discovery does not apply to this site
No MCP server — MCP discovery does not apply to this site
No developer-facing surface — skills do not apply to this site
No forms and no WebMCP code — nothing here for an agent to invoke as a tool
No commerce surface — agentic-commerce discovery does not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
Quels droits d'usage sont déclarés ?
/.well-known/security.txt not found
Create a /.well-known/security.txt file per RFC 9116. At minimum, include Contact: and Expires: fields. See https://securitytxt.org/ for a generator.
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.
Offrez à votre équipe des rapports complets, des corrections prioritaires et un suivi pour préserver les progrès après chaque livraison.