Divi Mega Pro stores each mega-menu layout as an entry in the et_pb_layout custom post type with metadata flagging it as a mega-menu container. Menu-item bindings live in wp_options under the plugin's own option key, mapping nav menu item IDs to layout IDs. The default WordPress menu admin shows menu items as a tree but gives no visibility into which mega-menu layout is attached, when it was last edited, or by whom.

SleekView reads the et_pb_layout CPT joined with the Mega Pro bindings stored in wp_options and exposes both as one queryable table. Filter to mega-menu layouts only. Sort by last edited to find stale menus. See which menu item from wp_term_taxonomy each layout is currently bound to. Spot orphan mega-menu layouts that no live menu item references.

Inline edits to status, slug, and author write through standard WordPress update calls so any Divi hooks fire normally. The Divi shortcode tree inside the layout stays untouched (that's still the visual builder's job) but the layout's metadata becomes editable per row. CSV export of the orphan-layouts view turns a yearly cleanup pass into a five-minute job.

Divi Mega Pro is the standard mega-menu solution for Divi sites and most sites running it have been running it for years across multiple navigation redesigns. Each redesign leaves layouts behind: the old products mega menu, the seasonal-campaign menu nobody trashed, the draft someone started for a launch that got cancelled. The default Divi admin gives no surface for these.

The et_pb_layout CPT mixes mega menus with Theme Builder layouts and saved Divi templates with no easy filter for Mega Pro entries specifically. Orphan mega-menu layouts no live menu references are completely invisible in the default UI because the binding metadata sits in wp_options under a key the admin doesn't surface. A queryable inventory changes the cost of an audit from a multi-day investigation to a half-hour pass through the grid.

Filter to orphan layouts and decide layout by layout what to keep. Find stale mega menus untouched in over a year and review them for relevance. Agencies running Mega Pro across dozens of client sites use this audit as a routine handover deliverable; in-house teams use it as quarterly housekeeping that prevents the operational debt from compounding.