So, how long does it take to build a website? A simple business site can be ready in days, a bilingual company site often takes a few weeks, and an online store or custom platform can run for months. The build itself is rarely the slow part. Most of the time goes on waiting: for content, for photos, for approvals and for access to the domain. This guide walks through each stage, gives general time ranges by type of site, and shows you what you can do to keep your own project short.

In short:
- There is no fixed answer. As a general estimate, a small company site takes from about a week to a few weeks, a store from one to three months, and a custom platform several months. Your scope decides where you land.
- Working time and calendar time are different things. A one-day design task becomes a week-long delay if it waits a week for feedback.
- Content, approvals, domain access, payment set-up and third-party integrations cause most delays, and most of them sit on the business owner's side.
- Count the timeline from the day your information is complete, ask for dates for each stage in writing, and name one person who approves.
- Launch is not the finish line for search. Google says crawling can take from a few days to a few weeks, and nobody can promise a date.
In this guide
How long does it take to build a website? The short answer
Ask three providers how long your website will take and you may hear "a week", "about a month" and "it depends". All three can be honest. The first is counting working days once everything has arrived. The second is counting the whole project from the first meeting. The third has not yet understood what you need.
It helps to separate two kinds of time. Working time is the hours someone actually spends planning, designing, building and testing. Calendar time is the number of days between the start and the launch. On most projects that run late, calendar time is far longer than working time, because the work keeps stopping while it waits for something.
Three things decide the length of any website project:
- Scope. How many pages and languages, and whether you need a store, bookings, online payments or a link to another system. Our guide on how many pages a website needs helps you size this part.
- Readiness. Whether your text, photos, logo and contact details exist today, or still have to be written and collected.
- Decisions. How many people must approve, how quickly they reply, and how many rounds of feedback you go through.
Scope is set by your type of business. Readiness and decisions are largely in your hands. That is why two websites of the same size can launch weeks apart.
Websites are rarely late because of design. They are late because of the gaps between stages.
The stages of a website project, and what makes each one longer
Every provider names the stages a little differently, but the order is much the same. Here is what happens in each one, what you are asked for, and what usually stretches it.
Brief and scope
You explain what the business does, who the customers are and what a visitor should do on the site. Together you agree the pages, languages and features. This stage is short when your needs are written down before the first call, and long when meetings end without decisions. Our website brief template turns it into a single conversation.
Content
Page text, service descriptions, photos of your work or products, the logo, phone numbers, the address and opening hours. This is the stage that varies most. If the provider writes the content from your information, it moves quickly. If you write and review every page with your partners, it can take weeks.
Structure and design
The menu and page order come first, then the look: colours, fonts, the layout of each section and where the contact buttons sit, with the phone layout designed first. Some providers show a static mock-up before building. Others design directly on a working preview, which saves a full approval round.
Build
The design becomes a working site: pages, forms, the WhatsApp button, the map, the second language. A brochure site sits at the short end. Anything with custom code or a connection to an outside system sits at the long end.
Review and changes
You check the site on a preview link and send your comments, the changes are made, and you check again. Making the changes is usually quick. The stage drags when comments arrive in pieces over several days, when partners disagree, or when new ideas appear that were never in the plan.
Testing
The site is tried on phones and computers, forms are sent for real, and links, images and speed are checked. It is a short stage, but skipping it causes most of the awkward problems people find after launch. Our website launch checklist lists the checks in detail, so we will not repeat them here.
Launch on your domain
The site moves to your domain, the SSL certificate is switched on and the site is connected to Google Search Console. The work is quick. DNS changes then need time to reach everyone, often a few hours depending on the settings. The real delay comes when nobody knows where the domain is registered, or the login sits with a former employee or an old designer.
Add the stages together and the same small company site can take two weeks or two months. The difference is rarely in the build. It is in content and review, the two stages that depend on you.

Typical timelines by type of website (general estimates)
The type of site sets a floor. No amount of preparation will put an online store with hundreds of products live in a few days. The ranges below are general market estimates, not statistics and not promises from any provider. They assume a project that runs normally, counted from the day your information is complete. Use them to judge whether a schedule you are offered sounds realistic.
| Type of website | General estimate (depends on scope) | What usually makes it longer |
|---|---|---|
| One page or an ad landing page | A few days to about a week | Persuasive copy, connecting the form to ad tracking |
| Company site, 5 to 10 pages, one language | About one to four weeks | Writing the content, several people approving |
| Company site in Arabic and English | About two to six weeks | Two sets of copy to write and review, right-to-left and left-to-right checks |
| Service site with bookings or advanced forms | About three to eight weeks | Booking rules, confirmation messages, calendar or payment links |
| Online store | About one to three months | Product data and photos, payment gateway activation, shipping set-up |
| Custom platform or web system | Several months or more | User roles, custom code, long testing |
Treat every row as a starting point for a conversation, not a quote. A provider who knows your scope should be able to give you a date for each stage, and explain what would move it.
Why a bilingual site takes longer
A bilingual site is really two sites sharing one design. Each text needs a second version written for that audience, not a word-for-word translation, and each page needs checking in both directions, because long headings, buttons and tables behave differently in Arabic and English. If different people review the Arabic and the English, add time for both. See our bilingual website design guide for what that work involves.
Why stores and platforms are measured in months
For a store, the theme is not the slow part; the data is. Every product needs a name, a description, photos, a price and options such as size or colour. Two hundred products means two hundred product cards to prepare and check. Payment gateways also review your business before they switch on live payments, and that review is outside the designer's control. Platforms add accounts, permissions and many cases to test, so they are usually planned in releases: a first version with the essentials, then additions.
What delays a website project, and how to avoid it
Ask any web designer about their late projects and you will hear the same causes. Knowing them in advance is the easiest way to avoid them.
Content that is "coming soon"
The services page waits for text, the projects page waits for photos. Send what you have now, even if it is incomplete, or choose a provider who writes the content from your information.
Too many approvers
Two partners, a marketing manager and a relative who is asked for an opinion, each replying on a different day. Name one person who collects views and sends the final answer.
Feedback in pieces
A comment in the morning, another at night, a third two days later that cancels the first. Review the whole site once and send one numbered list.
Domain and DNS access
A domain registered to a former designer, or a registrar login nobody remembers. Recovering access can take days. Check who controls the domain in the first week, not on launch day. Our guide to choosing a domain name explains why it should be in your own name.
Payments, on both sides
Many providers start a stage only after its payment arrives, so a slow internal approval stops the project. For stores, the payment gateway's own review adds time. Start it early; our guide to payment gateways in Saudi Arabia covers what to prepare.
Integrations and outside parties
A booking calendar, an accounting or CRM link, a photographer without a date, a translation office. Each depends on someone else's schedule. Run them alongside the design, not after it.
Scope that keeps growing
"While we are at it, let's add a small shop and online booking." Every new feature needs planning, pricing and time. Launch what you agreed, then add features in a second phase.
An unfinished logo
The logo sets the colours and tone of the site, so a logo still in progress holds everything up. Either wait for it, or launch with a simple text logo and swap it later.
Notice how many of these sit with the business owner rather than the designer. Providers do slip too: some take on more work than they can handle, or put small projects behind large ones. But once you have closed the delays that are yours, any delay from the provider is easy to see and easy to raise. If you sell online, also allow time for registration steps such as Saudi Business Center verification, which run on their own schedule.
One site, two timelines: a worked example
Take an engineering consultancy in Jeddah that wants a seven-page site in Arabic and English: home, about, services, projects, licences, request a quote, and contact. Same provider, same scope. The only difference is how ready the owner is. The figures are illustrative.
| Stage | Owner who is ready | Owner who is not ready |
|---|---|---|
| Brief | Two days: a written page list and three sites they like | Two weeks: three meetings without a clear decision |
| Content | Four days: company profile, project list and photos sent in one go | Three weeks: photos on engineers' phones, text written slowly |
| Design and build | Six days | Six days, then a week's pause to change colours after a logo update |
| Review | Three days: two rounds of grouped comments | Two and a half weeks: five rounds from three people |
| Testing and launch | Two days | A week: nobody knew where the domain was registered |
| Rough total | About three weeks | About ten weeks |
The designer's working time is almost the same in both columns. Seven weeks of difference came from waiting: for photos, for opinions, for domain details. And for those seven weeks the second consultancy had no site to send quote requests to.

How to shorten the timeline before the project starts
The surest way to shorten a project is to finish, before it begins, everything that can be finished. Each item below saves days later.
- Write the goal in one line. "Visitors request a quote" or "visitors message us on WhatsApp". A clear goal shortens design debates.
- List the pages. Even a rough list is the basis for both the timeline and the price.
- Pick three sites you like and note what you like about each: the colours, the layout, the way services are shown.
- Find a clean logo file, ideally with a transparent background or in vector form, not a screenshot from a social profile.
- Put your photos in one folder with clear names: premises, equipment, projects, products. Real photos beat stock images.
- Write down the basics: official name, a short description, one line per service, phone numbers, address, map location and opening hours.
- Check the domain. Do you have one, where is it registered, and do you hold the login?
- Name one decision-maker who receives the links, collects views and sends approvals.
- Book review time. One hour on a set day to check the preview on your phone and then on a computer.
- Freeze the scope. New ideas go on a "phase two" list, not into the current project.
- Start outside tasks early: the payment gateway application, your Google Business Profile and business email can all run in parallel with the design.
One more habit helps at the review stage: ask two or three customers or staff to try the preview on their phones, watch where they hesitate, and send their comments together with yours. Clear copy also speeds approval, because there is less to argue about; our guide to website copy that persuades shows what to aim for.
Put the timeline in writing: questions to ask before you sign
A spoken deadline is easy to forget. A written one holds both sides to account. Before you accept any offer, ask these questions and get the answers in the proposal:
- When does the clock start? On payment, or when your information is complete? The second is more realistic, but the proposal should say exactly what information is needed.
- What are the stages and their dates? One final date is not enough. Ask for a date for the design, for the preview link and for the launch.
- How many review rounds are included, and what happens if you need another one?
- How long do you have to reply? Some providers move the schedule if you reply late. That is fair when it is written down in advance.
- What if the provider is late? Will they warn you, and do you have a right to cancel or a refund?
- What does "launch" include? The domain connection, SSL, Search Console and handover, or are some of those later steps?
- Who writes the content? If it is you, the real project starts when you finish writing.
Be wary of a store with hundreds of products promised in a few days with no questions about product data or payments; of no written dates at all, only "soon"; of full payment upfront for a long project with no stages; and of no preview link, so you only see your site once it is public. Our guide on how to hire a web designer lists more questions to ask, and what a web design quote should include covers the rest of the proposal.
After launch: when will Google show your website?
Many owners search for their business name on launch day, find nothing, and assume something is broken. Appearing in search is a separate stage with its own timing. Google's guidance on asking for a recrawl says crawling can take from a few days to a few weeks, and that requesting a recrawl of the same URL again and again will not make it faster. Its SEO starter guide adds that some changes take effect within hours while others can take several months, and that there is no guarantee any particular site will be added to its index.
You cannot set the date, but you can remove the obstacles:
- On launch day, make sure the site is not blocked from search engines, verify it in Google Search Console and submit a sitemap. Google notes that a sitemap is especially useful for a new site with few links pointing to it, though it does not guarantee every page will be crawled and indexed.
- In the first week, request indexing once for the home page and your main service pages, then wait. Add the website link to your Google Business Profile and social accounts.
- In the first months, watch the page indexing report, improve thin pages and add pages that answer customers' questions. Rankings develop over months, and nobody can guarantee a position.
For the weeks that follow, see what to do after your website launches and how to get found on Google.
How Webnaa handles the timeline
Webnaa web design is built to take the usual waiting out of a project. The single timing commitment we make is this: we send your design on a preview link within 24 hours of receiving your complete information, before it goes live on your domain. How long the rest takes depends on your scope and your review, as this guide explains. What removes the waiting:
- We write the content in every plan, from the information you give us, so the project does not wait for you to draft each page.
- The scope is clear from the start. The type of site, the languages and the number of pages are chosen in the price calculator, where you see the price in seconds.
- Hosting and SSL are included, with a domain in your name on every site on your own domain, so there is no separate hosting contract to arrange.
- You review on a preview link from your phone before anything goes live, and if you do not like the design during the design stage, our money-back guarantee applies.
- Arabic, English or both, each with its own full interface rather than translated text.
Website design starts from SAR 39 a month for one page in one language on a Webnaa subdomain, billed yearly. A site on your own domain is priced by its type, languages and number of pages in the calculator. Online stores, booking, payments and custom web systems are separate services whose timeline depends on their size: we quote after a short call, and the consultation is always free. You can see each step on our how we work page.
See your design on a preview link before launch
Read what the website design service includes, then send us your business details to get started.
FAQ about website timelines
Can a website be built in one day?
A simple one-page site with ready content can be built in a day. A full company site needs time to write, review and test content on different devices. Rushing usually shows up as weak text and forms that do not work, so testing matters more than raw speed.
How long does it take to build an online store?
As a general estimate, often one to three months, depending on the number of products, how ready their photos and descriptions are, and how long the payment gateway and shipping set-up take. A small store with ready data sits at the short end. See our online store design service for what a store project covers.
Why is my website project late?
Check your side first: is the content complete, did approvals arrive on time, were new requests added? If all of that is in order, ask the provider for a written explanation and a new date, and check what your agreement says about delays.
Should I launch with some pages missing?
Yes, if the core pages are ready: home, services, about and contact. A blog or extra project pages can follow. Do not publish empty pages or pages that say "coming soon", because they weaken visitors' trust.
How long does it take for a new website to appear on Google?
There is no fixed date. Google says crawling can take from a few days to a few weeks, and it does not guarantee that any site will be indexed. Verify the site in Search Console, submit a sitemap, request indexing for key pages once, and publish content that answers your customers' questions.
Does a free website builder save time?
It can save build time, but you still write the content, choose the photos and test everything yourself, and free plans come with limits. Our guide to a free website for business explains what free plans include.
Summary
How long it takes to build a website is not one number. It is the sum of the brief, content, design, build, review, testing and launch, followed by indexing on Google. The type of site sets the minimum, and your readiness and speed of decision set how far past it you go. Prepare the content, logo and domain access before you start, name one approver, send feedback in one list, and ask for dates for each stage in writing. Do that, and a company website becomes a matter of days or a few weeks rather than months.
Sources (Reviewed November 2026): Google Search Central: ask Google to recrawl your URLs, Google Search Central: SEO starter guide, Google Search Central: learn about sitemaps. From Webnaa: pricing and price calculator, terms and conditions. Time ranges in this article are general estimates that depend on scope; they are not quotes or promises.