The Website Development Process, Stage by Stage

The website development process follows the same eight stages whether the site is built on WordPress, Next.js or anything else: discovery, content and structure, design, development, content entry, testing, launch, and aftercare. Each stage ends with something you approve, and each depends on the one before. Understanding what happens when, and what is expected of you, is the simplest way to keep a project on time.

The stages at a glance

1. Discovery

Discovery turns "we need a new website" into a plan someone can price and build.

It covers what the business does, who the customers are, what the site must achieve, what pages and functionality are needed, what exists already, and what the constraints are: budget, deadline, who signs off. If there is an existing site, discovery also includes a look at what currently ranks and gets traffic, because that has to be protected.

A good discovery stage ends with a written scope. If you sent a clear website brief at the start, discovery is quicker and the quote more accurate.

2. Content and structure

Before anything is designed, decide what pages exist and what each one says. This produces a sitemap, a list of pages and how they connect, and an outline for each main page type.

This is also the moment to decide who writes the copy. If it is you, start now. What pages does a business website need helps with the list itself.

Skipping this stage is the most common cause of a design that does not fit the real content.

3. Design

Design usually starts with the homepage and one representative inner page, often a service page. Once those are approved, the remaining templates follow the same visual language.

Good design at this stage is about hierarchy and clarity as much as appearance: what a visitor sees first, where the next step is, how readable it is on a phone. Mobile layouts should be part of the design, not an afterthought.

Feedback works best when it is collected into a single list from the person who will sign off. Five people sending separate emails produce contradictory changes and an extra revision round.

4. Development

The approved designs become working templates on a staging site, a private copy that is not visible to search engines. The content structure is set up, forms are connected, and any functionality is built: bookings, calculators, integrations, eCommerce.

This is the longest stage and usually the most predictable, provided the scope is clear. Delays here tend to come from outside the code: waiting for access to a payment provider, a CRM, or the domain's DNS settings. Gather those logins early.

If you are on WordPress, the WordPress development checklist lists what should be in place by the end of this stage.

5. Content entry

Real copy and images go into the templates. This is when layout problems show up: a heading that is twice as long as the placeholder, a service with no photo, a team page with three people instead of eight.

If content is ready, this is quick. If it is not, this is where the project stops: finished templates sit on a staging site waiting for words, and the launch date slides with them.

6. Testing

Before launch, everything is checked:

1. Devices and browsers. Phones, tablets, desktop; Safari, Chrome, Firefox, Edge.
2. Forms. Every form submitted, every notification received, including from a phone, and checked in spam folders.
3. Links. No broken internal links, external links opening correctly.
4. Speed. Measured on mobile, against Core Web Vitals.
5. Accessibility. Keyboard navigation, contrast, headings, form labels, alt text. Website accessibility for small businesses covers what to check.
6. SEO basics. Titles, descriptions, headings, canonical tags, sitemap, nothing accidentally set to noindex.
7. Redirects. If replacing an old site, every old URL with traffic or links redirected to its new equivalent.

You should test too. Click everything. Read everything. You know the business; you will spot errors a developer cannot.

7. Launch

Launch is usually a short, planned window:

1. Final backup of the old site, if there is one.
2. Point the domain at the new hosting, or switch the live site over.
3. Confirm HTTPS works on every version of the domain and redirects to one.
4. Allow search engine indexing and submit the sitemap in Search Console.
5. Check analytics and conversion tracking are recording.
6. Submit every form again on the live site.
7. Spot-check the most important old URLs redirect correctly.

Launch early in the week, not on a Friday afternoon, so problems are found while people are around to fix them.

8. Aftercare and handover

The first few weeks after launch surface the things testing missed. A good project includes a period for fixing them, plus:

• Training on how to edit the site
• A handover document with logins, plugins or dependencies, licences and renewal dates
• Confirmation that you own the domain, hosting and code

After that the site needs ongoing maintenance. Website maintenance: the complete guide covers what that involves.

How long does the whole process take?

For a typical small business site with content ready: four to eight weeks. With eCommerce or integrations: two to three months. The business website development guide has a fuller breakdown by project type.

Hypothetically, say a project is planned for six weeks. Design approval takes an extra week because feedback comes in three batches. Copy arrives two weeks after development finishes. The project now takes nine weeks, and none of the extra time was development. That pattern is far more common than technical delays.

What you should receive at each sign-off

Each stage should end with something concrete you can approve or reject. If a stage ends with nothing tangible, it is hard to say whether it is finished.

Approving each one in writing, even a short email, protects both sides. It makes clear what was agreed, and it stops a late change of mind from quietly becoming free extra work or a dispute.

How to keep your project on schedule

• Nominate one decision-maker on your side
• Start writing copy during discovery, not after design
• Send consolidated feedback, once per round
• Gather logins for domain, hosting and third-party services at the start
• Agree dates for each approval, not just the launch date

If you are planning a project, the website development service page sets out how I run each of these stages and what is included.