How Long Does It Take to Build a Website?
Key takeaways
- A simple site usually takes two to three weeks; a five-to-eight-page site takes four to six.
- The actual coding is the shortest part — most of the time goes on waiting for content.
- Having copy and photos ready at the start often halves the project time.
- Offers like 'website in 48 hours' deliver a filled-in template, not a site built for you.
- After launch it takes further weeks before Google finds the site fully.
The honest answer to "how long does a website take?" disappoints many people, because it doesn't start with a number. It starts with a question back: how quickly will your copy arrive?
Coding a typical business site is often done in one to two weeks. The project still takes four to six. The difference is waiting — for content, for photos, for decisions.
That isn't a criticism of clients. You have a business to run, and the website isn't the only thing on your desk. But once you understand where the time goes, you can steer it.
Contents
Realistic time frames
As a first orientation, assuming normal collaboration:
| Project | Duration |
|---|---|
| Simple site (one-pager) | 2–3 weeks |
| Site with 5–8 pages | 4–6 weeks |
| Bilingual site | 6–8 weeks |
| Site with bookings, a shop or integrations | 8 weeks or more |
These figures assume content arrives promptly and feedback doesn't sit for weeks. Both shift the numbers more than any technical requirement does.
Why a second language costs noticeably more time than just the translation is explained in the article on multilingual websites.
Where the time actually goes
Take a five-to-eight-page site and look at how the weeks divide up.
Call and proposal — about a week. A conversation, then a proposal. In between, your time to think it over. This week is often forgotten, but it belongs to the project.
Gathering content — one to two weeks. This is the biggest unknown. Copy, notes, photos, logo, access. If you have it ready, you skip this phase almost entirely.
Structure and copy — about a week. Your content becomes a structure and finished copy. You read and give feedback.
Development — about a week. The site gets built. This is the part most people assume takes longest. It's often the shortest.
Feedback — about a week. You see the site, raise requests, it's adjusted. Usually one or two rounds.
Launch — a few days. Connect the domain, check, go live.
Notice: of five weeks, perhaps one goes on what people picture as "building a website". The rest is coordination and waiting.
What speeds a project up
The levers sit mostly with you — which is good news, because you can pull them.
Content at the start. By far the biggest lever. Bring notes, photos and logo to the first call and you often halve the duration. What exactly to prepare is in the article on preparing a website project.
Quick feedback. A draft waiting three days for a reply adds three days to the project. The arithmetic is that simple.
One person decides. If every draft goes through several hands, the rounds double.
A clear goal. If you know what the site should achieve, there's less debate about details.
What slows a project down
The usual brakes, in order of frequency:
Copy doesn't arrive. The classic. "I'll send it next week" becomes three weeks.
The direction changes midway. Realising after the second draft that you actually wanted something else means partly starting over.
Access is missing. The domain sits with a former provider nobody can reach. That can cost weeks if it's only noticed just before launch.
New requests during development. An extra page here, a feature there. Small individually, noticeable together — and often a reason for additional charges.
"Website in 48 hours" — what's behind it
These offers exist, and they aren't dishonest. But it's worth understanding what you get.
In 48 hours you don't get a site built for you. You get a ready-made template with your name, logo and some copy dropped in. For some purposes that's entirely enough — much like a site builder.
What's missing is the engagement with your business, your customers and what the site should achieve. That's exactly what takes time, and exactly what separates a site that exists from one that brings in enquiries.
Whether a template serves you better than a developed site depends on your situation. There's an honest weighing-up in the comparison of site builders and developers.
Launched doesn't mean found
The last point surprises almost everyone: once the site is online, it's far from visible on Google.
Indexing a new site takes anywhere from a few days to several weeks. With a brand-new domain it tends to take longer, because Google doesn't trust it yet. Before the site appears near the top for competitive terms, months often pass.
Plan for that. If you need enquiries by a fixed date — an opening, say — don't launch the day before. Launch several weeks ahead.
Why a new site isn't found at first and what helps is explained in the article on indexing. And if you're replacing an existing site, it's worth knowing the particulars of a relaunch, where the concern is keeping visibility you've already built.
Time and money are linked
A project that takes twice as long as planned rarely costs twice as much — but it often costs more. Extra rounds, new requests, a change of direction: all of it takes working time.
The reverse holds too: good preparation saves not just weeks but money. How a website's costs break down is in the price breakdown.
Frequently asked questions
How long does a simple website take? A one-pager usually takes two to three weeks, a five-to-eight-page site four to six. What matters is less the technology than how quickly copy and photos are available.
Why does it take so long if the coding is quick? Because the coding is only a small part. Most of the time goes on gathering content, feedback and decisions. Of five weeks, often only one goes on actually building.
Can I speed the project up? Yes, mainly through preparation. With notes, photos and logo ready at the start and quick responses to drafts, you often halve the duration.
Are offers like 'website in 48 hours' legitimate? Usually yes, but what you get is a filled-in template, not a site built for you. For some purposes that's plenty — for a site meant to bring in enquiries deliberately, often not.
Is my site on Google straight after launch? No. Indexing takes days to weeks, longer for new domains. Reaching good positions for competitive terms often takes months.
When should I start the website if I'm opening on a fixed date? Several weeks before the date, so there's time for indexing after launch. Launching the day before brings hardly any visitors to the opening.
In short
The coding is the fastest part of a website project. The duration is set by content, feedback and decisions — and those sit largely with you.
Expect two to six weeks depending on scope, prepare your content to hit the lower end, and allow further weeks after launch before Google finds you.