Description
Jralo monitors your website on three fronts: accessibility, website QA and security. This plugin brings those results into WordPress and WooCommerce, with separate timestamps so you can see when each check last ran.
- Accessibility: WCAG 2.2 level A and AA checks using axe-core, with findings by severity.
- Website QA: broken links, broken images, page errors, failed files and slow pages.
- Security: the latest security audit score and grade, severity counts and findings. Checks cover security headers, cookies, exposed files and known vulnerabilities in libraries whose versions your site reveals. Paid plans include the evidence and fix steps; deeper checks require verified ownership and are managed in the Jralo dashboard.
The plugin is a connector to Jralo, not a firewall, malware remover or guarantee that your site is secure. Security audits and accessibility/QA checks are separate runs, not a claim of continuous attack prevention.
This plugin connects your WordPress site or WooCommerce store to your Jralo account. It works on any WordPress site and adds store-specific help when WooCommerce is active.
What you get in WordPress
- Your last check, on a Jralo page in wp-admin: when it ran, how many pages it opened, the number of accessibility problems by severity (critical, serious, moderate, minor), the biggest problems, and the website QA results.
- Traffic and attack monitoring: while connected, the plugin counts failed logins, suspicious probes, missing pages and AI-agent visits. On paid plans, hourly counts go to Jralo for attack alerts. This reports activity; it does not block requests.
- Security audit: see the latest audit date, score, grade, severity counts and findings in wp-admin. Free accounts see finding titles; paid accounts also see evidence and fix steps. Run a visitor-level security audit with its own button.
- Check now: start an accessibility and website QA check from WordPress, within your Jralo plan’s daily limit. Security audits have their own button and timestamp.
- Website Mechanic: Jralo’s AI agent fixes what the check found in your theme’s code and gives you a fixed copy of your theme as a file. You upload it under Appearance, Themes, preview it, and switch to it yourself. The plugin never changes your site’s files and never installs or activates a theme. Your first fix is free.
- One button to the full report and dashboard on jralo.com, where every problem is listed with how to fix it.
- The Monitored by Jralo badge, as a footer setting, a block and a shortcode, in four styles. The badge is off until you turn it on.
- For WooCommerce stores: a plain list of what a check covers on a store and what it does not, with links to your own shop, cart and checkout pages.
What accessibility and QA checks cover, and what they do not
A check opens your homepage and up to 5 pages linked from it, the way a visitor who is not signed in sees them. On most stores these are the shop page, category pages and product pages.
A check never signs in, never adds anything to a cart and never places an order. It does not open cart, checkout, account or sign-in pages: links to them are skipped on purpose. Test those by hand.
Automated testing finds many accessibility problems, not all of them. A check result is not a statement that a site meets any law or standard, and this plugin does not make a site meet one. It does not change how your site looks or works for visitors: there is no overlay and no widget.
You need a Jralo account
The plugin is free. With a free Jralo account you can connect your site, see your last check, run Check now, and place the badge block, shortcode or footer setting. Jralo’s paid plans are bought on jralo.com, not in this plugin. They add automatic daily accessibility, QA and security checks, security evidence and fix steps, and the live badge. Free accounts receive monthly security audits; paid plans also offer weekly reports and reports after a release, configured in the dashboard. The badge and public record have separate switches: you can show the badge while keeping your name, issues and directory record private, as “The badge” below explains.
The badge
The badge is an image served live by jralo.com. It shows the date of your site’s last check. Turn on the badge in your Jralo dashboard (a paid-plan feature); your public record and directory listing can stay private. The badge links to your public record only when you publish it; otherwise it links to Jralo. If the plan ends or checks stop, it says “Monitoring paused” with the date of the last check. Turn the badge off to stop showing it. Nothing appears in your footer unless you turn the footer setting on.
Shortcode: [jralo_badge], or with a style: [jralo_badge style="light"]. Styles: dark, light, color, compact.
External services
This plugin connects to Jralo (https://jralo.com/), the service that runs the checks. It is needed for everything the plugin does. Jralo is run by Misimi Corp, the plugin’s author.
Nothing is sent to Jralo until you paste a connection token and press Connect. Installing and activating the plugin makes no outside requests.
After you connect, the plugin makes these requests from your server to https://jralo.com/api/v1/:
- Reading your site’s check (
GET /api/v1/site): when you connect, when you open the Jralo page in wp-admin (at most once every 5 minutes), when you press Refresh, and twice a day in the background so the plugin knows whether your badge is still on. - Starting an accessibility and QA check (
POST /api/v1/site/check): only when you press Check now. - Starting a security audit (
POST /api/v1/site/security): only when you press Run security audit. It checks the connected site, never a URL supplied by a visitor, and does not run the deeper owner-verified audit. Latest security results are included when readingGET /api/v1/site. - Security activity (
POST /api/v1/site/traffic): hourly while connected on a paid plan, sends hourly counts of failed logins, probes, missing pages and AI-agent visits, plus up to ten addresses responsible for the most failed logins or probes. No page content, form fields, passwords, customer or order data is sent. - Removing the connection (
DELETE /api/v1/site/connection): only when you press Disconnect. - Website Mechanic (
/api/v1/site/fix): reading where your fixes stand when you open the Jralo page; sending your theme’s code only when you press “Send my theme’s code to Jralo and fix it”; and fetching the changed files only when you press “Download the fixed theme”.
What is sent with each request: your connection token, and the plugin’s name and version as the user agent. As with any web request, Jralo also sees your server’s IP address. Apart from the security activity counts and suspicious addresses described above, the plugin sends no page content, customer, order or product data. Website Mechanic is another exception, and only when you press its button: it sends the code of your active theme (its PHP, CSS, JavaScript, block template and JSON files, and for a child theme the parent theme’s code too), with the theme’s name and version. It sends no images, no database content and no settings. Jralo passes that code to the AI service that runs its fix agent (Website Mechanic is built on third-party AI models) and deletes it there when the run ends. Jralo keeps the files the fix changed for 30 days so you can download the fixed theme, then deletes them.
Website Mechanic never installs code on your site. The plugin fetches the changed files, checks each PHP file on your server (it must parse, and must not add calls that run commands, write files, load code or talk to the network), and builds a .zip of a copy of your theme for you to download. Installing it is your choice, through WordPress’s own Appearance, Themes, Add New Theme, Upload Theme screen.
What comes back: the web address of the site connected in your Jralo account, your plan’s name, when the last checks ran, their counts, and your security audit findings (with evidence and fix steps on paid plans). The plugin stores this in your WordPress database to show it to you.
Checks are made by Jralo’s servers, not by this plugin. When a check runs (because you pressed Check now, or daily on a paid plan), Jralo’s browser opens your site’s public pages over the internet, like any visitor.
The badge, if you choose to show it, is an image loaded from https://jralo.com/badge/ by your visitors’ browsers, and links to your public record only when you publish that record; otherwise it links to https://jralo.com/. When a visitor opens a page that shows the badge, their browser asks jralo.com for the image, which tells Jralo the visitor’s IP address and browser type, as with any image hosted on another site. The badge sets no cookies and runs no script. The plugin adds a suggested paragraph about this to Settings > Privacy > Policy Guide.
The plugin contains no advertising analytics. Its security activity monitoring is described above.
- Jralo Terms of Service: https://jralo.com/terms/
- Jralo Privacy Policy: https://jralo.com/privacy/
- Badge Terms: https://jralo.com/badge-terms/
Installation
- Install the plugin from Plugins > Add New, or upload the zip, and activate it.
- Open the new Jralo page in your WordPress admin menu.
- In your Jralo dashboard (a free account is enough), add your site. Under the site, open “Connect a WordPress or WooCommerce site” and press “Create a connection token”.
- Paste the token into the Jralo page in WordPress and press Connect.
- Press Check now to run your first check.
- Optional: to show the badge, turn on the footer setting, or add the “Monitored by Jralo badge” block or the
[jralo_badge]shortcode where you want it.
FAQ
Does this plugin make my site accessible, or meet a law?
No. It shows you the problems an automated check found so you can fix them. It does not change your site for visitors, and no plugin or automated test can state that a site meets a law or standard. Automated testing finds many accessibility problems, not all.
Is it an accessibility overlay?
No. The plugin adds no toolbar, widget or script to your pages. The only thing it can add to your public site is the badge image, and only if you turn it on.
Do I need WooCommerce?
No. The plugin works on any WordPress site. When WooCommerce is active, the Jralo page also explains what a check covers on a store and links to your shop, cart and checkout pages.
Does it cost anything?
The plugin is free. A free Jralo account lets you check one site up to 3 times a day by pressing Check now. Paid plans, bought on jralo.com, add automatic daily checks, exports of your record and the public record with the badge.
Does a check place test orders or touch my cart?
No. A check only reads public pages. It never signs in, adds to a cart or places an order, and it skips links to cart, checkout, account and sign-in pages.
Why is my badge not showing?
Turn on the live badge in your Jralo dashboard on a paid plan. Your public record has its own switch and can stay private. A new site’s badge appears after its first successful check. Until then the plugin prints nothing. The Jralo page in WordPress shows your badge status.
Check now ended with a message that my site stopped waiting. What happened?
A check takes about a minute, and some hosts stop waiting for an answer sooner than that. The check may still finish at Jralo: press Refresh after a minute.
Where is my connection token kept?
In your WordPress database, in the options table. The Jralo page shows only its last four characters. The token can read your site’s check results and start a check; it cannot change your Jralo account or billing. Pressing Disconnect removes it from your site and from Jralo, and you can also remove it in your Jralo dashboard.
What is removed when I delete the plugin?
Everything it saved: the token, the saved check result, the badge settings and its scheduled refresh.
My site is on a local or private address. Will it work?
The plugin will connect, but Jralo can only check sites that are reachable on the public internet.
Changelog
1.3.3
- Adds security audit results and an explicit Run security audit button in wp-admin.
- Presents accessibility, website QA and security as separate monitoring fronts, with honest scope and plan limits.
1.3.2
- Keep the live badge while the public record stays private. Badge clicks lead to Jralo when the record is private, and to the record when public. Updated the badge settings and instructions.
1.3.1
- Website Mechanic safety: a fix can no longer change a file that exists on your site unless it proves which copy of the file it based the change on, and the PHP check now also compares include and require targets and counts calls made through a variable.
- Clearer wording on what a free Jralo account covers and what a paid plan adds.
1.3.0
- Traffic and attack monitoring for the Jralo security audit (paid Jralo plans). While connected, the plugin counts failed logins, requests probing for weak spots (such as wp-login.php floods, xmlrpc.php and .env), pages not found, and visits from AI agents, and sends those hourly counts to Jralo, which emails you when something looks like an attack. No page content, form data or customer data is sent.
1.2.1
- When Jralo’s checker is busy, Check now says the check is queued and will finish in a few minutes, instead of showing an error. Press Refresh to see the result.
1.2.0
- The check result shows which accessibility laws are likely relevant to your site, from where your business is based and where your customers are, with a link to Jralo’s guide to each. This is not legal advice.
1.1.1
- The badge says “Monitoring paused”, with the date of the last check, when monitoring stops, instead of disappearing.
1.1.0
- Website Mechanic: send your theme’s code to Jralo’s AI fix agent and get back a fixed copy of your theme to upload, preview and switch to.
1.0.0
- First release: connect with a token, see your last check, Check now, the badge as a footer setting, block and shortcode, and WooCommerce help.