For WordPress Care Plans & Maintenance Resellers
Sell the maintenance plan with the evidence already attached.
A care plan is an easy yes when the owner can see what goes wrong without one. SiteAssay finds the sites running an outdated CMS, a JavaScript library with published vulnerabilities, or a certificate or domain about to expire. Then it keeps re-auditing them, and tells you the day something changes.
- 48
- Specialised checks run on every site, each against a published standard
- 2
- Monitoring schedules, weekly or monthly, for the sites you look after
- 18
- Report sections an owner can read without a developer beside them
- 7
- Days of free trial, with no card, to try it on your own clients
The findings a care plan exists to prevent
Each one is dated, checkable and cheap to fix on a plan, and expensive to fix after it bites.
An outdated CMS or stack
WordPress core behind the current release, read from what the homepage already exposes, plus the rest of the technology the site is built on.
Libraries with known vulnerabilities
jQuery, Bootstrap, React, Vue, Lodash and Moment versions matched against the public OSV vulnerability database, with the advisories counted.
A certificate or domain about to lapse
Days until the TLS certificate expires and days until the domain registration does. A lapse on either takes the site, and usually the email, with it.
Monitoring
The care plan that reports on itself.
Put a client's site on a weekly or monthly re-audit. When a serious problem appears, the health score moves, or enough changes at once that the site was clearly redeployed, you get an email that says what changed and links to the report. Everything below that bar is stored rather than sent, so the history is there when a client asks when something started.
How audits and scores work- Alerts on change, not on schedule
- An email only when something material moved, never a weekly report nobody opens.
- Before and after, in one report
- Re-run the audit after the work and show the owner the findings that cleared.
- Your name on it
- White-label reports on Pro and above, so the evidence arrives from your studio.
What a maintenance audit covers
The parts of a site that decay when nobody is watching them.
Broken links
Links on the site that lead nowhere, counted, so the clean-up has a number on it.
Security headers and TLS
HSTS, Content-Security-Policy, the redirect to HTTPS, mixed content and the certificate itself.
Exposed files
A public .git folder, an .env file, debug pages and backups left in the web root.
Speed over time
Core Web Vitals on every re-audit, so a plugin that slowed the site down shows up as a change.
Questions from maintenance and hosting resellers
Does SiteAssay log in to WordPress or scan plugins?
No. It reads what any visitor can see: the generator tag, asset paths, the public REST link and the readme. It does not try to log in, list users or guess plugin paths, so it is safe to run on a site you do not yet look after.
Does it replace an uptime monitor?
No. An uptime monitor checks every minute that the site answers. SiteAssay re-audits on a weekly or monthly schedule and tells you when the site got worse in a way an owner would care about. Most care plans want both.
Can I use it on sites I already maintain?
Yes, and it is the best place to start. Audit every client on day one so you own the before picture, then let the re-audits show what the plan has caught since.
Make your next care plan an easy yes
Audit any site free, or start a 7-day free trial with no card and put your own clients on a schedule.