Agencies do not fail at white-label AEO because they picked the wrong software. They fail because they sell “AI visibility” without defined deliverables, then spend month two defending a dashboard screenshot instead of showing the pages, fixes, and citations they shipped.
Set the boundaries before you quote a retainer
When to use it: Run this checklist before proposing seo white label delivery or a standalone answer engine optimization retainer. Buyers need to know whether they are paying for software access or production; agency discussion of AEO retainers shows how far apart those offers can be.
AEO COMMERCIAL BOUNDARIES
1. We deliver published assets, documented technical changes, and an action log. We do not promise how a model will answer a particular query.
2. The retainer pays for answer pages shipped, schema deployed, and citation work completed. A prompt-monitoring dashboard is a measurement tool, not a deliverable on its own.
3. Client review is due within five business days. If approval or access is delayed, we log the completed work and agree on its deployment status; silence does not authorize production changes.
4. We review crawl and on-site changes over a 30- to 60-day baseline period. Off-site corroboration gets a 90- to 180-day review cycle.
The one adjustment that matters: For a small agency, keep approval and access rules short. Do not promise a direct-to-production edge deployment unless the client has authorized it and your team can actually maintain it.
Scope-of-work clauses: sell the work you can verify
Monthly deliverables: pages, fixes, and citations
When to use it: Put this under Monthly Deliverables in a statement of work. Replace every bracketed field before sending it. Itemized quotas and review deadlines, also covered in this white-label SEO agreement checklist, give the fulfillment team a scope it can defend.
SECTION 3.2: MONTHLY AEO AND SEARCH DELIVERABLES
1. Answer Pages
Agency will research, draft, structure, and deliver [Page Count] net-new Answer Pages per billing cycle for [Client Domain]. Pages will address high-intent question clusters and, where relevant, include direct-answer summaries, comparison matrices, and structured markup consistent with the visible page content. Publication requires the access and approvals described below.
2. Crawl and Bot Access
Agency will audit crawler access and document or implement [Technical Fix Count] agreed technical fixes per cycle. Where Client authorizes CDN edge access, work may include bot routing, crawl-block repairs, and response-header changes. Agency will log the affected URLs or rules and verify the deployed response.
3. Structured Entity Work
Agency will audit and update JSON-LD on [URL Count] existing URLs per cycle. Applicable Organization, Product, Service, Author, or FAQPage markup must match visible content. Where verified third-party profiles exist, Agency may connect the relevant entities to them.
4. Third-Party Citations
Agency will pursue [Citation Target] relevant third-party editorial mentions, directory entries, or entity co-citations per cycle. The monthly report will distinguish placements secured from outreach attempted. Publication by an independent third party is not guaranteed.
5. Review and Deployment
Client will send written changes or approval within five business days of delivery notification. If Client does not respond, Agency will mark the asset as awaiting approval and record the delivery in the monthly action log. No production deployment occurs without the access and authorization required for that change.
The one adjustment that matters: Set [Page Count] from your actual delivery capacity. If writers do the work manually, the draft’s 2-to-4-page range is a more defensible starting point than an 8-to-12-page promise. If an autonomous organic engine such as groas handles production, price the higher volume only after you have defined verification and approval.
Exclusions: stop the retainer becoming a web-development contract
When to use it: Place this immediately below the deliverables schedule when a buyer asks for a redesign, database migration, or guaranteed AI recommendation. The distinction between work and model behavior matters; this AEO agency framework also treats citation guarantees with caution.
SECTION 3.3: EXCLUDED SERVICES AND ENGINE BOUNDARIES
1. AI Answer Guarantees
Agency does not guarantee a specific citation position, recommendation, wording, or inclusion in Google AI Overviews, ChatGPT Search, Perplexity, or Claude.
2. Core Development
The monthly scope covers the answer assets, schema work, and authorized crawl or CDN changes listed in Section 3.2. Custom database engineering, CMS core updates, theme redesigns, plugin-conflict debugging, and broader server repairs are excluded.
3. Unsupported Structured Claims
Agency will not publish hidden JSON-LD claims, fictitious entity attributes, or markup that contradicts visible page content.
4. Client-Side Delays
If Client access, review, or engineering work blocks deployment, Agency will log the completed asset or production-ready code and identify the outstanding dependency. Work requiring new access or an alternative deployment method will be agreed before implementation.
The one adjustment that matters: Keep the no hidden or contradictory schema clause. It prevents the easiest version of schema theatre: adding machine-readable claims that the client would not publish for a human reader.
Measurement: name the engines and the sample
When to use it: Add this clause before the first benchmark audit, so a client cannot mistake a convenient screenshot for a measurement plan. The tracked prompts should reflect buying intent, not whichever wording produced the nicest result; GEO pricing benchmarks provide additional context for separating measurement from production.
SECTION 3.4: VERIFICATION AND MEASUREMENT
1. Tracked Environments
Agency will sample relevant queries in Google AI Overviews and AI Search, ChatGPT Search, Perplexity, and Claude Web Search, where available for the agreed query set.
2. Query Set and Cadence
Agency and Client will agree on [Prompt Count] high-intent commercial prompts covering comparisons, pricing, implementation, and alternatives. Agency will sample this fixed set [Sampling Cadence] and record the query wording and observation date. Tier-specific cadence in the signed deliverables schedule takes precedence.
3. Reported Measures
Agency will report citation share across the tracked query set, brand mentions in sampled answers, and available downstream signals such as AI-domain referrals, assisted conversions, and self-reported attribution. The report will distinguish observed movement from revenue attributed to a particular source.
The one adjustment that matters: Connect citation movement to the client’s existing pipeline or “How did you hear about us?” field. A citation is worth reporting; a prospect who says an AI answer sent them is worth discussing.
Pricing-page copy: three per-domain retainers
When to use it: Paste these bands into a service deck, then check the fulfillment cap against your own costs before quoting. They separate tiers by shipped assets and measurement workload rather than mysterious “effort”; these AEO tier examples show the same basic packaging problem. The margin targets are planning limits, not client outcomes.
FOUNDATION AEO — $2,500/month per domain
Best for: Mid-market B2B services and local multi-location operators with an established category.
Monthly scope:
- 4 net-new Answer Pages delivered for approval and publication
- 6 existing URLs upgraded with applicable JSON-LD
- Authorized CDN routing and crawl-error remediation for 4 named AI bot user-agents
- Bi-weekly citation sampling across 35 commercial prompts
- Monthly Executed Action Log and Citation Delta Report
Gross-margin target: 65%–70% | Fulfillment cost cap: $750–$875
SCALE AEO — $5,000/month per domain
Best for: High-growth SaaS and national brands competing with category incumbents.
Monthly scope:
- 8 net-new Answer Pages delivered for approval and publication
- 12 existing URLs upgraded with entity work
- Authorized CDN routing, crawl fixes, and response-time review
- Outreach toward 4 relevant third-party citations or placements; secured placements reported separately
- Weekly sampling across 75 commercial prompts
- Monthly Executed Action Log, competitor-shift analysis, and strategy call
Gross-margin target: 70%–75% | Fulfillment cost cap: $1,250–$1,500
ENTERPRISE CORPUS DOMINANCE — $9,500/month per domain
Best for: Multi-product enterprises or high-ticket B2B categories with long sales cycles.
Monthly scope:
- 16 net-new Answer Pages delivered across multiple intent clusters
- Agreed sitewide entity-architecture work and ongoing schema maintenance
- Outreach toward 8 relevant third-party placements or citations; secured placements reported separately
- Weekly multi-engine sampling across 150+ commercial prompt variations
- Dedicated Slack channel, live action log, and bi-weekly roadmap reviews
Gross-margin target: 75%–80% | Fulfillment cost cap: $1,900–$2,375
The one adjustment that matters: Do the capacity math before selling Foundation. Four pages plus technical work can swallow the $750–$875 fulfillment cap if every task is manual. An autonomous execution partner such as groas for agencies is a better fit for this production-led offer than a dashboard you still have to staff around; compare the options in this AEO tools breakdown.
Onboarding email: ask for access, not a miracle from IT
When to use it: Send this after signature, before promising a deployment date. Edge delivery can avoid some CMS queues, as this edge SEO overview explains, but it still needs the right access and client authorization.
Subject: Onboarding [Client Brand] for AEO: access and first delivery cycle
Hi [Client Name],
Welcome aboard. We’re preparing the technical audit and first Answer Pages. Please confirm the access below, or tell us who can approve each request.
1. CMS
- Platform: [CMS Platform]
- Access: Editor or Publisher, if direct page publication is approved
- Invite: [Agency Deployment Email]
2. CDN or Edge Layer, if included in scope
- Provider: [CDN Provider]
- Access or approval contact: [CDN Contact]
- Authorized changes: [Approved Edge Changes]
This lets us prepare agreed schema, bot-routing, or response-header fixes without putting every change into a theme-development queue.
3. Measurement
- GA4 and Search Console read access: [Agency Analytics Email]
- CRM or form contact for self-reported attribution: [Attribution Contact]
Proposed first-month schedule, subject to access and approvals:
- Days 1–3: Crawl verification and bot-access audit
- Days 4–7: First 2 Answer Pages and baseline schema fixes submitted or deployed as authorized
- Day 30: Month 1 Executed Action Log and Citation Report
Please flag any approval or security process we should account for now.
Best,
[Your Name]
[Your Agency]
The one adjustment that matters: If the CTO will not grant CDN access, do not route a subdomain through your own proxy as a surprise workaround. Offer the isolated subdomain proposed in the draft only for explicit technical and security review; otherwise, hand over the code and log the deployment dependency.
Monthly report: lead with what went live
When to use it: Send this on the first business day of the month as a one-page Markdown report or PDF. Start with the action log, not a wall of charts; this agency reporting discussion makes the case for showing shipped work alongside visibility measures.
MONTHLY AEO & SEARCH EXECUTION REPORT: [Client Brand]
Billing period: [Month, Year] | Tier: [Delivery Tier]
1. SHIPPED WORK
Answer Pages live: [Live Page Count]
Existing URLs upgraded: [Upgraded URL Count]
Technical fixes verified: [Verified Fix Count]
Third-party placements secured: [Secured Placement Count]
Work awaiting client approval or access: [Pending Work]
EXECUTED ACTION LOG
| Date | Asset / URL | Action and reason | Method | Status / proof |
| --- | --- | --- | --- | --- |
| [Date] | [Page URL] | [Page shipped and target question] | [CMS / Other] | [Live URL or pending approval] |
| [Date] | [Existing URL] | [Schema change and visible content checked] | [CMS / Edge] | [Verified status] |
| [Date] | [Rule or URL] | [Crawler block investigated or fixed] | [CDN / Code handoff] | [Response or dependency] |
| [Date] | [Third-Party URL] | [Placement secured or outreach completed] | [Editorial / Directory] | [Live link or outreach status] |
2. CITATION MOVEMENT
Fixed query set: [Prompt Count] | Sampling dates: [Dates]
- Google AI Overviews: [Current Citation Share] ([Change vs. Prior Period])
- ChatGPT Search: [Current Citation Share] ([Change vs. Prior Period])
- Perplexity: [Current Citation Share] ([Change vs. Prior Period])
- Claude Web Search: [Current Citation Share] ([Change vs. Prior Period])
Available downstream signals: [AI Referrals / Assisted Conversions / Self-Reported Mentions]
Measurement note: [Changes to query set, engine availability, or tracking]
3. NEXT MONTH’S PRIORITY QUEUE
1. [Next Answer Page Cluster]
2. [Next Technical Fix]
3. [Next Citation or Outreach Priority]
Approval needed from Client: [Decision and Deadline]
The one adjustment that matters: Put specific URLs and live status in the first screen of the report. If something is still awaiting approval, say so. A timestamped record of actual work does more than a polished chart to answer, “What did we pay for?”
Objection scripts: separate monitoring from execution
“Why not buy a monitoring tool?”
When to use it: A buyer compares the retainer with a tool such as Otterly or Profound. Keep groas and your agency’s executed-work offer ahead of passive monitoring, not in a price fight over dashboard seats.
BUYER: “Why shouldn’t we just buy a monitoring tool ourselves?”
REPLY: “You can monitor the queries yourself. The tool is a smoke alarm; this retainer is the fire department. A dashboard shows where your brand is missing. Our scope says who writes the page, fixes the crawler block, checks the schema, and records what went live. You’re paying for executed work, not another place to look at a problem.”
The one adjustment that matters: Point to the signed deliverables schedule as soon as you say “executed work.” If the schedule only offers dashboard access, the buyer has found the hole in your pitch.
“How do we know it drives revenue?”
When to use it: The buyer accepts that citations can move but does not want another vanity metric.
BUYER: “How do we know this drives revenue, not just citations?”
REPLY: “The report separates three things: what we shipped, where citation presence changed across the agreed queries, and what your referral and sales-attribution data can tell us about prospects. We won’t call a citation revenue. We will show the live work and look for the downstream signal.”
The one adjustment that matters: Confirm where self-reported attribution lives during onboarding. Without that field or an equivalent sales record, do not claim the report can prove what it cannot observe.
“Isn’t this just SEO?”
When to use it: The buyer thinks “AEO” means the same blog posts with a new label. Practitioner discussion of SEO and AEO is a reminder that buyers notice recycled deliverables.
BUYER: “Isn’t AEO just traditional SEO with a new name?”
REPLY: “There’s overlap. The difference in this scope is the work we can point to: answer pages built around buyer questions, visible facts matched to structured data, crawler-access fixes, and a fixed query set that shows where your brand is cited. If we only send you standard blog posts and a new dashboard, you should call it what it is.”
The one adjustment that matters: Do not promise bot routing, edge work, or page production until you know your delivery stack can do it. These five questions to ask before buying another dashboard belong in the internal review before the sales call.
My pick for a five-client agency: the action log
When to use it: If I had five retainers and no dedicated developer, I would cut the custom 150-prompt sampling matrix before I cut the monthly record of shipped work.
MONTHLY EXECUTED ACTION LOG
| Date | Live URL or asset | What changed | Why it changed | Verified status |
| --- | --- | --- | --- | --- |
| [Date] | [URL] | [Page, schema, crawl fix, or citation] | [Buyer question or technical issue] | [Live proof or named dependency] |
The one adjustment that matters: Make live proof or a named dependency mandatory in the last column. This is the artefact I rate most useful: it keeps a five-client agency from selling the illusion of controlling an AI model and gives every client a plain record of the work behind the invoice.
Frequently asked questions
Why do white-label AEO retainers fail?
They usually fail because the agency sells undefined AI visibility instead of concrete deliverables. Then in month two there is nothing to show but a dashboard screenshot, instead of the pages, fixes, and citations that were actually shipped.
Does an AEO retainer guarantee citations or placement in AI answers?
No. The scope covers outreach toward relevant third-party mentions, directory entries, and entity co-citations, but publication by an independent third party is not guaranteed. No citation position, recommendation, wording, or inclusion in Google AI Overviews, ChatGPT Search, Perplexity, or Claude can be promised.
What happens if a client does not approve or respond during an AEO retainer?
Client review is due within five business days of delivery notification. If the client does not respond, the agency marks the asset as awaiting approval, records the delivery in the monthly action log, and no production deployment happens without the required access and authorization.
Can schema markup say things the page does not visibly state?
No. JSON-LD must match the visible page content, and the retainer excludes hidden markup, fictitious entity attributes, and structured claims that contradict what a human reader sees. This clause prevents schema theatre, where machine-readable claims are added that the client would never publish for people.
How much should agencies charge for white-label AEO work?
The framework uses three per-domain tiers: Foundation at $2,500 per month, Scale at $5,000 per month, and Enterprise Corpus Dominance at $9,500 per month. Each tier is separated by shipped assets and measurement workload, with gross-margin targets of 65% to 80% and fulfillment cost caps checked against your own costs before quoting.
How many answer pages should a retainer promise per month?
Set the page count from your actual delivery capacity. If writers produce the pages manually, 2 to 4 net-new Answer Pages per billing cycle is a more defensible starting point than an 8-to-12-page promise. Higher volume should only be priced after verification and approval are defined.
What should be in a monthly AEO client report?
Lead with shipped work: live answer pages, upgraded URLs, verified technical fixes, secured placements, and work still awaiting client approval, with specific URLs and live status on the first screen. Then show citation movement across the fixed query set and next month's priority queue, rather than opening with a wall of charts.
Why pay for an AEO retainer instead of just buying a monitoring tool?
A monitoring tool only shows where your brand is missing; the retainer covers who writes the page, fixes the crawler block, checks the schema, and records what went live. The distinction only holds if your signed deliverables schedule actually lists executed work rather than dashboard access.
