WebsitesModule 5: Launch and ownershipLesson 15 of 15
Course progress93%
14 min lesson · Updated August 2026
What happens after a website launches?
Website maintenance is the planned work of keeping content, software, infrastructure, access, measurement and recovery accurate, supported and useful after launch.
What you will learn
By the end, you will understand:
Create accountable maintenance areas and cadence
Distinguish backups, updates, monitoring and content governance
Plan safe changes with testing and rollback
Visual explainer
See the idea clearly.
A live website moves through monitoring, content review, backup, staging updates, regression tests, deployment, verification and recovery readiness in a repeating owned cycle.
Supported versions, dependency updates and compatibility.
Infrastructure
Hosting, domain, DNS, TLS, capacity and availability.
Security/access
Accounts, logs, incidents, least privilege and recovery.
Data/measurement
Forms, integrations, events, consent and retention.
Experience
Accessibility, performance, browsers/devices and task regression.
Backups and updates solve different risks
Updates fix defects and vulnerabilities but can introduce compatibility issues. Backups support recovery but do not prevent compromise and can themselves contain compromised data.
Use protected backups, test restores, stage risky changes and maintain a rollback procedure. Do not edit vendor/core files that updates overwrite.
A practical cadence
Cadence
Examples
Continuous/alerts
Availability, critical errors, security and failed submissions.
Frequent
Updates, backups, forms, key journeys and urgent content.
Monthly/quarterly
Access review, broken links, analytics quality, performance and high-risk content.
Event-driven
Release, migration, campaign, incident, legal/policy or business change.
Safe change workflow
01
Define change/acceptance
02
Back up and confirm rollback
03
Use version control/staging
04
Implement through supported extension
05
Test affected/dependent journeys
06
Deploy controllably
07
Verify production/logs
08
Monitor outcome
09
Document
Ownership prevents quiet decay
Named domain owner
Hosting/billing contact
Technical maintainer
Content owners
Form/enquiry owner
Analytics/privacy owner
Backup restore owner
Incident contact
Vendor licenses
Renewal calendar
Source repository
Handover plan
Maintenance should be risk-based
A campaign microsite and a healthcare portal need different depth. Prioritize security, data, revenue, accessibility and high-traffic/high-value paths.
Do not delay urgent security action until a monthly checklist, but avoid untested production changes without recovery.
Real-world example
Example: a form silently stops delivering
Example
The page still shows success after a mail-service credential expires, so no one notices lost enquiries. Maintenance adds end-to-end synthetic testing, delivery alerts, a fallback contact route and a named response owner.
Try this
Create a maintenance register
List domain, hosting, software, forms, backups, analytics, privacy, key content and integrations. Assign owner, check frequency, last verified date, evidence and escalation route.
Common questions
Questions beginners ask.
Why does a website need maintenance?
Software, security, business facts, browsers, integrations and user needs change.
How often should WordPress be updated?
Monitor supported releases and apply updates through a risk-based backed-up/tested process, prioritizing security fixes.
Is a backup enough?
No. It must be protected, retained appropriately and restored/tested, and other preventive controls remain necessary.
What is staging?
A separate environment for testing changes before production, with sensitive data handled safely.
What is rollback?
A documented way to return to a known working state if a change fails.
Who should own the domain?
The business should retain accountable control through a secured organizational account, not an inaccessible personal/vendor account.
Should content be reviewed?
Yes. Assign owners and event/date triggers for facts that can expire.
What should monitoring cover?
Important availability, errors, security signals, integrations and user journeys with actionable owners.
