If your website stops generating enquiries, “the server is online” is not the answer you need. Equally, a website editor may be unable to fix a hosting outage. Knowing who handles which layer helps you get the right person involved without repeatedly explaining the same problem.

I’m Roberto DaCosta, owner of OhTurbo! I recommend separating infrastructure, website work and business decisions, then agreeing how they connect. This guide gives you a practical issue router and a support brief you can use before the next urgent request.

Website maintenance vs hosting: compare responsibilities

Hosting is the infrastructure and service that stores and serves your website. Depending on the plan, the host may also provide platform backups, certificates, server security, caching or managed software updates. Confirm each feature, its limits and who acts when a problem occurs.

Website maintenance is the ongoing work on the website itself: reviewing software changes, checking important functions, managing agreed recovery tasks and making approved content or layout changes. Coverage varies by provider. An automated update feature does not tell you who tests the contact form afterward.

The business owner supplies accurate content, approves changes, decides priorities and retains clear account ownership. Someone must confirm whether the website is helping the business: are enquiries arriving, do service pages describe your services correctly and can customers complete the intended action?

These responsibilities overlap. The official WordPress update guide recommends a backup before an update. If the host supplies the backup and the maintenance team performs the change, both need to understand how recovery would work.

Website maintenance vs hosting: map task owners

The roles below are a starting point, not a promise about every provider’s contract. Replace the role with a named person or team in your own notes.

• Hosting availability and platform incidents: start with the host. Confirm support hours, incident reporting and what the host can investigate.
• WordPress, plugin or theme behavior: start with the website team. Confirm who reviews updates, tests changes and coordinates with software vendors.
• Content and layout edits: the owner approves the request; the website team publishes and checks it. Confirm what the agreement covers and what information the team needs.
• Backup and recovery: name the backup provider, the person authorized to restore and the person who verifies the recovered site. These may be different people.
• Domain and DNS: identify the registrar and whoever manages DNS. A hosting account and domain registration may involve different companies.
• Form and email delivery: the website team checks the form path; the mail provider may need to investigate delivery. The business owner confirms receipt.
• Renewals and account access: the account owner confirms billing, recovery and notices; the technical team receives only the access needed for agreed work.

For a recurring task schedule, use our WordPress maintenance checklist. For choosing an ongoing provider, our care-plan guide covers the evidence to ask for. This page focuses on routing and coordination.

Website maintenance vs hosting: route a support request

Open the situation closest to yours. The first contact is a starting point for investigation, not proof of the cause. Record the affected URL and time before making changes.

Backups and restores need a shared plan

Ask where backups live, what they include and which restore points remain available. The WordPress backup documentation explains that a typical recovery requires both files and database. The details depend on your installation and backup system.

A host may supply a restore button while another team understands which parts need recovery. Before restoring a live shop or booking site, agree what information the restore could replace since the backup. A full restore can be a much larger action than undoing one page edit.

Name the person authorizing recovery, the person performing it and the person checking the result. Keep those roles in writing. This is more useful than discovering during an outage that everyone thought another provider owned the restore.

Send a support brief that helps the next person act

Copy this into your support request and replace the brackets. Arrange credentials through your provider’s secure access process, rather than putting passwords in the message.

Website and affected URL: [public address]

Problem and business impact: [what cannot be completed]

First noticed: [date, time and time zone]

Steps to reproduce: [what you clicked and what happened]

Recent changes: [known change, or unknown]

Evidence: [error text or non-sensitive screenshot]

Other provider involved: [team and ticket reference]

Requested next step: Please confirm who owns investigation and the next update. Explain any proposed live change or restore before proceeding.

Authorized action and boundary: [what the owner has approved; what needs approval before a live change or restore]

Evidence needed to close: [the public page or function to retest, who checks it and who confirms the result]

Hypothetical example: A contact form displays success, but the owner receives no message. The website team checks the submission and mail handoff; the mail provider checks delivery; the owner confirms receipt of a new authorized test. The coordinator closes the issue only after verifying that result. No one has to guess that “hosting” or “maintenance” automatically owns every step.

How OhTurbo! fits into the responsibility map

At OhTurbo!, our care service keeps ongoing website work organized around a clear request and completed result. We offer hosting separately from our care fee. If you already have hosting, clarify the host’s responsibilities and the access or coordination needed for website work before changing providers.

Our website care plan includes unlimited eligible monthly edits without hourly caps. Included work and bonuses do not require extra payment. That makes it practical to keep improving service descriptions, photos and calls to action instead of saving small changes for a separate project.

We usually complete edits in less than 24 hours, depending on the request and having the information and access needed. Our month-to-month payments have no long-term contract; full-year payment includes a brand-new website design and development job completely free. We explain how larger requests and additional pages fit before work begins.

I would choose a setup with clear ownership and usable support over a vague promise that one label includes everything. Our maintenance cost guide covers the billing questions separately.

Request a free website review to identify what your site needs next. OhTurbo! serves businesses nationwide across the United States remotely.