Skip to content
AEOprobe
Financial content and crawler access

AEO for Financial services

Review financial product pages for current facts, visible terms, accurate authorship and accessible disclosures.

Updated

What to check yourself

Use a technical audit to check the page and access signals that can be observed. AEOprobe has no verified current industry-wide AI Overview percentage for financial services. An audit does not prove product suitability, regulated status or AI visibility.

Recommended schemas

FinancialProduct
The financial offering the page describesIt can include interestRate, annualPercentageRate or feesAndCommissionsSpecification when they are relevant and accurate. Not every product has all of these properties.
Organization, Person and Article
Real institutions, authors and editorial pages

Use only markup that applies and matches content visitors can see.

Google FAQ rich results stopped appearing from 7 May 2026.

Write helpful Q&A on the page and do not promise a rich result.

Common AEO issues

Common AEO issues, their impact and fixes
IssueImpactFix
Rates, fees or eligibility are inconsistentImpactReaders and tools can receive conflicting product terms.FixCheck current terms against the institution’s approved product information. Keep visible text and any applicable markup consistent.
Required disclosures are hard to findImpactReaders may miss qualifications or limitations that matter to their decision.FixKeep disclosures accessible and suitably prominent, as the institution’s compliance requirements ask. Do not move them for an unverified AI benefit.
Key facts exist only in an interactive calculatorImpactA crawler that does not run JavaScript may miss the underlying assumptions or rates.FixGive an accessible explanation of the current inputs and assumptions. Inspect the initial and rendered content.
Authorship or institutional identity is unclearImpactReaders cannot easily assess the source and currency of the information.FixShow real bylines, institution details and actual update dates. Markup does not establish regulated status or expertise.

Key tools

Step-by-step guide

  1. 1

    Select approved public product pages

    Record the offering, approved terms, source and date. Keep applications, customer accounts and private documents outside the public review.

  2. 2

    Inspect public crawler access

    Decide which uses of your public content you intend to allow.

    • Check each relevant crawler’s current documentation.
    • Search and training bots have different roles. For example, OAI-SearchBot is for search and GPTBot is for training.
    • Check robots.txt and hosting or firewall access separately.
    • Protect private content with authentication and authorization. Robots.txt is not access control.
  3. 3

    Verify terms and disclosures

    Keep rates, fees, eligibility and required disclosures accurate and accessible. Have the right owner at the institution review how they are presented.

  4. 4

    Validate relevant markup

    Describe the actual institution and financial offering. Include only applicable properties that match current visible facts.

  5. 5

    Publish an approved repair

    Publish the repair once it is approved. The institution stays responsible for reviewing product and disclosure accuracy.

  6. 6

    Recheck and retain evidence

    Compare the same URL and technical observation after publishing. A passing recheck is not evidence of regulatory compliance, suitability or citation gains.

From a finding to a checked repair

The free audit covers up to 3 pages and needs no sign-up. A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. A free account shows 5 findings for each site, and a paid plan shows them all.

A saved-site finding becomes a to-do with the evidence, what to change and how to check it. You or your developer publish the edits, then run a scoped technical recheck. Claude Code and Codex can work in the same flow. After a coding agent reports a fix, its recheck runs by itself within your weekly credit limit. Every other action that spends credits asks for your confirmation first.

AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Credit packs add extra credits to a Watch or Pro plan. Only customers with an active Watch or Pro plan can buy them. Credits that expire soonest are used first, usually the monthly ones. Bought credits stay valid for 12 months after purchase, even if your plan ends. They can still pay for audits and checks after your plan ends. They do not open the full lists without an active Watch or Pro plan. A page capture or recheck costs 1 credit. Your account shows what you can buy. See plans and credits and the coding-agent workflow.

Sources and technical guidance

Checked Oct 2026

Questions

Should I move disclosures below the main content for AEO?

AEOprobe has no evidence for that tactic. Keep required terms and disclosures accessible and suitably prominent. Follow the institution’s compliance requirements.

Does structured data guarantee AI search inclusion?

Google does not require special schema for generative search. Markup does not guarantee a citation.

What does AEOprobe check?

The audit checks robots.txt policies for AI crawlers and other technical page findings. For structured data it reads JSON-LD only. See the audit methodology.

How do I turn a finding into a published fix?

A saved-site finding becomes a to-do with what to change and how to check it. You publish the edits, then run a recheck. See the steps and costs on this page.

Check what AI crawlers can actually reach

Run a free audit to find public crawler, indexing, markup, and page-structure issues.

Run free audit