Keep a useful maintenance record
Log changes, incidents, checks, and unresolved risks. The next review should explain the site's condition and remaining priorities rather than list updates without showing what was verified. Record the date, reason, and owner of important changes.
Track requests, decisions, dependencies, and completion. Coordinate content changes with technical releases and measurement. Note changes in budget, capacity, and offers when reviewing performance.
Performance checks
Inspect representative pages and heavy assets before changing hosting. Image weight, plugins, third-party scripts, and templates can affect performance in different ways. Choose the next task from the review rather than repeating the calendar.
Remove unused accounts, use appropriate roles, and enable multifactor access where available. Keep software supported and document who can approve production changes. Document recurring costs and the person who controls each account.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities