How long does it take to build a website?

Building a website takes two to five days for a simple page you put together yourself, four to eight weeks for a showcase site made by a professional, and two to four months for an online store. A fully custom site often takes three to six months. The timeline depends on three things above all: the type of site you want, the person or tool building it, and above all your availability to supply the text, the images and the approvals at the right moment. That last point, almost never mentioned, is usually what decides whether a project runs six weeks or six months.

How long does it take to build a website?

A professional website is generally built in four to eight weeks for a showcase site, and you should count several months as soon as it involves selling online or genuinely specific features. That wide range comes down to what you put behind the word “site”. A single page presenting a business has nothing to do with a store of a hundred products wired to a payment and delivery system, and the two clearly don’t need the same amount of work.

To give you concrete reference points, here is how timelines break down by the type of site and by the way you build it. The table below starts from the moment the project is scoped, meaning once you know what you want and the content begins to arrive.

These durations match serious work, not a rushed version put online just to say it exists. A freelancer who quotes you eight weeks for a showcase site isn’t working more slowly than one who promises two weeks: they’re probably including the time to think through the structure, polish the design and prepare the search ranking, where the other hands over a shell you’ll have to redo. How long a site takes to build is often a good sign of how much care went into it.

You also have to separate two durations that people almost always confuse. There is the actual work time, meaning the number of hours spent building the site, and there is the calendar time, meaning the number of weeks between the first conversation and the launch. A showcase site can represent thirty or forty hours of real work and still stretch over six weeks of calendar time, simply because you have to wait for your text, let a mockup sit between two rounds of feedback and fit the exchanges into already full schedules. When a professional quotes you a timeline, they’re talking about the calendar, not the hours, and it’s normal for the two to be very different.

The online store deserves a mention of its own, because it’s the type of site whose timeline surprises people the most. Where a showcase site presents your business, a store has to handle a sale from start to finish, and it’s everything around that sale that takes time. You have to create a page for each product with its description, price and photos, connect one or more payment methods, set shipping fees and zones, and plan how stock is managed. A store’s design isn’t much longer than a showcase site’s, but this groundwork around the products is why you count in months rather than weeks as soon as you sell online. A useful rule of thumb is that the more products you sell and the more custom your checkout, the longer the store takes, so a small shop with ten products and a standard payment tool lands near the bottom of that range, while a large catalog with several delivery options and stock synced to a warehouse sits near the top.

What are the steps and how long does each one take?

A website project almost always follows the same broad steps, and each one has its own duration. Understanding this breakdown helps you know where you stand and spot the moments when it’s you, not the provider, holding the schedule in your hands.

Everything starts with scoping, the phase where you define what the site is for, who it speaks to and what it should contain. Writing a real website design brief takes one to two weeks, and it’s time very well spent, because a project poorly scoped at the start always goes off the rails later. Next comes the visual design, where you draw what the site will look like. The website mockup also needs one to two weeks, between the first proposal and your feedback.

Writing the content slips in alongside all this, and it’s often the most unpredictable step. Gathering the text, choosing the photos and preparing the information can take from a few days to several weeks depending on whether you had everything on hand or you’re starting from a blank page. Development and integration, meaning the technical build of the site from the approved mockup, then take two to four weeks for a showcase site and more for a store. You finish with a testing and correction phase of about a week, where you check that everything works on mobile as well as on a computer, before the launch itself, which only takes a day or two. Put end to end, these steps explain why a serious showcase site rarely needs less than a month of real calendar time.

To make this concrete, take the example of a five-page showcase site handed to a professional, with a responsive client. The first week goes to scoping and the opening exchanges. The second and third weeks go to the mockup and your feedback, while you gather your text alongside. The fourth and fifth weeks are spent on development and on placing your content into the site. The sixth week goes to testing, the last corrections and the launch. Six weeks, then, for a client who answers quickly. The same project, with text arriving in dribs and drabs and approvals taking ten days each, easily reaches three months for exactly the same work. That’s the best illustration of the fact that the timeline isn’t only about the provider.

What really stretches a website project?

What makes a project drift is almost never the speed at which the developer works, but the waiting time between steps. A site can sit blocked for three weeks simply because the text hasn’t arrived or because an approval is stuck in an inbox. This reality throws a lot of people who assume the timeline depends only on the provider.

Content is by far the main culprit. A professional can build a site’s structure in a few days, but they can’t guess for you what you want to say, or take the photos of your workshop or your dishes. As long as those pieces are missing, the site moves along half empty and the schedule stretches. The second culprit is the back and forth of approvals. Every time a mockup or a page waits a week for your opinion, that’s a week added to the project, and those waits add up fast across the whole journey.

Changes of mind along the way weigh heavily too. Deciding mid-build to add a store, to redo the whole site structure or to change visual direction mechanically pushes back the launch, sometimes by several weeks. That doesn’t mean everything has to be locked, but that these decisions are better made during scoping, when they cost only a conversation, than during development, when they cost finished work that has to be redone. A project where you answer quickly, where the content is ready and where the important decisions were made early moves twice as fast as an identical project left waiting.

How can you build your website faster?

The best way to go faster isn’t to push the provider, but to prepare your part of the work before the project even starts. Most of the time you can save comes down to what you have on hand the day the build begins.

Gather your text early, even in rough form. You don’t need to write like a professional copywriter, you need to say clearly who you are, what you offer and why someone should choose you. A provider can then rework that text, but they can’t start from nothing. Prepare your photos the same way, along with your logo if you have one, and the list of pages you think you’ll need. Thinking ahead about your website structure avoids discovering mid-project that a whole section is missing.

Pick a single point of contact to approve the steps, too. When five people have to weigh in on every mockup and never agree, each approval becomes a negotiation that lasts several days. One person who decides, even after consulting the others, moves the project along far faster. Finally, block time in advance for your feedback, rather than dealing with the project whenever you get a spare moment. A site doesn’t wait any better than another task: it just waits until you deal with it, and the day you decide to give it real attention, everything unblocks.

One last habit saves more time than any other, and that’s setting a realistic launch date at the start and working backwards from it. When a project has no end date, it drifts, because there’s always a reason to add one more page or polish one more detail. A date forces the useful decisions and keeps the small ones from swallowing whole weeks. Agree with your provider on when the site should be live, then treat that date as a real deadline on your side too, with the content and the approvals it implies. A site is almost never late because the work was too big. It’s late because nobody ever drew a line and said this is when we go live.

Build it yourself or hire a professional: what does it do to the timeline?

Building your own site seems faster on paper, but the time you think you’re saving, you mostly spend learning. A ready-made tool or an AI website builder gives you a base in a few hours, which impresses at first, except the base isn’t the site.

When you build your site yourself, the time doesn’t disappear, it simply moves. You aren’t paying a provider, but you spend your evenings figuring out the tool, fixing a menu that displays badly on mobile, working out why an image is blurry and guessing what Google expects. For a business starting on a tight budget, it’s an honest choice, and a simple page made this way can be enough for a few months. But count that time for what it is: dozens of hours you aren’t spending on your actual work.

Hiring a professional costs more money up front, but hands those hours back to you and spares you the expensive mistakes. The quoted timeline is longer because it includes real work on structure, design and search ranking, not because the work drags. There’s also a point people often forget: the time you spend fixing a homemade site ends up costing a lot in energy. A page that displays badly on a phone, a form that sends nothing, an unexplained slowness, these are all small problems you’ll have to solve alone, in the evening, without knowing where to begin. A professional settles them in a few minutes because they’ve hit them a hundred times before. So it comes down to where you want to spend your time more than to raw speed. If you’d rather keep it for your clients, a custom-built website will save you far more than the few weeks of lead time it needs. If you have time and the urge to learn, doing it yourself is still a fair option to start with.

The site is live: what keeps going after that?

The launch isn’t the end of the project, it’s the start of the part that decides whether your site is worth anything. Many people think a finished site will climb Google on its own, when visibility is built over the months that follow, not on the day you publish.

Search ranking takes patience, because a site that has just been published has no track record in Google’s eyes, and it needs time to earn the trust that will lift it up. In practice, getting your site to rank on Google and seeing regular visitors arrive usually takes three to six months of content published steadily, sometimes more in a competitive market. That’s one more reason to launch the site early rather than wait for the perfect version: the earlier it’s published, the earlier the ranking clock starts.

The content keeps living too, and a site left frozen for two years sends a poor signal, to your visitors as much as to Google, while a site fed with articles, new work and up-to-date information keeps climbing. That’s why it’s better to see the launch as a starting line than a finish line. On the day you publish, you have a solid site that presents your business, and that’s already a lot. But the real results, the visitors arriving through Google and the enquiries landing in your inbox, are built over the months that follow, as you add useful content and the site gains age. Planning a little time each month for this upkeep from the start, rather than treating the site as something delivered once and for all, completely changes its return over time. So a site’s real timeline doesn’t stop at the launch: it’s only just beginning.

Planning your website project without nasty surprises

The best way to avoid suffering the delays is to anticipate them. You now know that a serious showcase site needs four to eight weeks, that a store is measured in months, and that the largest share of that time comes down to your ability to supply content and approve quickly. A project is never late by chance: it’s late because a step is waiting for something, and most often, that something depends on you.

Before you start, take the time to define precisely what you want, to gather your text and images, and to choose the option that fits both your budget and your availability. If you’re still unsure what the project will cost you, the article on how much a website costs covers the budget side alongside this one, and the article on how to create a website details each step. And if you’d rather hand the project to someone who’ll hold the timeline because they scoped things from the start, let’s talk about your project: the best way to know how long your site will take is still to discuss it based on what you actually want.