Answers

Should banks keep FAQ pages and FAQ schema after Google retired FAQ rich results?

By ·

An open FAQ binder pairs answer cards with matching markup, beside a retired search embellishment and a separate AI review tray.

Banks should keep accurate, useful FAQ pages. Google’s retirement of FAQ rich results does not require blanket deletion of FAQ schema. Review existing markup with your site maintainer, keep it consistent with visible answers, and assess Google AI eligibility separately.

The short version

Keep useful FAQ answers, and review FAQ schema rather than deleting it automatically. For banks considering FAQ schema after Google retired FAQ rich results, the practical decision is whether the answers remain accurate and whether anything on the site depends on the markup. Google does not require special schema for its AI features.

Separate the answer, the markup, and the presentation

Treat these as distinct parts of your site and its search appearance:

Visible answers: The questions and answers a customer can read on your page.

FAQ markup: The structured data describing those questions and answers.

FAQ rich results: The Google Search presentation that has been retired.

Google AI eligibility: The conditions for a page to be eligible as a supporting link in AI Overviews or AI Mode.

Retiring a search presentation does not tell you whether your account-opening instructions or loan-payment answers are useful. Assess those answers on their own merits.

Google’s documentation update, dated June 15, 2026, says it removed the FAQ rich result documentation. It also says the feature is no longer shown in Google Search results, as announced in its May 2026 changelog.

That establishes the status of Google’s FAQ rich result feature. It does not establish how other answer engines use FAQ markup.

Google AI eligibility is a separate check

Google’s guide to AI features says there are no additional requirements or special optimizations necessary to appear in AI Overviews or AI Mode. It also says no special schema.org structured data is required.

A supporting page must be indexed and eligible for a Search snippet. Google does not guarantee indexing, inclusion, or serving, even when a page meets the requirements.

For your team, that means a markup check cannot substitute for an eligibility check. Valid FAQ markup is not evidence that Google will cite the page or name your institution.

Google also says important content should be available in textual form and structured data should match visible text. This gives you a concrete test: compare the answer customers can read with the answer stored in the markup.

If an answer exists only in an image, make it available as text. If the markup contains an older answer than the page, correct the mismatch. Neither task requires buying a measurement platform.

Audit existing FAQs before changing templates

Start with pages that answer consequential customer questions: eligibility, required documents, fees, account access, and payment instructions. Treat rates, fees, and disclosures with particular care.

Create a simple worksheet with these fields:

Visible answer. What to record: The exact answer a visitor can read.

Accuracy. What to record: Any outdated terms, instructions, or missing conditions.

Text availability. What to record: Whether the important answer is available as text.

Markup match. What to record: Whether structured data agrees with the visible answer.

Site dependency. What to record: What the maintainer needs to check before changing markup.

Google eligibility. What to record: Whether the page is indexed and eligible for a Search snippet.

Ask your site maintainer where FAQ markup comes from. Check whether the same component also produces visible answers, whether a template adds markup automatically, and whether existing checks still expect the retired search presentation.

These are inspection questions, not assumptions about your site. Removing a markup field and removing a customer-facing answer are different changes. Establish which change a proposed fix would actually make.

This is a useful handoff between marketing and digital teams: marketing checks the answer, while the site maintainer identifies how the page and markup are produced.

Decide what to retain, correct, or remove

Retain useful answers. Keep answers that resolve a real customer task and accurately describe your institution’s current offering. Do not remove them solely because the rich result disappeared.

Correct mismatches. Where structured data remains, align it with the visible text, consistent with Google’s guidance.

Review markup on its own merits. If it was maintained only for Google’s former FAQ presentation, reassess that purpose. Do not claim that the decision has the same effect across other engines.

Remove obsolete answers deliberately. A discontinued process or inaccurate product answer needs attention regardless of its markup. Decide whether to correct, replace, or remove the visible content first, then make the markup consistent.

Check the outcome without confusing the signals

After a change, verify the published page rather than relying only on the editing screen. Confirm that the answer is visible as text and that any retained structured data matches it.

Check Google indexing and snippet eligibility separately. Do not use the absence of a retired FAQ rich result as evidence that the page has failed.

For AI answer checks, record the exact customer question, engine, date, answer, and cited page. Repeat the same questions after changes. Treat a citation or omission as an observation, not proof that FAQ markup caused it.

Start with a page-level audit before considering template-wide changes.

Questions people ask

Should our bank delete all FAQ schema now?

No blanket deletion is warranted by the retirement of a Google presentation feature. Base the decision on the markup’s current purpose and the findings of your site audit.

Do we still need FAQ pages?

Keep pages that answer genuine customer questions accurately. Assess the usefulness of the answers separately from the search feature that once displayed them.

Does FAQ schema help us qualify for Google AI Overviews?

Google’s guide to AI features says no special schema.org structured data is required. A supporting page must be indexed and eligible for a Search snippet, and inclusion is not guaranteed.

What if the page is accurate but its FAQ markup is outdated?

Correct the mismatch or remove the outdated markup if your audit supports that decision. Google’s guidance says structured data should match visible text.

Does Google’s decision tell us what other AI engines do?

No. Google’s guidance describes its own features, not how other providers use FAQ markup. Assess each engine separately rather than assuming the same treatment.

Related
More on fixing what engines cannot read