We recently released version 1.3.1 of our WordPress plugin. It improves how Scanfully identifies your site, especially in more complex hosting setups.
Version 1.3.0 added direct links to the WordPress edit screen from our Broken Links Monitoring and Broken Media monitoring reports. Click a post in a report to open its edit screen.
You’ll need to be logged into WordPress, but if you’re not, you’ll see the standard WordPress login screen.
Version 1.3.1 is a refinement on top of that.
More reliable site URL detection
Scanfully now uses home_url() instead of get_site_url() when determining your site’s public URL.
get_site_url() reflects the WordPress installation URL, not always the URL visitors actually use. On many sites, especially those with a separate core directory, custom setups, or reverse proxy configurations, those two URLs are not the same.
By switching to home_url(), Scanfully aligns its monitoring with the real, visitor-facing URL. As a result, uptime checks, SSL validation, and other external scans now target the correct address more consistently.
Proxies and load balancers
SSL detection has also been improved for sites running behind reverse proxies, CDNs, or load balancers.
In these setups, WordPress often sees incoming traffic as non-HTTPS, even though visitors connect securely. This can cause tools to misreport SSL status or flag false issues.
Scanfully now handles these environments better by detecting SSL correctly, even when HTTPS is terminated upstream. This reduces false SSL warnings and gives you a more accurate picture of your certificate status.
Housekeeping
This release also includes internal meta changes and updates. These do not affect plugin behavior directly, but they help keep Scanfully aligned with current WordPress standards and plugin metadata requirements.
If your WordPress site is running Scanfully behind a proxy, CDN, or load balancer, you should see better Site Health information now.
Time to update that plugin!
Leave a Reply