Santander earns an Agent Readiness Score of 49 out of 100. The brand sits mid-pack among U.S. banks, with three strong acquisition surfaces (Checking, Cards, Investing) and three under-developed ones (Savings, Homepage, Help).
Santander is scored across 6 of 7 standard product surfaces. Lending is marked N/A: the brand exited residential mortgage origination via the 2022 Rocket Mortgage sale and operates servicing only.
Santander invests where it matters most for acquisition. The Checking, Credit Card, and Investing pages each ship structured FAQ content with six to eight real questions and full paragraph answers covering funding, eligibility, fees, and product mechanics. An agent asking what it takes to open a Santander checking account gets a clean, direct answer pulled straight from the page. Plain-language product naming helps: Ultimate Cash Back, Simply Right Checking, Select Money Market, PathFinder. The sitemap is current, robots.txt welcomes all crawlers, and the Liferay backend serves complete HTML on first byte.
Structured data coverage stops at FAQ tagging and the Corporation entity. Rates, fees, APYs, and reward percentages live as unstructured copy that agents must parse from prose. The homepage and Personal Loans pages ship zero structured data. Canonical tags resolve to the site root rather than the full page URL. Open Graph tags are missing on the homepage, and the HSTS header is configured at one day rather than the standard one year. A dedicated customer-service landing page sits absent, so an agent answering a contact or resolution question has to triangulate across a 57-page resources tree.
Santander has built genuinely useful agent-readable content on three of its highest-intent acquisition surfaces. The opportunity is to extend the same discipline to Savings, Help, and the homepage, and to add typed product data so rates and rewards become machine-quotable rather than prose-parsed.
Position within the mid-tier band of the AI Compass Index. Closest peer brands shown in order.
Every Agent Readiness Score splits into Technical Readiness and Content Architecture. The two halves point to different teams and different timelines.
