Control
Know who can access the website, renew its services, and recover its accounts. The business should be able to continue if a staff member or provider leaves.
Information · Website stewardship
Website stewardship is the ongoing care that keeps your site working after launch. It covers account access, updates, backups, accurate information, and the calls, forms, and booking links customers rely on.
Domain
DNS
Hosting
Website
Actions
The complete collection
Find who controls your domain, DNS, hosting, and website accounts, with an example account list and practical recovery checks.
↗02Understand what website maintenance should cover, with a sample review calendar, a useful change report, and questions for your provider.
↗03Find out what your website backups include, how much recent work a restore could lose, and what a useful recovery drill should demonstrate.
↗04Protect website accounts and customer information, understand provider responsibilities, and prepare a practical response to suspicious activity.
↗05Explore website hosting companies and service types, with official sources and guidance on support, responsibilities, costs, and portability.
↗06Keep public business details current with an approval process, a simple fact sheet, and a worked holiday-hours example.
↗07Identify barriers in website navigation, content, and forms, with owner checks and a clear role for professional accessibility evaluation.
↗08Understand website speed reports, choose useful repairs, and prevent slowdowns with practical tests and agreed performance budgets.
↗09Compare focused repairs, a staged rebuild, and a full redesign through three practical examples and questions to ask before approving work.
↗10Plan a website provider handoff with clear deliverables, tests of the new setup, a switchover sequence, and deliberate account closeout.
↗11Test forms, phone links, and booking links all the way to a staff reply, with a worked inquiry example.
↗12Prepare account access, exports, contract dates, and continuity options before ending or renewing a website service.
↗13Set up SPF, DKIM, and DMARC so form alerts, quotes, and review requests sent from your domain reach inboxes instead of spam.
↗14Keep your domain and security certificate from expiring, with auto-renew, registrar lock, grace periods, and shorter certificate lifetimes explained.
↗15Write a privacy policy that matches what your website actually collects, and understand when a cookie consent banner is needed.
↗What good care covers
Know who can access the website, renew its services, and recover its accounts. The business should be able to continue if a staff member or provider leaves.
Agree who handles updates, notices problems, and restores service. Test the recovery plan while the site is working.
Keep information current and check that customers can read, navigate, call, inquire, and book on the devices and tools they use.
Working with your provider
A clear plan names the work included, the response process when something fails, and the decisions that need your approval. Ask for a short report showing completed changes, checks performed, and unresolved issues.
These guides describe good practices across different kinds of websites. The work included in your service depends on the platform, its condition, and the scope you agree with the provider.
Explore Website Stewardship services ↗Questions business owners ask
It is the ongoing care of the website and the services it depends on. That includes keeping account access, updates, recovery, business information, and customer actions in good order, with clear responsibilities when something needs attention.
Hosting provides the environment where the site runs. Stewardship also asks who checks the site, maintains its software and information, tests customer requests, and responds when a problem appears. The exact division of work depends on the provider and agreement.
Keep control of critical accounts, confirm business facts, approve the scope of work, and identify the staff who handle customer requests. Your provider should explain and carry out the technical work you have agreed, then report results and open questions clearly.
No. A simple informational site, a content-management system, and an online store have different software, data, and support needs. Start with what the site does and the consequences of a failure, then agree the checks and recovery arrangements that fit.
Protect the operating foundation