Interactive checklist
Monthly WordPress care plan checklist
A full-width interactive checklist based on the monthly process WildPress uses for care plan clients. Filter by Maintenance, Performance, or Growth to see what each plan includes. Your progress is saved in this browser.
Checklist
25 checks
| Done | Care plan | Check | Guidance | Evidence to record |
|---|---|---|---|---|
| □ | Maintenance | Review open support requests and known site issues | Check outstanding client requests, recent issues, update notes, and anything that needs attention before routine maintenance starts. | Open support items reviewed |
| □ | Maintenance | Update WordPress core, plugins, and themes | Apply updates in a controlled way and check the important user journeys afterwards. | Updates completed and post-update checks passed |
| □ | Maintenance | Review plugin changelogs and compatibility | Look for security fixes, breaking changes, PHP compatibility issues, and abandoned plugins. | Plugin review notes |
| □ | Maintenance | Check the homepage and priority pages after updates | Browse the homepage, main navigation, primary service pages, and key landing pages to catch obvious visual or functional problems. | Priority page spot check completed |
| □ | Maintenance | Confirm daily full-site backups are running | Check backup freshness, file size, storage location, and failure alerts so there is a usable restore point if needed. | Latest full-site backup timestamp |
| □ | Maintenance | Confirm hourly database backups and off-site retention | Check database backup frequency and separate storage or retention where available, especially for sites with forms, orders, bookings, or publishing activity. | Database backup and retention check completed |
| □ | Maintenance | Review security alerts and malware scans | Investigate unexpected file changes, suspicious logins, vulnerable components, and firewall alerts. | Security dashboard reviewed |
| □ | Maintenance | Review vulnerable components and admin access | Check for known plugin or theme vulnerabilities, remove unnecessary admin access where appropriate, and confirm high-risk accounts remain protected. | Vulnerability and user access review completed |
| □ | Maintenance | Review uptime incidents and availability alerts | Check downtime alerts, recurring availability issues, and any host-level problems that may need follow-up. | Uptime log reviewed |
| □ | Maintenance | Review PHP, application, and server errors | Look for repeated PHP warnings, fatal errors, database errors, cron failures, and plugin conflicts before they become visible failures. | PHP and application logs reviewed |
| □ | Maintenance | Test forms, checkout, booking, or lead flows | Run real tests for the actions that generate enquiries, orders, bookings, subscriptions, or leads. | Test transaction or form submission |
| □ | Maintenance | Prepare monthly maintenance summary | Record what was updated, what was checked, any issues found, and any follow-up actions or support time used. | Maintenance summary prepared |
| □ | Performance | Review PageSpeed and Core Web Vitals signals | Check PageSpeed Insights and Core Web Vitals signals for key templates so speed regressions are not missed. | PSI or Core Web Vitals notes |
| □ | Performance | Check image weight, caching, and obvious speed bottlenecks | Look for oversized media, missing caching opportunities, slow templates, and simple improvements that can be handled within the plan. | Performance opportunities reviewed |
| □ | Performance | Run light crawl checks for broken links and metadata issues | Use crawl data to identify broken internal links, redirect chains, missing titles, duplicate metadata, and other quality issues. | Crawl issues reviewed |
| □ | Performance | Review storage, database bloat, and expired transients | Check hosting storage, old backups, large uploads, expired transients, and avoidable database clutter. | Storage and database review completed |
| □ | Performance | Review Search Console coverage and indexing signals | Look for indexing changes, sitemap issues, crawl warnings, and important pages that need attention. | Search Console coverage reviewed |
| □ | Performance | Confirm IndexNow submissions for changed URLs | For sites with IndexNow enabled, confirm recently changed URLs have been submitted and that the key file remains accessible. | IndexNow submission check completed |
| □ | Performance | Review schema.org markup and validation | Check important page templates for broken, missing, duplicated, or outdated structured data after theme, plugin, or content changes. | Structured data validation notes |
| □ | Performance | Add performance notes to the monthly summary | Record speed findings, crawl findings, and sensible follow-up actions so the client can see what has been reviewed. | Performance notes included |
| □ | Growth | Review analytics and conversion tracking | Check that key events, form submissions, calls, checkout, bookings, or other conversions are still being tracked usefully. | Analytics and conversion tracking reviewed |
| □ | Growth | Review analytics and conversion paths | Look for pages with traffic but weak conversion, broken journeys, content gaps, or changes in enquiry quality. | Analytics notes and next actions |
| □ | Growth | Review Search Console queries and ranking opportunities | Look for rising queries, pages with impressions but poor clicks, ranking drops, and practical SERP opportunities. | Query and opportunity review completed |
| □ | Growth | Update the monthly improvement roadmap | Turn findings from support, analytics, search, performance, and client priorities into a short list of recommended next actions. | Improvement roadmap updated |
| □ | Growth | Prepare for the monthly strategy call | Summarise completed work, current priorities, proposed improvements, and questions to discuss with the client. | Strategy call notes prepared |