---
title: "Indexing service"
manual: "TYPO3 Search Algolia"
version: "2.0"
permalink: "https://docs.typo3.org/permalink/meine-krankenkasse/typo3-search-algolia:configuration-indexing-service@2.0"
source: "Configuration/IndexingService.rst"
rendered: "2026-09-30T12:15:07+00:00"
---

# Indexing service {#configuration-indexing-service}

An indexing service defines which records of one type are indexed and
into which search engine they go. Create a new record of type
**Indexing Service** in the configuration folder.

![New record wizard with the record type Indexing Service](../Images/Configuration-003.png)

Enter a title and, optionally, a description. Select the indexer
**Type** and the **Search Engine** created before. The
built-in types are **Pages**, **Content elements**,
**News** (only when EXT:news is installed) and **Files**.
The form then shows the options of the selected type.

![Indexing service record form with type and search engine](../Images/Configuration-004.png)

A record type can have several indexing services, for example to index
different page trees into different indexes.

> [!WARNING]
> Frontend user group access restrictions are not evaluated, neither on
> pages, nor on content elements or news records, nor when a page passes
> its restriction on to its subpages. Such records are indexed like
> public records. Keep restricted pages with their subpages, and
> restricted content elements and news records, out of the pages
> selected in the indexing services.

> [!WARNING]
> The hidden state of a page is not applied to the records on it. Content
> elements and news records on a hidden page are queued, and queued again
> when they are saved. Keep pages that must stay out of the search out of
> the pages selected in the indexing services.

## Options by type {#configuration-indexing-service-options}

-   **Include content elements**

    -   *Type:* boolean
    -   *Types:* Pages

    Also index the content elements of each page. Their fields, as mapped
    in `module.tx_typo3searchalgolia.indexer.tt_content.fields` (see
    [Fields](https://docs.typo3.org/permalink/meine-krankenkasse/typo3-search-algolia:indexers-content-element-fields@2.0)), are stored in the page's
    `content` attribute, so no separate content element indexing
    service is needed. Records can get large this way, so check the record
    size limit of your Algolia plan.

-   **Content element types**

    -   *Type:* list
    -   *Types:* Content elements, and Pages with content elements included

    The content element types to index. Defaults to Bullet List, Header
    Only, Plain HTML, Regular Text Element, Table, Text & Images and
    Text & Media.

-   **Page type**

    -   *Type:* list
    -   *Types:* Pages

    Only index pages of the selected page types. Without a selection, all
    page types are included.

-   **Single pages**

    -   *Type:* list of pages
    -   *Types:* Pages, Content elements, News

    Pages whose records are indexed, without their subpages.

-   **Pages (recursively)**

    -   *Type:* list of pages
    -   *Types:* Pages, Content elements, News

    Pages whose records are indexed, including all subpages.

For the Pages type, pages with **Include in Search** disabled are
not queued, whichever of these two options selects them. If neither is
set, the records of the selected type are not limited by page. The other
options of the type still apply.

-   **File collections**

    -   *Type:* list of file collections
    -   *Types:* Files

    The file collections whose files are indexed. Files with
    **Include in Search** disabled in their metadata are skipped.