Small Business Website Maintenance Services: What to Pay For
Compare website maintenance proposals using a practical checklist for updates, backups, lead forms, renewals, incident response and ongoing support.

The quick read
Key questions at a glance
What should a small-business website maintenance plan include?
Define the systems covered, routine checks, update and recovery responsibilities, form monitoring, renewals and incident response. Agree which changes cost extra.
Do Wix, Squarespace or Webflow sites need maintenance?
Hosted platforms handle parts of the platform infrastructure. The business still needs an owner for domains, account access, content, links, forms, integrations and any recovery the chosen plan supports.
Who should maintain a WordPress website?
Assign responsibility for the host, WordPress core, themes, plugins, backups and verification after updates. Confirm which tasks your host handles and who owns the rest.
What are you paying a maintenance provider to do?
A useful website maintenance service keeps agreed customer journeys working, helps the team recover from failures and gives ordinary updates a named owner. Buy against an inventory of your pages, forms, integrations, accounts and subscriptions. Ask for a description of routine work, exception work and how the provider proves both were completed.
For a basic service site, the priority might be reliable enquiries and a current offer. A shop that takes payment online may also need checkout and fulfilment checks. A member portal may have stricter access and recovery requirements. These are different workloads. Compare quotes against the actual system rather than choosing from package names.
Write down what the website depends on
Ask whoever owns the site to list the platform, domain registrar, hosting account, payment services, booking system, analytics, business email, forms and connected services. Include the account owner, renewal date, recovery contact and dependency. If a contractor leaves, another authorized person should be able to find the information and understand the escalation route.
For a booking form, the dependency chain might include the website page, an external scheduler, a shared calendar, a confirmation email and a receptionist who checks exceptions. A working landing page can coexist with a broken scheduling chain. Give that chain a named owner from the customer's click through to the actual appointment record.
Record the public website and the administrative services separately. Domain administration, email and checkout may involve different suppliers. Ask which organization can make each kind of change and what access the maintenance provider needs. Store recovery details and credentials using the business's approved account management process.
Separate the work into clear categories
- Recurring checks. Test the main enquiry route, confirm essential pages load and review known renewals and failures.
- Planned changes. Apply approved updates, publish approved content or replace an integration through a scheduled process.
- Incidents. Triage an outage, a missing lead, a compromised account or a failure during payment.
- New projects. Add capabilities, redesign a page, migrate the website or commission new content.
- External commitments. Renew the domain and services, pay for required software and confirm account ownership.
Have each supplier price the same categories. If one proposal bundles editorial work and another covers technical care, separate them on paper so you can compare the scope.
Match the work to the platform
Hosted website builders
Ask what the provider controls and what the platform handles under the chosen plan. Your checklist should cover account access, domain connection, payment settings, form destinations, links, embedded tools and recovery options. Confirm how the platform stores previous versions or exports data for the exact features your business uses. Review the available options before calling a provider's copy a full backup. Wix plans, Squarespace plans and Webflow plans
A small consulting business might care most about whether a form reaches an inbox. A store operator might test a checkout and a refund through the approved test mechanism. A manager responsible for public updates might check whether approved editing permissions are still correct after personnel changes.
Self-hosted WordPress
Identify which responsibilities your host actually covers and what the site owner must handle. List WordPress core, themes and plugins and record where updates are managed. Plan a backup and verification step before consequential updates. WordPress recommends backing up before updating and documents supported update methods. WordPress update documentation
Make one representative list of critical workflows. Include editing a page, submitting an enquiry and using any business-critical plugin. For a booking or commerce site, test its particular workflow with the agreed environment and data. A dashboard that reports current versions is one check in a broader release process.
Custom websites
Find out where the code, deployment access, content, environment configuration and integrations live. Ask how a release is checked and what rollback affects. Reverting a website deployment and recovering business records can be different tasks. A support proposal should say who can perform each one and how the provider will keep the state consistent after recovery.
If the site uses a CMS or external database, document which system owns each kind of record. Ask how a later release will handle older records and changes that happened during a failure. Keep the restore process tied to the actual architecture rather than treating a code repository as the whole website.
Use a repeatable enquiry check
Give staff a short approved script. Open the public site on a phone, find the main service and submit a labelled test enquiry through the form. Confirm the screen gives the expected next step. Find the request at the destination and verify it has enough information to be handled. Repeat for a booking or payment route using approved test facilities.
Write down the URL, test time, expected result, observed result and owner. Capture only enough evidence to investigate later. If a routing rule directs urgent messages to a different mailbox, include a representative test for that route. For a business with several locations, ensure the right location receives the request.
Do a check after changes likely to affect the route. Moving an email provider, changing a consent setting or replacing a calendar integration can alter what happens even when the public design stays familiar. Assign someone to verify the journey after the change and monitor the first real enquiries.
Ask how incidents are triaged
Agree how to report a problem and what information to include. A good incident report identifies the affected URL or workflow, when it was observed, what the customer saw and whether the issue can be reproduced. Avoid sending credentials or private customer records through a general support channel.
Define urgency using business impact. A broken public payment or lead route may need rapid attention. A typo on a low-traffic archive page can go into planned work. Ask when someone acknowledges a report, who investigates it and what happens when a different provider must fix it. Response time and repair time describe different events, so confirm both in the agreement.
Agree who can authorize a temporary customer-facing change. An alternate phone number or an approved contact route may help while a supplier diagnoses the issue. Give the temporary route an owner and a review date so it can be removed once the original workflow works again.
Compare backups by what you can recover
List what you would need to restore after a real incident. Examples include content, images, approved configuration, form records, orders and redirects. Determine which supplier keeps each item, how far back recovery can go and whether recent changes would be lost. Store any independent copies according to the business's data handling rules.
A permitted restore exercise is more concrete than an assurance that backups run. Ask the provider to restore a representative copy in an isolated environment and show that it opens and contains the expected information. For a live order system, have the provider explain how the team would reconcile orders received after the recovered point.
Include account recovery in this discussion. A usable backup can still be difficult to apply when the only authorized owner is unavailable. Give the business a recoverable ownership path and keep the handover details current.
Compare the full bill before signing
List the subscription fee, included hours or tasks, extra change rate, third-party renewals and transition cost. Ask how unused capacity, emergency work and new requests are handled. Request an example invoice or an example month built around your actual requirements, with all assumptions stated.
Define routine content changes precisely. Updating an existing telephone number is different from interviewing the owner, writing a new service page, commissioning images and building an enquiry form. Ask for a simple scope boundary so staff know when to request a separate quote. The small business website costs guide explains how to separate build, software and ongoing work.
Get a monthly report you can act on
A short report can list checks completed, issues found, changes made, renewals due and decisions needed. Connect technical findings to a customer task. If a booking email failed, show when the team detected it, how the route was restored and what evidence confirms the fix.
Review the agreement when the site changes. Adding a payment route, a third-party membership or a busy campaign can change support needs. Keep the inventory and acceptance checks current so the plan reflects the website customers use today.
A worked example for a business that depends on bookings
Imagine a small training studio with a public timetable, a third-party scheduler and an operations inbox. Its most important website task is a first-time booking. The owner wants a care plan because staff sometimes learn about a problem only when a customer calls. Build the agreement around a complete booking journey and document a second route for customers who need assistance.
Create an approved test slot that staff can recognize. Verify that a phone visitor can find it, complete the test booking, see confirmation and receive the expected message. Check the record in the scheduling tool and confirm someone can cancel the test cleanly. Keep the evidence to the time, outcome and a reference safe to share with the maintenance provider.
Now trace the path when the slot disappears from the website but remains available in the scheduling account. Determine where availability is managed. If the timetable is manually copied, decide whether to simplify the page or assign someone to reconcile it. If it comes from an integration, record who can inspect the connection. Agree on an owner for each failure mode. This turns a vague request to keep the website working into an agreement the studio can check.
Set a baseline before changing the site
Record which routes are currently working and which problems are already open. Capture the expected homepage, primary service page, booking destination and contact response. Ask the supplier to mark any defects they find and explain whether fixing them is part of onboarding or a separate project. This helps both parties distinguish inherited problems from changes introduced during the care agreement.
Set a starting date for routine checks and decide where the evidence will be stored. A short shared record can be enough. Give a backup staff member access through the normal account process and ask them to locate the latest report. Include the contact information for the supplier and the person at the business who can approve chargeable work.
Rehearse a domain renewal with the actual owner
Find the registrar account and confirm the business has an authorized owner and an up-to-date recovery contact. Record the expected renewal date and the way the business receives notices. Ask who checks that the payment arrangement is current. Avoid opening a transfer or changing live DNS merely to demonstrate access.
Write a short handover note that explains where the website and email connections are managed and who can authorize changes. If the business uses a separate web host and email provider, show which account handles each part. Agree a review after staff changes or a supplier handover. This lets the owner see whether the renewal item in a proposal represents active work or a reminder they already manage.
Plan how work moves from request to acceptance
Define a request format with the URL, approved change, required date, acceptance check and person who can sign off. For instance, a studio that changes the cancellation window should provide the exact policy wording and identify where it must appear. The provider can check the public page and ask the scheduler owner to confirm the booking message. Assign someone to review all affected customer-facing information.
Agree how you handle conflicting instructions. A provider should know whether a marketing manager can change an offer or whether an operations owner must approve a booking policy. Keep the approved final wording in the same record as the change. If a new change is requested after approval, record it as a separate request so the team can tell what the original work covered.
Define recovery evidence before an incident
Ask the supplier to describe the recovery goal in ordinary terms. For the studio, restoring the public timetable might be the first priority, followed by confirming that recent bookings still exist and reviewing duplicate confirmations. Ask how the team would reconcile changes since the chosen recovery point and who is responsible for each system.
Keep the final check tied to a customer task. Confirm the booking route using a supported test, review the result from the staff side and record the relevant time. If a third party still needs to act, document the remaining impact and any approved workaround. The owner can then decide whether to communicate with customers or adjust availability.
Compare the same example month
Give each bidder a shared scenario. Assume the team publishes a minor update, receives a domain renewal notice and discovers a failed booking email in the same month. Ask the bidder to state who acts on each item, whether it falls within the base fee and what evidence appears in the report. Include one larger request, such as adding a new service with an intake form, so the bidder can show where project work begins.
Review the answers with the owner and someone who receives bookings. A technically thorough plan can still fail if no one knows how to report an issue or validate a fix. Choose the scope that fits the website's real responsibilities and budget, then save the agreed checks where the next person can find them.
Use a quarterly review to keep the agreement accurate
Check the inventory against the website customers currently use. Open the main navigation and look for newly added forms, payment routes or integrations. Ask who owns each one and what changed since the last review. If someone added a service outside the original project, confirm whether the maintenance provider knows it exists. Give the provider a current expected result for the new journey.
Review access with the site owner. If a staff member moved teams, use the appropriate administration process to update their access. Confirm that any replacement can find approved instructions for ordinary work. Check the reporting contact and the person who approves spending. A provider can respond faster when it knows who has the authority to decide what comes next.
Use the review to adjust frequency based on impact. A booking-heavy business may need more frequent checks of its core route around a launch. A rarely updated portfolio may need an occasional review of links and a process for checking changes as they happen. Let recent incidents and the site's use inform the schedule. Record the schedule in the agreement so it remains visible when staff change.
End by reviewing the supplier's evidence against the agreed outcomes. If an important check keeps returning an unexplained result, ask for the reason and a practical resolution. If a maintenance task has become unnecessary because an old integration was retired, remove it from the scope at the next agreed review. Keep any relevant records according to the business's retention rules. The remaining agreement should describe the site the business has today and the support that site needs.
Bring your current site, platform, most important enquiry route and any open support problems to Brands Essential. Ask for a maintenance scope that separates recurring checks, incident handling and improvements so you can compare it with your existing arrangement.
Frequently asked questions
Questions, answered
What should a small-business website maintenance plan include?
Define the systems covered, routine checks, update and recovery responsibilities, form monitoring, renewals and incident response. Agree which changes cost extra.
Do Wix, Squarespace or Webflow sites need maintenance?
Hosted platforms handle parts of the platform infrastructure. The business still needs an owner for domains, account access, content, links, forms, integrations and any recovery the chosen plan supports.
Who should maintain a WordPress website?
Assign responsibility for the host, WordPress core, themes, plugins, backups and verification after updates. Confirm which tasks your host handles and who owns the rest.
How much should I budget for maintenance?
Price the exact recurring scope and likely exception work. Include third-party renewals, internal time and the response level you require.
How can I tell whether a backup is useful?
Find out what it contains, where it is stored, how long it is retained and who can recover it. Ask for evidence from a permitted restore exercise on a safe environment.
Does maintenance cover website redesign or SEO content?
Those are separate workstreams unless the proposal lists specific deliverables. Compare the care plan, content work and redesign as separately scoped commitments.
Build a website around your customers and budget.
Tell Brands Essential what you need, what is already working and the budget you can sustain. Agree a useful first phase and the responsibilities before adding more.



