How long does it take to build a website? A realistic timeline

If you are planning a launch, a campaign or a funding round around a new website, the timeline matters as much as the price. And timelines are where expectations most often go wrong: a client imagines two weeks, the studio says ten, and both are partly right.

The short answer: a simple template website can be live in one to three weeks. A custom-designed small business site typically takes four to eight weeks. A larger marketing site with strategy, copywriting and a CMS takes eight to fourteen weeks. Ecommerce stores and web applications often take three to six months. The rest of this article explains what fills that time, so you can plan around it and avoid the delays that have nothing to do with design or code.

Typical website timelines by project type

• DIY site on a website builder: a few days to a few weeks, depending on how quickly you write content.
• Template site set up by a professional: 1 to 3 weeks.
• Custom small business website, 5 to 10 pages: 4 to 8 weeks.
• Marketing website with strategy and copy, 10 to 30 pages: 8 to 14 weeks.
• Website redesign with content migration: 8 to 16 weeks.
• Ecommerce store: 6 weeks for a themed store, 3 to 6 months for a custom one.
• Web application or platform: 3 months to a year or more.

Notice that design and development are rarely the longest parts. The calendar is mostly filled by decisions, feedback and content, and those depend on both sides of the project.

A six-week website project, week by week

To make this concrete, here is how a typical six-week custom website runs at a small studio like ours. Larger projects stretch each phase, but the order stays the same.

Week 1: Discovery and strategy

The first week is about understanding the business before drawing anything. That means a kickoff workshop, a look at analytics and search data, conversations about customers and competitors, and agreement on what the site must achieve. The output is a sitemap, a list of pages with the job each one does, and a clear definition of success.

Skipping this week is the most common way to lose three later. A design built on assumptions gets torn up when the assumptions turn out to be wrong.

Weeks 2 and 3: Wireframes and design

Wireframes come first: simple layouts that settle structure and content order without the distraction of colour and imagery. Once those are approved, the visual design follows, usually starting with the homepage and one inner page to set the direction, then rolling out to the remaining templates. Most projects include two rounds of feedback here.

Weeks 4 and 5: Development

The approved designs are built into a working website on a staging link you can click through anytime. Pages are built responsive from the start, the CMS is set up so you can edit content yourself, and forms, analytics and integrations are connected. Content goes in as it is ready.

Week 6: Testing and launch

The final week covers testing on real devices and browsers, speed optimisation, accessibility checks, SEO setup, redirects from any old URLs and a final content review. Launch itself is usually a short, planned moment: switch the domain, check everything works on the live address, submit the sitemap to Google and watch the first day’s data.

What slows a website project down

In our experience, technical problems almost never cause serious delays. These do:

• Content that isn’t ready. The number one cause of late launches, by a wide margin.
• Slow feedback. A week waiting for comments on a design is a week added to the end of the project.
• Too many decision makers. Every extra stakeholder adds a round of opinions, and late opinions are the most expensive kind.
• Scope creep. New pages or features added mid-project, each small, together significant.
• Unclear goals. If nobody agreed what the site is for, every review becomes a debate about it.
• Third parties. Waiting for access to a domain, a hosting account or an old developer who holds the keys.

Websites are rarely late because building them is slow. They are late because waiting is slow.

How to speed up your website project

You can’t compress design and development much without hurting quality. You can remove most of the waiting. Before kickoff:

• Start writing content now. Even rough drafts give the designer real material to work with.
• Name one decision maker who can approve work, and agree how others feed in.
• Gather access in advance: domain registrar, hosting, analytics, social accounts, brand files.
• Block feedback time in your calendar when each design round is due.
• Decide what can wait for phase two. Launching a focused site sooner usually beats launching everything later.

How long does a website redesign take?

Redesigns usually take longer than new builds of a similar size. There is existing content to audit, rewrite or migrate, existing search rankings to protect with a redirect map, and often internal history around why the current site is the way it is. Budget eight to sixteen weeks for most business redesigns. If you have hundreds of blog posts or product pages, the migration alone can take several weeks. Our website redesign SEO checklist covers that part in detail.

How long does it take to build an ecommerce website?

A store on Shopify using an existing theme, with a modest catalogue, can launch in four to six weeks. A custom-designed store with many products, variants, subscriptions or integrations with inventory, shipping and accounting systems typically takes three to six months. Product data is the equivalent of content on a marketing site: gathering clean photos, descriptions and specifications for every product takes longer than anyone expects.

How long does it take for a new website to show up on Google?

Google can index a new website within a few days of launch, especially if you submit a sitemap in Google Search Console. Ranking well is another matter. A brand new domain often takes three to six months to rank for competitive searches, and sometimes longer. A redesign of an existing site with proper redirects should keep most of its rankings, with a short period of fluctuation while Google re-crawls the pages.

When a quick launch makes sense

Sometimes speed genuinely matters more than polish: a product announcement, a funding round, a seasonal campaign. In those cases, a good approach is to launch a strong single page or a small core site first, then build out the rest in a second phase. You get something live and credible on the date that matters, without rushing the parts that need care.

Frequently asked questions