Building a Website for Your Business in Israel (2026): What to Decide Before You Start

What should you decide before building a website for your business?

Most website projects that go wrong went wrong before the first line of code. The owner asked for "a site", the builder quoted for the site he usually builds, and nobody wrote down what the site was supposed to change in the business. In ten years and 130+ builds, the projects that ran on time and stayed useful had the same five decisions made up front:

• The job: one main thing the site has to produce — inquiries, orders, bookings, or trust for people who already heard about you.
• The platform: chosen by that job and by who will maintain the site, not by what the builder happens to sell.
• The scope: which pages, which languages, which systems the site connects to — and what is explicitly left for later.
• The content: who writes the texts and supplies the photos, and by when.
• Ownership and upkeep: whose name is on the domain, the hosting and the accounts, and who updates the site a year from now.

Start from the job, not from the design

A site that has to bring inquiries is built around one action: a form, a WhatsApp button, a phone number that is easy to tap. A store is built around the product page and the checkout. A site whose job is credibility — the one people open after a referral — is built around proof: real projects, real names, clear contact details. These are three different sites, and a brief that says "something modern and clean" describes none of them.

Write the job as one sentence with a number you can check later: "ten inquiries a month from people looking for a kitchen renovation in the Sharon area". The number does not have to be right. It has to exist, because it is what you will measure the site against six months after launch.

Which platform fits which need?

There is no best platform, only a fit. I am not tied to one of them, so this is the order I actually think in: what the site does, who maintains it, and what it has to connect to. The table further down puts the same choices side by side.

• WordPress: a content or service site that will grow — more pages, a blog, landing pages, a second language. It runs 40.2% of all websites (W3Techs, 2 October 2026), so developers, plugins and hosting are easy to replace. The price of that freedom is upkeep: updates, backups and security are yours or your developer's.
• WooCommerce (a store on WordPress): a store that needs things a standard checkout does not do — business customers, price lists by customer type, quotes, a live connection to a CRM or an ERP. Full control, and a developer in the picture.
• Shopify: a store with a standard catalog and checkout, when you would rather pay a monthly plan than think about servers. In Israel remember that Shopify Payments is not available, so you connect a local payment provider and Shopify adds its own fee on each sale.
• Custom build: when the site is really a system — a customer portal, a booking engine with your own rules, an internal tool. Worth it only when no existing platform fits the process, because you also take on maintaining what was written for you.
• A website builder such as Wix: a first simple site you will edit yourself, with no integrations. It is a fair starting point. When the business outgrows it, the site is moved to another platform, not extended — plan for that day instead of being surprised by it.

What drives the cost of building a website?

Two quotes for "the same site" can be far apart because they are not for the same site. The price follows the work, and the work follows a handful of things you can list before you ask anyone for a number. I keep prices out of this guide on purpose; the published market ranges are in my article on what a website costs in 2026. What moves a quote up or down:

• Design: adapting a ready-made template, or designing every page type from scratch.
• The number of page types, not pages. Twenty service pages on one layout are one piece of work; five different layouts are five.
• Integrations: card payments, invoicing, a CRM, a booking calendar, shipping. Each one is a second system with its own account, rules and ways to fail.
• Content: whether you bring finished texts and photos, or writing, photography and translation are part of the project.
• Languages: Hebrew and English is not "the same site twice". Right-to-left layout, mixed Hebrew and English text and two sets of content all need real work.
• Moving from an existing site: carrying over content, products and customers, and redirecting the old addresses so the pages Google already knows are not lost.
• What happens after launch: hosting, updates, backups and small changes — included for a period, or billed separately.

Keep the two bills apart

The build is a one-off project. The running costs are separate and they go to other companies: the domain, hosting or a platform plan, paid plugins or apps, the payment provider. Ask every builder for both lists in writing, and ask which subscriptions will be in your name. A low build price with an open-ended monthly fee to the builder is a different deal from the one it looks like. I give a fixed quote after a short call, and the project scope estimator shows which kind of project yours is before we talk.

What decides how long it takes?

The build itself is rarely what holds a website up. The schedule slips on the things around it, and almost all of them are on the business side of the table:

• Content that is not ready. A designed page with no text in it cannot be finished, and "we will send it next week" is the most common sentence in a late project.
• Approvals. One person who decides keeps a project moving; a committee that meets once a week adds a week to every round.
• Third parties. A payment provider has to approve the business, a domain has to be transferred, an old supplier has to hand over access. None of it is in your builder's hands.
• Scope that grows on the way. Every "while you are at it" is reasonable on its own; ten of them are a second project.
• Migration. Moving a store with years of orders and customers takes checking, not only copying.

What to prepare before the first call

You do not need a specification document. You need answers to the questions a serious builder will ask anyway, and having them ready is the cheapest way to shorten a project:

• The one-sentence job of the site, with the number.
• Two or three sites you like and one you do not, with a line on why for each.
• The list of pages you think you need, and which of them already have text.
• The systems you already work with: invoicing, CRM, calendar, payment provider, email marketing.
• Access: who registered the domain and where, who hosts the current site, and whether you have the logins.
• Brand files: the logo as a vector file, colors and fonts, real photos of the business.
• A date that matters — a launch, a season, a campaign — and how firm it is.

The floor every business site in Israel has to meet

Four things are not optional extras, and a quote that does not mention them has left them out. This is not legal advice — for the first two, check what applies to your business with a professional.

• Accessibility. The service-accessibility regulations under the Equal Rights for Persons with Disabilities Law apply to private businesses that serve the public online, not only to public bodies. They require the site to meet Israeli Standard 5568 — which W3C lists as based on WCAG 2.0 — at level AA, and to carry an accessibility statement with a way to report a problem. The exemptions are narrow: an exempt dealer (osek patur) or a business whose average annual turnover is no more than ₪100,000 is exempt, and the wider exemption for turnover up to ₪1,000,000 covers only a site that was already running before the rules took effect in October 2017 — do not count on it for a new one. Ask what is tested, and by whom.
• Privacy. A site with a contact form collects personal data. Amendment 13 to the Protection of Privacy Law took effect on 14 August 2025 and gave the Privacy Protection Authority the power to impose monetary sanctions. At minimum: a privacy notice that says what you collect and which services process it.
• Mobile first. Google states that it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking". If something is missing from the mobile version, for Google it is missing.
• Speed you can measure. Google's Core Web Vitals give three targets: the main content shows within 2.5 seconds (LCP), the page responds to a tap in under 200 milliseconds (INP), and the layout does not jump (CLS under 0.1). Ask for them to be measured on the finished site, on a phone.

How do you judge who should build it?

A portfolio shows how sites looked on the day they launched. You are hiring for how they work, so test that. These checks take an hour and need no technical background; the longer list is in my guide to red flags when hiring a WordPress developer.

• Ask for three live sites and open them on your phone. Run each through Google PageSpeed Insights. A builder who cares about speed has sites that show it.
• Listen to the first questions. Someone who asks about your customers and your process before naming a platform is choosing for you. Someone who names the platform in the first minute is selling the one he has.
• Ask who owns what. The domain, the hosting account, the platform account and the code should be in your name from the first day, with your own login.
• Ask for the scope in writing: what is included, what is not, how many rounds of changes, and what a change outside the scope costs.
• Ask who does the work. With an agency, the person in the sales meeting is often not the one who builds; I compare the two honestly in freelancer or agency.
• Ask what happens the day after launch: who fixes a bug, who updates the site, and how you leave if you want to.

Where AI fits in

AI has made parts of a build faster: a first draft of a layout, repetitive code, test data, a first pass at product descriptions. I use it every day, and it is one reason a well-scoped project moves faster than it did a few years ago. It has not changed the five decisions above. A tool can produce a page in a minute; it cannot tell you that your business needs inquiries and not a catalog, or that the checkout you want is not possible on the platform you chose. That part is still judgment, and it is the part to pay for.

Where to start this week

Write the one-sentence job. List the pages and mark which have text. Check whose name the domain is registered under. With those three you can talk to any builder and compare the answers like for like. If the site is a store, read Shopify vs WooCommerce in Israel before the first call; if it is a service or content site, my WordPress development service page shows how I build one.