How long does it take to build a website? For many business websites, a realistic project can take anywhere from a few weeks to several months. The biggest influence is rarely the number of pages alone. Content readiness, feedback, functionality, ecommerce, integrations, migration work and the speed of decision-making can all change the schedule.
This guide explains what businesses should expect when commissioning a website in 2026 and 2027, from the first discovery call to launch. It also includes an interactive timeline calculator to create an illustrative project estimate based on the type and complexity of website you are planning.
How Long Does It Take to Build a Website?
A small brochure website with prepared content may be designed, developed and tested in roughly 3–6 weeks. A larger bespoke WordPress website may take around 6–12 weeks, while ecommerce websites and projects involving custom functionality, large content migrations or multiple integrations can take 8–16 weeks or longer.
| Website type | Illustrative timeframe | Typical complexity |
|---|---|---|
| Landing page / microsite | 1–3 weeks | Small amount of content and limited functionality |
| Small brochure website | 3–6 weeks | 5–10 pages, forms and standard CMS features |
| Bespoke WordPress website | 6–12 weeks | Custom design, templates, blog, forms and integrations |
| Ecommerce website | 8–16+ weeks | Products, payments, shipping and transactional testing |
| Complex / integrated website | 12–24+ weeks | APIs, CRM, membership, booking or bespoke functionality |
These are planning ranges, not guarantees. A five-page site can take longer than a 30-page site if it requires complex functionality or content arrives slowly. An experienced team with clear requirements, prepared assets and prompt feedback can move efficiently through a substantial project.
Interactive Website Timeline Calculator
Choose a few details for an illustrative build range. It is a planning tool, not a fixed quotation: requirements, availability, content, feedback and technical discovery can change a real schedule.
What Actually Affects a Website Build Timeline?
Page count matters, but it is only one variable. The bigger question is how much work must happen before each page can be approved and launched. A project may require brand decisions, copywriting, photography, information architecture, user journeys, custom design, CMS development, accessibility work, SEO migration planning, analytics, CRM connections and stakeholder approval.
Writing and approving copy is one of the most common dependencies. A project can be technically ready while waiting for service descriptions, biographies or photography.
A bespoke visual system requires more exploration and review than adapting an established brand to a simple set of templates.
Bookings, memberships, filtering, calculators, APIs and automation need specification, development and testing.
If some terminology is unfamiliar, my website design glossary provides an A–Z reference covering design, development, UX, SEO, hosting and ecommerce.
The Main Stages of Building a Website
Discovery and requirements — approximately 2–7 days
The project begins by establishing what the website needs to achieve: audiences, services, competitors, conversion goals, required pages, existing technology and systems the new website must communicate with. Clear scope here reduces rework later.
Sitemap and content planning — approximately 2–10 days
The sitemap establishes the information architecture. Existing sites may require a content audit before deciding which pages should be retained, combined, rewritten or removed. Search intent and internal linking are best considered here rather than bolted on at the end.
Wireframes and design — approximately 1–3 weeks
Wireframes focus on hierarchy and functionality; higher-fidelity design establishes typography, colour, spacing, imagery and components. Not every project needs formal wireframes for every page, particularly where pages reuse an agreed system.
Development — approximately 2–6+ weeks
Approved designs become responsive templates and working functionality. On a WordPress website design project this can include custom templates, reusable components, forms, blog structures, custom fields, plugin configuration and editor controls.
Content population — approximately 1–3 weeks
Copy, photography, case studies and products are added to the templates. This can overlap development. Real content matters because paragraph length, heading structure and image proportions influence the finished layout.
Testing, approval and launch — approximately 3–10 days
The site is tested across relevant devices and browsers; forms and integrations are verified; redirects are prepared where URLs change; analytics is checked; and final approval is completed. Accessibility is more effective when considered throughout design and development rather than treated as a final-day checklist.
How Timelines Change by Website Type
Landing pages and small websites
A focused landing page can be completed quickly when its objective, copy and visual direction are already defined. “One page” can still become a substantial project if it includes animation, custom illustration, complex forms or campaign integrations.
Brochure websites
A service-business website often combines a homepage, about page, contact page, service pages, case studies and blog. Once the design system is established, many pages can reuse components, making the number of unique layouts more important than the raw page count.
Bespoke business websites
Bespoke projects need more time for discovery, visual exploration, component design and review. Businesses looking for local support can see my approach to web design in Leamington Spa.
How Much Does Content Affect the Schedule?
Content can be the difference between a four-week project and one that remains unfinished for months. Design needs to know what each page is communicating, and development cannot fully validate templates using placeholder copy alone.
Gather service information, company details, testimonials, team biographies, photography, brand assets and existing analytics early. Copy does not need to be perfect on day one, but there should be enough real material to establish hierarchy and structure.
Decide who approves copy and design, gather original brand assets, identify missing photography, agree the main services and audiences, and nominate one person to consolidate stakeholder feedback.
How Long Does a WordPress Website Take?
WordPress itself does not determine the duration. A simple brochure site can be fast, while a heavily customised installation with custom content types, advanced filtering, multilingual content, memberships or APIs can be substantial. A typical bespoke WordPress website might take around six to twelve weeks as a planning range.
Time spent creating reusable components, sensible editor fields and consistent templates can reduce ongoing management work after launch. The objective should not simply be to launch quickly, but to create a site the business can realistically maintain.
How Long Does an Ecommerce Website Take?
Ecommerce needs additional testing because the site processes commercial transactions. Products, variants, tax, shipping, discounts, accounts, transactional emails, stock, payments and order administration may all require configuration.
A smaller ecommerce website design project might take around eight to sixteen weeks. Large catalogues, complex shipping, subscriptions, trade pricing or ERP connections can extend that substantially. Product data is often the hidden workload: hundreds of products with inconsistent images, categories or descriptions require preparation before import.
Do Website Automation and Integrations Add Time?
Usually, yes—but they can save considerably more time after launch. A form that simply emails a business is straightforward. One that validates data, routes enquiries, creates CRM contacts, assigns sales owners, sends personalised emails and records attribution has more moving parts.
For projects involving website automation, integrations should be identified during discovery. Leaving them until the end can expose field mismatches, authentication requirements or third-party API limitations after the main site has already been built.
Testing should include failure scenarios too: duplicate records, missing data, expired credentials and temporary third-party outages all deserve consideration.
Website Redesigns and Migrations Take Extra Planning
Replacing an existing website can require more planning than launching a brand-new site because there is already something to protect. Existing search visibility, backlinks, indexed URLs, analytics history and customer journeys all need consideration.
Where URLs change, map old URLs to appropriate new destinations and implement redirects. Google Search Central recommends preparing and testing the new site, creating URL mappings, implementing redirects and monitoring the move. It also notes that search visibility can fluctuate temporarily while moved URLs are recrawled and reprocessed.
A redesign schedule should therefore allow time to crawl the old website, identify important URLs, map redirects, check canonicals and internal links, update the sitemap and monitor the site after launch.
Testing, Accessibility and Quality Assurance
Testing should not be compressed into the final afternoon. Navigation, forms, buttons, responsive layouts, links, CMS editing, analytics, ecommerce journeys and integrations can all affect one another.
Accessibility also benefits from early consideration. W3C guidance recommends integrating accessibility throughout the production process and evaluating early and regularly. Colour choices, component behaviour, semantic structure and keyboard interaction can therefore be addressed while the relevant work is created rather than repaired later.
Check representative phone, tablet and desktop widths, including menus, long headings, tables and forms.
Test keyboard navigation, focus, validation messages, buttons and interactive components.
Submit forms, test integrations, check links and run complete ecommerce journeys where relevant.
Hosting, DNS and the Launch Process
The website needs reliable infrastructure. Hosting influences performance, backups, security, support and deployment, so it should be decided before launch day. Read more about my website hosting service.
Launch can include DNS changes, HTTPS checks, cache configuration, redirects, removing staging restrictions, analytics verification and sitemap submission. Google's documentation notes that sitemap submission is a hint rather than a guarantee of crawling or indexing.
Where URLs permanently change, Google recommends server-side permanent redirects such as 301 or 308 where appropriate and advises avoiding unnecessary redirect chains. Migration planning therefore belongs in the schedule rather than being improvised at launch.
What Usually Delays a Website Project?
Development is not always the bottleneck. Projects often lose momentum between stages: a homepage waits two weeks for approval, photography is booked after development begins, product data arrives in inconsistent spreadsheets, or a new stakeholder joins late and changes the agreed direction.
| Potential delay | Why it matters | How to reduce it |
|---|---|---|
| Content not ready | Pages cannot be finalised | Audit and assign content before kickoff |
| Slow feedback | Every approval pushes the next stage back | Agree review dates and one feedback owner |
| Scope changes | New functionality may require redesign | Define requirements during discovery |
| Missing access | Domains and external systems cannot be configured | Gather access early |
| Unplanned integrations | APIs can require technical discovery | List external systems before development |
| Large migration | URLs and metadata require mapping and QA | Crawl the current site early |
How Can You Make a Website Project Faster?
The best way to shorten a project is not to skip design or testing. It is to remove waiting time and uncertainty. Arrive with clear goals, appoint a decision-maker, prepare content early and give consolidated feedback against agreed dates.
Reusing a coherent component system can accelerate development without making every page identical. Service pages can share a structure while using different imagery, case studies, FAQs and calls to action. Deciding which features genuinely need bespoke development also prevents time being spent rebuilding functionality an established platform already handles well.
Sustainability and performance can be considered during the build rather than as later clean-up. Efficient imagery, considered third-party scripts and appropriate infrastructure can support a lighter site. I explore this in my guide to sustainable web design.
What Happens After the Website Launches?
Launch is a milestone rather than the end of a website's useful life. The first days and weeks are a good time to monitor forms, analytics, search crawling, redirects and real visitor behaviour. Content can then improve around actual questions and opportunities.
Businesses should plan updates, backups, security maintenance and ongoing content. Publishing useful resources expands the questions a site can answer; my web design and digital marketing blog is an example of building a growing content library rather than treating a site as a static brochure.
It is also important to separate build time from the time needed to establish search visibility. A website can launch today without immediately achieving strong rankings. Search engines still need to discover and process pages, and competitive visibility depends on much more than publishing the site.
What Should a Website Project Schedule Include?
A useful schedule should show more than one final deadline. Break the project into discovery, content, design, development, population, integrations, QA, client approval and launch. Identify which tasks can happen in parallel and which depend on another task being completed first.
Client responsibilities should be visible too. If a designer has three days to produce a revision but the plan contains no deadline for approval, the schedule represents only half of the process. Shared milestones create clearer expectations on both sides.
If the website is needed for an event, campaign, premises opening or product launch, work backwards and retain contingency before the public deadline. A website that is “finished” at 4pm on launch day leaves no sensible room for final QA.
Frequently Asked Questions
Can a website be built in one week?
Yes, a small, clearly defined website can sometimes be produced quickly when content, branding and requirements are ready. One week leaves little room for extensive bespoke design, stakeholder review or complex integrations.
How long does a five-page website take?
A straightforward five-page business site might take roughly three to six weeks. Page count alone is not enough to estimate a project because content, design, functionality and approvals can have a larger effect.
How long does a WordPress website take?
A bespoke WordPress business website commonly falls around six to twelve weeks as an illustrative range. Simpler builds may be quicker; custom functionality and migrations can take longer.
How long does an ecommerce website take?
A smaller ecommerce project might take around eight to sixteen weeks. Large catalogues, unusual shipping requirements, subscriptions and external integrations can extend that substantially.
Should all content be ready before design starts?
Not necessarily, but the structure and key messaging should be developed enough for the design to use realistic content. Leaving all copy until the end often creates rework.
Does changing hosting add time?
It can. A hosting migration may require backups, database transfer, DNS changes, SSL configuration, caching and post-migration checks.
How long before a new website appears in Google?
There is no guaranteed indexing or ranking timetable. Sitemap submission is a discovery hint rather than a guarantee, and rankings depend on many additional factors.
Is it better to launch quickly and improve later?
A deliberately scoped first version can make sense. That is different from launching an unfinished or untested website. Essential content, accessibility, security, analytics and conversion journeys still deserve appropriate attention.
Useful External Resources
For deeper technical guidance, see Google Search Central's site migration documentation, Google's sitemap guidance and the W3C guidance on planning and managing web accessibility.
Final Thoughts: How Long Should Your Website Take?
For most businesses, the useful answer is not “as quickly as possible”. It is long enough to make good decisions, but structured well enough that the project keeps moving. A focused brochure website may need only a few weeks; a bespoke WordPress, ecommerce or integrated platform may need several months.
Good preparation is the biggest advantage. Define the purpose, prepare content, identify integrations, agree who approves the work and leave enough time for testing. That creates a more predictable project than setting an arbitrary deadline and squeezing every stage into it.
Planning a Website for 2026 or 2027?
I can help define the scope, build a realistic project plan and take your website from initial ideas through design, development, testing and launch.
Web Design Services →Ecommerce Web Design →
