Find what is wrong with your shop before your customers do. PHP errors and the module behind them, slow pages, database, disk, security and mail, each with a plain explanation and the steps to fix it.
Last Update: 05 Nov 2026
Version: 2.0.3
Compatibility: PrestaShop 1.7.8.0 or newer (tested on 1.7.8.11, 8.2.8 and 9.1.5), PHP 7.2 or newer, MySQL or MariaDB
A shop rarely breaks all at once. A module starts throwing warnings, pages get slower week by week, the statistics tables fill up with old visits, debug mode stays on after a test, a backup archive lies in the web root where anyone can download it, and order e-mails quietly land in spam. Site Health Doctor watches all of this on your own server and tells you, in plain words, what is wrong, why it matters and how to fix it.
What it checks
PHP errors. Reads the PrestaShop logs (var/logs, the exception log and the log table) and the PHP error log, catches errors on the pages itself, groups the same error and tells which module or theme it comes from. A sudden spike of errors or a new fatal error becomes a problem on the Issues screen and an e-mail.
Server time. Measures 1 request in 10: time and memory, separately for shop pages, back office pages, AJAX, the API and the cron. Shows the slowest addresses and warns when the shop became slower than its own normal.
Database. Table sizes and growth, MyISAM tables, unused space, character sets, the statistics tables of PrestaShop that grew for nothing (connections, search statistics, the log), and the version of the database server.
Files and disk. Free disk space, the largest files, archives and database dumps in the web root, PHP files in the image folders, server tools left on the site, the install folder, and code overrides that can break after an update.
Security. Debug mode on a live shop, modules that are installed but disabled, modules that wait for the Upgrade button, files such as .env open to anyone, attacks and probes seen in the server access logs, password guessing on the back office login (PrestaShop 9), HTTPS, HSTS and the SSL certificate expiry.
E-mail. SPF, DKIM, DMARC and MX records of your domain, whether PrestaShop sends mail through the PHP mail function or SMTP, whether mail is switched off, and a test message to check that mail from the shop arrives.
Server and PrestaShop. PHP version and its end of support, memory limit, OPcache, missing PHP extensions, a shop left in maintenance mode, template compilation settings, a log folder that cannot be written, and whether the background checks run on time.
What you get
A health score from five areas: errors, performance, security, database and files, server and configuration. An area without data says "not measured" instead of pretending to be fine.
Every problem with the fix. What was found, why it matters and the steps to fix it, with the place in the PrestaShop back office. Hide an item for 30 days if you decided to live with it.
Alerts by e-mail for critical problems, without the same alert again and again, and a message when the problem is gone.
A weekly e-mail with the score, new and fixed problems, errors and server time.
A printable report of the last 7 days: print it or save it as PDF from your browser.
Its own item in the left menu of the back office, under Configure.
Light on your server, private by design
A customer request never waits for the module: no database query and no outside request runs during a visit. Only 1 request in 10 writes one line to a file.
The analysis runs in the background in short portions: after the back office pages are opened, and on time from a cron job if you turn on the cron address of the module in Settings and call it every 5 minutes.
Everything is collected and stored on your own server. No account and no connection to SiteGuarding are needed; the module only asks siteguarding.com, from the back office pages, whether a new version is out.
Visitor addresses are shortened before they are stored, page addresses are kept without the query string, and full log lines are never kept.
Screenshots
Fix it yourself, or let us do it
Every problem comes with the steps to fix it. If you would rather not do it yourself, the button next to the problem sends it to our engineers:
Fix it for me. Our engineer checks the problem and tells you the price before any work starts. Price after review.
Emergency help. The shop is down or shows fatal errors: we bring it back online and find the cause. Price after review.
Site health audit. Our engineer reviews the whole shop and sends you a report with the causes and a fix plan. Price after review.
No. Customer requests do not query the database or call anything outside. Only 1 request in 10 writes one line to a file, and all analysis runs in the background.
Does it change anything in my shop?
Only when you ask. The module checks and reports. The one-click clean-ups of Pro run only when you press the button, show what they will change first and keep a copy for 7 days.
Where does it keep its data?
In its own database tables and in the folder var/sgshd inside your shop. Nothing about your shop is sent to SiteGuarding.
Do I need an account?
No. The free module works without an account and without a licence key.
Which PrestaShop versions are supported?
PrestaShop 1.7.8.0 or newer, tested on 1.7.8.11, 8.2.8 and 9.1.5. One file works for all of them.
Does it work with several shops in one installation?
The module is for the whole installation and treats it as one site: it checks the installation once, with one set of settings and one history.
How do the background checks run?
After the pages of the back office are opened, and on time when your hosting calls the cron address of the module from a cron job (off by default, with its own key, shown in Settings). Settings shows when they ran last.
The Traffic screen says that no access log was found.
Server access logs are not readable for PHP on every hosting. On cPanel, turn on "Archive logs" in Raw Access, or enter the path of the log file in Settings. Everything else works without access logs.
What happens when I remove the module?
Uninstalling removes the module and its hook. The data stays unless you ticked "Delete all data when Site Health Doctor is uninstalled" in Settings.
Requirements
PrestaShop 1.7.8.0 or newer (tested on 1.7.8.11, 8.2.8 and 9.1.5) with PHP 7.2 or newer. MySQL or MariaDB.
Download
Free, no account needed. The folder inside the file is named siteguardinghealthdoctor: PrestaShop takes the module name from it, so upload the file as it is.
1. In the back office, open Modules > Module Manager, click Upload a module and drop prestashop-site-health-doctor.zip.
2. When the upload finishes the module is installed. Open Site Health Doctor in the left menu under Configure. The first checks start at once; some numbers appear after a day of data.
Pro: install the Pro add-on the same way, next to the free module, and enter your licence key in Site Health Doctor > Licence.
Updates
PrestaShop does not update modules from outside by itself: the screens of the module show a notice when a new version is out, with a download link and the steps. Upload the new file in Modules > Module Manager > Upload a module and, if the Module Manager offers it, press Upgrade next to Site Health Doctor. Settings, history and findings stay.
Changelog
2.0.3 First version for PrestaShop 1.7.8, 8 and 9, on one core with the WordPress, Joomla and OpenCart editions: checks with explanations and the steps to fix them, a health score by area, PHP errors from the PrestaShop logs grouped by module, sampled server time and slow addresses, database and disk, archives in the web root, bots and attacks from the access logs, SPF, DKIM, DMARC and MX records, PrestaShop settings (debug mode, mail method, template compilation, maintenance mode, modules waiting for the Upgrade button), alerts, weekly e-mail, printable report and a cron address.
Our website uses cookies, which help us to improve our site and enables us to deliver the best possible service and customer experience. See our policyAccept
