Description
- Find which blocks are used across your site.
- Fully Integrated with the WordPress Admin.
- Use filters to see Posts that use a specific block.
- Find Posts that use Reusable Blocks.
- Use the WP CLI to quickly find blocks from the command line.
- Use custom WordPress filters to extend the Block Catalog.
Getting Started
-
On activation, the plugin will prompt you to index your content. You need to do this first before you will be able to see the various blocks used on your site. You can also go to WP-Admin > Tools > Block Catalog to do this yourself. Alternately, you can run the WP CLI command
wp block-catalog indexto index your content from the command line. -
Once indexed, you will be able to see the different blocks used on your site in the Block Catalog Taxonomy.
-
Navigating to any Block Editor post type will also show you the list of blocks present in a post.
-
You can also filter the listing to only show Posts that have a specific block.
FAQ
1) Why does the Plugin require indexing?
Block Catalog uses a taxonomy to store the data about blocks used across a site. The plugin can build this index via the Tools > Block Catalog screen or via the WP CLI wp block-catalog index. After the initial index, the data is automatically kept in sync after any content updates.
2) Why does the name displayed in the plugin use the blockName attribute instead of the title?
If your blocks are registered on the Backend with the old register_block_type API, you may be missing the title attribute. The newer register_block_type_from_metadata uses the same block.json on the FE and BE which includes the Block title.
When the plugin detects such a missing title, it uses the blockName suffix instead. eg:- xyz/custom-block will display as Custom Block.
To address this you need to update your custom block registration. If this is outside your control, you can also use the block_catalog_block_title filter hook to override the title as seen here.
Where do I report security bugs found in this plugin?
Please report security bugs found in the source code of the Block Catalog plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
Screenshots
Changelog
1.6.3 – 2026-10-29
Added
- “Settings” page link right on the plugins page to review the settings of the plugin from there directly (#92).
Changed
- Change our default capability from
edit_poststomanage_categories. Note: this is a breaking change for Authors and Contributors who will no longer have access to trigger a catalog indexing (GHSA-38fv-295q-m8cf). - Bump WordPress tested-up-to version 7.1 (#84, #110, #119).
- Bump minimum supported WordPress version to 6.6 (#85).
Fixed
- Fatal error accessing object cache properties that may be protected/private in drop-ins (#96).
- Ensure the index deletion properly deletes terms (GHSA-r5x5-g636-fr9r).
Security
- Resolve GHSA-r5x5-g636-fr9r (GHSA-r5x5-g636-fr9r).
- Resolve GHSA-38fv-295q-m8cf (GHSA-38fv-295q-m8cf).
1.6.2 – 2025-02-03
- Changed: Bump WordPress “tested up to” version 6.7 (props @thrijith, @jeffpaul, @Sidsector9 via #74, #75).
- Security: Bump
webpackfrom 5.91.0 to 5.94.0 (props @dependabot, @peterwilsoncc via #68). - Security: Bump
serve-staticfrom 1.15.0 to 1.16.2 andexpressfrom 4.19.2 to 4.21.1 (props @dependabot, @Sidsector9 via #70). - Security: Bump
cookiefrom 0.6.0 to 0.7.1 (props @dependabot, @Sidsector9 via #76).
1.6.1 – 2024-07-09
- Changed: Update Support Level from
BetatoStable(props @jeffpaul, @dkotter via #56). - Changed: Bump WordPress “tested up to” version 6.6 (props @sudip-md, @jeffpaul via #60).
- Changed: Bump WordPress minimum supported version to 6.4 (props @sudip-md, @jeffpaul via #60).
- Security: Bump
bracesfrom 3.0.2 to 3.0.3 (props @dependabot, @faisal-alvi via #58). - Security: Bump
wsfrom 7.5.9 to 7.5.10 (props @dependabot, @faisal-alvi via #58).
1.6.0 – 2024-05-13
- Added: WP-CLI command,
export, to generate a CSV of the block catalog (props @dsawardekar, @psorensen, @Sidsector9 via #52). - Added: Classic Editor block detection (props @dsawardekar, @Sidsector9 via #53).
- Changed: Bump WordPress “tested up to” version 6.5 (props @sudip-md, @jeffpaul via #51).
- Changed: Bump WordPress minimum from 5.7 to 6.3 (props @sudip-md, @jeffpaul via #51).
- Changed: Replaced lee-dohm/no-response with actions/stale to help with closing no-response/stale issues (props @jeffpaul via #48).
- Security: Bump
expressfrom 4.18.2 to 4.19.2 (props @dependabot, @Sidsector9 via #50). - Security: Bump
follow-redirectsfrom 1.15.5 to 1.15.6 (props @dependabot, @Sidsector9 via #50). - Security: Bump
postcssfrom 7.0.39 to 8.4.33 (props @dependabot, @Sidsector9 via #50). - Security: Bump
10up-toolkitfrom 5.2.3 to 6.0.1 (props @dependabot, @Sidsector9 via #50). - Security: Bump
webpack-dev-middlewarefrom 5.3.3 to 5.3.4 (props @dependabot, @Sidsector9 via #50).




