SiteProof checks the basics of your WordPress website and tells you, in plain language, what needs attention, what to do first and what is already in good shape.<\/p>\n\n
Every check is saved. You can see what changed since the previous check, and save a report as PDF to show your team, developer or client what was checked and when.<\/p>\n\n
SiteProof is not a firewall, malware scanner or backup tool, and it does not change your website. It works alongside the security, backup and hosting tools you already use, and tells you whether the basics are in order.<\/p>\n\n
A result of \"Good\" means no issue was detected by that check. It is not a guarantee that your website cannot be compromised.<\/p>\n\n
SiteProof stores its check results in your WordPress database and works without an account. It does not send your website's data to SiteProof or to other services. The only requests it makes are the WordPress.org checks described under External requests.<\/p>\n\n
To show administrator accounts that are no longer used, SiteProof stores the date and time of each administrator's most recent login. No other personal data is stored, and this information is not shared. Reports never include usernames. Deleting the plugin removes all SiteProof data. SiteProof adds a suggested text to Settings \u2192 Privacy that you can use in your privacy policy.<\/p>\n\n
SiteProof uses the update information WordPress already collects. If that information is missing, for example right after you update a plugin, SiteProof asks WordPress to refresh it. WordPress then makes its standard update check to WordPress.org, the same request it makes automatically twice a day. To check whether your PHP version still receives security updates, SiteProof uses the same WordPress.org check as the WordPress dashboard and Site Health, at most once a week. SiteProof does not add any data to these requests. See the WordPress.org privacy policy<\/a>.<\/p>\n\n\n SiteProof does not block attacks or scan for malware, so yes: keep your security plugin, backups and hosting protection. SiteProof gives you an overview of whether the basics are in order and helps you show that they are checked regularly.<\/p><\/dd>\n Site Health shows a broad technical overview of your website right now, including performance and server settings. SiteProof focuses on security and maintenance, puts the most important actions first, adds checks Site Health does not do (such as inactive administrator accounts and whether a backup plugin is active), and keeps a history of every check so you can show what was checked and when.<\/p><\/dd>\n Once a week, automatically, and whenever you click \"Check now\". The weekly check uses WordPress's built-in scheduler, which runs when your website has visitors, so on a very quiet website it can run a little later.<\/p><\/dd>\n Only administrators. On a multisite network, only network administrators.<\/p><\/dd>\n WordPress does not keep a login history, so SiteProof records administrator logins itself. For an administrator account without a recent login, SiteProof needs 90 days of records before it can say whether the account is still used. The check explains when the result will be available.<\/p><\/dd>\n Click \"Save report as PDF\" on the SiteProof overview, or on any check in History. Your browser's print window opens, where you choose \"Save as PDF\".<\/p><\/dd>\n Yes, per site. Each site in the network gets its own checks and history. Because only network administrators can install updates on a multisite network, SiteProof is only visible to network administrators. There is no combined overview of all sites in the network.<\/p><\/dd>\n Yes. These filters are available:<\/p>\n\n Changes made with these filters are listed in every report, so readers can see when a report does not use SiteProof's standard checks.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
Is SiteProof a security plugin? Do I still need one?<\/h3><\/dt>\n
How is SiteProof different from Site Health?<\/h3><\/dt>\n
How often does SiteProof check my website?<\/h3><\/dt>\n
Who can see SiteProof?<\/h3><\/dt>\n
Why does a check say \"not checked yet\"?<\/h3><\/dt>\n
How do I create a report?<\/h3><\/dt>\n
Does SiteProof work on WordPress Multisite?<\/h3><\/dt>\n
Can developers change the checks?<\/h3><\/dt>\n
\n
siteproof_checks<\/code> to add or remove checks<\/li>\nsiteproof_max_administrators<\/code> (default 3)<\/li>\nsiteproof_inactive_admin_days<\/code> (default 90)<\/li>\nsiteproof_security_plugins<\/code> and siteproof_backup_plugins<\/code> to recognise more plugins<\/li>\nsiteproof_snapshot_retention<\/code> (default 52 saved checks)<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n