fidelity.com
scanné le 2026-08-27 19:53 UTC · en cache · actualisation dans 0 h · rubric 2026.11.0
Analyse publique non vérifiée
Bon
AgentSpeed teste avec quelle facilité des agents automatisés peuvent découvrir, comprendre et agir sur fidelity.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 ↓
Les détails techniques des vérifications sont en anglais, car ils proviennent directement du scanner.
Envoyez ceci à la personne qui modifie le site. Le lien affiche le score et la note sous forme d’aperçu, et il reste à jour : il relit le dernier scan au lieu de figer la valeur d’aujourd’hui.
Corrections prioritaires
failLink response headers+3 ptsDécouvrabilitéNo HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
Voir la marche à suivre
Ce que cela signifie
HTTP responses can carry a Link header: the same canonical and alternate-language information your HTML declares, but delivered in the response envelope itself. Agents that only send a HEAD request, or that decide what to do while the page is still streaming, read the header without parsing any HTML. Yours is missing (or carries none of the relations agents use: canonical, alternate, describedby).
Pourquoi c’est important
An agent triaging fifty URLs doesn’t want to download and parse fifty pages to learn which are duplicates of which. The Link header answers at the cheapest possible layer. Sites that provide it get correctly de-duplicated and correctly language-routed even by the most minimal fetchers.
À faire
- Emit a Link header alongside each page, mirroring what your HTML head already declares. Example: Link: <https://yoursite.com/page>; rel="canonical".
- Most stacks set this in one place: Next.js headers() config, an nginx add_header line, or a CDN response-header rule.
- If you serve translations, add rel="alternate" entries with hreflang, matching your HTML.
Ne perdez pas ce rapport
Recevez-le dans votre boîte mail, plus une alerte dès que le score de fidelity.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 →
Ce scan a noté une page. Votre site en compte bien plus.
Point faible de ce scan : la performance, 70/100 — des réponses assez lentes ou instables pour qu’un agent abandonne avant que la page ne réponde.
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 80/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.
Qualifies for certificationSilver
Right now, only you know this score. Your buyers ask AI before they buy, and certification is how you show them, and anyone comparing you to a competitor, that assistants can actually read, quote, and use your site.
- A public verification URL you can drop into a sales deck, a procurement questionnaire, or a partner review. Anyone can check it, dated and signed.
- An embeddable badge for your site, the visible version of a property competitors can’t claim without earning the score.
- Weekly re-checks for a full year. A deploy that breaks agent access gets caught before it costs you recommendations, and before the certificate would lapse.
Sites under 70 can’t buy this at any price. That’s what makes displaying it mean something.
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/fidelity.com"><img src="https://agentspeed.com/badge/fidelity.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 fidelity.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 fidelity.com. L’analytics du trafic IA dit si un agent est réellement venu, et quelles pages l’ont fait fuir.
Détail complet
18 pass3 warn5 fail11 skip
Découvrabilité
pass
robots.txt present
A robots.txt is reachable at the site root.
100/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
pass
Sitemap present
sitemap.xml reachable and referenced from robots.txt.
100/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
pass
Canonical URL
Canonical points to self: https://www.fidelity.com/.
100/100
skip
MCP server cardemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
skip
OAuth authorization metadataemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
skip
OAuth resource metadataemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
skip
API catalog / OpenAPIemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
skip
Web Bot Authemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
Lisibilité
skip
Markdown negotiationemerging
Agent-protocol discovery was not probed for this scan.
—
fail
Text-to-markup ratio
Visible text is 0.5% of HTML weight (6953/1286430 bytes). 28% of the document is inline script, 9% is markup.
4/100
pass
Content without JavaScript
Primary content is present in the initial HTML — agents without JS can read it. (Measured statically; a rendered comparison was not run because the static reading sufficed.)
90/100
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 14 headings total).
100/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
pass
Declared language
Declared lang="en".
100/100
warn
Page title
<title> is 128 characters; keep it under 70 so it isn't truncated.
60/100
warn
Meta description
Meta description is 310 characters; aim for 50–200 so it's neither thin nor truncated.
60/100
Données structurées
pass
JSON-LD present
Found 1 JSON-LD block.
100/100
pass
Structured data validates
2/2 checkable block(s) validated cleanly against schema.org.
100/100
fail
Schema type coverage
Page looks like Product / Article|BlogPosting|NewsArticle; missing JSON-LD type(s): Product, Article|BlogPosting|NewsArticle.
0/100
Cohérence : vos canaux sont-ils d’accord ?
skip
JSON-LD price matches the visible priceemerging
No price declared in JSON-LD, so there is nothing to cross-check. (Whether a price SHOULD be declared is the structured-data checks’ question.)
—
pass
JSON-LD name appears on the pageemerging
Declared entity name "Fidelity Investments" appears on the visible page.
100/100
pass
Declared language matches the contentemerging
Declared lang="en" matches the detected content language (en).
100/100
Actionnabilité
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
skip
Agent Skills manifestemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
skip
Commerce protocol manifestemerging
Not measured: the origin refused the commerce-discovery probes, which says we were not allowed to look, not that nothing is there.
—
pass
Primary action reachable
A primary offering and a price or call to action were both identifiable from the served HTML, so an agent can tell what this page sells and what it costs without running scripts.
100/100
pass
Reachability
HTTP 200 after 1 redirect.
100/100
pass
Primary action is clickableemerging
1 clickable element(s) carry an action an agent can take: <a> announcing "get started". An agent driving the page has something real to click.
100/100
skip
Filters reachable by URLemerging
This page does not offer to filter or sort a list, so there is nothing to address by URL. Pages without facets are not penalised here.
—
Performance
warn
Time to first byte
TTFB 1379ms. Slow. Agents time out aggressively.
40/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 1256 KB.
100/100
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.