Divi Pixel modules render inside Divi's shortcode tree, which lives in wp_posts.post_content alongside the _et_pb_use_builder flag in wp_postmeta. Pixel shortcodes use prefixes like [dipi_image_card], [dipi_breadcrumbs], and [dipi_modal]. The default WordPress admin treats those as ordinary posts, so finding every page that uses a specific Pixel module means running raw SQL or scrolling through dozens of Divi pages.

SleekView reads every Divi-built post plus the et_pb_layout library, joins them into one table, and exposes Pixel module usage as filterable chips. Filter to pages containing a specific dipi_* shortcode tag. Sort by last edited to surface stale layouts. Pin a saved view for each audit type so the next pass takes minutes rather than hours.

Inline edits to status, slug, and author route through standard WordPress update calls so any Divi or Pixel hooks fire normally. The shortcode tree containing the Pixel modules stays untouched (that's the Divi visual builder's job) but surrounding metadata becomes editable per row. CSV export of an audit slice hands the team a clean inventory of every Pixel-touched page on the site.

Divi Pixel is one of the most installed Divi enhancement plugins and the sites using it typically run it for years across multiple redesigns and campaign cycles. Each cycle leaves pages behind: old launch pages with Pixel modals, abandoned drafts using image cards, A/B test variants in the layout library that nobody trashed. The default WordPress admin lists those as ordinary posts with no indication of which Pixel modules they use or when they were last touched.

Stale layouts pile up quietly. Library entries with no live parent go unnoticed. Drafts owned by former staff sit in the database indefinitely.

None of this is Pixel's fault, it's the operational debt any high-volume builder add-on accumulates without an audit surface. A queryable inventory turns the audit from a multi-day project into a half-hour grid pass. Filter to pages using a deprecated Pixel module and migrate them.

Find every Divi draft owned by people who left the team. Agencies running Divi across client sites use this audit as a routine handover deliverable; in-house teams use it as quarterly housekeeping.