Blog / Case studies /
A year of managing client websites: what I’d tell myself
It’s been a year since I started managing client websites at Nivonix. WordPress, Shopify, other platforms, all of it. If I could whisper one thing to myself on day one, it would be this: the website is not just the page you can see.
A lot of the job sits underneath it: DNS, SSL, hosting, updates, analytics, plugin conflicts and the conversations that help another person use the site confidently. SEO matters, but the site has to remain available, understandable and safe enough for the work above it to count.
Learn the systems around the CMS
It is easy to begin with the visible task: edit a title, change a page or install an app. Then an issue appears and you discover that the domain points somewhere unexpected, the certificate has expired or an update changed a shared template.
I would tell myself to learn the supporting systems earlier. Know where DNS is managed, who controls the hosting account, how backups are restored and which person can approve a production change. You do not need to become an expert in every layer, but you need to know where responsibility sits and how to ask the right question.
Keep an inventory of the sites and their important services. Record the platform, hosting provider, domain renewal contact, backup method, key integrations and escalation route. Store credentials in an approved password manager, not in the inventory itself. A short record is more useful than trying to reconstruct the setup during an outage.
Treat operations as part of SEO
A search strategy cannot compensate for a site that is unavailable, insecure or broken after an update. Technical operations are not glamorous, but they protect the pages, forms and checkout flows that visitors rely on.
I would make monitoring specific to what the business needs. A homepage check can confirm that one URL responds, but it will not tell you whether a contact form submits, a checkout works or email notifications arrive. Test important journeys and define who acts when an alert appears.
The same applies to updates. An update is not complete when the dashboard says it ran. Check the pages and functions that matter, record what changed and have a rollback path. Use staging when available and avoid bundling unrelated changes into one release.
Document the reason, not just the action
A note that says “changed plugin setting” is difficult to use later. Record why the change was made, what pages it affects, who approved it and how you checked the result. This gives the next person context and helps the team understand what to revisit if something breaks.
Keep documentation short and easy to find. A list of every minor click is likely to become stale. Focus on decisions, dependencies, recovery steps and recurring tasks. If the detail changes often, link to the system that owns it rather than copying an old value into a static document.
This is especially important when several people touch the same site. Designers, writers, developers and client editors may each know only part of the setup. A shared record prevents one team’s change from becoming another team’s mystery.
Communicate before a surprise becomes a problem
Clients often need to know what a technical change means for their daily work. Explain the impact in plain language: what will look different, what they need to test and who to contact if something does not behave as expected.
I would send updates early when a change has a deadline or could affect access. A short message before a rollout is better than silence followed by a long explanation after someone notices an issue. Be clear about what is known, what is still being checked and when you will follow up.
Do not promise a ranking or a recovery date you cannot control. Promise the work you can do: investigate, report what you find and recommend a next step. This sets a more trustworthy expectation than confident guesses.
Make training part of delivery
A site handover should help the owner do routine work without depending on you for every small edit. Show them how to publish, preview, update product details or handle the parts of the CMS they will own. Give them a concise reference for common tasks and explain which changes need technical support.
Training is not a one-off screen share that nobody can revisit. Let the person try the workflow, ask where they got stuck and improve the documentation. Keep access appropriate to the task; a content editor does not necessarily need administrator access.
Respect the differences between platforms
WordPress and Shopify share some principles, but their details differ. Plugins and themes on WordPress are not the same as apps and theme sections on Shopify. URL rules, hosting responsibilities, checkout controls and content models vary.
I would spend time understanding the platform before applying a familiar fix. A solution that works on one CMS can cause duplicate pages or a broken workflow on another. Check the documentation, test safely and explain the trade-off to the site owner.
Build room for interruptions
A plan for several sites needs space for unplanned work. An SSL warning, a broken form or an urgent product update can arrive while a larger project is underway. Keep a short list of priorities and make it clear what can wait. This helps the team respond to genuine risk without treating every request as equally urgent.
I would also agree how requests are submitted and who can approve them. A message in one chat, an email thread and a ticket can leave different versions of the task. Choose a shared place for the request and record the decision there. The process does not need to be heavy; it needs to give everyone the same version of what is happening.
Related reading
- Managing several client websites at once: the system I use
- How I talk to clients during a core update
- Change logs for websites: why I write down every fix
If I could pass one habit back to my first week, it would be to write down the system and the reason behind each important decision. What part of your website operation only one person currently understands?