Before you write another line of FAQPage markup, there is something you need to know.
On 7 May 2026, Google added a deprecation notice to its FAQ structured data documentation. FAQ rich results no longer appear in Google Search, for any site, including the government and health domains that held the last remaining eligibility.
That does not mean FAQ schema is worthless for financial products. It does mean most advice written before May 2026 is now misleading, and that the real work for financial sites was always somewhere else.
Here is what changed, what to keep, and what actually moves the needle for regulated financial content.
What Changed on 7 May 2026
Google retired the feature in three phases:
- May 2026. FAQ rich results stopped appearing in Google Search.
- June 2026. The FAQ search appearance filter, the Search Console rich result report, and Rich Results Test support were removed.
- August 2026. FAQ rich result data disappeared from the Search Console API.
That last date matters operationally. Teams running automated dashboards or BigQuery exports against the Search Console API needed to update those calls or risk silent null returns in downstream reporting. If your client reporting still queries that field, check it today.
Google published no blog post and gave no reasoning beyond the documentation banner.
The Distinction That Decides Everything
Half the industry declared FAQ schema dead within a day. The other half declared it more important than ever for AI search. Both reactions miss the same distinction.
The rich result was the expandable question-and-answer dropdown under your listing. That is gone.
The schema is the markup telling a machine that one block is a question and another is its answer. That remains a valid Schema.org type.
FAQPage markup will not throw errors, will not trigger a manual action, and will not damage rankings if you leave it in place. Google has repeatedly stated that unused structured data does not cause problems for Search.
Only the visual feature ended. The markup was not deprecated.
Should Financial Sites Keep FAQ Schema?
The answer depends on why it is there.
| Page Type | Recommendation | Reasoning |
|---|---|---|
| Genuine Q&A pages, help centres, support hubs | Keep | The schema describes what the page actually is |
| Product pages with a real FAQ section | Keep if questions are genuine and visible | Harmless, and honestly descriptive |
| Pages where FAQs were added purely for the SERP dropdown | Remove the FAQs, not just the markup | The content was never for readers |
| Thin FAQ blocks written to trigger the feature | Remove both | Filler on a YMYL page is a liability |
For help centres and support hubs, the schema is not a layer on top of the content. It is the content. The deprecation changes nothing structural for those pages.
The uncomfortable version of this advice: if removing the FAQ section would improve the page for a reader, it was never really an FAQ.
There is also an honest reading of why this happened. FAQPage was designed for pages whose primary purpose is question-and-answer content. The far more common case, a product page with an FAQ section bolted on, had no accurate markup alternative. Publishers chose misrepresentation because the reward sat on that side of the choice.
The AI Citation Claim, Examined Honestly
You will read that FAQ schema improves your odds of being cited by ChatGPT, Perplexity, or AI Overviews. Treat that as unproven.
Google published its first dedicated generative AI search guide on 15 May 2026 and stated plainly that structured data is not required for AI Overviews or AI Mode, and that no special Schema.org markup exists for them.
The best available data is also more ambiguous than the confident claims suggest. Ahrefs scanned six million URLs and found AI-cited pages were roughly three times as likely to carry JSON-LD. That is correlation. Ahrefs then followed 1,885 pages that added JSON-LD between August 2025 and March 2026 against 4,000 matched controls. The follow-up showed AI Mode citations up 2.4% and ChatGPT up 2.2%, neither statistically significant, while AI Overview citations fell 4.6% relative to controls.
Cited pages tend to have stronger links, real editorial history, cleaner technical setups, and recognised brands. Assigning the win to markup alone is where people go wrong.
Keep FAQ schema on financial pages if it honestly describes the content. Do not sell it to a compliance team as an AI visibility strategy.
FAQ Schema Best Practices That Still Apply
Where you keep it, implement it properly.
- Maintain strict content parity. Every question and answer in the markup must appear visibly on the page, in the same wording.
- Use one FAQPage entity per page. Multiple competing blocks create ambiguity.
- Write questions people actually ask. Pull them from support tickets, call logs, and search queries, not from a keyword tool.
- Answer completely in the answer field. No teaser text pointing elsewhere.
- Use JSON-LD, placed in the head or body, rather than microdata.
- Do not mark up promotional copy as an answer. That was always against the guidelines and is now pointless as well.
- Validate with Schema.org tooling, since Google’s Rich Results Test no longer covers FAQ.
Why Financial Products Need More Than FAQPage
Here is the part most FAQ-focused advice skips entirely.
Financial content sits inside Google’s Your Money or Your Life category, where accuracy expectations are highest. Generic markup does not capture what a financial product actually is.
Schema.org provides a dedicated hierarchy. FinancialProduct is the parent type, subclassed into BankAccount, PaymentCard, LoanOrCredit, InvestmentOrDeposit, PaymentService, and CurrencyConversionService.
Those types carry properties generic Product markup cannot express: interestRate, annualPercentageRate, feesAndCommissionsSpecification, loanTerm, loanRepaymentForm, amount, and areaServed.
That last property matters more than it looks. Jurisdiction tagging through areaServed specifies where a product is licensed and available, a precision requirement that generic schema does not impose and that regulators very much care about.
The Schema Types That Matter for Financial Products
| Type | Use For | Key Properties |
|---|---|---|
| FinancialProduct | General products and services | name, description, provider, interestRate, feesAndCommissionsSpecification |
| LoanOrCredit | Mortgages, personal loans, credit lines | amount, interestRate, annualPercentageRate, loanTerm, loanRepaymentForm |
| BankAccount / DepositAccount | Current and savings accounts | amount, interestRate, availableChannel |
| InvestmentOrDeposit | ISAs, retirement accounts, funds | amount, currency, feesAndCommissionsSpecification |
| PaymentCard | Credit and debit cards | annualPercentageRate, feesAndCommissionsSpecification |
| Organization / BankOrCreditUnion | The institution itself | name, sameAs, address, identifiers |
| FAQPage | Genuine question content | mainEntity with matching visible Q&A |
Prioritise the product-level types. A correctly marked-up mortgage page communicates far more to a machine than an FAQ block ever did.
Use the sameAs property on your Organization markup to link authoritative external profiles. Entity clarity does more for a regulated brand than any single rich result ever did.
Compliance Rules Specific to Financial Schema
Structured data on a financial product page is a public statement about that product. Treat it accordingly.
- Never state a rate, fee, or term in markup that differs from the visible disclosure. Divergence is a compliance exposure, not an SEO error.
- Never imply protections you do not have. Deposit insurance, regulatory authorisation, and licensing claims must be accurate and verifiable.
- Tag jurisdiction explicitly where products are geographically restricted.
- Version-control rate changes. When a rate updates on the page, the markup must update in the same release, not the next sprint.
- Route markup through the same review as the disclosure copy. If legal signs off the visible text, legal signs off the structured data.
- Keep an audit trail of what was published when, since financial claims may need to be evidenced later.
This is general guidance rather than legal or compliance advice. Anything touching rates, protections, or regulatory status should go through your own compliance function before publishing.
Content Parity Is a Regulatory Issue, Not Just an SEO One
Most SEO guidance treats parity as a Google guideline. In financial services it is more serious than that.
Markup claiming a 4.5% rate on a page displaying 4.2% is a discrepancy in a public representation of a regulated product. It does not matter that only machines read one of them.
Build parity into the deployment process rather than checking it in an audit. Rate values should come from a single source that populates both the visible page and the JSON-LD, so the two cannot drift.
An Implementation and Governance Workflow
- Inventory. List every page carrying FAQPage markup and classify it against the keep-or-remove table above.
- Clean up. Remove FAQ blocks that existed only for the rich result.
- Fix reporting. Update any Search Console API queries referencing FAQ rich result data.
- Prioritise product markup. Add or correct FinancialProduct and its subtypes on rate-bearing pages.
- Bind values to a single source. Rates and fees populate visible content and markup from the same field.
- Add compliance review to the schema deployment checklist.
- Validate quarterly across templates, not on one sample URL.
Mistakes Worth Avoiding
- Stripping FAQPage markup in a panic from pages where it honestly describes the content.
- Keeping FAQ filler because “AI might read it.”
- Selling FAQ schema internally as an AI citation strategy.
- Marking up rates that differ from the visible page.
- Using generic Product schema for regulated financial products.
- Leaving Search Console API calls pointed at retired FAQ fields.
- Validating one page and assuming the template is clean.
The Short Version
FAQ schema is comprehension markup now, not a visibility feature. Keep it where it describes real questions, remove it where it was decoration, and stop expecting anything from it in the SERP.
For financial products, the higher-value work sits in FinancialProduct and its subtypes, tied to accurate rates, correct jurisdictions, and disclosures that match. That work survives algorithm changes because it is simply an honest machine-readable description of what you sell.
FAQs
Is FAQ schema still worth using in 2026?
Yes, where it honestly describes real question-and-answer content. It no longer produces any visible Google Search feature.
Did Google deprecate FAQPage schema?
No. Google deprecated FAQ rich results on 7 May 2026. FAQPage remains a valid Schema.org type that can stay on your pages.
Does FAQ schema help with AI search citations?
It is unproven. Google states structured data is not required for AI Overviews, and controlled studies show no statistically significant citation gain.
Which schema types should financial product pages use?
FinancialProduct and its subtypes, including LoanOrCredit, BankAccount, InvestmentOrDeposit, and PaymentCard, alongside Organization markup.
What is the biggest schema risk for financial websites?
Markup that states rates, fees, or protections differing from the visible disclosure, which creates compliance exposure rather than just an SEO error.
