Can AI Read BrokerCheck and IAPD? What an Advisor Site Must Carry

FINRA's BrokerCheck and the SEC's Investment Adviser Public Disclosure site are the authoritative public record of who an advisor is: registrations, employment history, exams, and disclosure events. A person in a browser sees all of it. A program that downloads the page without running its JavaScript sees almost none of it, and several AI crawlers are reported to work that way.

That gap changes what an advisor's own website is for. It is part of AI visibility for financial advisors, and it is the least obvious part, because the records look perfectly public.

What we observed on 2026-09-26

We fetched pages from both sites with a plain HTTP request, the way a non-rendering crawler would. The findings are narrow and dated:

BrokerCheck is open to crawlers. Its robots.txt disallows nothing and points to a sitemap of profile URLs.
A BrokerCheck profile's raw HTML is a shell. An individual summary page came back at about 4 KB, carrying only the site's generic title ("Find a broker, investment or financial advisor"), with no individual's name in it. The profile content is loaded by script after the page opens.
IAPD behaves the same way. A firm summary page returned about 4 KB carrying the same generic title as the IAPD homepage.
IAPD closes its brochure paths. The IAPD robots.txt disallows /firm/brochure/ and the older brochure viewer, which is where Form ADV Part 2 lives.

Who renders and who does not

Google says Googlebot renders JavaScript as part of indexing, in its JavaScript SEO basics, and its AI features guidance says AI Overviews and AI Mode need only normal indexing and snippet eligibility. So Google's AI surfaces are the likeliest to see a rendered BrokerCheck profile.

For the others the evidence is thinner. A December 2024 analysis by Vercel with MERJ, which is vendor research rather than a platform statement, reports that none of the major AI crawlers it examined, including OpenAI's, Anthropic's ClaudeBot and PerplexityBot, render JavaScript. OpenAI's own bot documentation describes OAI-SearchBot and ChatGPT-User without saying either way.

Put together, and labeled as inference: an assistant that relies on a non-rendering fetch and opens a BrokerCheck or IAPD profile is likely to receive a generic title and nothing about the person. We have not run prompts to confirm how any assistant actually handles this, and we are not claiming that any assistant does or does not cite these sites.

Your site becomes the readable copy of the identifiers

If the regulator page is opaque to a text fetch, the advisor's own page is often the only place the connecting facts appear as plain text: the person's name next to a CRD number, next to the firm's name, next to a working link to the exact profile. That does not replace the regulator record. It gives a machine the key to look it up and a sentence it can quote.

The same logic applies to the firm's own disclosure documents. The Form CRS relationship summary, which the SEC's investor bulletin says covers services, fees and costs, conflicts, the standard of conduct and disciplinary history, is required to be on the adviser's website if it has one. Hosting it as selectable text on your own domain, rather than only as a scanned image, keeps it readable.

What to do

Put each advisor's CRD number in visible text on their bio, and the firm's CRD and SEC file number where the firm is described.
Link to the exact BrokerCheck and IAPD profile URLs, not the search homepage.
Publish Form CRS and the ADV Part 2A brochure as text documents on your domain, and link them from the pages that describe fees and services.
Check your own site passes the same test: view the page source, not the rendered page, and confirm the names and numbers are there. The general version of that check is in content AI cannot see.

Not legal, compliance or investment advice. This describes how AI systems read an advisory practice in public; which rules bind you depends on how you are registered, and your compliance department decides what you publish.

Questions

Does ChatGPT read BrokerCheck?

We have not measured it. OpenAI documents OAI-SearchBot for ChatGPT search and ChatGPT-User for fetches made on a user's behalf, and does not say whether either renders JavaScript. Vendor research from Vercel and MERJ reports that the major AI crawlers it tested do not execute JavaScript, and a BrokerCheck profile's raw HTML carries no person's name, so a non-rendering fetch would see a generic page.

Should I copy my BrokerCheck disclosures onto my website?

That is a compliance decision, not a visibility one. What this page recommends is narrower: state your CRD number and link to your exact BrokerCheck or IAPD profile, so the identifier is readable as text on a page you control.

Why BrokerCheck and IAPD may be invisible to AI fetchers, and what your site has to carry instead