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. From wp-admin it reports fewer: five groups — accessibility, Theme Builder, Divi Library, content coverage and WooCommerce — need Divi’s builder framework, which that screen does not load, so they are skipped there and Diagnostics names them 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.

A few thousand checks run against your actual install, and the run reports its own total rather than a number we printed here — not our demo — covering every tool the plugin ships. 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.

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. The connection panel shows Claude attached in real time; the setup tutorial walks the first run, and support reads these results first.