Beyond pages

Pages are where most tools stop. Blog posts, shop pages and the Theme Builder are the rest of the site, and with Checknaut Pro your assistant builds those too: posts on any site, Theme Builder templates on Divi 5 and Elementor Pro, and WooCommerce store pages on Divi 5.

Posts and shops

Gutenberg blog posts on any site, and on Divi 5 the WooCommerce shop, cart, checkout and product pages (My Account excluded), built against the same design system as everything else — so the shop does not look like it came from a different site than the homepage.

Theme Builder and Library

Headers, footers and templates. Checknaut reads and writes the whole Theme Builder and the Divi Library, so a change to a footer link is one edit in one template rather than forty edits across forty pages. On Elementor, Checknaut Pro also creates and changes Elementor Pro theme templates — headers, footers, singles, archives, popups and loop items — with their display conditions.

A way back everywhere

One step back before every Theme Builder or Library write — a WordPress revision, or a saved copy of the previous content where revisions are switched off. One bad header write is every page on the site, so a template gets exactly the same guarantee as a page.

What’s covered

Plain WordPress posts — this site’s own blog is written that way, because prose belongs in the editor and layout belongs in Divi — WooCommerce pages on Divi 5 built with your store’s real context, and Theme Builder headers, footers and templates, with a guard that warns before a new template would clobber one matching the same pages.

Plans

These writers are included in every paid plan — the plans differ by seats, not features: Solo covers one site, Pro five, Agency twenty and Studio fifty, from $99/year. The free tier still audits every page they produce, so you can hold the output to the same standard as the rest of the site.

The common thread is context: the plugin hands your assistant your store’s products, your templates’ display conditions and your posts’ structure before anything is written, so the output fits the site it lands on instead of arriving generic. And because every write is journaled, the same undo and snapshot guarantees that protect pages apply out here too — a template change is as reversible as a heading fix.

What the WooCommerce tools have and have not been tested against. For 5.0.0 the page and post writers were exercised on the plain, Divi and Elementor test sites (WordPress 7.1). WooCommerce was not. A separate check on 24 September 2026 built a shop, cart, checkout and product template on a Divi 5 test site with WooCommerce 11.1.2, but no run behind the self-test numbers on this site had WooCommerce active, so treat these tools as shipped and unverified here rather than as proven, and check them on staging before a client store.

The plugin is honest about it in both directions: on a site with no WooCommerce it withholds its WooCommerce tools by name and says why, instead of offering a tool that cannot work. On Divi 5, building the shop, cart or checkout page replaces that page whole, so it asks for confirmation first.

See pricing