Most people sign off a website on the part they can see: the design. Yet much of the website development process happens out of sight, in choices that decide whether the site is fast, secure, easy to edit and affordable to run.
This guide explains them in plain English: the layers every business website is built from, each stage from set-up to ongoing care, and the decisions that should be yours, not your developer’s.
The short answer
A business website is a stack of layers: a domain and its DNS settings, hosting, a content management system (CMS), a front end (the templates visitors see), plugins and integrations, and the data they store. Once the plan and design are approved, the website development process runs in six stages: set up accounts and environments, build, enter content, test on a private staging site, launch to the live site, then keep it updated and backed up. Owners don’t need to code, but should own every account and sign off testing.
The layers of a website, and what each one decides
Each layer is chosen, and often paid for, separately, so each one needs an owner.
| Layer | What it decides | Who should own it |
|---|---|---|
| Domain and DNS | Whether visitors and email reach you | Your company, as registrant |
| Hosting | Baseline speed, uptime and server security | Your company’s account |
| CMS | Who can change what, and how easily | You, with an administrator login |
| Front end | The look, accessibility and much of the speed | You, with licences in your name |
| Plugins and integrations | Features, and much of the upkeep and risk | You, listed and licensed |
| Data | What you could lose, and your privacy duties | You, with tested backups |
Domain and DNS: your address and its signposts
Your domain is registered through a registrar and renewed periodically. DNS records are its signposts: A or CNAME records point to the server that shows your website, MX records to the one that receives your email, and TXT records prove ownership to tools such as Google Search Console and help stop others sending email in your name.
Why it matters. Website and email share a domain but often not a server, so a careless DNS change at launch can bring the new site up and quietly stop email.
Check it yourself. Confirm your company is the registrant and you can log in to the registrar.
Hosting: where the site lives
Hosting is the server that stores your site and sends it to visitors. Shared hosting splits one server between many sites, so busy neighbours can slow you down; a virtual private server (VPS) reserves resources for you; managed plans add backups, updates and server-level security. Hosting sets the floor for speed: no front-end polish fixes a slow server.
The CMS: who can edit what
A content management system is the software your team logs in to when editing pages and images. WordPress, the most widely used CMS on the web, runs on hosting you choose. Hosted builders such as Wix and Shopify bundle hosting and CMS into one subscription: less to manage, less control, harder to leave (see WordPress vs Wix vs Shopify).
How to choose a CMS walks through the choice. A headless CMS separates editing from the front end, which suits some larger projects and adds cost to most small ones.
Front end vs back end
The front end is everything that runs in the visitor’s browser: the HTML, CSS and JavaScript that produce the layout, text, images and menus people see and use. The back end is everything that runs on the server: the CMS, database and code that store content, process forms and assemble each page before it is sent.
A contact form has both: the fields are front end; saving the enquiry and emailing it to your sales team is back end.
On WordPress, the theme or page builder (such as Elementor or Breakdance) produces the front end; WordPress itself, written in PHP, and its MySQL or MariaDB database are the back end.
Plugins and integrations
Plugins add features to a CMS, such as forms, SEO fields, languages and caching. Integrations connect the site to outside tools: your CRM, booking system, email marketing and analytics. Each is code someone else maintains, adding updates, possible conflicts and another way in for attackers.
Solid builds use fewer, well-maintained plugins; WordPress best practices shows how to spot the difference, and website integrations explained covers connecting your tools. If the “integration” is really a custom system with logins and workflows, you may need a web application rather than a website.
Data: the part you can’t rebuild
Designs and code can be rebuilt; content and form entries often can’t. Content usually lives in a database and images as files, so backups need both, stored off the server and tested by restoring them. Form entries often hold personal data, bringing duties under whichever privacy laws apply to you.
The website development process, stage by stage
Development is one of the ten ingredients of a good website, and its stages begin once the plan and design are agreed.
1. Foundations: accounts and environments
Domain, hosting, licences and the CMS administrator account are set up in your company’s name from day one. The site then lives in three environments:
| Environment | Who sees it | What happens there |
|---|---|---|
| Development | The developer | Building and trying things out |
| Staging | Your team, behind a password | Content entry, review, testing and sign-off |
| Live (production) | Everyone | Real visitors and real enquiries |
A staging site is a private copy of your website, hosted like the live one, where changes are checked before visitors see them. Keep it behind a password: a “noindex” setting only asks search engines not to list pages; it doesn’t stop anyone with the link from opening them.
2. Build: templates, back end and version control
Developers turn the approved design into page templates and reusable blocks, set up the back end (content types, forms, user roles and languages) and connect integrations. A good build serves its editors too: blocks that hold their layout whatever text goes in, and roles that let marketing publish without touching settings. Each language needs its own pages and URLs, which is far easier to plan than to retrofit.
Code belongs in version control, usually Git, so every change is recorded and can be undone. One rule follows: code moves up, content moves down. Code travels from development to staging to live; after launch, content is edited on the live site and copied down when developers need realistic data. Pushing a staging database over a live site can wipe out recent enquiries and edits.
3. Content entry
Real text, images and translations go into staging. Start early: real content breaks layouts that looked perfect with placeholder text, from long headings to languages that run longer. Late content is a common reason launches slip.
4. Testing
Testing is more than “does it look right on my laptop?” Before launch, check that:
Your part is acceptance testing: use the site as a customer would, and sign off only what you have checked.
5. Launch
Launch is a planned switch, not a button. The domain points to the new site, HTTPS is confirmed and staging protections come off, including WordPress’s “Discourage search engines from indexing this site” box, a classic reason new sites never appear in Google. The sitemap goes to Search Console and forms are retested on the real domain. The website launch checklist covers every check; changing servers too is its own job, covered in moving to a new host.
6. Care after launch
A website is software. The CMS, theme and plugins release updates, including security fixes, so someone must apply them (tested on staging first), keep backups and monitor uptime. The website maintenance checklist sets out what needs doing, and how often.
Where speed is decided
Speed isn’t bolted on at the end. Every layer contributes:
- Hosting: how quickly the server responds.
- CMS, plugins and caching: how much work each page takes to build.
- Front end: how heavy each page is, from images to fonts and scripts.
- Third-party tags: chat widgets and tracking pixels you don’t control.
Google’s Core Web Vitals give measurable targets, assessed at the 75th percentile of real page loads: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less. For fixes layer by layer, continue with the website speed optimisation guide.
The decisions that should be yours
You can delegate the build. These decisions you shouldn’t:
Every guide in the web development series
Each goes deeper on one decision:
| If you need to… | Read |
|---|---|
| Pick a platform | How to choose a CMS |
| Weigh up headless | What is a headless CMS? |
| Scope custom software | Website or web app? |
| Judge a WordPress build | WordPress best practices |
| Connect your tools | Website integrations |
| Harden your site | WordPress security |
| Prepare to go live | Website launch checklist |
| Change hosting safely | Moving to a new host |
| Budget for upkeep | Website maintenance costs |
| Plan routine upkeep | Website maintenance checklist |
| Run a large site | Website governance |
Frequently asked questions
What is the difference between web design and web development?
Web design decides how a site looks and works for visitors: structure, layouts, visual style and the path to an enquiry. Web development turns that into working code and makes the site fast, secure and editable. They work best planned together.
How long does the website development process take?
There’s no standard timeline: it depends on the number of templates, languages and integrations, and on how quickly content and feedback arrive. Ask for a written timeline with milestones, and what the provider needs from you at each.
What happens if my developer disappears?
If you own the domain, hosting and admin logins, and the site runs on a mainstream CMS with documented code, another developer can take over. If the domain is in their name or the code is locked away, you may face a rebuild.
What to do next
A website is only as strong as its weakest layer, and most layers are invisible from the homepage. Know who controls each one and how each stage will be checked.
Planning a new site? Our website design and development service runs from planning and design to a WordPress build you can preview throughout, a managed launch and editor training, with the domain, hosting and full admin access in your name. A website care plan then handles updates and backups; pricing shows what each package includes.
Inherited a site and unsure what’s underneath? A free website audit checks the parts visitors feel, from speed and security to how easily people can get in touch, and ends with a short list of what to fix first that you can forward to your developer.