Use case

Find where Gutenberg blocks are used across WordPress

When someone asks where a Gutenberg block is used, the hard part is rarely finding one obvious page. The hard part is building a trustworthy site-wide answer across normal content, shared structures, and block variants that look similar but should be handled differently.

Problem statement

Questions like “where is this CTA used?” or “which pages still use this block?” usually arrive right before cleanup, QA, redesign, support, or migration work starts. If the answer is incomplete, every step after that gets slower and riskier.

For the broader workflow map, browse WordPress Gutenberg Block Audit & Refactor Use Cases .

Product path

In DXM Block Toolkit, this usually starts broad, then narrows into exact sources only if the first counts are not enough to answer the question.

Blocks inventory -> View sources -> Advanced Source Filters -> Export

When this matters #

This workflow matters whenever the team needs exact block visibility before making a change.

A developer needs to find every source using one Gutenberg block before editing or removing it.
A content or support task starts with a vague question about where one CTA, disclaimer, or layout block still appears.
A cleanup or migration depends on a filtered source list, not a guess based on a few known pages.
A team needs evidence across patterns, template parts, or navigation as well as normal editorial content.

Why manual work is risky #

Manual block discovery can work on a small site, but it gets unreliable as soon as the content surface broadens.

WordPress editing flows are built for changing one source at a time, not for answering site-wide impact questions quickly.
The same block name can show up in many contexts, which makes page-by-page review noisy and easy to miss.
Without indexed evidence, teams end up repeating the same search work every time the question comes back.

How DXM Block Toolkit helps #

DXM Block Toolkit turns block usage discovery into a repeatable workflow instead of a one-off hunt through the WordPress admin.

Block inventory provides a current list of indexed Gutenberg blocks and their counts.
View sources drills into the exact posts, pages, custom post types, patterns, template parts, and navigation items behind each block record.
Filters help narrow the list when the same block type contains several design variants, attributes, or copy patterns.
Exports and source-backed worklists make the result easy to hand to QA, content teams, or another developer.

Concise workflow #

A concise discovery workflow keeps the answer practical and easy to verify.

Run a fresh scan so the inventory baseline is current enough to trust.
Find the target block in block inventory and review its broad usage counts.
Open View sources to inspect the exact records behind that block.
Apply source or block-content filters when only one variant, attribute, class token, or text fragment should stay in scope.
Export the filtered source list or use it to prepare the next cleanup, QA, redesign, or refactor task.

If you need the operational steps, continue with How to Find Where a Block Is Used in WordPress Gutenberg .

Move into a related workflow when usage discovery becomes redesign planning, bulk replacement, or shared-structure review.

Content cleanup

Find Outdated CTAs

Isolate outdated CTA copy, disclaimer text, or campaign wording inside repeated Gutenberg blocks before cleanup or replacement widens to every instance.

Find outdated CTAs or campaign content inside Gutenberg blocks

Redesign impact