Ask how long does it take to build a website and the honest answer is that it depends mostly on its scope, on how ready the content is and on how quickly decisions are made: a focused brochure site is usually a matter of weeks, while a large site with an online store, several languages or integrations takes a few months. If you are asking how long to build a website of your own, the most reliable answer comes from sizing each phase on its own, because each phase is lengthened or shortened by different things.
Last updated: 30 October 2026.
This guide covers the phases of a website project, a comparison by type of site, what makes projects run late, how a redesign differs from a new build, and how to shorten the schedule without cutting the parts that matter.
How long does it take to build a website, and what decides it?
Five things set the length of almost every website project. The first is scope: how many page types, templates and features the site must carry at launch. The second is content: whether the words, pictures and product data already exist or still have to be written and produced. The third is the brand: whether a finished identity is in place or is being decided alongside the site. The fourth is integrations: booking, payments, a CRM, an existing product database. The fifth, and the one buyers underestimate most, is the speed of decisions and feedback on the client side.
At Odduel, a creative and technology agency in Barcelona and São Paulo, we plan website development phase by phase for exactly this reason. A single figure for “the website” hides where the weeks really go, and it hides the part of the schedule that the client controls.
In short: a website is a sequence of phases, not one block of work. Discovery and design take a meaningful share of the time, the build and the content take the largest share, and testing and launch are shorter but cannot be skipped. Each phase has its own drivers. Fix those drivers early and the timeline becomes predictable.
What are the phases of a website project?
Most website projects move through the same six phases. They overlap in practice, and in a well-run project content work starts during design rather than after the build, but each phase has a distinct purpose.
- Discovery and scope.
- Structure, content plan and wireframes.
- Visual design.
- Build and integrations.
- Content entry, testing and quality checks.
- Launch and the first weeks after it.
Discovery and scope
Discovery turns “we need a new website” into a written scope: who the site is for, what visitors must be able to do, which pages and features the first version needs, what can wait, and which systems it must connect to. It takes a small share of the schedule and has the largest effect on everything after it.
What lengthens it: several stakeholders with different goals, no agreement on who the site is for, or a business that is still changing its offer. What shortens it: one person who can decide, a short list of what the first version must not include, and analytics or customer feedback from the current site.
Structure, content plan and wireframes
Here the site map is fixed, each page type gets a wireframe (a plain layout without the finished design), and every page gets a content brief: what it must say, what it needs in pictures, and which search query it should answer. This is also where redirects from old addresses are planned when a site already exists.
Its length follows the number of distinct page types, not the number of pages. Fifty articles share one template; a home page, a service page, a case study and a contact page are four.
Visual design
Visual design turns the wireframes into the finished look, usually starting with the home page and one inner page, then extending to every template and to mobile, tablet and desktop widths. Interactive moments, such as how a menu opens or how pictures appear on scroll, are designed here too.
A site built on an established identity moves faster than one where the logo, colours and type are still open. The number of review rounds matters more than the number of screens: each round needs time for feedback and time for changes.
Build and integrations
The build is where the largest share of the time usually goes. Developers set up the platform, build each template as a reusable part, connect forms, analytics, consent and any integrations, and make the site editable by the people who will run it. Choosing the platform early matters: the trade-offs are set out in a comparison of Webflow and WordPress.
In a good studio, AI now carries much of the repetitive production: component code, first drafts of tests, image preparation, first-pass translations. That shortens the build noticeably. It does not shorten the decisions about what the site should do, or the review of what was produced, which stay human work.
Content entry, testing and quality checks
Content is entered into the finished templates, then the site is checked on real devices and browsers: layout at every width, forms, speed, accessibility, search basics and redirects. Our website QA checklist lists what a careful pass covers before launch.
What lengthens it: content that arrives late or in the wrong form, many languages to check, and late changes to scope that reopen templates already tested.
Launch and the first weeks
Launch itself is short: the domain is pointed, the site map is submitted to search engines, and tracking is confirmed. The first weeks after it are part of the timeline too, because real visitors always find something worth adjusting, and search engines need time to read the new addresses.
How long does each type of website take?
The table compares common kinds of website by what drives their timeline. The durations are relative, from our experience of how projects of each kind usually run, not promises: a short brief turns them into dates for your project.
| Type of website | Typical scope | What drives the timeline | Relative duration |
|---|---|---|---|
| Landing page | One page, one goal, a form | Copy and the single design | Shortest: a matter of weeks |
| Brochure or company site | A handful of page types | Content readiness, review rounds | Short: several weeks |
| Content-led site or blog | Many articles on a few templates | Editorial plan, migration of old posts | Medium |
| Online store | Catalogue, cart, payment, shipping | Product data, payment and tax set-up, testing | Longer: a few months |
| Multilingual site | Any of the above in several languages | Translation, review in each language, localised search | Adds a phase to any type |
| Platform or web application | Accounts, dashboards, custom rules | Back-end logic, integrations, security | Longest: planned like software |
A landing page is the exception that proves the rule: its scope is small, so the time goes almost entirely into copy and one design. Its timeline is set less by the build than by how quickly the message is agreed.
Why do website projects run late?
Most delays come from outside the code. In our experience the same causes appear again and again.
- Content arrives late. Templates are ready and waiting for words and pictures that nobody was assigned to produce.
- Feedback is slow or contradictory. Several people review the same design at different times, and comments arrive in different places.
- Scope grows without anything leaving. A new feature is added mid-build, but no other feature is moved to a later phase.
- Integrations are tested late. Access to the booking tool, the shop system or the CRM arrives only when the build is nearly finished.
- The brand is not settled. Colours or the logo change after design is approved, which reopens every template.
- Legal and consent texts are left to the end. Privacy notice, cookie banner and terms are needed before launch and often need a lawyer’s review.
Each of these is easier to prevent than to fix. A named owner for content, one channel and one person for consolidated feedback, and a written list of what the first version does not include remove most of the risk.
Does a redesign take less time than a new website?
Not always. A redesign keeps the domain and often the content, which can save time, but it adds work a new site does not have: auditing the existing pages, deciding what to keep, migrating content, and mapping every old address to a new one with permanent redirects so that search rankings and inbound links survive. Google Search Central explains how to move a site with URL changes without losing its search history.
A redesign is quicker when the structure stays broadly the same and the content is in good shape. It is slower when the site has grown over years, holds hundreds of pages of uneven quality, or runs on a platform that exports content badly. Plan the migration as its own line in the schedule, not as a task for the last week.
How do legal requirements affect the timeline?
For a European business, some requirements belong in the plan from the start, because adding them at the end costs more time than building them in.
Since 28 June 2025, the European Accessibility Act applies to many consumer-facing services sold online in the EU, including e-commerce. Building to accessible standards from the first template is quicker than auditing and repairing a finished site; the W3C’s accessibility guidelines are the usual reference for what that involves.
Personal data collected through forms, accounts or analytics falls under the GDPR, which shapes the consent banner, the privacy notice and the choice of tools. For a shop, prices, taxes and checkout texts must be right in every country you sell to. None of these is long on its own, but each needs a decision from the client side, so each needs a place in the schedule.
How can you build a website faster without cutting quality?
Shortening the timeline is mostly about removing waiting time, not about working faster on the same scope. These steps make the biggest difference.
- Write a short brief before the first meeting. Goals, audience, must-have pages, examples you like and the date that matters.
- Name one decision-maker. Others can comment, but one person consolidates feedback and approves each phase.
- Start content on day one. Assign every page to an owner and write against the content briefs while design is under way.
- Fix the brand first. If the identity is changing, finish it before the site’s visual design begins.
- Launch a focused first version. Move secondary features and lower-priority pages to a second phase with its own date.
- Give access early. Domain, hosting, analytics, payment and integration accounts should be ready before the build starts.
- Agree review windows. A fixed number of working days for each round keeps the schedule honest on both sides.
Quality usually suffers when time is saved in the wrong places: skipping discovery, testing only on one device, or launching without redirects. Those shortcuts cost more time after launch than they saved before it.
What does a website timeline look like in practice?
When we built the Nothing To Eat website, the identity was complete before the site began, which let design and build follow straight on from it. The build did not have to wait on brand decisions, and the people who run it edit it through a simple dashboard rather than through code.
The same pattern holds for most of the sites we build: when the brand, the content owner and the scope are settled at the start, the schedule is set by the work itself. If you are still weighing what a site of your size involves, our guide to landing page design cost explains where the effort in a single page goes, and how much a website costs covers the budget side of the same decisions.
Questions people ask
How long does it take to build a simple website?
A simple website with a few page types, a contact form and content that is ready to use is the quickest kind of project, usually a matter of weeks from brief to launch. The real length depends on how fast feedback arrives and whether the brand already exists, more than on the build itself.
How long does it take to build an e-commerce website?
An online store usually takes a few months, because the catalogue, payment, shipping, taxes and order emails all need to be set up and tested. Product data is the most common cause of delay: clean names, prices, variants and photographs ready early make the shop timeline far more predictable than any technical choice.
Can a website be built in a week?
A single landing page with ready copy and an existing brand can sometimes be built in about a week. A full company site rarely can, because discovery, design approval, content and testing each need time for decisions and checks. Compressing those steps usually moves problems from before launch to after it.
How long does a website redesign take?
A website redesign often takes about as long as a new site of the same size, sometimes longer. The extra work is the audit of existing pages, the content migration and the redirect map that protects search rankings. It is quicker when the structure stays similar and the current content is in good condition.
Does AI make website development faster?
Yes, for the repetitive production: component code, test drafts, image preparation and first-pass translations. A studio that uses it well delivers in noticeably less time. AI does not speed up the decisions about what the site should say and do, or the human review of the result, which shape the schedule most.
When will I get a realistic timeline for my website?
A realistic timeline follows a short brief and a discovery conversation, once scope, content, brand and integrations are known. Before that, any figure is a guess. A good studio returns a phase-by-phase plan with its assumptions written down, so you can see which decisions on your side move the launch date.
If you are planning a new website or a redesign and want to know how long yours will really take, send us a short brief: we will come back with a phase-by-phase plan and the assumptions behind it. You can talk to us about your project, or read how we approach website development.
Further reading: Website redesign cost in 2027: what drives it, with a sample budget.
