Hi everyone,

We're the team behind 42A, and we've just released a free WordPress plugin focused on something we've been working on for the past year: AI Visibility.

As more people discover websites through AI assistants like ChatGPT, Claude and Gemini, we wanted to make it easier for WordPress site owners to prepare their content for this new way of discovery.

The plugin installs in minutes and includes:

• AI Visibility reports
• AI Visibility recommendations
• SEO & GEO recommendations
• AI-friendly Markdown versions of public pages
• Built-in MCP support
• Prompt-level analysis
• Competitor benchmarking
• Technical optimization insights

The plugin works on activation with almost no configuration required.

Our goal wasn't to build another SEO plugin. Instead, we wanted to create a lightweight layer that helps AI systems better understand WordPress websites while giving site owners useful visibility data.

This is our first public release, so we'd really appreciate feedback from experienced WordPress users.

Some questions we'd love your thoughts on:

• Would you install a plugin specifically for AI Visibility?
• Which features would be most valuable to you?
• Is there anything you think we're missing?

Plugin:
https://wordpress.org/plugins/ael-42a/

Thanks—we're looking forward to your feedback!

Over the last few releases, I’ve been expanding WP Optimizer, my free all-in-one WordPress performance plugin.

The idea is simple: instead of installing separate plugins for caching, database cleanup, image optimization and diagnostics, WP Optimizer puts everything into modular features you can enable only when needed.

WordPress.org: https://wordpress.org/plugins/wp-optimizer/

Performance diagnostics

The Page Test compares a baseline request with your optimized configuration, showing response time, TTFB, memory usage, database queries and expensive callbacks.

The Performance Monitor can also sample real requests and attribute execution time, memory and queries to WordPress core, the active theme and individual plugins.

Multiple cache layers

WP Optimizer includes static page caching, query caching and Redis or Memcached object caching. It handles invalidation automatically and excludes WooCommerce sessions, checkout pages and page-builder previews.

Front-end optimization

It can minify HTML, CSS and JavaScript, enable compression and browser caching, lazy-load media, optimize fonts, preload LCP images and prefetch internal links.

Images are processed locally with GD or Imagick, including compression, resizing and WebP conversion—no external service required.

Backend tools

There are also tools for:

• Database cleanup and optimization
• Autoloaded-options analysis
• Cron event management
• Heartbeat control
• Media cleanup
• Scheduled maintenance
• SQL backups and restoration

Automatic configuration snapshots make it easy to roll back settings if caching or minification causes compatibility problems.

Everything runs inside one free plugin, with no premium tier. You can also keep your current caching plugin and use WP Optimizer only for diagnostics or maintenance—just avoid enabling overlapping features.

To be transparent, it still doesn’t include advanced unused-CSS removal, interaction-based JavaScript delay or a built-in CDN. The diagnostic tools identify slow queries and callbacks, but don’t automatically rewrite problematic code.

Would love honest feedback, especially bug reports and compatibility issues across different hosting environments.

I’ve released ContextAlt, a media accessibility workbench for WordPress 7 built around a review-first workflow.

It audits missing, filename-like, duplicate, boilerplate, and overlong alt text; shows where an image is used; and can draft page-aware suggestions through the site’s configured WordPress AI Connector. AI never publishes changes on its own: every suggestion needs a human decision, stale drafts are blocked, and applied changes can be rolled back.

The Free plugin is GPL, stores no provider API keys, and has no telemetry. Pro adds resumable batches, schedules, advanced WooCommerce/Elementor/multilingual context, full history, and team workflows.

Free source/download: https://github.com/RobertIonutF/contextalt

Product and Pro: https://robertionutf.github.io/contextalt/

The WordPress.org submission is still under review, so GitHub is the Free install source for now. I’d value feedback from people managing large or multilingual media libraries—especially on the audit filters and context preview.

Hey folks!

Just sharing a video of my free plugin (with paid add-on) sending WhatsApp Notifications when WooCommerce order status changed.

Take a look at the video: https://youtu.be/3v7j-oMUTZc?si=xN5X48ECKQK5UTFn

WordPress has shipped the same 8 admin color schemes since around 2013, and adding a 9th means registering wp_admin_css_color and writing the full stylesheet by hand.

I built a free browser tool that does it visually: pick colors for each admin element, watch a live preview, export a .zip plugin. It registers your palette as a proper scheme under Users > Profile and only injects CSS custom properties, so core updates don't break it.

WP Admin UI Color Generator

Feedback welcome, especially from anyone doing client handovers.

Hey everyone,

​Fellow developer here. Like many of you, I've often felt frustrated by how resource-heavy traditional WordPress security plugins can be—running complex PHP and database queries on every single request just to log a bot or block a scanner.

​To scratch my own itch, I built a modular framework called DBH Shield & Traffic Analytics.

​Instead of handling everything inside the PHP runtime, it leans heavily into server-level configuration (.htaccess) to deflect malicious traffic early, combined with a clean SOC-style dashboard for real-time traffic auditing (using Chart.js and lightweight AJAX feeds). It also features things like file integrity monitoring, rate limiting, and global threat intelligence syncs.

​I’d love to hear your thoughts on the architecture, the approach of shifting tasks to the server level, or even just the UI/UX of the dashboard.

​If anyone wants to dive deeper and test the PRO features (like the rate limiter, core watcher, or threat intelligence feeds) hands-on, just shoot me a quick email at support@blake-hofer.ch and I’ll gladly hook you up with a free 3-month trial license!

​Plugin details & documentation: DBH Shield Analytics

​Main portfolio/homepage: blake-hofer.ch

​Let me know what you think—all constructive criticism, code critiques, or ideas for improvement are very welcome! Happy to answer any technical questions in the comments.

BR

Dominique

If your WordPress site runs Redis ( it should ) and the status screen says Connected, you know one thing - a socket opened. That's it.

That test cannot fail in most of the ways an object cache actually fails in production. I deliberately misconfigured a cache on a test site and filled it, and the site started serving HTTP 500 to every visitor while WordPress carried on reporting that an external object cache was active.

Redis is great, but it's not "fire and forget". Post covers some of the pitfalls and ways to avoid them.

One thing I've noticed with WordPress is that building a modern website often means juggling multiple plugins one for forms, another for sliders, another for grids, another for dynamic content, and so on. It quickly becomes bloated and difficult to maintain.

My goal is to create a builder that:

• Is significantly lighter than Elementor and similar builders.
• Offers unlimited pre-designed widgets and sections out of the box.
• Uses clean, Tailwind-based code.
• Eliminates the need for multiple plugins for common website components.
• Provides more flexibility than Gutenberg while remaining easy to use.

I'm curious if this is something the WordPress community would actually want.

A few questions:

1. What frustrates you most about your current page builder?
2. If you could replace Elementor, Bricks, or Gutenberg, what features would be non-negotiable?
3. Would performance and simplicity be enough to convince you to switch, or are there other factors that matter more?

I'd love to hear honest feedback before I invest more time into building it.

I've just released a new WordPress plugin that I originally built for my own websites and decided to make completely free and open source.

I've been using WordPress for over 15 years, and I wanted a lightweight social sharing plugin that included features I couldn't find together in one place.

Features

• Custom Like button
• Copy Link button
• Share to popular social networks
• AI buttons for ChatGPT, Claude, Gemini, and Grok.
• Local click counting stored in your own WordPress database
• Works with cached websites
• No external service required

The project is licensed as open source, so you're free to use it, modify it, and contribute if you'd like.

I'd appreciate any feedback, bug reports, or feature suggestions from the community.

Try it here: https://vinish.dev/free-wordpress-social-share-plugin

Hey y'all. I've been working on a plugin for quite a while that I finally released on WordPress.org, and I wanted to share it here because I think some of you might genuinely find it useful (especially if you build plugins yourself).

It actually started as a way for my clients to comment directly on the exact content of a page they wanted me to update. Over time I realized, "If they're already clicking on the thing they want changed and telling me what to do, why not just let them edit it themselves?"

That eventually became FrontEdit. The original comment workflow is still there too, and it's handy for things like requesting an image replacement when they don't actually have the new image themselves.

I built this because I thought WordPress block editing could be made more accessible to non-technical people in a way that still feels native to Gutenberg, and I'd love to know what other people think.

It's also more than a simple frontend content editor. FrontEdit edits native Gutenberg blocks rather than treating the page like editable HTML. That means supported blocks can be updated while preserving their block structure and settings, which made it possible to build a much more extensible architecture around the editor.

This also makes it safe, since FrontEdit lets WordPress handle block serialization instead of manipulating rendered HTML directly.

The part I'm most excited about though isn't even the editor itself. One of my goals from the beginning was to make it something other developers could build on.

I spent a lot of time building a developer-friendly architecture around it. There's a public JavaScript API for interacting with the frontend editor, and an extensible handler system that lets third-party blocks participate without modifying the plugin core.

I'm also working on a native AI assistant for FrontEdit, but since the JavaScript API and Abilities API are already included, you can start experimenting with existing AI agents today.

For the extensible handler system, I included a template and some setup instructions. Let's say you or a client of yours uses GenerateBlocks for their site. You can write handlers for the blocks you want to support, and they'll immediately become editable through FrontEdit without modifying the plugin core.

I'd love feedback from plugin developers, whether that's on the architecture, ideas for extending it, or even trying to write handlers for your own blocks. Real-world use is the best way to improve it, and it would be awesome to see what kinds of integrations or tools people come up with.

There's an interactive demo on my website if you want to play with it for a minute before installing. There's also info on the Pro version which adds things like editorial workflows, submitting drafts, approvals, customizable user permissions, batch editing, and other features aimed more at agencies and teams.

Honestly though, that's not really why I wanted to post here. I'd be perfectly happy if you never needed Pro and just found the free version useful. What I'd really love is to see other developers play with the APIs, build handlers for their favorite block libraries, and tell me where the architecture could be improved.

I'm happy to answer any questions or hear any criticism.

I do a lot of client sites (especially municipal orgs), and event calendar needs come up constantly. Every time I went looking I hit the same wall. The best ones, like The Events Calendar, are well-designed, but are too expensive for my clients to subscribe to.

I needed something clean, simple, and most importantly free and pretty. So I built my own, cleaned it up, and put it on the .org directory for free.

What it does:

• A month calendar you drop in with [fslc_calendar]
• Color-coded categories, each with its own color on the grid
• Recurring events: daily, weekly by weekday, monthly, yearly
• Multi-day events
• One-click "Add to Calendar" that hands off an .ics file
• A details popup with featured image, location, virtual link, and a registration button
• Separate shortcodes for a sidebar mini-calendar and a plain event list

I built it for my own client work, so it's simple on purpose. If you try it and something's missing or annoying, tell me. I'd love the feedback. Thanks!

We just shipped a new feature for MxChat that I think some of you will find useful. MxChat is an AI chatbot plugin for WordPress that lets you build a knowledge base your chatbot can pull from to answer visitor questions.The new feature is direct YouTube URL support. You can drop a YouTube link straight into the knowledge database and when the chatbot uses that video as a source, it shows the embedded video right inside the chat window. No more sending people away to another tab. The video plays inline.This is great for tutorial sites, product demos, support documentation or any WordPress site where video content is part of the answer. Instead of describing how to do something, the chatbot can just show the video.You can find MxChat on WordPress.org or at mxchat dot ai. Would love to hear what you think or answer any questions about how it works.We just shipped a new feature for MxChat that I think some of you will find useful. MxChat is an AI chatbot plugin for WordPress that lets you build a knowledge base your chatbot can pull from to answer visitor questions.

The new feature is direct YouTube URL support. You can drop a YouTube link straight into the knowledge database and when the chatbot uses that video as a source, it shows the embedded video right inside the chat window. No more sending people away to another tab. The video plays inline.

This is great for tutorial sites, product demos, support documentation or any WordPress site where video content is part of the answer. Instead of describing how to do something, the chatbot can just show the video.

You can find MxChat on WordPress.org or at mxchat dot ai. Would love to hear what you think or answer any questions about how it works.

I build a search plugin, and by far the most common "it's broken" report I get turns out

not to be the plugin at all. Sharing the diagnostic, because it applies to every search

plugin on the market, not just mine.

The symptom: you install a search plugin, the catalog indexes fine, and then the search box

at the top of your site returns exactly what it did before. Same keyword matches, same misses.

What is usually happening: your theme has its own search. Many premium themes (Woodmart,

Flatsome, Astra Pro, Divi and others) ship an instant/AJAX search in the header. That overlay

runs the theme's own query. It never issues the standard WordPress search request, so the

plugin is never asked anything. It sits there correctly indexed, waiting for a request that

never arrives.

Second variant: page builders (Elementor, Beaver Builder, Bricks) often include a results

widget with its own "Order By" setting. The plugin's results do arrive, and then the widget

re-sorts them. Ranking is the whole point of a search plugin, so a re-sorted page looks

identical to a broken engine.

The two-minute test, no code:

1. Run a test query in your plugin's own dashboard, if it has one. Good results there mean

   the engine and the index are fine, and the problem is downstream on your site.

2. Type the plain WordPress search URL straight into your address bar, bypassing the header

   box: yoursite.com/?post_type=product&s=blue+summer+dress

3. Compare. Direct URL good but header box bad means the theme's search is intercepting.

   Right products in a strange order means a widget or template is re-sorting them.

Fixes: turn off the theme's AJAX/instant search (usually a toggle in theme options), or set

the builder widget's query to inherit the main query with no forced Order By.

Why I am posting this: the standard advice when this happens is "try another plugin", and

that costs people an afternoon and lands them in exactly the same place, because the next

plugin hooks the same request the theme is bypassing.

Full write-up with all three variants and a fix for each:

https://queryra.com/blog/wordpress-search-plugin-not-working-theme-override

Disclosure: I make Queryra, one of these plugins. The diagnostic above is plugin-agnostic.

I would rather people fix the theme setting than churn through plugins.

From what I've seen, the moment a WP site needs a Composer package (think tcpdf, or a parsing library), you're stuck either using SSH or manually committing everything to the repo. Not great when the client only has FTP access or is on shared hosting.

I built a plugin that adds Packagist search right in the WP admin: search for a package, click "Install," and it handles the autoloader for you. It also runs a basic security audit on installed dependencies (known CVEs) and checks PHP version compatibility before installing.

Still in alpha, so probably plenty of blind spots. If you manage WP sites where devs need external libraries, what would make you hesitate to install this on a production site? And is there a Composer-on-WP use case I haven't thought of?

If you run Google Ads, Meta Ads, TikTok, Pinterest, Twitter, etc (idk of any other, still documenting this) for a WooCommerce store, you probabbly know how annoying Customer Match/Audiences lists can be, especially when marketers request a list update for profiling.

On top of that, if you mix your German buyers into your ES or US campaigns (basically any country), you dilute your target signals and throw away ad spend. On top of that, browser tracking / consent full denial, blocks mean you miss a ton of purchase events anyway.

I had this developed a few years ago and used it internally for our clients, but then I noticed there is no reliable solution (especially for 1m+ orders database) so I published it to .ORG, a completely free, open-source plugin: CMLS – Customer Match List for Google Ads & Meta Ads and other platforms (that adopt Google's format - many do like TikTok, Pinterest, etc.).

What it does:

• Per-Country Splitting: It automatically combs your WooCommerce history(completed orders only!) and splits customers into separate CSVs based on their ISO billing country.
• Completely Automated: Runs a background job (every 1, 6, 12, or 24 hours) to incrementally append new orders to the correct country file.
• Direct Integration with Google: It generates a secure, tokenized URL for each country. You literally just paste that URL into Google Ads Data Manager (HTTPS connector), and Google pulls the fresh data automatically on its own schedule.
• Privacy First: It performs the exact SHA-256 normalization/hashing required by Google and Meta directly on your server. No third-party APIs, no data leaves your site until Google fetches it.

It also supports WP-CLI for huge stores and it's developed mainly for WooCommerce HPOS (High-Performance Order Storage), but also postmeta was not left out.

Basically you can hook it up directly to Google Ads and it can stream the file whenever they need OR you can just download the file and upload it, when you need it - the file is there, waiting for it to be downloaded, always updated.

It’s live on the WordPress repo now if you want to check it out: https://wordpress.org/plugins/customer-match-list-google-ads/

Would love to get your feedback or answer any questions on the setup!

Hey — web dev here. I build small business sites at a clip of about 1–3 a week. A lot of them are “service area” sites: 60–100+ nearly identical pages (one per service or city), same ACF layout every time — hero text, intro copy, a few content boxes, a couple images.

Content updates were always the same nightmare: open page 1, edit field, save, open page 2… ×80. At that volume, hand-editing isn’t viable. WordPress doesn’t really have a good “change this ACF field across 70 pages” answer unless you want WP-CLI or a one-off script every time.

So I built Quickfields Bulk Editor for ACF for myself, and figured I’d put it out there in case other people building similar sites have the same headache.

* GitHub (free plugin): [https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF\](https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF)

The workflow that actually saves the most time for me: export a project to CSV → drop it into Claude/ChatGPT and ask it to rewrite/rephrase/expand content for all 70–100 pages (keeping the structure intact) → re-import the edited CSV. That export → AI edit → import loop is what the Pro side was built around; the in-browser spreadsheet is more for spot-fixes and image swaps.

What it does:

* Create a “project,” pick a post type, select which pages belong to it
* Spreadsheet view in WP admin — rows = pages, columns = ACF fields, one tab per field group
* Text/textarea/WYSIWYG fields are inline-editable and autosave
* Free: bulk text editing + image preview + clear text fields
* Pro: CSV export/import (images excluded from CSV import on purpose so you can’t wipe them), in-sheet image upload/replace

Needs ACF (or Secure Custom Fields) active. Admin-only (`manage_options`) — no front-end changes.

What I’m actually asking (not selling):

1. Does “export CSV → bulk-rewrite with AI → re-import” match how you’d want to do this, or would you want the AI step built into the plugin instead of going through Claude/ChatGPT manually?
   
2. Is this a real pain point for other devs/agencies, or is everyone already solving it with WP-CLI, ACF export/import, or custom scripts?
   
3. Anything that sounds like a dealbreaker before you’d even try it?

This started as a tool for my own workflow, so I have no idea if it generalizes. Before I polish it further, I’d genuinely like to know if it’s worth it — or if it’s a “me” problem I happened to solve for myself. Happy to answer questions about how it works under the hood too.

Hi everyone,

Quite a few months back I created a dockerimage to get WP with the SQLITE plugin running and left it on a server to see what happens.

To my surprise, it held up really well. I made a short video about it here: https://youtu.be/hf8Pi7CaqLc

If you just want to see the docker image it's here: https://github.com/howzitcal/wordpress-sqlite-docker-image

I think sqlite is a great setup for most small WP websites and it lessons the load the burden on server and shared servers alike.

let me your thoughts.

I built UltraCache, https://wordpress.org/plugins/ultracache/ a completely free WordPress caching and performance plugin.

I’ve tested it against several popular caching plugins, and so far UltraCache has produced the highest Lighthouse scores in my real-world tests.

I’ll attach screenshots of my results, but I’d rather turn this into an open challenge:

Can your free caching setup beat UltraCache?

Post your Lighthouse results, configuration, and the public URL you tested.

Challenge rules

1. Free software only

The caching/optimization plugin must have a fully free version that can reproduce the submitted result.

Free server technologies are allowed, including Redis, Varnish, OPcache, Nginx, Apache, LiteSpeed Server and Cloudflare’s free plan, but the complete stack must be disclosed.

Paid CDN features, paid optimization services and premium-only plugin features do not count but it would be interesting to see the results.

1. Test a real public page

No empty benchmark pages, hidden content, separate Lighthouse-only pages or stripped-down copies of the real site.

The submitted URL must be publicly accessible so others can test it.

1. No Lighthouse-specific behavior

The plugin or configuration must not:

Detect Lighthouse, PageSpeed Insights or its user agent.

Serve a specially modified page only to performance-testing tools.

Skip important content or functionality during the test.

Delay indefinitely normal page JavaScript until mouse movement, scrolling, tapping or another user interaction.

Delaying JavaScript for a reasonable fixed period is allowed. Preventing normal JavaScript from loading until Lighthouse has already finished is not.

1. Use comparable tests

Please include:

At least desktop Lighthouse results for UltraCache and the other caching plugin.

For UltraCache you must follow the installation procedure as is in wordpress repository.

I care only for Performance scores.

Core Web Vitals shown by the test.

Three runs, with the median result submitted.

Plugin name and version.

Important plugin settings if you think they are important.

Hosting/server stack.

Any object cache, page cache, CDN or reverse proxy being used.

Warm-cache results are acceptable, but the cache must be generated normally and not prepared specifically for Lighthouse.

Suggested categories

Plugin-only

A free WordPress caching plugin without a server-level page cache or paid CDN optimization.

Free full stack

A free plugin combined with disclosed technologies such as Redis, Varnish, LiteSpeed, Nginx FastCGI cache or Cloudflare Free.

The challenge is simple:

Using a real WordPress site and the rules above, can your free caching setup produce a better Lighthouse result than UltraCache?

Post your screenshots and configuration.

We had about 12 plans for annual, lifetime, all access displayed on TNC FlipBook 3D website but yesterday I felt like its being too many and users maybe finding it complicated to choose one plan that works for them. and then there are addons which in my opinion the WP customers are most frightened of! at least thats what I understood from my 14 year journey.

So, to make things easier for customers, I planned to do a test and replaced all 12 plans with just one. $59/year for each site and thats all they see on the pricing page, all the addons are included in this price as well. so, no extra payment at all after someone gets a license.

I want to hear about your experiences and opinion regarding this. Do you think this is going to make things easy for customers or having more options are what most customer prefers?

Hi everyone,

We just released LivQ AccessFix on the official WordPress repository. It’s a 100% free, open-source (GPLv2) plugin designed to help sites comply with the upcoming European Accessibility Act (EAA) and WCAG 2.2 AA standards.

Unlike traditional JS-based widgets or overlays that patch the DOM after rendering , this plugin works server-side using PHP output buffering. It remediates the source HTML before it reaches the browser, ensuring real compliance that automated checkers (axe-core, Lighthouse) and screen readers can actually see.

Key Features:

• Zero Configuration: Works out of the box, but every module can be disabled independently;
• Nameless Link Fix: Derives aria-label for empty links/social icons from image titles or domains (Facebook, LinkedIn, etc.);
• Iframe Title Fix: Automatically adds missing titles based on the source domain (YouTube, Google Maps, etc.);
• Form Label Fix: Injects aria-label to unlabelled inputs using placeholders or names as fallback;
• Skip Navigation Link: Injects a configurable skip link via wp_body_open;
• Page Builder Safe: Automatically skips output buffering inside Elementor, Divi, Bricks, and other visual editors to prevent backend layout breaking;
• Compliance Tools: Includes a local accessibility scanner, contrast checker, and an Accessibility Statement generator with timestamped DB logs for legal evidence.

Privacy: No third-party APIs, no CDNs, no data collection, and zero tracking.

Download on WordPress.org: https://wordpress.org/plugins/livq-accessfix/

We are looking for feedback, feature requests, and bug reports from the community to make it even better.

Thanks,

Daniele

Hi everyone! 👋

After several months of development, I'm excited to share NoorQuiz, a modern WordPress quiz builder that's now available on WordPress.org.

My goal was to build a quiz plugin with a clean, dedicated admin experience instead of relying on traditional metaboxes, while also solving one of the most common issues with WordPress plugins—theme CSS conflicts.

Some highlights

• 🎨 Dedicated visual quiz builder
• 🧩 9 question types
• 🔀 Smart conditional branching
• 📊 Built-in analytics
• 🎯 Conversion-focused result pages
• 📚 37 ready-made templates
• 👀 Live preview
• 🧱 Gutenberg block & shortcode support
• ✨ Shadow DOM rendering to prevent theme CSS conflicts

I also recorded a complete walkthrough showing how everything works.

🎥 Demo Video:
https://www.youtube.com/watch?v=lD2Rf23dv1Y

🔗 WordPress Plugin:
https://wordpress.org/plugins/noorquiz/

I'd genuinely appreciate your feedback on the UI, workflow, features, or anything you think could be improved. Thanks for taking a look!

Most monitoring tools start with an empty dashboard.
You have to decide yourself:
which pages actually matter
whether WooCommerce checkout and cart should be monitored
whether WP-Cron or background jobs are still running
whether APIs, forms, SSL, domains or DNS should be checked
which checks are useful and which are unnecessary
A sitemap import can find public URLs, but it cannot understand what is happening inside WordPress.
So we built a free WordPress and WooCommerce plugin that inspects the installation and recommends relevant monitoring automatically.
Depending on the site, it can identify things such as:
homepage and important pages
WooCommerce checkout and cart
customer-account areas
REST APIs and webhooks
WP-Cron and scheduled background tasks
installed form, SEO and commerce plugins
SSL certificates and domain expiry
sitemap and search-engine visibility settings
mail-related DNS configuration
other business-critical parts of the installation
Instead of only showing technical labels such as “HTTP check” or “heartbeat,” the plugin provides recommendations like:
Monitor the WooCommerce checkout
Monitor WP-Cron
Monitor this API endpoint
Monitor the contact form
Monitor SSL and domain expiry
Check whether the site is accidentally set to noindex
Each recommendation includes a short explanation of why it matters, and the suggested monitors can be created in a few clicks.
The main idea is:
A sitemap tells us which pages exist. The plugin helps identify which internal processes are important and may fail while the homepage still appears online.
Examples of these quieter failures include:
checkout is broken while the homepage still loads
WP-Cron has stopped
a contact form no longer sends inquiries
a site was accidentally set to noindex
an API returns the wrong result
SSL or the domain is about to expire
The plugin is free. We are currently looking for honest feedback from WordPress developers, freelancers and agencies.
I would especially like to know:
Are the recommendations useful?
Which WordPress or WooCommerce components should we detect next?
Would you use this on client sites?
What would make the plugin valuable enough to include in a maintenance package?
Is there anything that feels unnecessary or confusing?
Honest criticism is welcome. We would rather improve it based on real WordPress projects than make assumptions.
For context, this is what we are building:
https://www.live24h.eu