Small business website maintenance guide.

1. Give every maintenance task an owner

A checklist without responsibility becomes a wish list. Name the person or provider who checks the website, approves changes, controls each account, receives alerts, monitors enquiries, and decides what is urgent.

• Keep an ownership record for the domain, DNS, hosting, website administration, business email, analytics or search tools, paid software, and backups.
• Record recovery email addresses, multifactor-authentication ownership, renewal dates, and the safe process for granting or removing access.
• Define what the website owner handles, what a hosting provider handles, and what requires a developer, designer, content owner, or legal reviewer.
• Choose a review frequency based on how often the site changes, the platform, customer impact, and security exposure.

A practical starting schedule

Frequently changing or business-critical sites may need daily or weekly attention. A small brochure site may use a lighter routine. Start with quick weekly checks, a fuller monthly review, and an annual ownership and policy review, then adjust using real issues and change history.

2. Back up before changing software

Updates can fix security and compatibility problems, but applying them without a recovery path can create a different outage.

1. Read the update notes and confirm compatibility with the current runtime, theme, plugins, extensions, and custom code.
2. Take or verify a current backup of the files, database, and configuration needed to restore the website.
3. Use a staging environment for higher-risk or bundled changes when the platform and plan allow it.
4. Apply changes in a controlled order and keep a record of versions, time, person, and reason.
5. Clear the appropriate cache, then test public pages, administration, forms, search, login, purchases, bookings, and other important paths.
6. Restore or roll back when the agreed failure threshold is reached; do not stack more unplanned changes on an unclear failure.

3. Review security and access as an ongoing task

• Remove accounts that are no longer needed and use the least access required for each active person or integration.
• Use unique passwords, protected recovery methods, and multifactor authentication where it is supported.
• Review administrator users, login alerts, software versions, security notices, unexpected file changes, and relevant logs.
• Renew and check HTTPS certificates, domains, software licenses, and services before expiration.
• Keep development tools, backups, logs, environment files, and staging sites away from public access.
• Document how to report a suspected compromise, who can isolate the site, where a clean backup is stored, and when outside expertise is needed.

No maintenance routine guarantees that an incident cannot happen. The goal is to reduce avoidable risk, notice important changes, and make recovery more controlled.

4. Check the paths customers actually use

Do more than open the homepage. Use a phone and a larger screen, and periodically test the site with a keyboard.

• Open representative pages and check navigation, footer links, buttons, breadcrumbs, downloads, images, video, and the 404 page.
• Submit every important form and verify that the message reaches the intended mailbox. Test validation, success, and controlled failure states.
• Check business name, email, service area, hours if published, current packages, prices, legal links, and customer instructions.
• Look for clipped text, layout shifts, poor contrast, missing focus indicators, unlabeled fields, confusing errors, and horizontal scrolling.
• Review broken links, server errors, unusually slow responses, large assets, and meaningful changes in representative performance measurements.

Record the browser, device or viewport, page, connection, server environment, tool, and date with performance results. A single score does not prove permanent speed for every visitor.

5. Keep content and search information accurate

• Assign a source and review date to prices, package limits, company details, team names, legal statements, service areas, statistics, and third-party claims.
• Update or remove expired offers, former services, old staff details, broken downloads, unsupported advice, and duplicated pages.
• Give each useful page a clear topic, one main heading, descriptive subheadings, a distinct title and description, and internal links that help the visitor continue.
• Keep canonical URLs, robots rules, the XML sitemap, redirects, and structured data aligned with the visible, approved website.
• Review search performance and real customer questions before adding location or article pages. Do not create near-duplicate pages solely to target keyword variations.

Rankings cannot be guaranteed. Maintenance can keep technical signals and content accurate, but search results also depend on relevance, competition, reputation, changes made by search engines, and factors outside the website.

6. Keep a change record and a clear support route

For each maintenance cycle, record the date, owner, backup reference, updates, checks, findings, fixes, deferred work, and next review date. This makes a future issue easier to trace.

• Classify problems by actual business impact rather than using “urgent” for every request.
• Include the website, affected page or feature, start time, exact symptoms, recent change, people affected, and a safe screenshot.
• Do not send passwords, private keys, recovery codes, or full payment-card details through ordinary support email.
• Separate routine content edits, maintenance, larger development work, provider outages, and security incidents so each follows the right process.

NivoraHost customer support is staffed by email 24/7, and we aim to send an initial reply within 4 hours. The reply may confirm receipt or ask for details; this target is not a resolution deadline or service-level guarantee.