blog / planning / 11 min read

How Long Does It Take to Build a Website? Real Timelines, Week by Week

How long does it take to build a website? Honest answer: anywhere from a few days for a template you fill in yourself to several months for a custom store with integrations. For a professional business site, the build itself is rarely the slow part. Content, feedback and decisions are. This guide shows what happens each week, what really sets the pace, and a calculator that shows how much of your launch date sits in your own inbox.

short answer

The short answer

Project typeTypical timeline with meWhat usually slows it down
Single landing page1–2 weeksCopy and offer not finalized
Small business site (5–10 pages)3–7 weeksContent and photos arriving late
Custom lead generation site8–10 weeksApprovals on design and messaging
WooCommerce store6–12 weeksProduct data, payments, shipping rules
Bilingual or custom-plugin build6–10 weeksTranslation, layout testing in both languages, custom logic

02 · planning

So, how long does it take to build a website? It depends on five things

People asking "how long to build a website" usually want one number. The truth is your timeline is the sum of five variables, and only two of them belong to your designer.

  • BIGGEST FACTOR

    Content readiness — Is your copy written, are your photos chosen, is your product data in a spreadsheet? If not, writing it becomes the critical path. Every time.

  • YOURS

    Feedback speed — Each review round waits on you. Two days per round versus ten days per round can be the difference between launching this month or next quarter.

  • SCOPE

    Page count and templates — Ten pages on two templates is quicker than ten pages on ten templates. Unique layouts take design and build time.

  • TECHNICAL

    Functionality — Booking, memberships, multiple languages, payment gateways, CRM integrations and custom plugins each add design, build and testing work.

  • PLATFORM

    Custom vs template — A theme gets you live sooner; a custom design takes longer but fits your business instead of the other way round.

Notice that the first two are entirely on the client side. That's not me passing the blame. It's the most useful thing you can know, because it means a big chunk of the timeline is under your control.

03 · planning

How long does it take to build a website, week by week

Here's what a typical custom website development timeline looks like with me, phase by phase. Durations are my own working ranges; your project gets a dated version in the proposal. You can see the full method on my process page.

  1. 01

    Discovery and planning — 3–5 days — We agree goals, audience, pages, features and the one action each page should drive. I map the sitemap and, for SEO, the keyword each page targets. Output: a scope and a dated website project timeline.

  2. 02

    Content gathering — runs in parallel — You provide or approve copy, photos, logos, testimonials you're allowed to use, and product data. If I'm writing copy, this is where drafts get reviewed.

  3. 03

    Wireframes and design — 1–2 weeks — Layout first, then visual design for key templates (homepage, service page, contact, blog). Usually two review rounds.

  4. 04

    Development — 2–5 weeks — I build the approved designs in WordPress: theme, responsive layouts, forms, integrations, speed and on-page SEO foundations.

  5. 05

    Content load and QA — 3–5 days — Real content goes in. I test on phones, tablets and browsers, check forms, fix broken links, and check speed against Core Web Vitals targets.

  6. 06

    Your review — 3 working days — You click through everything on a staging site and send one consolidated list of changes.

  7. 07

    Launch — 1–2 days — Domain and DNS, SSL, redirects from any old URLs, analytics, Search Console, sitemap submission. DNS changes can take up to 48 hours to propagate everywhere.

  8. 08

    Post-launch care — 2 weeks — I watch for errors, indexing issues and form delivery after go-live, and fix anything that slipped through.

Your developer controls the build. You control the calendar.

04 · planning

How long does it take to design a website?

Design is often treated as one step, but it's really three: structure, look, and approval. How long does it take to design a website? With wireframes, two rounds of feedback on the key templates and a clear brief, my range is 1–2 weeks. Without a brief, design rounds turn into discovery in disguise, and that's where timelines drift.

The single best way to speed up design is to arrive with opinions. Bring three sites you like and say why. Bring one you hate. "I like it" and "I don't like it" are fine; "can we see a few more options?" with no direction behind it adds a week.

Myth

A designer who quotes a shorter timeline is just faster.

Fact

Sometimes. More often the quote leaves out content, revisions, testing or launch tasks. Compare what's included in each phase, not just the total. My guide to hiring a web designer has the questions to ask.

05 · planning

How long does it take to build a professional website vs a DIY one?

How long does it take to build a professional website compared to doing it yourself? A DIY builder can have you live faster, but "live" and "working" aren't the same thing.

Option

DIY website builder

RecommendedMy pick

Professionally built site

If you're torn between platforms, my WordPress vs Wix comparison walks through the trade-offs. And if you only need one page to test an offer, a landing page instead of a full website can be live much sooner.

06 · planning

Calculate your own waiting time

Here's the part almost nobody puts in a timeline: waiting. Every review checkpoint pauses the project until feedback comes back. You can't change how long development takes, but you can see how much your own turnaround adds.

Interactive tool

Website timeline waiting-time calculator

This tool needs JavaScript to run.

07 · planning

How long does it take to build a ecommerce website?

Yes, people really type "how long does it take to build a ecommerce website" into Google, and it's a fair question, because stores are where timelines stretch the most. A store has everything a business site has, plus:

  • Product data: titles, descriptions, prices, variations, images and SKUs for every product. A spreadsheet that's ready on day one saves weeks.
  • Payments: gateway accounts need approval from the provider, which can take time you don't control. Apply early.
  • Shipping and tax rules: zones, rates, free-shipping thresholds and tax settings per region.
  • Legal pages: returns, privacy and terms, reviewed by you or your advisor.
  • Testing: real test orders on every payment method, emails, stock levels and refunds.

For a WooCommerce store, my range is 6–12 weeks depending on product count and integrations. More on how I build them on my ecommerce website development page. Planning the search side too? My guide to SEO for WooCommerce covers product and category pages.

08 · planning

Timeline killers to avoid

Things that quietly add weeks

  • No single decision-maker — Feedback from five people who disagree means rounds multiply. Nominate one person to consolidate.
  • Scope creep mid-build — "Can we just add a booking system?" after development starts means redesigning, rebuilding and retesting.
  • Content written last — Writing copy after design forces layout changes when the real words don't fit.
  • Piecemeal feedback — Ten emails over two weeks instead of one consolidated list slows every round.
  • Domain and hosting access lost — Nobody remembers the registrar login. Launch day waits while you recover it.
  • No timeline in writing — If your proposal doesn't have a dated website project timeline, there's nothing to hold either side to.

09 · planning

Get ready before kickoff

Tick what you already have. Every box you can tick before we start comes straight off your timeline.

Website kickoff readiness

Not sure where your current site stands before you rebuild? A free website and SEO audit shows what's worth keeping, which also shortens planning.

10 · planning

Timeline and budget move together

A faster timeline doesn't always cost more, but a bigger scope always takes longer. Adding pages, languages or integrations moves both numbers at once. My website cost guide breaks down what drives budget. My pricing page lists packages with typical timelines. If you want strategy, design, build and SEO handled as one project, see website design and development.

faq

How long does it take to build a website? FAQs

Something else? Ask me directly.

How long does it take to build a website for a small business?

For a five to ten page business site with content ready, my typical range is 3–7 weeks. The build is predictable; content, feedback speed and approvals cause most delays. Templates can be quicker but trade away flexibility, speed and SEO control. Your proposal should include a dated plan for each phase.

What is a typical website development timeline?

Most projects follow the same phases: discovery and planning, content gathering, wireframes and design, development, content load and testing, client review, launch, and post-launch checks. The length of each phase depends on scope and on how quickly decisions are made. A good proposal shows each phase with a date, not just a total.

Can a website be built in a week?

A single landing page or a simple template site can be, if the copy, images and decisions are ready on day one. A custom multi-page site with SEO, forms and testing done properly usually can't. If someone promises a full custom site in a week, ask exactly what they're leaving out.

What slows down a website project the most?

Content and feedback, almost always. Copy written late, photos not chosen, multiple stakeholders giving conflicting feedback, and changes in scope halfway through. Technical surprises happen too, like lost domain logins or slow payment gateway approvals, but they're easier to avoid with a kickoff checklist.

Does SEO add time to building a website?

Doing SEO foundations during the build adds very little: keyword mapping during planning, clean structure, fast templates, proper titles and redirects. Bolting SEO on after launch takes longer and often means redoing pages. Ranking itself takes time after launch and can't be guaranteed by anyone.

Is it faster to redesign an existing website?

Not always. You may reuse content and structure, but a redesign also needs redirects, careful URL mapping and SEO checks so you don't lose existing rankings. If the current content is strong, planning goes faster; if it needs rewriting, it can take as long as a new build.

free audit

Want a real date, not a guess?

Tell me what you need and I'll send a dated plan for each phase, so "how long does it take to build a website?" stops being a guess and becomes a date in your calendar, with a clear list of what I need from you along the way. Start with a free audit of your current site, or book a quick call.

Free audit · No obligation · Reply within one business day

keep reading