Published September 11, 2026 · Updated October 27, 2026
Your money market account page ranks on the first page of Google, and a customer who lands on it sees the rate only after typing a ZIP code. The terms sit in an accordion, the fee schedule is a PDF, and your structured data still carries last quarter's rate. Your customer can work around all that. A crawler that doesn't run scripts or type into forms may find no rate and no fees, and the figure in your code may match nothing on the page.
If you run those pages, here's what to fix on product and branch pages, in your schema and for Perplexity, and what to check before a template ships. We assume your pages already lead with the answer, and we leave crawler-by-crawler access settings to an AI visibility audit.

You optimize a bank product page for AI Overviews by making it indexable and eligible for a snippet, with the facts your customers ask about in HTML text near the top. AI Overviews and AI Mode draw on Google's Search index, so most of this is the work that already makes your page rank. The difference is that one passage, not the whole page, can land in front of your customer.
Google's generative AI optimization guide adds one condition. Your site has to be included in generative AI features through a Search Console setting. The same guide says you don't need to chop content into small chunks. Microsoft describes Copilot's process as parsing pages into smaller pieces judged separately. Write each section to answer one question clearly and you've covered both.
Rate, fee and eligibility pages are Your Money or Your Life content in Google's rater guidelines, so a stale or unreadable figure costs more here than on most sites. Give every element of your product page a version a crawler can read.
| Page element | What to build | Why |
|---|---|---|
| Rates and fees | An HTML text table with an "as of" date, rendered in the page's initial HTML rather than inserted by a script | Google says important content should be available as text, and in published tests the crawlers used by ChatGPT and Perplexity did not run JavaScript |
| Rates that depend on location | A page whose crawlable version shows a rate a customer can actually get, such as a state-level page or a clearly qualified rate, with the wording approved by compliance | Google says it will not load content that requires typing, so a rate that appears only after a ZIP code is entered is unlikely to be seen by Googlebot, and crawlers that do not run scripts will not see it either |
| Account terms in tabs or accordions | Keep the answer to the main question visible on load, with supporting detail in expandable sections if needed | Google accepts tabs and accordions when the content is in the HTML, but Microsoft warns that AI systems may not render hidden content |
| Fee schedules and disclosures | An HTML page or section for the core terms, with the PDF kept as the formal document | PDFs are indexable, but Microsoft notes they often lack the headings and structure that help AI systems parse them |
| Product variants | One canonical page per product, with campaign, state and legacy versions redirected or pointed to it | Google treats redirects and canonical tags as strong signals, and Bing says duplicates can delay updates in AI answers |
| Dates | A visible "Rates as of" or "Last updated" date that matches any date in the structured data | Google asks for consistent dates and lists changing dates without real changes as a warning sign |
| Snippet controls | A review of nosnippet and max-snippet on product templates, and data-nosnippet only where compliance wants a passage kept out of answers, never on disclosures that must travel with a rate | Google applies these controls to AI Overviews and AI Mode, and Bing now supports data-nosnippet in its AI answers too |
| Interstitials | Overlays rather than redirects for eligibility or entry gates | Google says intrusive dialogs make content harder to understand and advises against redirecting for consent |
The location-based rate is the problem most specific to banks. If you price deposits or loans by market, a crawler that can't enter a ZIP code sees a page with no rate at all. The fix is partly a product decision, because any rate your page shows must be one you actually offer. Regulation Z and Regulation DD set the advertising rules for rate pages, so have your compliance team approve the wording.
Watch page speed too. A personalization script that hides your page until it loads delays Largest Contentful Paint, the time it takes the main content to appear.
Bing says more about freshness than Google does. It calls the lastmod field in a sitemap a key signal for recrawling, and in a 2025 talk, as Search Engine Roundtable reported from an attendee's summary, Microsoft's Fabrice Canel recommended IndexNow to push updates as they're published. So when you change a rate, update your sitemap and send an IndexNow ping.

Before you touch any markup, open your highest-traffic rate page with scripts disabled and look for the rate and the fees. If you can't find them, that template is your first fix.
A bank website should use a small set of schema types that describe the bank accurately, keep every value in them identical to what the page shows, and not expect schema alone to change AI visibility. We'd put Organization on your homepage, BankOrCreditUnion on each branch page, BreadcrumbList across the site, and Article markup with author and dates on your educational content. Product types from schema.org are optional, since Google offers no search feature for them.
| Schema type | Where it goes | What Google does with it | Bank caution |
|---|---|---|---|
| Organization | Homepage or about page | Helps Google identify the bank and choose the logo in results and the knowledge panel | Use legalName for the registered name and list official profiles in sameAs. Google suggests the iso6523Code property with prefix 0199 for a Legal Entity Identifier |
| BankOrCreditUnion, a LocalBusiness subtype | Each branch page | Local business markup can describe hours, departments and location | Google asks for the most specific subtype but does not name bank types, so this choice rests on schema.org's hierarchy |
| BreadcrumbList | Every page | Shows the page's place in the site hierarchy | Keep it consistent with the visible navigation |
| Article or BlogPosting | Educational and insight content | Supports byline dates and authorship | Dates and author names must match the page |
| FinancialProduct types, such as DepositAccount, LoanOrCredit, MortgageLoan and CreditCard | Product pages, if used | No Google search feature exists for them | Rates in interestRate or annualPercentageRate must update with the page, and APY has no dedicated property, so labeling is a compliance decision |
| FAQPage | Any page with visible questions and answers | Google stopped showing FAQ rich results on 7 May 2026 | Google said in 2023 that unused markup causes no problems, but it no longer earns a search feature |
| Review or AggregateRating | Not on the bank's own branches or products | Google does not show review rich results for LocalBusiness or Organization when the entity controls its own reviews | Embedding a third-party review widget does not change that |
So don't expect markup alone to win you citations. Ahrefs tracked 1,885 pages that added JSON-LD between August 2025 and March 2026 against 4,000 matched control pages and found no meaningful lift in citations on AI Overviews, AI Mode or ChatGPT. The pages were already heavily cited and Perplexity wasn't tested, but it's the only study we found with matched controls.
The other studies agree. Search Atlas found domains with extensive schema cited no more often than domains with little, and SE Ranking tied visible FAQ sections, not FAQ schema on its own, to more ChatGPT citations. A small searchVIU experiment found ChatGPT, Claude and Perplexity ignored JSON-LD when fetching a page live, though engines with a search index may still use it when indexing.
The platforms themselves are warmer. Google says structured data isn't required for generative AI search but is still worth using for rich results, and Microsoft's Bing team says schema helps AI systems interpret content.
What you do need to check is whether your markup carries outdated rates. A rate in JSON-LD that lags your page breaks Google's rule that structured data must match visible content and sits where your reviewers don't look, so ask compliance to review the markup with the page. If your systems can't update both from one source, you're safer leaving rates out of the markup.
Banks get cited by Perplexity when its crawler can reach and read their pages, when those pages carry current passages that answer the question on their own, and when the outside sources Perplexity tends to cite describe the bank accurately. We found no Perplexity guide to earning citations, so this rests on its technical documentation and vendor studies.
Perplexity runs its own index, which it describes as tracking more than 200 billion URLs, and scores fine-grained units of each document against the query. So one well-built section can be retrieved on its own. Bury your answer and you give Perplexity little to work with.
None of that counts until Perplexity can reach your page. Cloudflare began asking new domains at sign-up in July 2025 whether to allow AI crawlers and blocks them by default, so a CDN or firewall can keep Perplexity out even when your robots.txt lets it in. Run the crawler and firewall checks from an AI visibility audit for your bank first. In Vercel and MERJ's analysis of crawler traffic from late 2024, PerplexityBot didn't run JavaScript, so anything you load only by script is unlikely to be read.
Freshness counts too. An Ahrefs study of 17 million citations found AI assistants cited content that was 25.7% fresher on average than pages ranking in organic results, and Perplexity listed its references newest first. A visible "as of" date on your product page gives readers and Perplexity a dated fact.
Perplexity also spreads its citations widely. Profound found Reddit holding 46.7% of the citations among Perplexity's ten most cited domains, but only 6.6% of its citations overall, so no single source dominates. Ask Perplexity a few of your customers' questions and note which outside sources it cites about your bank.
Banks optimize branch pages for AI search by giving every real branch its own crawlable page with the same name, address, phone number, hours and services as its Business Profile and other listings. Local answers draw on your pages and on listing data, so the two have to agree.
Here the evidence is clearer. Google says it compiles Business Profile information partly from a business's official website, and its generative AI guide says Business Profiles help businesses appear in AI responses as well as regular results.

Keep your expectations in check, though. SOCi, a local marketing software company, found the average financial services brand, in a segment that also includes insurers, mortgage companies and tax firms, in Google's local three-pack 44% of the time, but recommended by ChatGPT only 3.1% of the time and by Perplexity 9.9%. That gap is a reason to get the basics right on every branch page.
Give each branch page content of its own. Google's doorway policy lists city-targeted pages that funnel users to one page among its examples. A real branch with its own hours, services and staff is fine. A templated city page where you have no branch matches Google's examples.
Business Profiles have their own rules, and several hit banks directly. Google allows one profile per location, asks every location of a chain to use the same name, and bans marketing taglines in the name, using a US bank's slogan as its example.
Give Bing Places and Apple Business Connect the same care. Microsoft says registering with Bing Places helps keep details eligible for AI-generated responses. Apple said at the 2023 launch of Business Connect that place cards reach Apple Maps, Siri and other apps, and the tool is now part of Apple Business.
Put a handful of your branch pages next to their Google, Bing and Apple listings and note every field that disagrees. That tells you how much cleanup your network needs.
One template change can break rendering, markup or canonical tags on every page built on it, so run these checks on each release of your product and branch templates, not only in an audit.
Paste the list into your release checklist and hold any template that fails a line.
As a performance marketing and AI search agency, we turn checks like these into tickets for your web team, each with its evidence, such as the raw HTML a crawler received, and the template it affects, so one fix reaches every page built on it. That work is part of our SEO and AI search services for banks.
Get a clear picture of your bank's AI Search visibility, competitive positioning, and biggest opportunities for improvement with our AI Visibility Assessment.
AI Visibility AssessmentOnly if the markup and the page draw on the same rate source and update at the same moment. You can test this by changing a rate in a staging environment and checking that the page and the JSON-LD change together. If they don't, mark up the product type and leave the rate to the page text.
Fetch the page with scripts disabled or view its raw source, since that is close to what crawlers that do not run JavaScript receive. Search Console's URL Inspection shows what Googlebot rendered, and Bing Webmaster Tools' AI Performance report shows which of your pages Copilot cites. Server logs show whether each platform's crawler is reaching the pages at all.
Not necessarily. Google allows an ATM attached to a branch, or one inside another business, to have its own Business Profile, named as the bank's name plus "ATM" without location details, and a branch page can list an attached ATM and its hours. For standalone ATMs, you can choose between profiles, an ATM locator with crawlable links and dedicated pages for the locations that warrant them.
Copyright © 2026 CB/I DIGITAL INC. All rights reserved | Privacy Policy