What is a website?
The definition sounds trivial until something breaks. Knowing which layer owns a problem, domain, DNS, hosting, CMS or page content, is what lets you fix it or ask the right person. Most launch delays come from confusing these layers.
The essentials
The domain is the address; hosting is the storage and server.
- Pages are files generated by a CMS or built as static HTML.
- A site also includes the technical layer: DNS, SSL, redirects and analytics.
How it works in practice
This is how we would act on “What is a website” in practice, starting with the checks that block everything else.
- Register the domain in the business's own name.
- Choose hosting that matches the platform and expected traffic.
- Point DNS to the host and enable HTTPS.
- Add a content management process and a backup routine.
What to measure
Measure “What is a website” with one first-party source per number, and record the baseline date.
- Uptime and response time.
- HTTPS validity and certificate expiry.
- Pages indexed versus pages published.
Where teams go wrong
None of these “What is a website” mistakes looks dramatic on the day it is made; the cost appears later.
- Letting a web designer own the domain registration.
- Skipping HTTPS because the site has no checkout.
- Having no backup or update process.
Where this fits
Filed under Websites and builders, this page answers “What is a website” without requiring the rest of the section first.
Frequently asked questions
What is a website and how does it work?
What is the difference between a website and a web page?
Do I need a website for my business?
Sources we checked
These are primary or first-party documents. Where the page describes our own method, it is marked as our experience rather than presented as an official rule.
Something inaccurate or out of date? Tell us and we will correct it.