# AEO operator 2026 Human Guide

## What This Is For
Operate AEO as an evidence-driven system across demand, access, retrieval, citation, brand visibility, narrative, and business outcome. It gives the agent a clearer input/output frame for AEO operator 2026: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the AEO operator 2026 agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for AEO operator 2026.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the AEO operator 2026 guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- official engine documentation, help centers, webmaster guidance, protocols
- primary research / controlled experiments / platform-published datasets
- large observational datasets such as Profound
- expert commentary and case studies
- Date-stamp time-sensitive claims.
- If official guidance and observational research conflict, use official guidance for eligibility/controls and treat observational findings as hypotheses to test.
- Never transfer a percentage into a client forecast without validating model, industry, language, geography, prompt set, and date.
- Prefer the newest relevant study when datasets conflict.
- Segment Google AI Overviews, AI Mode, and Gemini rather than collapsing them into one surface. Segment ChatGPT, Perplexity, Copilot, Claude, Grok, and shopping/local experiences separately.
- Refresh the dated findings in this skill with current web research when the user asks for latest/current behavior or when mechanics may have changed.
- crawl logs, Search Console, Bing Webmaster, analytics, CRM, or AEO exports
- business goal: visibility, citations, recommendations, accuracy, sentiment, traffic, pipeline, revenue, shopping, or a combination

## Decision Points And Nuance
The original skill emphasizes: Non-negotiable rules, Evidence protocol, Intake, Choose the workflow, Core diagnostic: the AEO visibility stack, Access and eligibility, Retrieval fit, Citation readiness, Brand visibility and narrative, Source ecosystem.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Treat AEO as probabilistic. Never promise a citation, mention, ranking, recommendation, traffic lift, or revenue lift.
- Separate engines, models, surfaces, languages, markets, and time periods. Do not transfer behavior from one to another without evidence.
- Build prompt portfolios from real user demand when available. Do not simply convert an SEO keyword list into prompts.
- Never recommend fake reviews, fabricated citations, astroturfing, Wikipedia manipulation, doorway pages, mass prompt-variant pages, or scaled low-value AI content.
- Do not prescribe llms.txt, special "AEO schema", mechanical answer chunks, or FAQ proliferation as universal visibility tactics.
- Never transfer a percentage into a client forecast without validating model, industry, language, geography, prompt set, and date.
- Do not add these mechanically. A short page can be excellent if it fully serves the task.
- Do not use direct AI referrals as the sole measure of value.

## Copy-And-Paste Prompt
```text
Use the AEO operator 2026 human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the Profound skill entry for `aeo-operator-2026`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# AEO Operator 2026

Operate AEO as an evidence-driven system spanning demand -> access -> retrieval -> citation -> brand visibility -> narrative -> business outcome. Diagnose the bottleneck before prescribing tactics.

## Non-negotiable rules

Treat AEO as probabilistic. Never promise a citation, mention, ranking, recommendation, traffic lift, or revenue lift.

Separate engines, models, surfaces, languages, markets, and time periods. Do not transfer behavior from one to another without evidence.

Use official platform documentation for eligibility, crawler controls, feeds, structured-data requirements, and product behavior.

Use Profound and other observational research as priors, benchmarks, and experiment inputs, not as official ranking-factor documentation.

Separate four outcomes: visibility, citation influence, answer framing/accuracy, and business impact.

Benchmark the category/model source mix before prescribing owned content, PR, Reddit, YouTube, LinkedIn, institutional coverage, or other channels.

Build prompt portfolios from real user demand when available. Do not simply convert an SEO keyword list into prompts.

Optimize intent families and concrete fact needs, not one exact prompt wording. Query fan-out can materially change retrieval.

Prefer unique evidence, first-hand expertise, current facts, clear entities, strong information architecture, and useful source ecosystems over formatting tricks.

Never recommend fake reviews, fabricated citations, astroturfing, Wikipedia manipulation, doorway pages, mass prompt-variant pages, or scaled low-value AI content.

Do not prescribe llms.txt, special "AEO schema", mechanical answer chunks, or FAQ proliferation as universal visibility tactics.

Measure trends, not screenshots. Record prompt cohort, engine/model, locale, date, sample size, and uncertainty.

## Evidence protocol

For current or changing platform behavior, browse before asserting facts when browsing is available.

Use this hierarchy:

1. official engine documentation, help centers, webmaster guidance, protocols
2. primary research / controlled experiments / platform-published datasets
3. large observational datasets such as Profound
4. expert commentary and case studies

Rules:

- Date-stamp time-sensitive claims.
- If official guidance and observational research conflict, use official guidance for eligibility/controls and treat observational findings as hypotheses to test.
- Never transfer a percentage into a client forecast without validating model, industry, language, geography, prompt set, and date.
- Prefer the newest relevant study when datasets conflict.
- Segment Google AI Overviews, AI Mode, and Gemini rather than collapsing them into one surface. Segment ChatGPT, Perplexity, Copilot, Claude, Grok, and shopping/local experiences separately.
- Refresh the dated findings in this skill with current web research when the user asks for latest/current behavior or when mechanics may have changed.

## Intake

Infer what you can. Ask only when a missing field blocks useful work.

Useful inputs:

- brand/company/domain
- market, language, geography
- products/services/topics
- priority answer engines
- competitors
- audience and decision stage
- prompt/query data
- pages/content to audit
- crawl logs, Search Console, Bing Webmaster, analytics, CRM, or AEO exports
- Profound data when available: Prompt Volumes, Visibility/Share of Voice, Mention Position, Citation Share, Citation Categories, Co-citation, Co-mention, Query Fanouts, Agent Analytics/Bot Visits, Pages, Human Referrals, Shopping, FactCheck
- business goal: visibility, citations, recommendations, accuracy, sentiment, traffic, pipeline, revenue, shopping, or a combination

If only a domain is supplied, perform a best-effort public audit and distinguish observed evidence from unavailable internal data.

## Choose the workflow

Use the smallest workflow that answers the actual question.

| User need | Workflow |
| --- | --- |
| Site/domain audit | Full AEO audit |
| Competitors winning | Prompt + citation gap |
| Create/optimize a page | Content opportunity |
| Crawlers/indexing/technical | Technical eligibility |