Quick answer: The business should own domain, hosting, primary admin, tracking and key licenses; the maintenance provider should use dedicated accounts with suitable permissions and change records.
Why this matters for website maintenance
A business website should not only be online. It should capture leads, protect trust, support campaigns and have clear ownership when issues appear. If checks happen only after incidents, problems are often discovered late: lost forms, slow pages, broken tracking or security warnings. This is why these items belong in recurring WordPress maintenance or website management.
1. Domain and DNS must belong to the business
If the domain sits in a personal account or old agency account, the business can lose control during expiry or disputes.
The important point is evidence: tested URL, test time, owner, issue found and next action. This makes reporting clearer and avoids subjective discussions when website issues appear.
2. WordPress admin should be role-based
Do not share one admin account. The provider should use a dedicated account so changes are traceable and access can be revoked.
The important point is evidence: tested URL, test time, owner, issue found and next action. This makes reporting clearer and avoids subjective discussions when website issues appear.
3. Hosting, backup and licenses need ownership clarity
Hosting, plugin licenses, theme licenses, SMTP, CDN and backup need clear payment, alert and recovery owners.
The important point is evidence: tested URL, test time, owner, issue found and next action. This makes reporting clearer and avoids subjective discussions when website issues appear.
4. Tracking and Search Console should not belong to individuals
Analytics, Search Console, Tag Manager and pixels should live under business-controlled accounts or shared admin access.
The important point is evidence: tested URL, test time, owner, issue found and next action. This makes reporting clearer and avoids subjective discussions when website issues appear.
Quick checklist
| Area | What to check | Goal |
|---|---|---|
| Domain/DNS | Business-owned | Avoid loss of control |
| WordPress | Dedicated accounts | Trace changes |
| Hosting/backup | Clear owner | Recover reliably |
| Tracking | Company account | Keep data |
How this should appear in maintenance reports
This item should appear in the monthly website maintenance report with a clear status: checked, watch, action required or outside the current scope. If it affects leads, security or active campaigns, classify it under the website maintenance SLA.
Common mistakes to avoid
If this item is not part of the maintenance workflow, the business may not see the issue immediately. The problem usually appears during campaigns, plugin updates, order handling, security audits or handover to a new owner. Common mistakes include:
- Keeping domain, hosting, WordPress admin and plugin licenses under a personal email of an employee or former vendor.
- Sharing one admin account among several people with no 2FA and no change accountability.
- No handover of DNS, backup, Search Console, Analytics and email access when changing vendors.
Information to prepare before IT Systems checks
Maintenance should not become guesswork. Preparing clear input helps the technical team check faster, report with evidence and avoid missing items that affect the business:
- Domain, hosting, DNS, WordPress admin, SMTP, CDN/cache and tracking account list.
- Legal owner, daily operator and approver for important changes.
- Process for granting, revoking, password rotation, 2FA and handover evidence.
How IT Systems includes this in maintenance
Business websites need a clear permission model: the company owns the assets, the maintenance team receives enough access to operate, and important changes are recorded. At onboarding, IT Systems should review access before technical changes so incidents are not blocked by missing DNS, hosting or backup permissions.
If the issue relates to forms, email or tracking, compare it with the website lead-loss checklist. If it relates to speed or resource limits, connect it with website speed optimization, business WordPress hosting or Cloud VPS. If it relates to updates and security exposure, review WordPress security services and the process for a slow or broken website after plugin updates.
Business decision note
Access ownership is also a risk-management topic. The maintenance provider should not become the only party who can access critical assets, and the business should not rely on one personal account either. The safer model is company-owned accounts, named users, limited roles, 2FA, a password vault or access log, and a documented emergency path. This protects the business during staff turnover, vendor change or urgent incident response.
Frequently Asked Questions
Does a small website need this check?
Yes, but the scope can be lighter. At minimum, schedule periodic checks so silent issues do not continue unnoticed.
Should every issue be fixed immediately?
Not always. Prioritize by business impact: lead loss, security or downtime comes first; cosmetic improvements can be scheduled.
Is this included in website management pricing?
It depends on scope. Review website management pricing to separate recurring work, extra requests and focused projects.
Need more controlled website operations?
Let IT Systems review your website and recommend the right maintenance scope
IT Systems can review technical health, forms, security, speed, content and recurring reports so the website supports business better.
