Automated Kinsta Site Audit Reports
Every Monday, WebRun signs in to MyKinsta, walks every site in the account, records the age of the last backup, the PHP version, the SSL certificate expiry, disk and bandwidth use against plan, and whether staging is in sync, writes the whole audit into a dated Notion page with red items first, and queues a Twilio SMS only when something is genuinely critical.
How do I audit all my hosted sites for backups, PHP version and SSL expiry?
WebRun audits every site in your MyKinsta account each Monday, recording backup age, PHP version, SSL expiry, and disk and bandwidth use against plan. It writes a dated audit page in Notion with problem sites at the top and queues a Twilio SMS for you to release only when a finding is genuinely critical.
- Every site is checked weekly against the same standard
- Expiring certificates and stale backups surface before they bite
- SMS is reserved for critical findings and still needs your release
Built for web agencies · WordPress developers · IT teams · managed hosting clients
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
my.kinsta.comin a real browser with your saved login - no setup, no API keys. -
1
Kinsta - audit every site
WebRun opens Kinsta to audit every site. - Sign in to MyKinsta and open the sites list
- For each site record the date of the most recent backup, the PHP version in use, the SSL certificate expiry date, and the primary domain
- Record disk space and bandwidth used against the plan allowance
- Note whether a staging environment exists and when it was last updated
- Mark as red any backup older than 24 hours, any PHP version no longer supported, any certificate expiring within 30 days, and any resource above 85 percent of plan
Done when Every site has a full row of audit values and a red or green mark.
-
2
Notion - write the audit page
WebRun opens Notion to write the audit page. - Create this week's audit page in your hosting Notion database, dated
- Put one table row per site with backup age, PHP version, SSL expiry, disk and bandwidth use
- Sort red items to the top and add a one-line summary of how many sites need attention
- Link the page to last week's so the trend on each site is easy to follow
Done when This week's audit page exists in Notion with red items first.
-
3
Twilio - queue an SMS on critical items
WebRun opens Twilio to queue an SMS on critical items. - Draft an SMS only for critical findings: a certificate expiring inside seven days, a backup older than three days, or a resource above 95 percent of plan
- Queue the message in Twilio for your approval instead of sending it
- Use only numbers on your saved internal on-call list. Clients are never texted
- Queue nothing at all in a clean week
Done when Critical findings have an SMS queued for your release, or the week was clean.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Can it change my hosting settings?
No. WebRun reads MyKinsta and writes the findings to Notion. It never restores a backup, changes a PHP version, renews a certificate, clears a cache, or deploys anything. Every fix stays a human action.
Will it text me every week?
Only for critical findings, and even then the SMS is queued in Twilio for you to release. A clean week produces a Notion page and nothing else.
Does it work across many sites in one account?
Yes. Every site in the account gets its own row in the weekly table, and red items are sorted to the top so a 40 site account still reads in under a minute.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.