Anywhere Elementor uses the elementor_library custom post type to store reusable templates and exposes them as shortcodes (typically [elementor-template id="123"]) you can drop into any post, page, or theme location. The default WP admin shows templates in one screen and the posts that embed them in another, with no connection between them.

SleekView reads wp_posts filtered to post_type=elementor_library for the template inventory, and uses a contains-text filter on post_content in wp_posts to find every post that embeds a given template ID. Pin saved views per template to see exactly where it's used. Group embeds by host post type (post, page, custom). Filter by status, author, and last edited.

Inline edits to template metadata (status, title, author) run through wp_update_post so Elementor hooks fire normally. The template layout JSON inside _elementor_data stays untouched. CSV export of any audit slice acts as a client deliverable or internal record of template usage across the site.

Anywhere Elementor makes it easy to build a reusable block once and drop it into a dozen posts. That convenience is exactly what creates template debt over time. After a year of campaigns, a typical site has CTA blocks, promo strips, signup forms, and footer experiments scattered across the elementor_library CPT, most of them embedded somewhere, some of them not embedded anywhere anymore.

The default Elementor template list shows the templates but not their usage counts. The default post list shows the content but not which templates it embeds. A queryable inventory joins the two.

Templates with zero embeds become a saved view ready to retire. Templates with dozens of embeds become an obvious candidate for editorial review before any change. Agencies use the grid for handover deliverables; in-house teams use it before a redesign to plan which templates survive and which get archived.

The audit cost drops to the cost of opening the table.