How long does it take to have a website made?

“How soon can it go live?” is the question straight after “what does it cost?”. An honest answer begins with a caveat: nobody can sensibly predict the duration of a website project without knowing what is being built and how fast the input arrives. Anyone who promises a fixed number of weeks before they know your wishes is promising something they cannot know. So in this article we explain which phases a project consists of, where the time really goes and what you can do yourself to speed things up. We deliberately name no standard number of weeks. Only for a defined package can we agree a duration; for our Growth package, for example, one is stated, and for custom work we agree it in the quote.

It is rarely the build that takes the time

The build itself is usually the most predictable part. The time goes into what happens around it: waiting for copy and photos, decisions that get stuck, new wishes halfway through and dependencies on other parties, such as an accounting integration or a supplier who has to give access. A project of a few weeks becomes a project of a few months if nobody decides. Keep that in mind for every phase below.

The phases of a website project

1. Intro call and scoping

In the first conversation we determine goal, audience, scope and priorities. The result is a quote with scope, schedule and price. This phase does not usually take long, unless several people in your company have to agree. Thinking about goals in advance helps: read Preparing a website project for a checklist.

2. Moodboard and direction

Before a pixel is built, you fix the mood: colours, imagery, tone. The advantage of a moodboard is that at that point you can still change direction cheaply. If you only say at the first full version that it should be a completely different style after all, that is the most expensive place to find out.

3. Structure and content

Here it is decided which pages there will be, how they connect and what is on them. Google's SEO Starter Guide stresses that you should create content that is helpful and reliable, and that clear page titles and a logical structure help people and search engines. Writing copy takes far more time than most business owners expect, and it is the phase that most often falls behind. Have the copy written for you, write it yourself or start with a first version that we sharpen together: choose, but make the choice early.

4. Design and build

Design and build often overlap, especially with custom code. The number of different page types and the amount of functionality set the time here. A form is quickly done; a custom integration with an external system is not. Performance and accessibility belong in this phase and not in a separate track afterwards: web.dev describes through Web Vitals which measurements for loading, interactivity and visual stability matter most, and the W3C Web Accessibility Initiative advises planning accessibility throughout the project rather than as a separate check at the end.

5. Feedback and changes

Every feedback round has a turnaround: you look, collect comments, we process them. If you need two days to respond, that is fine, but it moves the rest of the project by exactly that many days. The number of rounds and the speed of your responses are the most influenceable parts of the schedule. Agree in advance how many rounds there are and who has the final say.

6. Testing and preparing for launch

Before launch we test on different devices and screen widths, check forms and email delivery (see email delivery: SPF, DKIM and DMARC), and set up analytics and monitoring. If you are replacing an existing site, there is an extra step: moving from old to new addresses. In its documentation on site moves, Google writes that you make a map of old and new URLs, set up permanent redirects and that those redirects generally stay in place for at least a year. Google also advises changing one thing at a time during a migration: if you switch domain, system and design all at once, mistakes are hard to trace. You can read more in Moving a website without losing SEO.

7. Launch and the weeks after

On launch day the redirects go live, the sitemap is submitted in Search Console and we check that everything is reachable. Google states that for a small to medium-sized site it can generally take a few weeks for most pages to move in the search results, and that visibility may fluctuate in the meantime. That is normal. So it is wise not to schedule a launch right before a busy period or a campaign.

What most often delays the schedule

1. Content that arrives late. Copy, photos, logos, prices, team photos: everything you are the source of.
2. Too many people deciding. Every extra decision-maker increases the chance of contradictory feedback.
3. New wishes in the middle of the project. They can be entirely valid, but they belong in a next phase or an adjusted schedule, not slipped in quietly.
4. Dependencies on third parties. Access to a domain, a link with a booking system or an accountant who has to look along.
5. Legal items that come last. A privacy statement, cookie choices and an accessibility statement take time if they only come up at delivery; see cookies and GDPR.

What you can do to speed things up

• Deliver content before the design is finished. Real copy gives a better design than placeholders.
• Appoint one decision-maker. One point of contact, one set of feedback.
• Collect existing material in one go: good-quality logos, photos, services, frequently asked questions and reviews.
• Block response times in your diary for the feedback rounds.
• Start with the core. A strong first version with the most important pages goes live sooner than a complete site, and then you expand.

How to judge a schedule

A good schedule does not just name an end date but also intermediate steps, what is expected from you and when. Be wary of a schedule without your tasks: it looks as if everything rests with the agency, but that is rarely so. Also ask what happens if a milestone shifts because of delayed input: does the end date move with it, or is there an arrangement? That belongs in the agreements, not in a discussion afterwards.

And after launch?

A website is not finished on launch day. You connect Search Console to the site to see how Google sees it, you track whether enquiries come in and you plan maintenance. What to arrange for that is in the maintenance checklist.

In summary

The duration of a website is determined by the quality of the input and the speed of decisions, far more than by the building itself. Want to know what that looks like for your project? Book a free intro call, look at our custom websites or our packages.

Sources

Reviewed on 28 October 2026 against the sources below. Rules and guidelines change; this article is general information, not legal or tax advice.

• Site Moves and Migrations (Google Search Central)
• Planning and Policies Overview (W3C Web Accessibility Initiative)
• Web Vitals (web.dev)
• SEO Starter Guide (Google Search Central)
• About Search Console (Search Console Help)

Book an intro call