AEO Client Onboarding: A 30-Day Setup That Captures Both Search And AI Baselines

A new AEO client engagement begins. The agency team meets internally to plan onboarding. The discussion gravitates toward standard SEO onboarding practices: access requests, technical audit, content review, strategy development. Three weeks in, the team realizes they have not yet established the AI engine visibility baseline that the AEO engagement specifically requires. The AI engine work has to be added to the schedule alongside the SEO work, compressing both. The result is that the day-30 deliverable feels rushed and the client sees the agency as unprepared.

This pattern is common when agencies move from SEO-only to AEO engagements without updating their onboarding playbook. The traditional SEO onboarding misses the AI visibility baseline that AEO requires. The result is engagements that start with incomplete foundations.

This piece unpacks the structured 30-day AEO onboarding playbook: the activities each week, the deliverables produced, and the stakeholder alignment that supports successful engagements. The work is more substantial than traditional SEO onboarding but produces stronger foundations for the engagement's outcomes.

Why AEO Onboarding Needs Its Own Playbook

AEO onboarding differs from SEO onboarding in specific ways.

• AI visibility baseline - The engagement needs to capture the brand's current AI citation rates across major engines. The baseline informs both immediate priorities and the long-term measurement of engagement impact. SEO-only onboarding skips this; AEO-specific onboarding includes it.
• Engine coverage decisions - The engagement should establish which engines are tracked, which markets, which query categories. The scoping decisions affect every subsequent measurement and reporting decision.
• Brand entity audit - AEO depends substantially on brand entity recognition (Wikipedia, Wikidata, sameAs links, etc.). The audit of current entity state surfaces gaps that affect priorities.
• AI engine specific content audit - The audit looks at content not just for traditional SEO quality but for AI engine extractability: citable first sentences, named author authority, structured data fit. The dimensions differ from traditional content audits.
• Cross-functional stakeholder mapping - AEO engagements typically touch more stakeholders than SEO-only engagements: PR (for brand authority), product (for category positioning), customer success (for case studies), legal (for compliance content). The onboarding should map these.

The combination of these dimensions produces an onboarding that is more comprehensive than traditional SEO onboarding. The 30-day structure handles the breadth without rushing any specific dimension.

For agencies migrating from SEO to AEO, the onboarding update is one of the higher-leverage internal changes. Better onboarding produces better engagement starts; better starts produce better outcomes.

For brands evaluating agencies, asking about the AEO-specific onboarding playbook surfaces the agency's actual readiness. Agencies that describe traditional SEO onboarding for AEO engagements indicate the AEO sophistication may be thinner than claimed.

Week 1: Access, Stakeholders, And Baseline Discovery

Week 1 establishes the operational foundation.

Day 1 to 2: Kickoff meeting and team introductions. The agency team meets the brand stakeholders. The meeting clarifies engagement scope, success metrics, communication cadence, and key decision-makers. Both teams understand who they are working with.

Day 2 to 3: Access requests and credential exchange. The agency gets access to Google Search Console (added as user, not owner), Google Analytics, Bing Webmaster Tools, Naver and Yandex Webmaster Tools if applicable, content management system (read access initially, write access negotiated), any existing SEO platforms (Ahrefs, Semrush, dashboards), and any internal tooling relevant to the engagement.

Day 3 to 5: Stakeholder mapping. The agency identifies cross-functional stakeholders beyond marketing: PR, product marketing, customer success, sales operations, legal, engineering. Each stakeholder's interest in the engagement is documented.

Day 5 to 7: Initial discovery interviews. The agency conducts 30 to 60 minute interviews with each key stakeholder. The interviews cover: their understanding of the engagement, their goals, their concerns, their existing knowledge of search and AI visibility, and their availability for ongoing collaboration.

Day 7 to 10: Document collection. The agency requests: prior SEO audits, current content strategy documents, brand guidelines and voice documents, customer personas, competitive analyses, brand positioning materials, current PR coverage, internal product documentation, existing schema implementation documentation.

The Week 1 outcome is operational readiness: the agency can access the brand's systems, knows who the stakeholders are, and has the documentation to inform subsequent work. The stakeholder interviews particularly inform priorities; the document collection enables analysis.

For agencies, Week 1 is often less satisfying than later weeks because the work is logistical rather than analytical. The temptation is to rush through Week 1 to get to "real work." Resist this. Strong Week 1 foundations produce strong subsequent weeks.

For brands, providing access promptly and committing stakeholder time to interviews accelerates the engagement start. Delays in Week 1 cascade through the entire onboarding.

Week 2: Technical Audit And Content Analysis

Week 2 focuses on the deep technical and content assessment.

Day 8 to 11: Technical SEO audit. The agency runs comprehensive technical audit covering: crawlability and indexation analysis, page speed and Core Web Vitals, mobile usability, structured data implementation and validation, internal linking patterns, sitemap coverage, robots.txt configuration, HTTP headers, schema markup coverage, and AI bot configuration (GPTBot, ClaudeBot, etc.). The audit produces a prioritized list of technical issues.

Day 11 to 14: Content portfolio analysis. The agency analyzes the existing content portfolio: total content volume, topic distribution, content quality assessment, traffic per piece, ranking distribution, citation evidence in AI engines, schema coverage per piece, internal linking patterns. The analysis surfaces strong assets, weak assets, and content gaps.

Day 14 to 15: Brand entity audit. The agency assesses the brand's entity state: Wikipedia presence, Wikidata entry, Organization schema implementation, sameAs link coverage, executive bio pages, founder and key personnel documentation, third-party directory listings, and cross-platform brand name consistency.

The Week 2 outcomes include: a documented technical SEO issue list with priority rankings, a content portfolio analysis showing strengths and gaps, an entity audit showing brand authority signal status, and identification of any critical technical issues requiring immediate attention.

The Week 2 work is intensive. A thorough technical audit takes 2 to 3 full days of senior analyst time. The content portfolio analysis can take 2 to 4 days depending on portfolio size. The entity audit is typically 1 day. The total work is consistent with the week's scope but requires dedicated capacity.

For agencies with junior team members, Week 2 is often supplemented with senior analyst review. The junior team can do initial analysis; senior review catches issues that junior analysts miss.

Week 3: AI Visibility Baseline And Competitive Mapping

Week 3 focuses on the AI engine work that distinguishes AEO from traditional SEO.

Day 15 to 17: AI visibility query set construction. The agency defines the query set that will be used to measure AI visibility throughout the engagement. Typically 25 to 75 queries covering: branded queries (mentions of the brand by name), category queries (general queries in the brand's category), buyer-intent queries (commercial searches users make near purchase decisions), comparison queries (brand vs competitor), and informational queries (how-to and educational searches the brand should be cited for).

Day 17 to 20: Baseline AI citation sampling. The agency runs each query in the query set against ChatGPT, Claude, Perplexity, Gemini AI Mode, Microsoft Copilot, and any additional engines relevant to the brand. Each query is sampled multiple times (5 to 10 typically) to account for response drift. The brand's citation rate per engine per query is calculated.

Day 20 to 22: Competitive AI visibility mapping. The agency runs the same query set focused on the brand's primary competitors. The competitive analysis reveals: which competitors dominate which queries, which queries have low overall citation density (opportunity), which queries have high overall density (harder to break into), and where the brand sits relative to competitors per query.

Day 22 to 24: Citation pattern analysis. The agency analyzes patterns in the baseline data: which queries the brand wins, which engines treat the brand favorably versus unfavorably, what content types the engines cite (when the brand is cited at all), and what sources the engines prefer for the brand's category.

The Week 3 outcomes include: a documented AI visibility baseline with citation rates per query per engine, competitive visibility analysis showing the brand's position relative to top competitors, identification of high-priority queries for improvement, and patterns suggesting tactical priorities.

The Week 3 work requires either substantial manual sampling capacity or platform tooling (Profound, AthenaHQ, Otterly.ai). Manual sampling for the full query set across multiple engines takes 8 to 16 hours; platform-automated sampling takes a few hours of setup plus the platform's actual sampling time.

Building citation gravity provides the broader framework; Week 3 establishes the baseline that subsequent gravity work measures progress against.

Week 4: Roadmap Construction And Stakeholder Alignment

Week 4 synthesizes the prior weeks' work into the engagement roadmap.

Day 25 to 27: Roadmap construction. The agency synthesizes the technical audit, content analysis, entity audit, and AI visibility baseline into a prioritized roadmap. The roadmap typically covers: immediate technical fixes (first 30 days), foundational content work (first 90 days), brand entity scaffolding (first 90 days), content production cadence (ongoing), competitive positioning work (ongoing), and longer-term strategic initiatives.

Day 27 to 28: Internal review and refinement. The roadmap goes through internal agency review. Senior strategists, content leads, and technical specialists each review their respective sections. Refinement produces a more polished and accurate final document.

Day 28 to 29: Stakeholder review meeting. The agency presents the roadmap to the brand's stakeholders. The meeting is interactive: the agency walks through findings and recommendations, stakeholders provide feedback, and adjustments are negotiated. The meeting typically runs 2 to 3 hours.

Day 29 to 30: Final roadmap and engagement formalization. Based on stakeholder feedback, the roadmap is finalized. The final document is shared with all stakeholders. The engagement formally transitions from onboarding to execution.

The Week 4 outcomes include: a comprehensive 90-day roadmap with specific deliverables and timelines, alignment among internal stakeholders about priorities, established communication and reporting cadence, and clarity about what success looks like.

The roadmap should be specific. Vague roadmaps produce vague execution. Specific roadmaps with named deliverables, dates, and responsibilities produce accountability and momentum.

The Day-30 Deliverable And Handoff To Execution

The day-30 deliverable consolidates the onboarding work into a referenceable document.

The structure of a strong day-30 deliverable includes:

• Executive summary - The state of the brand's current SEO and AI visibility, the major findings from the audit work, the top 3 to 5 strategic priorities, and the expected outcomes from the engagement.
• Technical SEO state - The audit findings, the priority issue list, the remediation roadmap, and any urgent issues requiring immediate attention.
• Content portfolio assessment - The analysis findings, strong and weak content identification, content gaps relative to topic cluster strategy, and content production priorities.
• Brand entity state - The current entity authority signals, gaps requiring attention (Wikipedia, Wikidata, schema), and entity scaffolding roadmap.
• AI visibility baseline - The query-set definition, the per-engine citation rates, the competitive positioning, and the high-priority queries for improvement.
• 90-day roadmap - The specific deliverables, dates, and responsibilities for the first 90 days. The roadmap should be detailed enough that progress can be tracked against it.
• Measurement framework - The metrics that will be tracked, the reporting cadence, the dashboard setup, and the regular review cadence (weekly tactical, monthly strategic, quarterly business review).
• Stakeholder summary - Who is responsible for what, how communication flows, and how decisions are made.

The deliverable typically runs 30 to 60 pages depending on the engagement scope. The depth justifies the document's role as the engagement's reference foundation.

The handoff to execution should be explicit. The next day starts the execution phase; the team knows what to work on and the brand knows what to expect.

For ongoing engagements, the day-30 deliverable becomes the baseline against which monthly and quarterly progress is measured. The reference back to the original findings produces continuity and accountability.

Six Onboarding Mistakes That Undermine The Engagement

Six common mistakes that affect AEO onboarding outcomes.

1. Rushing through Week 1 logistical work. Slow access requests, delayed stakeholder interviews, and missing documentation cascade into subsequent weeks. The logistical foundation matters.
2. Skipping AI visibility baseline. The most distinctive AEO onboarding element is the AI visibility baseline. Engagements without it have no objective measure of AI engine progress.
3. Generic technical audits. Audits that produce 100-page reports of low-priority issues produce roadmaps that focus on tactical fixes instead of strategic priorities. Prioritize the audit findings.
4. Anonymous or non-substantive stakeholder interviews. Interviews that get quick generic answers produce shallow understanding of the brand. Substantive interviews produce the insights that inform priorities.
5. Vague roadmap recommendations. "Improve content quality" or "build brand authority" produces no executable work. Specific recommendations with named deliverables produce engagement traction.
6. Day-30 deliverable that does not document baselines. The deliverable should be reference-worthy for the engagement's lifetime. Documents that fail to capture the starting state become useless within a few months.

Frequently Asked Questions

Can the 30-day onboarding be compressed for urgent engagements?

Partially. Some elements can be compressed (stakeholder interviews can be combined, document collection can run in parallel). Other elements have minimum time requirements (AI visibility sampling needs multiple sampling cycles to be reliable). The compressed onboarding typically takes 18 to 22 days at the minimum.

What if the brand cannot provide all the access we requested in Week 1?

Adjust the scope based on available access. Missing some access (Google Analytics access, for example) reduces what the agency can analyze but does not block the engagement. Missing critical access (Search Console, content management) requires escalation; the engagement may need to delay until access is provided.

How should agencies handle clients who do not have prior SEO audits or strategic documents?

Build the missing foundation as part of onboarding. The technical audit, content portfolio analysis, and competitive mapping produce the documentation the brand should have had. The onboarding becomes both setup and foundational documentation.

Should onboarding be billed separately from the ongoing engagement?

Most agencies bundle onboarding into the monthly fee for the engagement. The first month's fee covers the substantial onboarding work; subsequent months cover ongoing execution. Some agencies bill onboarding as a separate fixed-fee project before the ongoing engagement; both approaches work.

How do we know if the onboarding was successful?

Three signals. First, the day-30 deliverable is substantive, specific, and actionable rather than generic. Second, the brand's stakeholders understand the engagement priorities and feel aligned with the agency's approach. Third, the first 30 days of execution produce tangible progress on the prioritized work (technical fixes shipping, content production starting, etc.).

What if the day-30 stakeholder review meeting surfaces major disagreements?

Address them directly. Major disagreement typically reflects either incomplete stakeholder alignment during Week 1 or substantive differences of opinion about strategy. Either way, resolving the disagreement before execution starts is essential. Sometimes the resolution requires additional discovery work or executive escalation.

AEO client onboarding is one of the most important phases of the engagement. The structured 30-day approach captures the baselines and develops the roadmap that subsequent execution depends on. Engagements with strong onboarding produce strong outcomes; engagements with weak onboarding struggle throughout.

The discipline involves dedicating appropriate time and capacity to the onboarding work rather than rushing through it. The investment pays back through engagement clarity, stakeholder alignment, and measurable progress.

If your agency wants help refining your AEO onboarding playbook, or your team is evaluating how an agency should onboard your AEO engagement, that work sits inside our generative engine optimization program. The engagements that produce durable AEO outcomes are the engagements whose onboarding established clear foundations for the execution that follows.