`) is not part of the parent's direct text.
* Matching is **case-sensitive** and matches **substrings**—`more` matches "more", "Read more", and "moreover".
* When an element matches, the **whole element and its contents** are removed.
* Used alone, the filter applies to **every element** on the page. Combine with [Type](#type-element_type), [Class](#class-element_class), or [ID](#id-element_id) via **+** to narrow the match.
**Examples**
* **Exclude** Type `a` + Text `Subscribe`—removes a subscribe link, keeps the surrounding paragraph
* **Exclude** Type `p` + Text `Sponsored`—removes paragraphs whose direct text contains "Sponsored"
**What this filter can't do**
* Remove a word or sentence from inside a paragraph while keeping the rest of the paragraph
* Match text split across child tags (e.g. `Subscribe`) or formatted inline (e.g., `Hello world
`—filtering for `world` on the `` will not match because `world` is inside ``)
For fragmented or heavily formatted paragraphs, use [XPath](#xpath-element_xpath) to target the wrapping element instead—for example, a newsletter paragraph identified by a link:
```text theme={null}
//p[.//a[contains(@href, 'newsletter')]]
```
#### XPath (`element_xpath`)
Matches elements using a full [XPath](https://www.w3.org/TR/1999/REC-xpath-19991116/) expression. When XPath is set, other filter fields are ignored.
**How matching works**
* Enter a complete XPath expression—e.g. `//*[@role='dialog']` or `//aside[contains(@class, 'sidebar')]`.
* Provides the most precise control for complex document structures.
* Best escape hatch when [Text](#text-element_text) filters cannot match fragmented markup you do not control (common with third-party CMS and RSS-sourced HTML).
**Examples**
* **Exclude** `//*[@role='dialog']`—removes dialog/modal elements
* **Exclude** `//p[.//a[contains(@href, 'suscripcion-newsletter')]]`—removes a newsletter sign-up paragraph identified by its subscribe link, regardless of how text is split across `` and `` tags inside
### Processing type and filters
When sending content through the API, the `type` field determines whether [content filters](#filters) are applied.
| Action | Filters applied? |
| ------------------------------------------------------------ | ---------------- |
| Article has `auto_segment` and you click **Regenerate** | Yes |
| Article has `auto_segment` and you send new HTML via the API | Yes |
| Article has `manual_segment` and you click **Regenerate** | No |
Articles created or last saved via the dashboard Editor use `manual_segment` by default. Set `type` to `auto_segment` when sending content through the API if you want filters to apply.
For more detail, see [Processing types](/api-reference/content/processing-types) in the API reference.
## FAQs
Common causes:
* **Automatic extraction** included the content—add an **Exclude** filter targeting the relevant HTML element and regenerate.
* **No Exclude filter** matches the element—inspect the page HTML, choose the right [filter type](#filter-types), and regenerate. For formatted paragraphs, Text alone may not work—try Class, ID, or XPath.
* An **Include** filter is too broad—review Include filters; they strip everything outside the match.
Common causes:
* **Automatic extraction** excluded the content—add an **Include** filter targeting the relevant container and regenerate.
* An **Exclude** filter is too broad—e.g. a Class filter using a substring that matches editorial elements. Review and narrow the filter.
* The article uses `manual_segment`—filters no longer apply. Regenerate via API with `type: auto_segment`, or edit in the Editor.
The Text filter only checks an element's **direct text**, not text nested in child tags. This often affects real article markup:
* `Hello world
`—Text `world` on Type `p` matches
* `Hello world
`—Text `world` on Type `p` does **not** match
* Text split across multiple `` tags will not match as a single phrase on the parent ``
**Fix:** use [XPath](#xpath-element_xpath) to target the parent element—e.g. by a distinctive `href`, `id`, or class on a child link rather than the paragraph text.
If the paragraph contains a distinctive subscribe link, use an **Exclude** XPath filter:
```text theme={null}
//p[.//a[contains(@href, 'newsletter')]]
```
Replace `newsletter` with a distinctive part of the subscribe URL. Avoid excluding by a generic class name (e.g. a class meaning "body" applied to all paragraphs)—that can remove the entire article.
If you only need to remove the link and keep the paragraph, use **Exclude** Type `a` + Text matching the link text (e.g. `Subscribe`).
Filters apply on the next extraction or regeneration after you save them. Existing content is not updated automatically—click **Regenerate** on affected items, or re-import/re-publish through your integration.
Filters do not apply to content last saved in the Editor (`manual_segment`). See [When filters apply](#when-filters-apply) for the full breakdown by integration.
New accounts include [default Type filters](#default-filters)—a set of **Include** and **Exclude** rules that run automatically. The **Include** presets keep only common editorial element types (`p`, `h1`–`h6`, `div`, etc.) and strip everything else. Check **Settings → Extraction → Filters** for organization-wide (**All projects**) rules as well as project-specific ones.
## Getting help
If you encounter issues or have questions, [contact support](/docs-and-guides/support/get-support). Include the article URL or HTML snippet and the filters you have configured.