Part 2 — The AVO discipline

2.1 Formal definition

Authority and Visibility Optimization (AVO) is the discipline of measuring and engineering brand authority and visibility for AI-mediated brand discovery. It defines what success means in the AI search era — when discovery surfaces are synthesized rather than listed — and provides the conceptual framework, methodology, and measurement instruments required to engineer for that success.

AVO is structured as a closed practice loop with three named components:

Component	Role
The Authority Score (AS)	Predictive measurement that establishes the diagnostic baseline. AS quantifies the conditions of authority that determine whether AI systems will treat the brand as citable.
The OMG Protocol	Methodology that operationalizes AS findings into action. Three pillars (Optimize, Manifest, Generative) and thirty canonical actions, selected based on what AS reveals.
The Visibility Score (VS)	Empirical measurement that verifies outcome. VS quantifies whether the executed OMG work in fact produced AI-mediated visibility.

The loop closes through re-measurement: VS validates or contradicts what the AS-directed OMG work was intended to produce, and a re-measurement of AS confirms whether the underlying readiness has shifted. The cycle continues as the brand’s authority and visibility compound.

This is the canonical AVO practice cycle: measure, act, verify, re-measure. A practitioner measuring AS without acting on its findings is conducting a survey, not practicing AVO. A practitioner doing OMG actions without AS to direct them or VS to verify them is executing tactics, not practicing AVO. AVO is the closed loop, not any single component within it.

In single-sentence form: AS tells the practitioner where to work. OMG is the work. VS proves whether the work succeeded. This formulation appears in the public methodology paper and is the framing the team uses when explaining AVO to brand stakeholders.

2.2 The umbrella claim

AVO is positioned as the umbrella discipline above the tactical layer of GEO, AEO, and AIO. The three tactical disciplines address different surfaces — synthesized AI outputs, extractive answer features, broad AI consumption readiness — and operate in parallel. AVO contains them by providing the strategic frame within which they are deployed: which surfaces matter for a given brand, in what proportion, with what success criteria, and how their performance is measured against shared instruments.

This containment is not subordinating. GEO, AEO, and AIO remain useful and named tactical specialties. Practitioners can deploy them under any organizational frame. AVO simply offers the strategic discipline — the loop — that connects tactical execution to outcomes a brand can measure and act upon at portfolio scale.

For the practitioner, the umbrella claim has practical implications:

• When a brand stakeholder asks “should we focus on GEO or AEO,” the correct response is neither. The correct response is that AS measurement will reveal which surfaces are bottlenecks for the brand’s specific situation, and OMG action selection will direct work toward those surfaces. GEO and AEO tactics are tools deployed under AVO’s strategic direction, not alternatives to AVO.
• When a competing agency proposes a “GEO engagement” or “AEO program,” they are offering tactical execution without the strategic discipline that determines whether the tactical work produces measurable outcome. The brand may engage them and see specific tactical improvements (more featured snippets, better extractive surface coverage) without producing measurable AS or VS movement, because the tactical work was not directed by diagnostic measurement.
• When the practitioner explains AVO to a brand stakeholder unfamiliar with the discipline, the umbrella claim provides the framing that distinguishes AVO from tactical alternatives without dismissing the tactical work itself. AVO does not compete with GEO; AVO is the discipline that decides when and how GEO is deployed.

2.3 The Digital Authority Funnel

The relationship between SEO, AVO, and the tactical layer is captured in the Digital Authority Funnel — a three-stage model with parallel tactical execution.

Stage	Discipline	Role
Stage 1	SEO (Foundation)	The brand exists on the public web, is indexed by traditional search engines, and is reachable by the crawlers that feed both search ranking systems and AI training corpora. Foundation work — robots configuration, sitemap validity, performance, basic on-page structure — remains necessary in the AI era.
Stage 2	AVO (Strategic Discipline)	The brand operates the AVO practice loop. AS measures authority. OMG executes the methodology. VS verifies outcome.
Stage 3	Tactical Execution Layer (GEO, AEO, AIO operating in parallel)	Specific tactical execution within the AVO discipline — surfacing in generative answers, occupying extractive answer features, optimizing readiness for AI consumption.

The funnel is read top-to-bottom for dependency: Stage 3 depends on Stage 2, which depends on Stage 1. A brand cannot execute Stage 3 effectively without operating Stage 2, and a brand cannot operate Stage 2 without Stage 1 foundations.

The funnel is read across-the-rows for operations: a mature brand operates at all three stages simultaneously, with different teams, time horizons, and ownership at each stage. SEO foundation work is continuous and never finished. AVO strategic loop runs continuously. Tactical layer execution proceeds in parallel as AVO directs.

A common error among brand stakeholders and inexperienced practitioners is to read the funnel as a sequence in time: complete SEO, then start AVO, then start tactical execution. This is incorrect and produces stalling. Stage 1 foundations are continuous; treating them as a phase to be completed before Stage 2 begins postpones Stage 2 indefinitely. The correct reading is: each stage’s dependency on the prior stage is real, but each stage’s operation runs continuously and in parallel.

For the practitioner, this means a typical engagement does not begin with “we’ll do SEO foundations for three months, then start AVO.” It begins with concurrent assessment of all three stages, identification of bottlenecks at each, and parallel work that respects the dependency structure (no Stage 3 work that depends on incomplete Stage 1 foundations) while not waiting for any stage to be “done.”

2.4 What AVO is and is not

A clear specification of what AVO is requires drawing the line against adjacent practices that share vocabulary, surface, or audience. The lines below are operational, not definitional — they help the practitioner identify when a piece of work belongs in AVO scope versus when it belongs in another discipline.

AVO is not search engine optimization for AI. SEO operates against ranking; AVO operates against citation readiness and citation outcome. The two disciplines share some prerequisites (technical accessibility, structured data) but their measurement structures, action catalogs, and theories of change are different. A brand that achieves SEO success does not by virtue of that success achieve AVO success.

AVO is not Generative Engine Optimization, Answer Engine Optimization, or AI Optimization. GEO, AEO, and AIO are tactical specialties; AVO is the strategic discipline within which they are deployed. A brand purchasing GEO-only services receives tactical work without strategic direction; a brand purchasing AVO services receives strategic direction that includes GEO, AEO, and AIO tactical work as appropriate.

AVO is not brand awareness measurement. Brand awareness measures whether human audiences recognize and recall the brand. AVO measures whether AI systems treat the brand as authoritative and cite it in synthesized answers. The two measurements are correlated for some brands and uncorrelated or even inversely correlated for others. A brand with strong human awareness but weak machine-recognizability is real and common.

AVO is not content marketing. Content marketing produces content for human audiences with the goal of brand affinity and conversion. Some content marketing work overlaps with the Manifest pillar of OMG — depth of subject-matter content, regular publication, editorial discipline — but the goals and measurements differ. Content marketing measures engagement, conversion, and amplification; AVO measures authority and visibility on AI surfaces. A brand can have effective content marketing and weak AVO if the content does not satisfy the conditions for AI citation.

AVO is not public relations. Public relations earns coverage in publications and manages brand narrative. Some PR work overlaps with the Generative pillar of OMG — earning citations from authoritative publications — but the mechanisms differ. PR optimizes for human readership and editorial coverage; AVO uses earned citations as inputs to authority measurement. A brand can have effective PR and weak AVO if the earned coverage is not in publications AI systems treat as reliable.

AVO is not Wikipedia editing. Specific actions within AVO involve Wikipedia and Wikidata work (G-11 in the OMG action catalog), but Wikipedia editing as a service is not equivalent to AVO. Wikipedia editing is one tool within one action within one pillar of one component of AVO.

The practitioner’s task in framing engagement scope is to identify which of these adjacent practices the brand is already engaged in, which produce AVO-positive side effects, and which need to be supplemented or redirected to support the AVO loop.

2.5 The three commitments of AVO

AVO is defined by three commitments that distinguish it from alternative frameworks. These commitments are non-negotiable; a practice that withdraws any of them is not AVO.

Commitment 1: Loop-first

AVO is the closed cycle of measurement, action, and verification. Measurement without action is a survey. Action without measurement is tactics. Verification without a baseline is outcome research. AVO is the loop that connects them: AS surfaces where readiness is deficient; OMG executes the work; VS verifies whether the work succeeded; re-measurement closes the cycle.

For the practitioner, loop-first has operational implications:

• An engagement that does not include AS measurement is not an AVO engagement. If a brand requests “AVO services” without baseline measurement, the practitioner’s first task is to establish AS measurement before any OMG action can be properly directed.
• An engagement that includes AS measurement but does not include subsequent VS measurement is incomplete. AS findings alone direct work but do not verify it. A brand that measures AS quarterly without VS measurement is investing in diagnostic work without verification work, and cannot distinguish OMG actions that succeeded from OMG actions that did not.
• An engagement that runs OMG actions without consulting AS findings is tactical execution that may or may not produce AVO outcome. Such work is not wrong; it is undirected. The practitioner should redirect such work toward AS-informed action selection before continuing.

The loop is also what makes AVO defensible as a discipline rather than a checklist of tactics. The 30 OMG actions, considered in isolation, can be found in various forms across the marketing literature. What makes them AVO is that they are selected based on AS findings and verified against VS measurement. The selection-and-verification structure is the discipline; the action catalog is the inventory.

Commitment 2: Multilingual-first

AVO specifies first-class support for English, Indonesian, Japanese, Korean, and Traditional Chinese as primary languages. Multilingual support is foundational architecture, not feature flag. Every datapoint, every measurement, every action is specified to operate across these languages without silent failure modes. Extension to additional languages is a matter of calibration, not architectural change.

For the practitioner, multilingual-first has operational implications:

• A brand operating in only one language is still subject to multilingual considerations: any datapoint that detects multilingual readiness will register correctly low for a single-language brand. The practitioner does not need to remove multilingual considerations from scope; they will simply produce expected results for the brand’s actual language scope.
• A brand operating in multiple languages requires AS measurement per language. The brand may have AS = 60 in English and AS = 12 in Japanese, and these are not averaged into a single brand AS — they are measured separately and treated as distinct engagement scope.
• OMG action work in language B does not transfer from work in language A. A brand that completed a Manifest-pillar action set in English has not by virtue of that work made progress in Japanese. The actions must be repeated, with adaptation, in each language scope the brand operates in.
• Some actions are inherently more language-sensitive than others. Optimize-pillar actions tend to be relatively language-neutral (technical infrastructure, structured data) — they work the same way across languages. Manifest-pillar actions are highly language-specific (content depth, attribution patterns, claim density). Generative-pillar actions are profoundly language-specific (each language community has distinct media landscapes, citation patterns, knowledge-graph cultures).

The team’s working assumption is that multilingual scope is engagement scope. A brand’s engagement is implicitly defined by which languages are in scope. Adding a new language is a meaningful expansion of engagement, comparable to adding a new business unit.

Commitment 3: Portfolio-scale

AVO is built to operate across many domains simultaneously. The methodology, the measurement instruments, and the practice loop are designed to function at the scale of a brand portfolio (multiple domains, multiple Focuses per domain) rather than at the scale of a single page or a single keyword.

For the practitioner, portfolio-scale has operational implications:

• The AS measurement instrument operates per-domain. A brand with multiple domains (parent brand, subsidiary brands, regional sub-domains, specific product properties) requires per-domain AS measurement. Aggregating across the portfolio is a separate analytical step, not a property of the underlying measurement.
• Focus selection happens per-domain. Each domain in scope has a Focus declared for it, and the Prompt Book is generated from the Focus. A parent brand’s Focus and a subsidiary’s Focus may be related but are not identical.
• OMG action work happens per-domain. An action like G-11 (Wikipedia and Wikidata Optimization) executed for the parent brand’s domain does not transfer to the subsidiary’s domain. Each domain in scope requires its own action work.
• Reporting and quarterly review happens per-portfolio. While measurement and action are per-domain, the strategic conversation with the brand stakeholder is at portfolio level, with diagnostic detail at the domain and Focus level.

This commitment shapes how the team scopes engagements and how the SaaS implementation is architected. Brands operating on a single domain are a degenerate case of the portfolio-scale architecture; the methodology serves them but is not optimized for them. Brands operating on dozens or hundreds of domains are the architecturally-anticipated case, and the methodology and tooling are built around that scale.

2.6 What Avonetiq specifically contributes to AVO as a public discipline

The AVO discipline is published openly under CC BY 4.0. Avonetiq is the originating publisher and the primary calibrator-of-record, but AVO is not Avonetiq’s proprietary intellectual property. Other implementations of AVO are anticipated and welcomed; the discipline is deliberately structured to allow this.

What Avonetiq contributes specifically:

• The originating methodology specification — the public paper that defines the discipline, the OMG Protocol, the AS-VS measurement model, the practice loop, and the multilingual commitments.
• The first calibration — Avonetiq’s implementation of AVO, calibrated against APAC and English markets, is the first complete operational instance of the discipline. This calibration is not part of the open methodology; it is implementation craft that varies by deployment.
• The first production tooling — Avonetiq’s SaaS is the first production-grade implementation of the AVO loop at portfolio scale across multiple languages. The tooling is not part of the open methodology; alternative implementations are possible and may be built by others.
• Ongoing methodology stewardship — Avonetiq maintains the public methodology, accepts errata and proposals through GitHub and Zenodo, and is responsible for shipping subsequent versions (v1.1, v2.0). This stewardship role is held by Avonetiq for as long as the team chooses to hold it; the open methodology is structured to survive a stewardship transition if one becomes appropriate.

What Avonetiq specifically does not claim:

• That AVO can only be practiced by Avonetiq. Implementations by other organizations are anticipated and the methodology is structured to enable them.
• That Avonetiq’s calibration values are part of the methodology. Calibration is implementation craft; the methodology specifies the structure within which calibration happens.
• That Avonetiq’s tooling is part of the methodology. The methodology can be implemented with different tooling, including non-software tooling for small-scale work.

For the practitioner, this distinction has practical implications when communicating with brand stakeholders, partners, or competitors. AVO is the open discipline; Avonetiq is the implementation. Calibration values, tooling, and operational craft are Avonetiq’s. The methodology — the structure of the discipline — is the field’s.

---