sncf-connect.com
gescannt 2026-08-23 01:39 UTC · aus dem Cache · Aktualisierung in 0 h · rubric 2026.11.0
Nicht verifizierter öffentlicher Scan
Mangelhaft
AgentSpeed prüft, wie leicht automatisierte Agenten sncf-connect.com finden, verstehen und darauf handeln können. Der Score gewichtet fünf Kategorien der Maschinenlesbarkeit; die Striche auf dem Bogen sind die 37 einzelnen Checks dahinter.
Unvollständige Messung: Nur 50 % des Rubrik-Gewichts lieferten Ergebnisse (2 von 5 Kategorien), daher wird keine Note gezeigt. Der Score deckt nur das Gemessene ab.
Technische Check-Details erscheinen auf Englisch, denn sie stammen direkt aus dem Scanner.
Wichtigste Fixes
Checks mit dem Tag „emerging“ sind Agent-Protokoll-Standards von 2026, die der Großteil des Webs noch nicht umgesetzt hat. Früh dabei zu sein ist ein Vorteil, kein Mangel.
failReachability+28 Pkt.HandlungsfähigkeitTerminal HTTP 403.
Schritt für Schritt anzeigen
Was das bedeutet
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.
Warum es wichtig ist
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.
So geht’s
- 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.
Diesen Bericht nicht verlieren
Jetzt ins Postfach, plus eine Nachricht, sobald sich der Agent-Readiness-Score von sncf-connect.com ändert. Kostenlos, jederzeit abbestellbar.
Sollen wir das für Sie übernehmen? Monitor scannt wöchentlich neu und meldet jede Änderung, $29/mo. Monitoring starten →
Direkt beheben
Generierte, einsatzbereite Dateien für die Lücken oben. Kopieren oder herunterladen und ins Repo legen.
Dieser Scan hat eine Seite bewertet. Deine Website ist mehr als eine Seite.
Schwächste Kategorie in diesem Scan: Handlungsfähigkeit, 0/100 — die Aktionen, die diese Seite Menschen bietet, sind für Agenten schwer zu finden oder abzuschließen.
Bewertet wurde nur die Startseite. Preise, Doku und Checkout liegen auf anderen Seiten: genau denen, die Assistenten zitieren, wenn sie dich empfehlen. Ein Wert von 14/100 hier heißt: Agenten übersehen schon auf deiner besten Seite Dinge. Der Deep Scan ($29) prüft deine Startseite plus bis zu 10 weitere Seiten, die wir finden, gegen alle 37 Checks und liefert ein PDF mit jedem fehlgeschlagenen Check und dem konkreten Fix, sortiert nach dem, was dich am meisten Sichtbarkeit kostet. Einmalig, in Minuten geliefert, kein Abo.
Was der Agent empfängt
Zeig deinen Score
Binde dieses Badge auf deiner Website ein. Es verlinkt auf diesen Live-Scan und aktualisiert sich bei jedem 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>Diesen Score beobachten
Diesen Bericht per E-Mail erhalten, plus eine Nachricht, wenn sich die Agent-Readiness von sncf-connect.com wirklich ändert: ein Check verschlechtert sich oder der Gesamtwert fällt.
Zwei Dinge lösen nie eine E-Mail aus: Score-Änderungen durch eine neue Rubrik von uns (das ist ein anderes Messinstrument, keine Änderung an deiner Website) und Bewegungen, die sich nur durch zeitabhängige Checks erklären, die von Lauf zu Lauf schwanken.
Lieber nach eigenem Zeitplan, mit Slack oder Webhook statt E-Mail? Score-Drift-Monitoring ist in jedem Bezahlplan enthalten.
Dieser Score sagt, ob ein KI-Agent sncf-connect.com lesen könnte. KI-Traffic-Analytics zeigt, ob tatsächlich einer kam, und welche Seiten ihn abgewiesen haben.
Vollständige Aufschlüsselung
2 pass1 warn10 fail24 skip
Auffindbarkeit
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
Lesbarkeit
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.
—
Strukturierte Daten
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.
—
Kohärenz: Stimmen Ihre Kanäle überein?
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.
—
Handlungsfähigkeit
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.
—
Mehr als der Scan
Betreibst du eigene KI-Agenten? AgentSpeed überwacht sie auch in Produktion: jeden Lauf, Latenz, Kosten und Fehler, mit Alarmen, wenn etwas bricht. Kostenlos bis 10.000 Events pro Monat, keine Kreditkarte.
Erstellen Sie solche Reports für jeden Kunden: White-Label-PDFs und wöchentliches Monitoring für bis zu 15 Domains, $149/mo. AgentSpeed für Agenturen →
Methodik und Grenzen
Dieser Score misst die Lesbarkeit für automatisierte Agenten gemäß der öffentlichen Bewertungsmatrix 2026.11.0. AgentSpeed bewertet weder Sicherheit noch Legitimität, Datenschutz oder finanzielle Vertrauenswürdigkeit.