| Internet-Draft | AI Visibility Lifecycle | October 2026 |
| Lynch | Expires 9 April 2027 | [Page] |
This document describes the 11-Stage AI Visibility Lifecycle, a proposed analytical model of how AI systems discover, understand, trust and show websites to people. The eleven stages fall into three related phases -- AI Comprehension (Stages 1-5), Trust Establishment (Stages 6-8), and Human Visibility (Stages 9-11). The lifecycle is non-linear: Stages 1-2 come first for any page; Stages 3-11 are weighed together, and a domain can be progressing in several at once. Its figures are illustrative examples (analytical estimates), and its descriptions of how AI systems work are inferred from observed behaviour, not documented internals. Its contribution is a common vocabulary and a dependency map for telling crawlability from visibility and for measuring each element, with the claims that rest on outside research cited to it in the deposited specifications. Its figures and some of its mechanisms are provisional and remain to be tested.¶
This Internet-Draft is NOT the canonical source for the AI Visibility Lifecycle framework. The framework is deposited at Zenodo under the concept DOI https://doi.org/10.5281/zenodo.18460710, which resolves to the latest deposited version. This Internet-Draft mirrors the specification for IETF community accessibility and reflects framework version 0.7.1 (October 2026). Where this Internet-Draft and an earlier deposited version differ, the later version governs.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 9 April 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The AI Visibility Lifecycle (version 0.7.1) provides a structural model for understanding how AI systems discover, evaluate, trust, and surface websites to human users. This framework is observational and analytical, not prescriptive. This document does not propose a standard, protocol, or recommendation for implementation.¶
Every figure in the framework -- timelines, success rates and conditions met, trust thresholds, exposure levels and classification bands -- is an illustrative example (analytical estimate) drawn from observation, not established fact, and remains to be tested. Descriptions of how AI systems work are the framework's model, inferred from observed behaviour, not documented internals. In the framework specification and its stage specifications, a statement that carries a citation rests on the sources cited; a statement without one is the framework's model, inferred from observation and still to be tested. This document summarises them; the citations are in the deposited specifications. The lifecycle does not claim that any AI platform runs eleven internal stages: systems may combine, reorder, repeat or leave out what the stages describe. A domain's standing can differ by page, topic, query, country, platform and time, so a stage given for a whole domain is an aggregate. 'Lifecycle' describes how a domain's visibility progresses, not a sequence of processing steps; the instruments for measuring each stage are kept separately.¶
This document mirrors the framework specification, version 0.7.1; earlier versions are deposited at Zenodo [ZENODO]. Companion papers on ambiguity elimination [AMBIGUITY] and website visibility reporting [REPORTING] provide additional context. The framework is also being developed collaboratively through the W3C AI Visibility Lifecycle Framework Community Group [W3C-CG].¶
A stage is a condition in a dependency map, not a step in a strict sequence. Stages 1-2 come first for any page: a page must be discovered and ingested before it can be used. Stages 3-11 are weighed together as parallel dimensions of evidence, and a domain can be progressing in several at once; total journey time equals the slowest-resolving dimension, not the sum of all stages. There are no shortcuts: weakness in any of Stages 3-11 lowers the chance of human-facing visibility.¶
The work sits in two layers: the ranking systems, which decide which pages and sources are candidates, and the language model, which reads them and writes the answer. Visibility has two surfaces: placements in search results, and, in AI answers, a share of appearances around a stable core of sources.¶
The eleven stages are organised into three related phases:¶
AI systems discover, interpret, classify, harmonise, and check the domain's knowledge structure for corroboration with established knowledge from authoritative sources.¶
AI systems build trust, formally accept the domain as reliable, and shortlist it for answers (candidate surfacing).¶
AI systems observe the domain's first user interaction signals, establish baseline visibility, and scale visibility based on positive performance.¶
Google describes the first step for its Gemini models in its own words: "The model analyzes the prompt and determines if a Google Search can improve the answer" [GEMINI-GROUNDING]. The understanding the lifecycle takes from this is that memory steers retrieval. Memory is made of the web the model has already crawled, processed and learned to trust, and it is redrawn and updated as models are retrained. It decides question by question whether a search runs, and it shapes the searches the model writes and the candidates it picks.¶
Every AI answer that draws on the web therefore passes through the lifecycle at some point: at answer time, through retrieval, or earlier, when the web the model learned from was crawled and processed. The lifecycle describes how a domain reaches AI answers. It is measured on the retrieval route, and the same stages bear on what models learn and carry in memory.¶
Discovery: crawling, fetching and rendering. AI systems discover the domain through URL submissions, sitemaps, inter-domain signals, or autonomous exploration, and pages are fetched and prepared for analysis. How often a page is crawled can follow how much search traffic it already receives. No trust exists yet.¶
Extracted content is converted into internal semantic representations that can later be reasoned over, compared, and synthesised, and the domain's concept structure is recorded. For AI answers built on a search engine's index, this work is done by the search engine at indexing.¶
AI systems determine what kind of website a domain is: non-commercial, commercial, or hybrid, by its site purpose. This classification bears on every other stage, including the strictness of evaluation and the trust threshold weighed in Stage 7. Purpose clarity is essential.¶
Formerly: AI Harmony Checks. AI systems check whether the website is internally coherent: consistent structure, definitions, purpose, and schema across all pages. Pages must agree with each other conceptually and structurally. Chaotic, contradictory, or low-coherence domains are weighted down early.¶
Formerly: AI Cross-Correlation. AI systems check whether the site's content is corroborated by established knowledge from authoritative sources, such as government databases, foundational references, scientific repositories and occupational frameworks. AI systems do not always weigh conflicting sources reliably.¶
AI systems gather evidence of reliability across stability, accuracy, consistency, neutrality, structural integrity, and purpose transparency. Trust (in industry terms, source reliability) is iterative, not binary.¶
Once trust signals meet the trust threshold, the domain is weighted as a reliable reference and becomes eligible for use in answer synthesis, citations, and multi-source reasoning. Trust alone does not make it visible to humans.¶
In industry terms, retrieval. AI systems assemble a shortlist of viable contributors for a given informational need, weighing query relevance and competing sources. This is not final ranking.¶
Formerly: Early Human Visibility Testing. The domain is exposed to a small fraction of human-facing results -- AI answers and search results -- and its first user interaction signals build up: which results users choose, whether they quickly return to the results, and how they respond to answers that draw on the domain.¶
The domain holds placements in search results that do not fluctuate wildly and are no longer removed immediately or automatically, and, in AI answers, a share of appearances around a stable core of sources. This stage establishes the first reliable human traffic baseline.¶
Formerly: Growth Visibility and Human Traffic Acceleration. If baseline performance is strong, AI systems expand visibility across regions, query families, device types, and tail depths.¶
Stages 1-2 come first for any page; Stages 3-11 are weighed together as parallel dimensions of evidence.¶
Each stage is reached as fast as the system gathers enough evidence: architectural quality sets how quickly evidence builds, and site purpose (non-commercial, commercial, hybrid) sets how much is needed, through the trust threshold weighed in Stage 7.¶
Crawlability (access and fetching, Stage 1) does not equal visibility (Stages 9-11).¶
AI search does not operate exactly like traditional search engine optimisation, nor does it replace it: for AI answers built on a search engine's index, that engine's own ranking factors apply.¶
Framework versions are released as Zenodo DOI deposits under the concept DOI; this document reflects version 0.7.1.¶
This Internet-Draft is NOT the canonical source. The framework is deposited at Zenodo. Citations are best made against the concept DOI, which always resolves to the latest deposited version:¶
Concept DOI: https://doi.org/10.5281/zenodo.18460710¶
Framework version 0.7.1, reflected in this document, is to be deposited under the same concept DOI. Where this document and an earlier deposited version differ, the later version governs.¶
Companion specifications are deposited separately, each with its own concept DOI: ambiguity elimination [AMBIGUITY] and website visibility reporting [REPORTING]. The eleven stage specifications corresponding to Sections 3.1 through 3.11 are deposited individually and indexed at the publisher's site listed below.¶
The framework is developed collaboratively through the W3C AI Visibility Lifecycle Framework Community Group [W3C-CG]. The group was proposed on 10 February 2026 and launched on 24 February 2026 under a Community Group charter (version 1.0, 25 February 2026). It is chaired by the author of this document. The group operates under the W3C Community Contributor License Agreement. Its deliverables are not W3C Standards and are not on the W3C Standards Track.¶
Publisher index of deposited specifications: https://aivisibilityarchitects.com/ GitHub mirror (non-citable): https://github.com/Bernardnz/ai-visibility-lifecycle W3C Community Group: https://www.w3.org/community/ai-web-visibility/ Community Group mailing list: https://lists.w3.org/Archives/Public/public-ai-web-visibility/ Community Group GitHub Repository: https://github.com/ai-visibility-architects/ ai-visibility-lifecycle-cg¶
This document describes an observational framework and does not define any protocols, data formats, or executable specifications. There are no security considerations directly applicable to this document.¶
This document has no IANA actions.¶
Updated to framework version 0.7.1 (October 2026): the framework's specifications now cite the published research behind each evidenced statement; this document states what the framework contributes and what is provisional, what it does not claim, and how memory and retrieval relate to the lifecycle (Section 2.1).¶
Stage names and subtitles: Stage 4 AI Harmony (formerly AI Harmony Checks); Stage 5 AI Knowledge Corroboration (formerly AI Cross-Correlation); Stage 6 AI Trust Building (Accumulating Evidence); Stage 9 Early Human Visibility (formerly Early Human Visibility Testing); Stage 10 Baseline Human Visibility; Stage 11 Growth Visibility (formerly Growth Visibility and Human Traffic Acceleration).¶
The lifecycle is described as non-linear, in three related phases: Stages 1-2 come first; Stages 3-11 are weighed together. Each stage is reached as fast as the system gathers enough evidence: architectural quality sets how quickly it builds, and site purpose sets how much is needed.¶
Figures are stated as illustrative examples (analytical estimates); descriptions of AI systems are stated as the framework's model, inferred from observed behaviour.¶
The relation to search engine optimisation is corrected: for AI answers built on a search engine's index, that engine's own ranking factors apply.¶
The canonical source notice states which framework version this document reflects.¶