> For the complete documentation index, see [llms.txt](https://docs.search.io/developer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.search.io/developer-documentation/fundamentals/pipelines.md).

# Pipelines

The configuration of an intelligent search algorithm can be extremely complicated. Pipelines break down this problem into smaller pieces that can be easily mixed, matched, and combined to create an incredibly powerful search experience.

### What are pipelines?

Pipelines are easily configurable YAML-based scripts that define a series of steps that are executed sequentially when indexing a record (record pipeline) or performing a query (query pipeline).

Indexing as well as relevance and ranking in Search.io are powered by pipelines. Although the most commonly used features are exposed via the UI settings, editing pipelines directly gives you access to more powerful and flexible capabilities.

### Benefits of pipelines

There are several advantages to pipelines versus the approach most other search engines take today:

1. Each component does one thing, so they are easy to understand.
2. The state is passed from step to step, so it’s easy to build highly complex workflows.
3. Each step can be turned on/off using conditional expressions. For example, personalization can dynamically boost results based on information in user profiles.
4. The highly complex engine query requests are constructed for you at runtime.
5. They can be versioned, AB tested and much more.

{% content-ref url="/pages/2Ctdh6NdnTiAa9UYhiFm" %}
[Query pipelines](/developer-documentation/fundamentals/pipelines/query-pipelines.md)
{% endcontent-ref %}

{% content-ref url="/pages/VuK7E6UJPqZ6yBHalWyf" %}
[Record Pipelines](/developer-documentation/fundamentals/pipelines/record-pipelines.md)
{% endcontent-ref %}

{% content-ref url="/pages/WntSAYyZo6UsgmNCQ4z2" %}
[Steps](/developer-documentation/fundamentals/pipelines/steps.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.search.io/developer-documentation/fundamentals/pipelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.