Checknaut

Sharraxaad

Checknaut checks every page of your WordPress site and tells you, in plain English, what a visitor would trip over and what to do. Where it can make the change itself, there is a Fix button, and every fix can be undone.

Free, with no page limit, no account and no AI service.

How it works

  1. Open Checknaut. The first visit checks the whole site, in about a minute.
  2. Home shows one score out of 100 (Excellent, Good, Needs work or Needs attention) and the three fixes that matter most.
  3. Open a fix: what is wrong, on which pages, whether visitors will notice, and what to do. Click Fix, or mark it “It’s fine as is” with your reason.
  4. Undo history lists every change Checknaut made, each with its own Undo.

Six plain groups

Everything found lands in Broken, Looks unfinished, Easy for everyone, Found on Google, Speed or Safety, marked Critical, Warning or Good to fix. Behind them run seven audits: site QA, accessibility, SEO, performance, Site Health, legal pages and design consistency. They fetch each page the way a visitor does and read what is actually served. What they cannot see (content a builder generates at render, a host that blocks loopback requests) is named, never counted clean.

One-click fixes, free

Image descriptions from your Media Library, heading structure, zoom on phones, skip link, main landmark, SEO fields (with an SEO plugin), image compression and the security switches. Here each Fix button fixes one page. Fixes are written into your site at the source: no overlay, nothing tracked about your visitors.

Images, no outside service. Pick a Size (Small, Medium, Large) and a level (Low, Medium, High), preview on your own images, then run it on the library, the flagged images or a selection. Shrunk in proportion, never cropped or enlarged, and compressed only as far as a measured similarity score allows at your level. WebP where your host can write it, or keep JPEG and PNG. Originals are kept until you remove them, so every image and every run has an Undo. The screen explains each choice and names any other optimiser or image CDN it finds. Images never leave your server; the plugin downloads no code. Pro adds a browser best-quality mode (keep the tab open), compression of new uploads and AVIF.
Also free: Pages (every page and post, what built it, when it changed, how many things it has to fix), internal link checks, snapshots, runtime diagnostics, a read-only switch, a Deep Space theme and the admin in nine languages.

Three builders are written: Divi 5, Elementor and the block editor. Every other builder (Bricks, Beaver Builder, Breakdance, Oxygen, WPBakery and the rest) is detected by name, audited from its rendered page, and refused for writes rather than guessed at.

Checknaut Pro is a separate, paid plugin sold at checknaut.com. It fixes a problem on every page in one click and adds Launch Check, speed tools, site reports, scheduled audits, legal page drafts, filters and CSV export on Pages, and the AI connector (Claude, ChatGPT or any MCP client). This plugin contains no AI connector: it serves no MCP endpoint, registers no REST route of its own and calls no AI service. Its screens show locked previews of Pro, which each user can hide.

What it will not do. Audit output is automated static analysis: a floor, not a certification of ADA, WCAG, GDPR or any other law, and not legal advice. Nothing is written to a page without a way back.

WordPress is a registered trademark of the WordPress Foundation. Divi is a registered trademark of Elegant Themes, Inc. Elementor is a registered trademark of Elementor Ltd. Checknaut is an independent product by Abcreative, LLC and is not affiliated with, authorized by, endorsed by, or sponsored by any of them. All other product names and brands are the property of their respective owners.

Admin typefaces: Figtree and Plus Jakarta Sans, self-hosted under the SIL Open Font License 1.1.

External services

This plugin connects to the services below, only when the feature that needs them is used.

  • WordPress.org (api.wordpress.org): Site Health compares your core files with WordPress.org’s published checksums, runs WordPress’s own update check, and reads each installed plugin’s directory listing (last update, tested version) to flag abandoned plugins. Sends your WordPress version, locale and plugin slugs. Privacy policy: https://wordpress.org/about/privacy/
  • Your own site: audits and diagnostics fetch this site’s pages as a visitor would. Nothing leaves the server.
  • DNS: Site Health looks up your domain’s SPF, DMARC and MX records with your server’s resolver. Only the domain name is sent.
  • RDAP (rdap.org): when the Site Health audit runs, it asks rdap.org (which redirects to your registry) for your domain’s expiry date. Only the domain name is sent; cached 24 hours; the checknaut_health_domain_lookup filter turns it off. Privacy: https://about.rdap.org/ · https://www.icann.org/privacy/policy
  • Link checker (only with Checknaut Pro): when a link check runs, each URL linked from the checked page(s) gets a HEAD or GET request. Only the URL is sent, not your site’s address.
  • Google Fonts (fonts.googleapis.com, fonts.gstatic.com): only when a font family is recorded for loading (Checknaut Pro does this for a Google font Divi does not load), visitors’ browsers fetch its stylesheet from Google. The plugin sends nothing to Google. Privacy FAQ: https://developers.google.com/fonts/faq/privacy · Privacy policy: https://policies.google.com/privacy · Terms: https://policies.google.com/terms
  • WPVulnerability (www.wpvulnerability.net): off unless you turn it on in Site Health. Each audit, and Pro’s re-check after an update, sends the WordPress version and plugin/theme folder names, custom ones too (none with a non-wordpress.org Update URI). The service sees your server’s IP address and a Checknaut user agent. Cached 12 hours. Terms: https://www.wpvulnerability.com/license/ · Privacy: https://www.wpvulnerability.com/privacy/
  • Checknaut checkout (checknaut.com/buy/): only when you click Choose on Checknaut Upgrade to Pro, your browser opens our store’s checkout in a frame. What you enter there goes to our reseller, the merchant of record: https://checknaut.com/privacy-policy/
  • Hostinger API (developers.hostinger.com): only if you save a Hostinger API token (Settings Environment), the plugin asks Hostinger to purge its cache after a fix. Sends your domain and token. Terms: https://www.hostinger.com/legal/universal-terms-of-service-agreement · Privacy: https://www.hostinger.com/legal/privacy-policy

Sawir-shaashado

Rakibaad

  1. Upload and activate the plugin. Any theme.
  2. Open Checknaut. The first visit runs a full check. Every finding the plugin can repair gets a Fix button.
  3. If anything refuses, Tools Diagnostics Self-test checks the install itself.

Staging first, independent backups on. The plugin’s revisions, snapshots and undo are conveniences, not backups.

SBI

Is it really free?

Yes: every check on every page, the score, every one-click fix, Undo history and Pages. No page limit, no account, no trial. Checknaut Pro is a separate plugin.

Does it need an AI account?

No. Checks, fixes and the score run in wp-admin, and the plugin calls no AI service.

Does it change my live site?

Only when you click Fix. Every write keeps a copy and has an Undo; the read-only switch in Settings refuses every write.

How long can I undo a fix?

Up to 30 days. If you have edited the page since, Undo stops rather than overwrite your edit.

Does it add anything to my visitors’ pages?

Only what you switch on or a repair you apply needs: a skip link, a viewport fix, structured data, SEO meta tags when no SEO plugin is active and, on Divi, the CSS variables for your design tokens. No JavaScript unless you apply the skip-link fix or switch on the Motion framework.

What personal data does it keep?

The Site history records sign-ins, user, plugin and content changes, with the username and a shortened IP address. It stays in your own database, is deleted after the retention period you set, and is removed when you delete the plugin. Suggested text is added to Settings Privacy Policy Guide.

Which builders?

Checks: any. Fixes, and page building with Pro: Divi 5, Elementor and the block editor; other builders are refused for writes. Divi 4: audits and a rescue plan.

Dibu-eegisyo

18 Nofeembar, 2026
The ability to connect Checknaut to my LLM has been a real game changer for me. Working on our websites through ChatGPT, Claude, or another supported assistant makes so much possible through a conversation. I find that incredible, and it has dramatically improved my productivity. But what I keep coming back to is my time. My time! Checknaut saves me so much of it and allows me to focus on other tasks that need my attention. When you’re juggling client work, website projects, and everything else that comes with running an agency, you appreciate that pretty quickly. Managing WordPress websites means there is always something to check. A plugin updates, a layout shifts, a link breaks, or something needs attention after a content change. Multiply that across several client websites, and the checking alone can take a considerable amount of time. Checknaut helps us identify issues, understand what needs attention, and work through fixes more efficiently. One of the things I appreciate most is that it can help fix many of the issues it finds. Being able to move from identifying a problem to addressing it makes a huge difference in how useful the plugin is day to day. Our experience with Divi 5 was a big part of what brought us here. We started building with it during the alpha stage, and let’s just say there were some frustrating moments! We needed a better way to catch problems and reduce the repetitive checking involved in website development. Those everyday challenges helped shape Checknaut into something we now use in our own work. It also continues to be useful after a website launches. WordPress websites keep changing as themes, plugins, and content are updated. Having a tool we can return to for ongoing checks helps us stay on top of maintenance and gives us better visibility into what needs attention across our client sites. Connecting it to my LLM adds another level of convenience. I can ask questions, investigate issues, and work through supported website tasks in a conversation. That has become one of my favorite parts of using Checknaut because it fits so naturally into how I already work. We still review changes and use our judgment, but Checknaut helps us get through the work more efficiently. Less time spent on repetitive checks means more time for clients, other projects, and the tasks that require our direct attention. That is the biggest benefit for me, and it’s why I’m so excited about this plugin. Full transparency: I work at SnowdriftCO, where we use Checknaut and helped with its development. I want to be completely clear about that relationship. But now that it’s developed and part of our regular workflow, I’m also someone who uses it and benefits from it firsthand. We helped build something we needed, and now I get to experience how much easier it makes my work. The productivity improvement, the LLM connection, and especially the time it saves me are why I’m so enthusiastic about it.
Akhri dhammaan 1 dibu-eegis

Ka-qaybgalayaasha & Horumariyayaasha

“Checknaut” waa softiweer il furan. Dadka soo socda ayaa wax ku biiriyay kaabahan.

Ka-qaybgalayaasha

Ku tarjun “Checknaut” luqaddaada.

Ma xiisaynaysaa horumarinta?

Baadh koodka, fiiri bakhaarka SVN, ama iska qor diiwaanka horumarinta adigoo adeegsanaya RSS.

Isbeddellada

2.3.1

  • New: restart CC’s walk-through from Settings or the dock (“Start over”). Home shows the welcome again. Your history and the “Read your score” tour stay done; other missions are re-checked from your site. Per user, per site. Translated into all eight languages.