Social Signals
A Third Of Fintech Is Invisible To AI Agents
Jun
A 3rd of the highest fintech web sites on the earth ship lower than 80% of their homepage content material in uncooked HTML. That’s the model of the web page an AI agent will get when it visits, earlier than it decides whether or not to spend the compute on a full browser render. Most of them don’t.
The Construction pillar of Machine-First Architecture says crucial info should not rely on client-side JavaScript. Rendering independence. Till final month, this was a design precept. Now it’s a quantity, and the quantity is uncomfortable.
On Could 25, I measured 274 fintech homepages from the CNBC World’s High Fintech Corporations 2025 record. I made two sequential measurements on every one: a uncooked HTTP fetch with no JavaScript execution, and a full browser render with Playwright. The hole between the 2 readings is the hole an AI agent has to shut by itself. 36% of those web sites drive it to try this work for a very powerful web page on the property. The complete examine is printed on Web Performance Tools.
Most AI Visibility Protection Skips The Rendering Step
Most AI visibility protection focuses on schema markup, structured content material, brand authority signals, and optimization for AI Overviews, ChatGPT search, Perplexity citations, and Gemini’s grounding pipeline. The recommendation stacks up quick.
All of that assumes the agent noticed your content material within the first place.
Most AI crawlers don’t render JavaScript. GPTBot, ClaudeBot, PerplexityBot, the AI user-agent landscape feeding the fashions you are attempting to be cited by, they make HTTP fetches and stroll away. They don’t seem to be browsers. Running a real Chromium occasion per web page prices compute that multiplies throughout the hundreds of thousands of pages these techniques wish to learn. So that they don’t, by default. They take what comes again within the uncooked HTTP response and transfer on.
There are exceptions. Google’s crawler runs a deferred rendering pipeline for some pages. Some AI techniques will render for high-value targets, or render selectively when the uncooked response appears to be like empty. The sample isn’t absolute. However the manufacturing default for the crawlers that feed the biggest AI techniques on the internet right this moment is uncooked HTTP fetch, no JavaScript, take what’s there.
This creates a spot that customers don’t see. An actual customer opens your web site in a browser. JavaScript runs. The web page assembles within the viewport. Content material hundreds, structure settles, the hero picture arrives. The customer sees what you constructed. The AI agent fetches the response earlier than any of that occurs. No matter doesn’t present up within the first HTML response is, for that agent, not there.
That is what the Construction pillar of Machine-First Structure is about. Vital info should not rely on client-side JavaScript. The web page have to be parseable from the uncooked HTTP response, not from the browser-rendered view 5 seconds later. This isn’t a efficiency desire dressed up as structure. It’s a visibility requirement for the AI agents that now read the web on behalf of users.
Till just lately, the rendering-independence requirement was an argument. You might learn the spec, have a look at the crawler behaviors, draw the conclusion, and nonetheless disagree about how a lot of an issue it’s in apply. There was no quantity you possibly can level to.
The fintech information provides you the quantity.
Two Reads On The Similar Web page: Uncooked HTML, Then Browser Render
The check on every of the 274 fintech homepages was easy: two sequential measurements, run on Could 25, 2026, from Portugal. The primary was a uncooked HTTP fetch towards the canonical homepage, no JavaScript executed, no matter bytes got here again within the response. The second was a full browser render utilizing Playwright 1.60.0 with Chromium 148.0.7778.96 in non-headless mode, capturing the web page at 5 seconds post-TTFB and once more at community idle. All measurements ran from Portugal on Could 25, 2026, on residential broadband, viewport 1280 by 800, no community throttling.
For every web site, content material was extracted from the ,
Three reads on the identical web page, in the identical session, separated by what the browser needed to do to make the web page full: uncooked fetch, five-second render, community idle.
The fascinating a part of the curve isn’t the network-idle studying on the finish. Virtually each web site within the pattern resolves to full content material by community idle. The fascinating half is the raw-fetch studying at the beginning, as a result of the uncooked fetch is the learn most AI crawlers truly take.
36% Ship Much less Than 80% Of Their Content material With out JavaScript
Out of 274 fintech homepages measured, 99 returned lower than 80% of their closing content material from the uncooked HTTP fetch. That’s the headline quantity. Thirty-six %.
Inside that 99, the distribution is steep. Fifty-five web sites (20% of the total pattern) returned lower than 30% of their content material with out JavaScript. Forty-seven of these web sites returned zero. The HTML response carried a shell, the structure scaffolding, some inline scripts, no readable content material. Regardless of the homepage was meant to speak required a JavaScript runtime to speak it.
The 47 zero-content web sites embody main exchanges, well-known neobanks, giant lending platforms, a number of public firms, and types an individual in finance would acknowledge with out prompting. I’m not going to name them out individually. Naming the web sites would distract from the architectural statement beneath. Whether or not your homepage exhibits as much as an AI agent in any respect is at the moment a perform of choices that no person on the workforce was serious about in these phrases once they had been made.
The 24 web sites within the 60-to-79 partial-visibility band have a unique drawback. They present as much as the agent, however not all the way in which. The agent will get a hero headline, perhaps the first navigation, perhaps a worth proposition. It doesn’t get the product descriptions, the belief alerts, the calls to motion, the third-party logos. No matter was determined to render on the shopper facet is the half the agent doesn’t see, and that half tends to be the half that was made dynamic as a result of somebody wished it to really feel interactive.
There’s a restoration curve, and the restoration curve is the place the story sharpens. Of the 274 web sites, 273 attain 80%-plus visibility as soon as an actual browser renders the web page for 5 seconds. Ninety-nine %. The content material exists. The web sites usually are not damaged. They’re gated behind a runtime that the manufacturing AI crawlers don’t pay for.
The median web site within the pattern takes 21 instances longer to succeed in community idle than to return its uncooked HTTP fetch. Thirty-four web sites (12%) don’t attain community idle in any respect inside the 30-second cap. That may be a separate drawback, however it factors to the identical root trigger. The associated fee hole between fetching an internet site and studying it’s widening, and the crawlers can’t preserve absorbing the distinction.
Stripe, Adyen, And Plaid Show The Stack Is Not The Drawback
100 and one web sites within the pattern returned 100% of their homepage content material within the uncooked HTTP fetch. Full visibility earlier than any JavaScript ran. The record consists of Stripe, Plaid, Adyen, Marqeta, Remitly, Starling Financial institution, Neo Monetary, Backbase, Thought Machine, and 92 others.
Fiserv returned an entire homepage in 58 milliseconds. Acorns in 76. Trustly in 89. Ledger in 100. Take a look at what these web sites truly are. Fiserv is a payments-and-banking infrastructure firm at a $60 billion scale. Acorns runs a shopper app. Ledger is a hardware-wallet vendor with a product catalog. They’re utilizing fashionable stacks, content material administration techniques, regional CDNs, the works. They’ve determined that the content material the homepage exists to speak shall be there within the uncooked response, they usually haven’t let the framework selection override that call.
That is the reply to the plain pushback. The pushback is {that a} fashionable stack requires client-side rendering, that single-page functions are how the net is constructed now, that asking for server-rendered HTML is asking engineering to step again 5 years. The fintech pattern disproves that by itself. The web sites operating the quickest uncooked responses took the rendering-independence requirement severely once they made architectural decisions, or rebuilt to take it severely after the very fact.
There are exceptions to this learn contained in the pattern. Three web sites underperformed on the five-second render window, despite the fact that they ultimately accomplished. All three are Asian firms measured from Portugal, and the latency penalty possible accounts for the curves moderately than the structure.
The Web Performance Tools study examined homepages solely, from one geographic origin, on sooner or later, with one measurement per web site. It didn’t measure inside pages. It didn’t check a number of areas. It didn’t check content material gated behind scroll or click on. The image this dataset provides you is the homepage of the largest fintech firms on the earth, on a single day in Could, fetched from Western Europe. That may be a slice. A helpful slice for the load-bearing query this text is about, however a slice.
The load-bearing query is whether or not the rendering-independence requirement holds at scale throughout a big, fashionable, well-resourced business cohort. The fintech pattern solutions it. Many of the cohort will get it proper. A 3rd will get it fallacious, and the third that will get it fallacious consists of manufacturers sufficiently big that the architectural selections nearly definitely handed by means of a number of rounds of senior engineering overview with out anybody naming AI visibility as a constraint.
Fintech Is The place The Homepage Is The Belief Sign
Most classes can afford a few of their homepage to be invisible. A shopper SaaS firm can lose a hero subhead, and most of its guests won’t really feel the distinction. A media web site can carry the masthead by means of schema and nonetheless rank for the subjects the physique covers. Fintech isn’t most classes.
For a fintech, the homepage is the place regulated disclosures reside. The licensing footnote. The deposit insurance coverage language. The bank-partner attribution. The safety certifications. The nation availability matrix. The chance warning beneath the speed quote. These are the weather that flip a model from “an fascinating product” into “a factor I might truly put cash into.” A reader scanning the homepage is searching for them. So is an AI agent answering a query about which supplier to belief for a selected use case.
When 17% of the cohort returns zero content material within the uncooked response, what disappears is the regulatory and belief layer of the model. The agent doesn’t see the financial institution associate. It doesn’t see the deposit insurance coverage. It doesn’t see the safety certifications. It sees a shell.
The class compounds the issue in a second method. Fintech shopping for selections are research-heavy. An individual opening a financial savings account, choosing a fee processor, deciding which dealer to fund, evaluating a pockets, they undergo a number of rounds of comparability earlier than they act. That comparability loop is the a part of the funnel that has migrated into AI surfaces the quickest. Eric van Buskirk’s clickstream study of 846,000 Google sessions confirmed AI Mode customers shut their loops contained in the AI 64% of the time, by no means clicking by means of.
The fintech analysis loop is more and more occurring inside an AI floor, and the agent doing the work for the person is selecting from a candidate set assembled out of the uncooked HTML it may fetch. If a fintech homepage returns zero content material within the uncooked response, the model by no means enters the candidate set the agent is selecting from. It’s absent earlier than the comparability begins.
That is what the Construction pillar of Machine-First Structure exists for. The pillar is the upstream requirement that makes each downstream AI visibility technique attainable. Schema markup doesn’t assist when the agent can’t learn the web page. Citation strategy doesn’t assist when the mannequin by no means noticed the content material to quote. Model authority alerts don’t assist when the homepage that carries them returns empty bytes to GPTBot. Construction is the ground. Every little thing else stacks on it.
The fintech pattern exhibits the ground is damaged for one in three of the largest manufacturers within the class. The pattern is a snapshot. Tomorrow, a few of these web sites shall be totally different, and among the web sites that scored nicely right this moment could have drifted within the fallacious route. The 36% will transfer. What issues is that till final month, there was no quantity in any respect, and now the dialog about AI visibility for this class has a load-bearing measurement connected to it.
Run The Audit On Your Personal Homepage
Open Chrome. Open DevTools. Hit Cmd+Shift+P on Mac or Ctrl+Shift+P on Home windows. Sort “Disable JavaScript” and hit enter. Reload your homepage.
What you see is what the agent sees. In case your hero, your worth proposition, your product description, your belief alerts, your CTAs, and your regulatory disclosures are all seen, your homepage is passing the Construction pillar. If the hero is there however the physique is gone, you’re within the partial-visibility band, someplace between 60% and 79% of your closing content material. If the web page is clean or near it, you’re in the identical tier because the 47 zero-content web sites within the fintech pattern.
That is the most affordable audit within the AI visibility class. It takes 30 seconds. No log-file evaluation, no paid instruments, no assembly with engineering. The result’s binary sufficient that you don’t want to argue about methodology. Both the agent can learn your homepage, or it can’t.
If the audit fails, the repair paths are framework-specific however well-known. Subsequent.js has server-side rendering and static era, each of which return content material within the uncooked HTTP response. Astro and SvelteKit ship server-rendered by default. React functions may be prerendered route by route utilizing instruments like Prerender.io or Cloudflare Pages’ prerendering layer, which serve a snapshot of the rendered web page to crawlers with out altering the runtime structure for customers. Vue and Angular have equal patterns.
The selection between these paths is an structure dialog, not a content material dialog. Most groups don’t have to rebuild. They should add a server-rendering layer for a selected set of routes: homepage, pricing, product pages, weblog index, something the model will depend on for first-impression or belief alerts. The architectural change doesn’t must ripple by means of your entire software.
Stripe, Adyen, Plaid, Marqeta, and the 97 different web sites within the 100%-raw-visibility record of the fintech pattern didn’t decide easier stacks. They picked architectures that revered the rendering-independence requirement and shipped the content material within the uncooked response. The pushback that the Construction pillar requires going again to server-rendered PHP from 2009 is the fallacious form of pushback. The pillar requires the content material to be there on the HTTP response layer. The way you get it there may be as much as the stack you have already got.
What This Pattern Does Not Inform You
The examine measured 274 homepages on sooner or later from one origin. Inside pages had been out of scope, which implies an internet site with a great homepage and weak product pages would go the check and nonetheless have the visibility drawback on the routes that drive conversion. Geographic variation was out of scope. Per-crawler habits was inferred from the raw-versus-render hole moderately than probed straight. Content material gated behind scroll or click on is its personal class of agent visibility failure, and the examine didn’t check it.
A query this dataset can’t reply is whether or not AI crawlers will begin rendering extra pages as compute prices come down. They could. Some already do for high-value targets. If all of them did, your entire framing of this piece adjustments. The 36% would nonetheless be invisible on the raw-fetch layer, however could be readable on the rendered layer, and the urgency of the rendering-independence requirement would soften. I don’t assume that’s going to occur at scale quickly, however I’m looking ahead to it.
Rendering Independence Was At all times Actual. Now It Has A Quantity
A 3rd of the highest fintech web sites on the earth are partially invisible to AI brokers. Rendering independence is now not a design precept to argue about. It has a quantity.
The agent shall be again tomorrow. The crawl would be the identical crawl. The HTML would be the identical HTML. In case your homepage doesn’t return its content material within the uncooked response, the agent that fetched it is going to be working from a shell, and the reply it provides the person who requested about your class shall be assembled from the web sites that did return their content material.
Open DevTools. Disable JavaScript. Reload your homepage. The web page that hundreds is the web page the agent noticed.
Extra Assets:
This put up was initially printed on No Hacks.
Featured Picture: Roman Samborskyi/Shutterstock
#Fintech #Invisible #Brokers
