Reading your coverage report

The scan answers one question: how much of this site converts on its own, and what needs you? It reads your Elementor content and changes nothing, the dashboard says so plainly: nothing changes until you convert.

The headline number

At the top you get a percentage, how much of this site converts automatically, and, underneath, the same thing counted in elements: how many convert automatically, how many need review, and how many need manual work.

Read the percentage as a planning number, not a grade. A site at 92% is not “8% broken”; it’s a site where most of the work is already done and the rest is named for you.

The groups

Your pages are grouped by what happens next.

To convert

Pages that carry Elementor data and haven’t been converted yet. This is your queue.

Rows tagged Woo content, needs a license are WooCommerce pages, products and product templates on an unlicensed site. They stay listed, so you can see the whole picture, but the tag stands where the Convert button would be until you activate a license.

Converts cleanly

Pages the engine expects to convert with nothing needing your attention. These are the ones to convert in bulk with confidence.

Needs your eyes

Pages that will convert, but where something changed shape, was approximated, or couldn’t be carried. This is not a failure list. Most entries are small and specific, a carousel that can’t reproduce one behaviour, a widget whose closest Bricks equivalent styles a slightly different node.

Each one is named, with the widget and what happened to it, rather than left for you to spot. The review queue explains how to work through them, and what it can and can’t tell you.

Migrated cleanly

Pages already converted with nothing outstanding. Once every page is here and nothing is waiting on your eyes, the dashboard tells you it’s safe to remove Elementor.

Third-party widgets

Widgets from add-ons the engine doesn’t convert, Essential Addons, OoohBoi, and most of the Crocoblock pack, become a labelled placeholder card on the converted page, naming the add-on where it can. You get a visible marker in the right place rather than a silent gap, so you know exactly what to rebuild and where.

One add-on family is now an exception. JetEngine listing grids convert into native Bricks query loops: the listing design you built comes across and repeats over your live data, and inside each card the JetWooBuilder archive price and add-to-cart button convert too. The query itself carries as far as Bricks can express it, and anything it can’t, a filter reading a per-product custom field for example, is named in the review queue rather than quietly dropped. Every other Jet widget still becomes a placeholder card.

What the scan can’t tell you

The scan reads your content, not your intent. It can tell you a slider will convert; it cannot tell you the slider was already broken, or that you’d rather rebuild that section anyway. Treat a converted page as a draft to review, which is what the preview switcher and the review queue are for.