How Long Does It Take to Build a Website?

The short answer

A small site built from a theme can take a few weeks; a custom site or web application takes months. Inside that, two projects of the same size can finish far apart, because the slowest part is rarely the build. It is usually waiting: for content, for feedback, for a decision someone else has to sign off.

So when you ask a developer "how long?", the useful answer is not a single date. It is a plan with each phase, what it needs from you, and when. Ask for that, and the timeline becomes something you can manage rather than something that happens to you.

The phases of a website project

Most website projects, including the ones we build, run through the same steps. Each one has its own output and its own reasons to stretch.

1. Discovery

Goals, visitors, the content you have and the content you need, and what a successful launch looks like. This is short when one person can answer the questions and has a clear goal, and longer when several people or departments need to agree.

2. Plan

A sitemap and the key page layouts, so you can see the structure before any design work. A site with a handful of page types plans quickly; one with many audiences, services or locations takes more thought.

3. Design

The main pages in your brand, reviewed on phone and desktop. The number of design rounds is the biggest variable here, and it depends on how clear the brief is and how many people give feedback. Starting from an existing theme or design system is faster than a fully bespoke design.

4. Build and content

The site is built on a private staging copy you can click through, and the content goes in. Build time grows with the number of different page layouts and with features such as booking, a shop, memberships, multiple languages or integrations with other systems. Content entry grows with the number of pages, and with whether content is new or moved from an old site.

5. Test and launch

Speed, forms, accessibility, redirects and search basics are checked before the site goes live. Our website launch checklist lists what we check. Fixing what testing finds is part of this phase, so plan for it rather than treating the launch date as the day building stops.

6. After launch

The first days after launch are for watching: errors, forms, analytics and search. Ongoing care starts here.

What makes a project take longer

• Scope that grows. New pages or features added halfway through push everything after them. Keep a list for phase two instead.
• Custom functionality. Features that proven plugins or services cannot cover need to be designed, built and tested from scratch.
• Integrations. Connecting to a CRM, booking engine, stock system or payment provider depends on that system's documentation, access and test accounts, which are often outside your developer's control.
• Content migration. Moving many pages from an old site, cleaning them up and mapping old URLs to new ones takes time. If the site already earns search traffic, it is time well spent; see redesigning without losing search traffic.
• Many decision-makers. Each extra reviewer adds a round of feedback, and conflicting feedback adds another round to resolve it.

What depends on you

This is the part most timelines quietly assume. Your developer can only move as fast as these arrive:

• Content. Page text, photos, team bios, product details, prices and opening hours. Content is the most common cause of delays. Decide early who writes each part, and start before design is finished.
• Brand assets. Logo files, colours and fonts, ideally in the formats your designer asks for.
• Feedback. Clear, consolidated feedback in one place, from one person who can make the final call.
• Access. Logins for the domain registrar, DNS, current hosting, analytics, Search Console and any third-party services the site will use. Hunting for an old password can hold up a launch more than any bug.
• Approvals. Sign-off on the design, the content and the launch date by whoever needs to give it.

A good proposal marks these steps clearly. If yours does not, ask; it is one of the questions in our guide to choosing a web developer.

Outside steps with their own timelines

Some steps are run by other organisations and cannot be hurried by anyone on the project. Start them early.

Domains

If you need to move a domain to a different registrar, check the rules first. Under ICANN's transfer policy, a registrar may deny a transfer within 60 days of the domain's initial registration or a previous transfer, or while a 60-day change-of-registrant lock applies. Your registrar must give you the transfer authorisation code within five calendar days of your request. You do not need to move the domain to launch a site; pointing its DNS at the new hosting is enough.

Google Search

Launching a site does not put it in Google straight away. Google's own guidance is that "it can take a few weeks for Google to notice a new site, or any changes in your existing site" (Google Search Central), and that crawling after you request it "can take anywhere from a few days to a few weeks" (Ask Google to recrawl your URLs). Submitting a sitemap in Search Console on launch day helps Google find your pages.

When you replace an existing site with new URLs, Google says a small to medium-sized website "can take a few weeks for most pages to move, and larger sites take longer", and recommends keeping redirects from the old URLs "generally at least 1 year" (site moves with URL changes).

Google Business Profile

For a local business, a verified Google Business Profile often matters as much as the website. Google says verification reviews take up to 5 business days, and if you verify by postcard, most codes arrive within 14 days. Our SEO basics guide covers what to do with the profile once it is live, and our Google Business Profile guide walks through setup and verification.

How to keep a project on schedule

1. Write a short brief before asking for quotes: goals, pages, features, systems, who provides content, and your deadline.
2. Name one decision-maker who gathers feedback and gives the final answer.
3. Start content on day one, in parallel with design, not after it.
4. Launch the essentials first. Put nice-to-have pages and features in a second phase with its own date.
5. Agree feedback turnaround in the plan, the same way the developer commits to delivery dates.
6. Work back from fixed dates. If the site must be live for an event or campaign, say so at the start, and leave room for testing and fixes before it.

Frequently asked questions

How long does a small business website take?

A small site built from a theme can take a few weeks; a custom site or web application takes months. Content readiness and how fast feedback comes back often matter as much as development time.

Why do website projects run late?

Most often because content, feedback or approvals arrive later than planned, or because new pages and features are added halfway through. A plan that marks what is needed from you, and when, prevents most of it.

When will my new website show up on Google?

Google says it can take a few weeks for it to notice a new site, and that crawling can take from a few days to a few weeks. Submitting a sitemap in Search Console on launch day helps.

Can we launch first and add pages later?

Yes, and it is often the fastest route. Launch the pages and features that matter most, then add the rest in a planned second phase.

Do I need to transfer my domain to launch a new site?

No. The domain can stay with your current registrar; it only needs its DNS records pointed at the new hosting.

Planning a new site? See how we approach website development, read how to write a project brief and what drives website cost, or email info@creahive.com with your brief and your deadline.