Diagnostics

A full run against your exact install: the PHP floor, the WordPress and Divi versions, Divi itself, the connector and every tool group. The suite reports its own totals on every run, so the number moves with your install and your plugin set. On a Divi site wp-admin reports fewer than the connector does: one group, WooCommerce, needs Divi’s builder framework, which that screen does not load, so it is skipped there and Diagnostics names it on screen. It reports named failures rather than a green tick, so a problem tells you which contract broke instead of that something, somewhere, is wrong.

The things that break a connection, checked before you hit them: REST availability, SSL, and whether the Divi 5 builder is actually enabled.

The misconfigurations hosts actually cause, named with the fix rather than a stack trace — so you can send your host a sentence they can act on instead of a screenshot of an error.

About 2,400 checks on the free plugin, and about 3,450 with Checknaut Pro, run against your actual install (on the 5.0.0 test site with WordPress 7.1 and Divi 5.13.1: 2,386 and 3,447), depending on your theme, your plugins and whether the run exercises the write path, and the run reports its own total rather than a number we printed here — not our demo — covering the engines, the write path and the connector. Runs pause cleanly and resume, so they finish even under strict hosting budgets. Read scope touches nothing and is safe on production; write scope exercises a temporary draft it deletes afterwards. The full suite ships in the download from this site; the WordPress.org build carries the runtime diagnostics only.

After installing or upgrading the plugin, after a Divi update, or when something behaves oddly — a failure names what broke instead of leaving you guessing. Common install and connection questions are answered in the FAQs. The connection panel shows your assistant attached in real time; the setup tutorial walks the first run, and support reads these results first.