sncf-connect.com
scanné le 2026-08-23 01:39 UTC · en cache · actualisation dans 0 h · rubric 2026.11.0
Analyse publique non vérifiée
Défaillant
AgentSpeed teste avec quelle facilité des agents automatisés peuvent découvrir, comprendre et agir sur sncf-connect.com. Le score pondère cinq catégories de lisibilité machine ; les graduations de l’arc sont les 37 vérifications individuelles derrière.
✉ Recevoir ce rapport par e-mail + être alerté des changements ↓
Mesure incomplète : seulement 50 % du poids de la grille a produit des résultats (2 catégories sur 5), aucune note n’est donc affichée. Le score ne couvre que ce qui a été mesuré.
Les détails techniques des vérifications sont en anglais, car ils proviennent directement du scanner.
Corrections prioritaires
Les vérifications marquées « emerging » sont des standards de protocole agent de 2026 que la majorité du web n’a pas encore adoptés. Être en avance est un atout, pas un défaut.
failReachability+28 ptsActionnabilitéTerminal HTTP 403.
Voir la marche à suivre
Ce que cela signifie
Before reading anything, an agent has to reach your page: one request, a clean answer. Yours didn’t answer cleanly. The finding above says exactly what happened: an error status, a connection failure, or a chain of redirects before any content arrived.
Pourquoi c’est important
Agents give up much faster than browsers. A human waits through three redirects and a retry; an agent on a time budget records "unreachable" and answers from other sources. Every other measurement on this page happens only after this one succeeds, so this failure hides everything else your site does right.
À faire
- Read the finding above: it names the status code and counts the redirects we followed.
- If it is a redirect chain, collapse it to one hop. The classic chain is http → https → www → final page; configure your host to jump straight from any variant to the final address in a single redirect.
- If it is a 4xx or 5xx status, your server is refusing or failing the page. Fix the route or the error before anything else on this page.
Ne perdez pas ce rapport
Recevez-le dans votre boîte mail, plus une alerte dès que le score de sncf-connect.com change. Gratuit, désinscription à tout moment.
Vous préférez qu'on s'en charge ? Monitor rescanne chaque semaine et signale tout changement, $29/mo. Activer la surveillance →
Corriger
Des fichiers générés, prêts à déployer, pour les lacunes ci-dessus. Copiez-les ou téléchargez-les dans votre dépôt.
Ce scan a noté une page. Votre site en compte bien plus.
Point faible de ce scan : l’actionnabilité, 0/100 — les actions que cette page propose aux humains sont difficiles à trouver ou à accomplir pour un agent.
Seule la page d’accueil a été notée. Vos tarifs, votre documentation et votre paiement vivent sur d’autres pages : celles que les assistants citent quand ils vous recommandent. Un 14/100 ici signifie que des agents ratent déjà des choses sur votre meilleure page. Le Deep Scan ($29) audite votre page d’accueil plus jusqu’à 10 autres pages que nous découvrons, sur les 37 vérifications, et envoie un PDF listant chaque échec et sa correction exacte, classés selon ce qui vous coûte le plus de visibilité. Paiement unique, livré en quelques minutes, sans abonnement.
Ce que l’agent reçoit
Affichez votre score
Intégrez ce badge sur votre site. Il renvoie vers ce scan en direct et se met à jour à chaque rescan.
<a href="https://agentspeed.com/scan/sncf-connect.com"><img src="https://agentspeed.com/badge/sncf-connect.com" alt="AgentSpeed agent-readiness score" height="56"></a>Suivre ce score
Recevez ce rapport par e-mail, puis une alerte quand la compatibilité agents de sncf-connect.com change vraiment : une vérification qui régresse, ou le score global qui baisse.
Deux choses ne déclenchent jamais d’e-mail : un changement de score dû à la publication d’une nouvelle grille (c’est un autre instrument de mesure, pas un changement de votre site), et un mouvement expliqué uniquement par des vérifications dépendantes du temps, qui varient d’un passage à l’autre.
Vous préférez votre propre rythme, avec Slack ou un webhook plutôt que l’e-mail ? Le suivi de dérive du score est inclus dans toutes les offres payantes.
Ce score dit si un agent IA pourrait lire sncf-connect.com. L’analytics du trafic IA dit si un agent est réellement venu, et quelles pages l’ont fait fuir.
Détail complet
2 pass1 warn10 fail24 skip
Découvrabilité
fail
robots.txt present
No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.
0/100
pass
robots.txt allows AI agents
All 9 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt but missing H1 header and markdown links. Not scored.
100/100
warn
Sitemap present
sitemap.xml reachable but not referenced from robots.txt, so agents may miss it.
70/100
skip
Link response headers
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Canonical URL
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Lisibilité
skip
Markdown negotiationemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Text-to-markup ratio
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Content without JavaScript
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Heading hierarchy
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Cookie wall blocks content
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Declared language
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Page title
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Meta description
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
Données structurées
skip
JSON-LD present
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Structured data validates
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Schema type coverage
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
Cohérence : vos canaux sont-ils d’accord ?
skip
JSON-LD price matches the visible priceemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
JSON-LD name appears on the pageemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Declared language matches the contentemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
Actionnabilité
skip
Paywall / login wall
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
skip
WebMCP actionsemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
Commerce protocol manifestemerging
No agentic-commerce discovery manifest (x402 at /.well-known/x402.json, UCP at /.well-known/ucp, or ACP at /.well-known/acp.json). Agents that buy pre-flight these before attempting a transaction; publishing the one for your commerce protocol is how they learn you accept agent-initiated purchases.
0/100
skip
Primary action reachable
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
Reachability
Terminal HTTP 403.
0/100
skip
Primary action is clickableemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Filters reachable by URLemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
Performance
skip
Time to first byte
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Full render time
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Page weight
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
Au-delà du scan
Vous exploitez vos propres agents IA ? AgentSpeed les surveille aussi en production : chaque exécution, sa latence, son coût et ses échecs, avec des alertes quand quelque chose casse. Gratuit jusqu’à 10 000 événements par mois, sans carte bancaire.
Produisez ce type de rapport pour chaque client : PDF en marque blanche et surveillance hebdomadaire jusqu’à 15 domaines, $149/mo. AgentSpeed pour les agences →
Méthodologie et limites
Ce score mesure la lisibilité pour les agents automatisés selon la grille publique 2026.11.0. AgentSpeed n’évalue ni la sécurité, ni la légitimité, ni la confidentialité, ni la confiance financière.