Skip to content
AEOprobe
Client audit and repair workflow

AEO for Agencies

Build an evidence-based review of your clients’ public pages, with clear repair owners and technical rechecks.

Updated

How to frame client work

This is a suggested workflow for delivering client work. It makes no claim about agency demand, market size or typical results. Before you present an audit as client work, agree on the public pages, the evidence, the implementation owner and the measurement scope.

Recommended schemas

Organization and Service
The agency and its actual offerings
A suitable LocalBusiness subtype
A real local business
Article
Genuine editorial content or case studies

The generic ProfessionalService type is deprecated.

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
Audit and implementation responsibilities are unclearImpactA finding can remain unresolved when nobody owns the change or publishing step.FixBefore work starts, assign the page, evidence and proposed repair, and name the publisher and recheck owner.
Client scope exceeds the selected planImpactSaved sites, page limits, audit allowances and credit balance all limit the work you can propose.FixCheck the current allowances. Free supports 1 base saved site, Watch 1 (up to 3 with extra sites) and Pro 10 (up to 100). A saved-site audit costs 20 credits. It checks up to 10 pages on Free, 50 on Watch or 100 on Pro.
Case-study claims lack supporting evidenceImpactTechnical changes can be wrongly presented as the cause of ranking, revenue or citation improvements.FixUse real evidence, dates, scope and limitations. Label examples and separate observed outcomes from causal claims.
Service pages promise unsupported outcomesImpactClients can mistake a diagnostic result for guaranteed visibility or a complete implementation.FixDescribe actual deliverables and review boundaries. Do not promise guaranteed AI citations. Do not promise an API, batch or white-label workflow that has not been verified.

Key tools

Step-by-step guide

  1. 1

    Agree on evidence and scope

    Choose the client’s public URLs and intended audience. Record which pages and controls are in scope and who can approve edits.

  2. 2

    Run a technical review

    Start with the free audit. Use a saved-site audit when you need more pages.

  3. 3

    Verify findings and source facts

    Review the evidence and unknowns with the client. Separate access findings, markup checks and editorial judgments.

  4. 4

    Prepare the implementation handoff

    Hand the saved-site to-dos to whoever publishes the edits.

  5. 5

    Publish and recheck

    The client or authorized developer publishes approved edits. Recheck the same technical findings and record anything unchanged or uncheckable.

  6. 6

    Report the right acceptance level

    Report scope, sources, published changes and recheck results. Keep customer acceptance, traffic and observed citations separate from the technical report.

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

Does AEOprobe provide an unlimited white-label agency API?

No. AEOprobe’s plans do not include white-label reports, batch audits or a public API. Agencies use the saved-site audit, repair and recheck flow within their plan and credits.

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