> **Important: Pagefind 1.5.0 introduces the Component UI, which replaces the
> Default UI (pagefind-ui.js / PagefindUI). It includes a search modal, better
> accessibility and customization.** Full component guide:
> https://pagefind.app/llms-component-ui.txt
# Configuring what content is indexed
You can control what content on your site is indexed via `data-pagefind-*` tags on your HTML elements.
## Limiting what sections of a page are indexed
By default, Pagefind starts indexing from your `` element.
To narrow this down, you can tag your main content area with `data-pagefind-body`:
```html
+
Condimentum Nullam
Nullam id dolor id nibh ultricies.
```
If `data-pagefind-body` is found anywhere on your site, any pages without this attribute will not be indexed. This means that if you tag your blog post layout with `data-pagefind-body`, other pages like your homepage will no longer appear in search results. This is usually what you want — if not, just add `data-pagefind-body` there as well.
Multiple `data-pagefind-body` elements may exist on a page, and their content will be combined.
> Note that metadata and filters that are set outside of this element will still be used. If this is not what you want, see the [root selector](/docs/config-options/#root-selector) CLI configuration option.
## Removing pages from Pagefind's index
Once a `data-pagefind-body` attribute exists on any page of your site, any pages without this attribute will not be indexed. As such, the best way to remove pages is by adding `data-pagefind-body` to the pages you **would** like to index.
If this isn't possible, see the [Pagefind CLI's glob option](/docs/config-options/#glob) to limit the files that Pagefind reads.
## Removing individual elements from the index
Pagefind has built-in elements that are not indexed. These are organizational elements such as `