1. Prepare knowledge
Documents or records are collected, cleaned and divided into useful passages.
RAG is a technical approach that retrieves relevant external information and supplies it to a generative model before or while the model creates an answer.
The term was introduced in a 2020 research paper describing models that combine parametric memory—the knowledge stored in model weights—with non-parametric memory retrieved from an external index.
RAG is used because a language model’s internal knowledge may be incomplete, old or too general for the task. Retrieval can provide current documentation, company records, research papers, product information or other domain-specific material.
Documents or records are collected, cleaned and divided into useful passages.
The passages are stored in a searchable system, often using embeddings, keywords or a hybrid method.
A user question is used to locate passages likely to contain the needed information.
The model receives the question and retrieved context, then creates a response based on both.
Some systems add reranking, query rewriting, citation generation, tool calls, filters, permissions and post-generation fact checks. “RAG” therefore describes a family of architectures rather than one fixed implementation.
Google also describes retrieval-augmented generation as one of the techniques used in its generative search features, where relevant and current pages can be retrieved from the Search index to support a response.
RAG does not automatically make an answer correct. The final response depends on the quality of the knowledge base, indexing, retrieval method, query, permissions, prompt and model.
The best passage may not be found, or an irrelevant passage may rank higher.
The retrieved material may be wrong, outdated, incomplete or contradictory.
The model may misinterpret the retrieved text or add unsupported claims.
Weak permissions, prompt injection or careless document handling can expose information or alter behaviour.
Good RAG systems therefore need evaluation, monitoring, source maintenance and clear boundaries.
| Term | Type | Main question | Who applies it? |
|---|---|---|---|
| RAG | Technical AI architecture | How can an application retrieve external knowledge and use it to generate an answer? | AI engineers, product teams and developers |
| GEO | Publishing and visibility strategy | How can content become more useful or visible in generated answers? | Publishers, marketers, organizations and site owners |
| REG | Entity and retrieval guidance framework | How can the correct entity be recognized and the correct information be retrieved? | Businesses, publishers, data stewards and visibility specialists |
REG can improve the public information that a RAG-enabled system might retrieve, but REG is not part of the RAG code. GEO can improve the quality or usefulness of source content, but it does not control the retrieval pipeline.
A company builds an internal support assistant using manuals, policies and service records.
These references support the established definitions and technical explanations on this page.