Hosting makes your website available; maintenance keeps the software and its connections looked after. A backup stores recoverable information; support handles problems and agreed changes. These services may be bundled, but they are not interchangeable.
Read what is actually covered
Ask which components are updated: framework, CMS, plugins and integrations. Specify whether the provider tests forms and other important journeys after updates. “Updates included” should explain responsibility when a change causes a compatibility issue.
Clarify whether content edits and design changes are covered or separately quoted. Webility’s website offer distinguishes hosting renewal from maintenance and modifications. Confirm your actual agreement rather than assuming every annual fee buys ongoing development.
Check recovery, not just backup frequency
Ask what is backed up, where it is stored and who can restore it. Database, media and configuration may need different handling. A backup statement is incomplete without a restoration process and suitable access.
Discuss restore testing and the practical limits of recovery. An old backup may lose recent changes; a complex integration may require reconnection. Avoid promises of zero downtime or zero data loss unless an explicit, supportable arrangement exists.
Agree incident handling
Separate an urgent outage or broken payment flow from a routine wording change. Ask about contact channels, service hours and response expectations. “Unlimited support” can still exclude important work, so request concrete examples.
Keep domain and supplier accounts under appropriate business control. Document the setup and handover process so changing providers does not require rebuilding from scratch.
Comparison checklist
- Hosting, maintenance and content work separated.
- Update testing and recovery responsibilities named.
- Support hours and escalation explained.
- Account ownership and exit arrangements documented.
Request a plan matched to your website’s dependencies and business importance. Pay for clear ongoing care rather than reassurance without an operating process.
A brief you can use to compare proposals
Use the following as an illustrative procurement check, not a promise of results or a fixed package. Ask the provider to turn it into named deliverables, exclusions and a test you can witness before accepting the work.
Require response expectations, restore testing and included editing hours to be written into the support scope.
A published example to inspect
A calm, editorial website for a beauty studio, bringing natural sugaring, manicure services and booking into one coherent experience. Visitors can compare treatments and prices, understand sugaring, explore the studio and continue to booking from clearly placed calls to action.
Inspect the project: Maison Lumia
This published example illustrates presentation and visitor flow. It is not evidence of a conversion uplift, a ranking position or a price for your own project. Compare the scope you need with the capabilities actually demonstrated, then ask what would be different for your business.
Primary reference
Next.js documentation. Use the reference to check terminology and platform requirements when briefing a provider; the proposal still needs to define your own implementation and responsibilities.
Continue your comparison
Website Redesign Without Losing Google Rankings: What to Ask Your Agency
Discuss your project
Website maintenance and hosting · See our website and service pricing
Send your current website, target customers and the problem you want to solve. We will discuss the appropriate scope, responsibilities and next step before you commit.