---
title: Index page content
slug: '3122'
canonical_url: https://docs.coveo.com/en/3122/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Index page content
By default, each Sitecore item is indexed in a Coveo index using only the field information retrieved in Sitecore.
However, some items have more information than what's defined in the fields.

This section describes the different content indexing options available and their effect on relevance and performance.

## How indexing the HTML of items affects results

The HTML representation of the page content will be set by the index as free-text searchable content.
Free text content and free text fields can be queried by entering the search terms directly in the search box.

Using the Coveo JavaScript Search Framework, HTML content enables the [CoveoQuickview](https://coveo.github.io/search-ui/components/quickview.html) component on the search results.

In the [Coveo Platform](https://docs.coveo.com/en/186/) **Content Browser**, the items with HTML rendering will have a `File Type` attribute equal to `HTML` while the rest of the content will be of type `sitecoreitem`.
See [Inspect items with the Content Browser](https://docs.coveo.com/en/2053/) for more details.

![Sitecore Item Types | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/sitecore-item-types.png)

## Available HTML content processors

An HTML representation of a page content can be created with and without executing an HTTP request to get the complete page content.

### Processors which perform HTTP requests

Although sending an HTTP request during the indexing process is resource-intensive, it's sometimes the only way to retrieve related content only available when the page is rendered in a browser.

The recommended Coveo for Sitecore processor for this purpose is the `FetchPageContentProcessor` processor.
More configurable than the `HTMLContentInBodyWithRequestsProcessor`, the `FetchPageContentProcessor` processor has been the default HTML content processor since the October 2018 release of Coveo for Sitecore 4.1.
See [Index page content with the FetchPageContentProcessor](https://docs.coveo.com/en/2326/) for more details.

If you upgraded from Coveo for Sitecore 4 to Coveo for Sitecore 5, you might still be using the `HTMLContentInBodyWithRequestsProcessor` processor.
Coveo for Sitecore 5 provides a simple mechanism to switch from the `HTMLContentInBodyWithRequestsProcessor` to the `FetchPageContentProcessor` processor.
See [When currently using HtmlContentInBodyWithRequestsProcessor](https://docs.coveo.com/en/2326#when-currently-using-htmlcontentinbodywithrequestsprocessor) for more details.

If you embed search-driven components in your Sitecore layouts, this can lead to many unnecessary queries when a processor performs an HTTP request to fetch the HTML content of a page.
Coveo for Sitecore provides mechanisms to ignore your search-driven components, whether through processor configuration or by detecting HTTP requests originating from a Coveo agent.
See [The postProcessing section](https://docs.coveo.com/en/2326#the-postprocessing-section) and [Avoid search queries in page quickview](https://docs.coveo.com/en/2152/) for more details.

### Processor which doesn't perform HTTP requests

HTTP requests can significantly slow down the indexing process and should be avoided if possible.

Use the `BasicHtmlContentInBodyProcessor` processor to create an HTML representation of the item without sending an HTTP request.
See [Index with the BasicHtmlContentInBodyProcessor](https://docs.coveo.com/en/2324/) for more details.