Native WordPress Blocks

Listdom supports native WordPress blocks alongside its existing shortcodes. Blocks let you compose directory pages and listing content visually without replacing the saved layouts, search forms, permissions, or checkout configuration that power them.

Add a Listdom block

1. Open a page that uses the WordPress block editor. If you also want to edit listings with it, enable Listdom → Settings → General → Integrations → Block Editor; that setting is not a prerequisite for inserting Listdom blocks on ordinary pages.
2. Edit the page in the WordPress block editor and search the inserter for Listdom.
3. Insert the block for the task: a saved directory layout, search form, Add Listing form, dashboard, authentication, profile, checkout, order summary, or simple map.
4. Choose the relevant saved layout or configuration in the block controls. Check the editor preview, save, and test the published page as the intended visitor or listing owner.

The integration includes a saved-layout block, 27 listing-element blocks, and eight application blocks. Listing elements need a suitable listing context; adding one to an unrelated page does not select a listing automatically. Use the appropriate page, template, or template-part context when building reusable listing content.

Templates and existing content

Listdom blocks can be used in pages and supported Site Editor templates and template parts. Existing Listdom shortcodes remain supported, including older saved layout blocks and shortcodes inside synced patterns. There is no requirement to rebuild working shortcode pages simply to adopt blocks.

For a saved directory layout, continue configuring its skin, filters, and display rules in Listdom → Shortcodes. For a search block, configure the search form in Listdom first. A block is another placement method, not a bypass for those settings.

Add-on blocks

Active supported add-ons expose their own blocks. These include integrations for ACF, Ads, Auction, Booking, Claim, Compare, Connect inquiries, Favorites, Franchise, Google Places, Items, Jobs, Local Logic, Reviews, SMS verification, Stats, Membership pricing, Team, and Top Up. The owning add-on must be active and its normal dependencies and permissions still apply.

If an add-on block is missing, check the add-on’s installation, activation, license where required, and configuration. Native blocks do not unlock paid functionality or replace checkout, access, or moderation rules.

Check the complete visitor flow

Previewing a block is not the same as completing its action. Test search and pagination on the published directory, sign-in and registration with the intended roles, and forms and checkout in a safe test environment. Check both desktop and mobile layouts and avoid inserting duplicate checkout or authentication flows unnecessarily.

See Frontend Dashboard, Template Builder, and Payments for the underlying workflows.