# The scan and the overview - Pruneline 1.x documentation

> Scan your site, see what it reads, and use the overview to find what needs a look.

Everything Pruneline reports comes from its scan. The scan only reads. Start it on the **Overview** tab of **Tools → Pruneline**.

![Tools → Pruneline: scan the site, then see how many items each list has to look at, and which editors and page builders your pages use.](https://storage.extendiment.com/media/866/screenshot-1.png)

## Scan your site

1. Go to **Tools → Pruneline**.
2. Click **Scan the site** (or **Scan again** after the first time).
3. Wait for the progress bar. The page reloads with the results when the scan is done.

Under the button, **Last scan finished … ago** says how fresh the results are. Before the first scan, every other tab says Pruneline hasn't scanned the site yet and offers the same button.

Big sites are scanned in batches, a few seconds at a time, so the scan never times out. If you close the page during a scan, it carries on the next time you open **Tools → Pruneline**.

> [!TIP]
> You don't need to scan after every edit. When you save a post, in the WordPress editor or a page builder, Pruneline reads it again straight away. Scan again after you install, update, switch off or delete plugins or themes, or after importing content.

## What the scan reads

- **Your content**: posts, pages and every other kind of content plugins keep as posts, including templates, template parts, synced patterns, navigation menus and page-builder templates. Revisions, attachments, menu items, the trash and WooCommerce orders aren't read.
- **Drafts**: published and private content always. Drafts, pending and scheduled posts too, unless you turn that off in [Settings](settings-and-site-health).
- **Page-builder layouts**: Elementor's widgets, and the layouts of Beaver Builder, SiteOrigin Page Builder, Bricks, Oxygen, Divi and WPBakery. See [Page builders and templates](page-builders).
- **Block widgets**, in **Appearance → Widgets**.
- **Your theme's files**: with a block theme, the template and template-part files of the active theme (and its parent), so the parts, patterns and menus they use count as used.
- **Your plugins' and themes' code**: which blocks, Elementor widgets, options, tables and scheduled events belong to which plugin. Each plugin is read once, and again when it is updated. Pruneline keeps what it learned after a plugin is deleted, so it can still name it later.

## The overview

After a scan, the **Summary** table lists each list with a short description and a number under **To look at**:

| List | What the number counts |
|---|---|
| **Missing blocks** | Blocks that are missing or need confirmation |
| **Missing widgets & modules** | Page-builder widgets and modules that don't work now |
| **Templates** | Templates with no reference found |
| **Patterns & parts** | Patterns, parts and menus with no reference found |
| **Hidden everywhere** | Pages with Elementor elements hidden on every device |
| **What breaks** | Inactive or deleted plugins and themes that something still depends on |
| **Leftover data** | Leftover items you can clean up |

Click a list's name to open its tab. **Editors in use** lists the block editor and each page builder found, how many places use it, and whether it is active.

## Working with the lists

Every list works like the lists in WordPress:

- Click a view at the top, such as **Missing** or **No reference found**, to show only those rows.
- Search, and sort by any column.
- Set how many rows a page shows under **Screen Options**.
- Hover over a row for **Where used** or **Details**: every place it is used, with a link to edit each one.
- **Download as CSV**, next to each list's description, downloads the list in the current view. A search doesn't narrow the download. A row's detail page has its own **Download as CSV** link.

## Related

- [Blocks](blocks)
- [Page builders and templates](page-builders)
- [Troubleshooting](troubleshooting)

Source: https://extendiment.com/plugins/pruneline/docs/1.x/the-scan