# Settings and Site Health - Pruneline 1.x documentation

> Choose whether drafts are scanned, turn the Site Health check and the Elementor panel on or off, and read the Site Health result.

## Settings

Go to **Settings → Pruneline**. The page has three checkboxes under **Scanning**, all ticked by default:

| Setting | What it does |
|---|---|
| **Drafts**: **Also scan drafts, pending and scheduled posts** | Drafts are what goes live next, so a missing block in a draft is worth knowing about. Untick it to scan only published and private content. Takes effect from the next scan. |
| **Site Health**: **Report scheduled events left by inactive or deleted plugins in Site Health** | Adds the check described below. |
| **Elementor editor**: **List the page's shortcodes in the Elementor editor, and whether each one works** | Shows the [Elementor editor panel](elementor-editor-panel). |

Click **Save Changes**.

> [!NOTE]
> With drafts left out, a template or pattern used only in a draft shows "No reference found". Keep drafts ticked before you trash templates.

> [!TIP]
> **Tools → Pruneline** has a **Settings** button next to its title, and the Plugins screen has a **Settings** link under Pruneline.

## The Site Health check

When a plugin is switched off or deleted, the events it scheduled stay. WordPress keeps trying to run them, and nothing answers. Pruneline adds a check for that to **Tools → Site Health**, under the **Performance** label.

- **No scheduled events are left from inactive plugins**: all is well.
- **Inactive plugins left scheduled events behind**: a recommendation that lists each event with the plugin that left it, and a **Review them in Pruneline** link to the scheduled events on the [Leftover data](leftover-data) tab, where you can export and delete them.

The check counts WP-Cron events and pending Action Scheduler actions that Pruneline has traced to an inactive or deleted plugin. Events it can't trace aren't reported here, but they're listed under **Unknown owner** on the **Leftover data** tab. Run a scan first: Pruneline traces events from the plugins' code it has read.

## Related

- [The scan and the overview](the-scan)
- [Leftover data and cleanup](leftover-data)
- [Elementor editor panel](elementor-editor-panel)

Source: https://extendiment.com/plugins/pruneline/docs/1.x/settings-and-site-health