ChecknautCompatibility, privacy, and limits
Know which builders support editing and where data is sent.
Supported builders
| Builder | Audit | Pro editing |
|---|---|---|
| Divi 5 | Stored content and supported live checks | Pages, modules, Theme Builder, loops, supported WooCommerce layouts; design-system authoring with the Builder Pack, part of Pro |
| Elementor | Supported element-tree and live checks | Pages and supported design controls; templates and loops require the relevant Pro integration |
| Block editor | Blocks and supported live checks | Create and replace page/post content as a whole |
| Divi 4 | Audits and the free rescue compatibility check; rescue repairs need the Builder Pack, part of Pro | Page building requires Divi 5 |
| Other builders | Rendered-page and install checks within stated scope | Detected, named and refused for writes |
Rescuing an older Divi site
The rescue scan classifies up to 300 pages, finds broken builder metadata, old shortcodes and missing-module references, and gives an ordered repair plan. The check is free; the repairs are part of the Builder Pack, which comes with every Checknaut Pro plan. It is not a one-click complete migration. Back up, review the plan, repair shared chrome before dependent pages, and verify each change.
Which versions should I trust?
Use your install's site context and the current changelog. Historical test totals describe a named release and environment, not every installation. Missing integrations are reported rather than counted as tested. These docs describe Checknaut 2.0.0.
Where does my data go?
Audits, fixes, scores and recorded history live on your WordPress server. Checks can make requests needed for the feature: linked URLs, DNS, public domain records, and plugin-health sources. Pro contacts Freemius for licensing/updates and any screenshot, stock-image, host-cache or fleet services you configure. See the privacy policy for service details.
What changes when I connect an AI?
Your assistant can request site content and send that content to its own provider under your agreement with that provider. Checknaut does not independently call an AI model. Consider the sensitivity of content before granting access.
Does it inject an accessibility overlay?
Supported fixes change content or settings at the source. The plugin is not an accessibility overlay. Front-end output can include enabled repairs, SEO/schema output, fonts/tokens, and optional motion. Review the actual feature you enable rather than assuming there is never any front-end output.
Compliance and performance
No automated score certifies ADA/WCAG or legal compliance. Performance audits identify available signals and issues; they do not guarantee Core Web Vitals or revenue improvements. Use manual testing and specialist review where required.
Removing the plugin
Deleting one Checknaut copy (free or Pro) while another is still installed keeps your settings, history and audit records. Deleting the last copy removes what Checknaut stored. Export anything you need to retain first. Native page content is distinct from the plugin's records; keep a full backup.
Need help with your install? Contact support. Related: Getting started.
Reviewed for Checknaut 2.0.0 on 31 October 2026.