Block inventory
See instance counts and source counts in one place.
WordPress block audit for technical teams
Know exactly where your WordPress blocks are used.
DXM Block Audit gives WordPress teams deterministic visibility into Gutenberg usage with block inventory, source drill-down, scan health, and export-ready reporting across modern content structures.
Source drill-down
Open exact pages, templates, and related sources.
Scan health
Check freshness before cleanup, migration, or reporting.
Deterministic visibility
Inventory, source drill-down, and scan health for cleanup, redesign, and handoff.
Operational blind spots
Stop guessing where blocks are used.
Gutenberg sites accumulate usage across posts, pages, reusable content, template parts, and navigation structures. DXM Block Audit gives your team a deterministic inventory so change impact can be reviewed before cleanup, migration, or redesign work moves forward.
Hidden usage surfaces
Block usage spreads across posts, pages, patterns, template parts, and navigation structures that are easy to miss manually.
Change impact is hard to prove
Without exact source evidence, cleanup, replacement, and redesign work turns into guesswork about what will break.
Stale or incomplete evidence
If scan health and freshness are unclear, audit answers become harder to trust, share, and act on.
Product evidence
See what the audit actually shows.
DXM Block Audit starts with inventory and expands into source drill-down, scan health, and export-ready reporting so teams can inspect evidence, not rely on assumptions.
Block inventory
See inventory and source drill-down together.
Review block-level inventory with instance counts and source counts, then open exact usage locations when cleanup or redesign work needs verification.
- Instance and source counts by block type
- Source drill-down across pages, posts, templates, and related content
- Useful filters that stay workable on larger WordPress sites
Scan health
Check freshness before you trust the audit.
A full scan builds the authoritative baseline. From there, scan status, freshness signals, and recent lifecycle events help teams decide whether the audit is current enough to act on.
- Latest scan status in plain language
- Freshness guidance before results are shared
- Recent scan events for operational context
Source evidence
Open source-backed evidence and export the filtered view.
Open the exact sources behind a block, narrow the view by source type or quick scope, and export the filtered evidence without leaving the audit workflow.
- Quick scope and source-type filters inside the modal
- Live source rows across pages, templates, and reusable content
- Filtered CSV export from the same evidence view
Additional admin views
Patterns, template parts, and navigations stay in the same audit workflow.
Reusable content, theme structures, and navigations keep the same inventory, source counts, and drill-down model, so teams can review the full WordPress surface without context switching.
Patterns tab
Reusable content stays visible.
Reusable patterns keep the same references, source counts, and source drill-down workflow without shifting into a separate reporting surface.
Template parts tab
Theme-level structures stay visible.
Template parts keep the same inventory, source counts, and drill-down model, so theme-level cleanup and release work can be reviewed with the same evidence-first workflow.
Navigations tab
Navigation structures stay in the audit.
Navigation structures stay in scope too, so cleanup and redesign work can account for menus alongside posts, pages, and patterns.
Modern WordPress coverage
Coverage across modern WordPress content.
The audit goes beyond post content so teams can understand reusable and theme-level structures with the same calm, source-backed workflow.
Patterns audit
Audit reusable and synced pattern entities separately from raw block-type usage.
Template parts
Track template part references and unresolved targets that need follow-up before release work.
Navigations
Audit direct navigation references before cleanup, migration, or redesign work lands.
Multisite support
Support multisite audit scenarios while keeping scan execution in the relevant site context.
Write-controlled scans
Use dry-run validation workflows while keeping full index writes behind a valid write-enabled license.
Workflow overview
How the audit workflow works.
DXM Block Audit starts with a full scan that builds the authoritative baseline. From there, teams can inspect inventory, verify exact usage, and export findings for reporting or handoff.
Run a full scan
Build the authoritative baseline index from the current WordPress state.
Review inventory across entities
Inspect blocks, patterns, template parts, and navigations in one audit workflow.
Verify usage with source drill-down
Open exact source locations before cleanup, replacement, or redesign work moves forward.
Export findings and continue operations
Share filtered results, support handoff, or continue into operational workflows when needed.
Operational tooling
Built for operational WordPress teams.
The product stays calm in the UI, but the underlying workflow is built to support technical teams that need repeatable audit operations.
REST API surface
Inventory, source, scan, config, and license-aware workflows are exposed through a REST surface built for operational use.
WP-CLI workflows
Run scan and reporting workflows in repeatable command-line operations when UI clicks are not enough.
Export workflows
Filtered inventory and source-level exports support reporting, QA, and delivery handoff outside the plugin UI.
Multisite-aware scope
Network Admin can surface aggregated audit visibility while scans still run in the relevant site context.
Plans and licensing
Choose the yearly plan that fits your workflow.
Choose the yearly subscription that matches your production surface. Billing, renewal, and cancellation are handled through Lemon Squeezy as Merchant of Record.
Single
$129 /year
Best for one production site.
For independent builders and lean teams managing one production site.
- 1 production site entitlement
- Full block audit workflow
- Subscription-backed updates and fixes
- Email support
Agency
$299 /year
Best for agencies and teams managing multiple production sites.
For agencies and teams managing multiple production sites.
- Up to 25 production site entitlements
- Full block audit workflow
- Subscription-backed updates and fixes
- Priority email support
Yearly subscription billed in USD. Lemon Squeezy checkout shows the final charged amount, including any applicable tax or VAT, before purchase. Plans renew yearly until canceled in the Lemon Squeezy billing portal. Initial purchases are eligible for refund within 14 days.
Support and operations
FAQ
Answers to the questions that usually come up before purchase, rollout, and recurring scan work.
Need a licensing or rollout answer?
Start with the documentation for install and activation steps, or contact support if your team needs a direct answer before rollout.
What does DXM Block Audit scan?
DXM Block Audit scans stored Gutenberg content and indexes supported source types across blocks, patterns, template parts, navigations, and related editorial content.
Does it modify post content?
No. Scans read stored Gutenberg content and write only to DXM Block Audit index tables. They do not modify post content.
Does it work with custom blocks?
Yes. Registered custom blocks that appear in indexed content are surfaced alongside core blocks in the inventory.
Does it support multisite?
Yes. The plugin supports multisite audit scenarios. Network Admin can surface aggregated audit data, while scans still run in the relevant site context.
Can I export the results?
Yes. DXM Block Audit supports export workflows for inventory and source-level data. Large exports may be capped by default unless developers override export limits.
Do I need a license for every scan workflow?
Dry-run validation workflows are available, but full index writes require a valid write-enabled license. Updates also require an active license.
How do licensing, renewal, and refunds work?
DXM Block Audit code is licensed under GPLv2 or later. Paid subscriptions cover one or up to 25 production-site entitlements, yearly updates, support, and account-backed entitlements. Plans renew yearly until canceled in the billing portal. Lemon Squeezy checkout shows the final charged amount, including any applicable tax or VAT, before purchase. Initial purchases are eligible for refund within 14 days.
Ready for the next cleanup window
Make Gutenberg usage visible before the next cleanup or migration.
Use DXM Block Audit to move redesign, cleanup, and handoff work onto source-backed evidence your team can inspect, trust, and act on.
- Source-backed inventory before cleanup or redesign work moves forward
- Export-ready evidence for QA, reporting, and handoff
- Yearly updates with a 14-day refund window