How to Build a Website: A Step-by-Step Plan

Most businesses that decide to build a website open with the wrong question: "Which platform should we use?" That question comes fourth. The two ahead of it — what job the site has to do, and who will write the content — decide what the platform needs to be. Choosing before answering them is a coin toss.

This article sets out the order: which step comes before which, what gets decided at each one, and what you should be holding at the end of it. The figures come from TurkStat's 2026 enterprise survey, which is the closest thing there is to a census of where businesses in Turkey actually stand.

The short answer: seven steps

1. Decide what job the site does. Selling, collecting enquiries, or proving you exist?
2. Register the domain and hosting in your own name. Not the agency's.
3. Prepare the content before the site exists. Copy, images, prices, references.
4. Choose the platform. Hosted service, WordPress, or custom code.
5. Build the technical foundations during the build. Adding them later is expensive.
6. Run the pre-launch check. Mobile, speed, forms, URLs.
7. Write down who maintains it. Launch is the start of the work, not the end.

Reverse that order and two things follow in almost every project: the schedule slips while everyone waits for content, and after launch it turns out nobody owns the site.

Half of all businesses still have no website

According to the 2026 results of TurkStat's Information and Communication Technology Usage Survey in Enterprises, 56.7 percent of enterprises with at least 10 employees owned a website (TurkStat, press release no. 58021).

In the same survey, 92.7 percent used a fixed-line internet connection. Connectivity is close to universal. A website is a coin flip.

There is a row in that chart that argues against what we sell, and it should not be skipped: 57.7 percent of enterprises used social media, more than the 56.7 percent that owned a website. For a lot of businesses, the first presence on the internet is now an account, not a site.

Admitting that does not make the site pointless; it changes the site's job. A social account is rented ground — the rules, the reach and the risk of removal belong to the platform. A site is property. Which one does which job is exactly what step one settles.

Who builds sites, and who does not

Website ownership climbs steadily with headcount.

The gap between sectors is sharper than the gap between size bands. In the same survey's table, the rate is 93.1 percent in telecommunications and computing and 91.4 percent in finance and insurance, 68.6 percent in manufacturing, but falls to 45.5 percent in transport and storage, 43.5 percent in accommodation and food service and 38.7 percent in construction (TurkStat, 2026 data).

The read is straightforward. If ownership is low in your sector, a good site is something most of your competitors do not have. If it is high, the site is not an advantage but an entry ticket, and the advantage has to come from what is inside it.

If you want to know which platforms large sites choose, we scanned 162 popular Turkish home pages in Next.js vs WordPress.

Step 1 — Decide what job the site has to do

A website does one of three jobs: it sells, it collects enquiries, or it proves you are real. Few sites do all three well, because the home page each one needs is different.

The data suggests most sites are doing the third. TurkStat puts the share of enterprises selling via the internet or electronic data interchange at 17.1 percent for 2025 (TurkStat, 2026 release). Set that against 56.7 percent website ownership and the conclusion is hard to avoid: for most owners, the site is not a sales channel.

Separating the three jobs is the first meeting's work:

• If you want sales, e-commerce brings its own set of decisions; how to set up an e-commerce site covers them separately.
• If you want enquiries, a page built for one campaign usually outperforms the home page; what is a landing page explains the structure.
• If you want to be checked out — by a buyer, a candidate or a supplier who already knows your name — the measure of success is different; corporate website design takes that case.

The output of this step is one sentence: "This site exists so that this person can do this thing." Without it, the next six steps have nothing to be measured against.

Step 2 — Put the domain and hosting in your own name

The domain registration, the hosting account and DNS control belong in your accounts. The agency gets added as an authorised user; it does not become the owner.

This is the cheapest step in the project and the most frequently skipped. When the domain sits in the agency's account, moving away later depends on that agency's cooperation. Domain, hosting and DNS explains how the three differ without the jargon, and who owns the code covers how to get code, content and account ownership written into the contract.

Step 3 — Prepare the content before the site exists

What delays a website project is almost never the software. It is the content.

Design is the work of placing text and images that already exist. What gets placed instead of missing content is a placeholder, and a site full of placeholders cannot be approved. Projects that plan to write the copy "before we go live" slip for this reason: writing takes the client's own hours, and those hours are invisible on the agency's schedule.

What should be ready before the build starts:

• What each page says, and how many pages there are
• Service or product descriptions, and prices where you publish them
• Real photographs — the team, the product, the premises; stock is the fallback
• Contact details, opening hours, and an address and map if you have one
• References, and client names you have permission to use
• Legal pages: privacy policy, terms, and any sector-specific notices

Filling that list usually takes one to three weeks. It can run alongside the build. It cannot start after it.

Step 4 — Choose the platform

The reason this is step four and not step one is that the answer falls out of the first three steps.

Here is the part you would not expect from us: the platform decides far less about site speed than people assume. In field data, sites built on modern frameworks can pass Core Web Vitals less often than WordPress sites do. The full comparison and the numbers behind it are in custom code vs WordPress; the wider set of options is compared in the website development guide. Headless CMS explained covers when that approach is actually worth it.

What really drives the platform choice is a different question: who is going to update this site, and how often?

Step 5 — Build the technical foundations during the build

Each of the following costs almost nothing when it is built in, and can mean rebuilding part of the site when it is added afterwards.

• The main content should be in the HTML the server sends, not assembled later in the browser.
• URLs should be readable and permanent. Google recommends readable words over long ID numbers, and hyphens between words (Google Search Central, URL structure).
• The mobile version is the site. A section that exists on desktop and is dropped on mobile largely does not exist for Google.
• Speed thresholds are a design target: main content loaded within 2.5 seconds, interaction response at or under 200 milliseconds, layout shift no greater than 0.1 (web.dev, Web Vitals).
• Canonical tags, the sitemap and robots.txt have to be set up correctly.
• Structured data goes in on day one.
• Accessibility should not be patched on at the end.

What makes a website SEO-friendly explains each item and how to test any site against them in ten minutes. Core Web Vitals covers which design decisions break the speed thresholds, and web accessibility covers why that item is no longer optional.

Step 6 — The pre-launch check

The launch-day list should be short. A long one means earlier steps were skipped.

1. Open the site on a phone. Is every desktop section there?
2. Actually submit the forms. Which inbox does the mail land in, and who reads it?
3. Walk every page. Empty pages, placeholder text, broken images?
4. Check the URLs. Is HTTPS working, and are redirects in place if there was an old site?
5. Measure the speed. Is the mobile result inside the thresholds you set during the build?
6. Let the search engines in. Has the block you put up during the build been removed?

If you want to see points four and five together, our free SEO checker reports most of these in a few seconds. Point six is the most expensive mistake new sites make: a site that blocks indexing during the build and forgets to unblock it at launch stays invisible in search for months.

Step 7 — Who maintains the site after launch?

Settle this before the build starts, because in most businesses the honest answer is "nobody".

In TurkStat's 2026 data, only 10.8 percent of enterprises with 10 to 49 employees employed an ICT specialist (TurkStat, press release no. 58021). In the same survey, 9.4 percent of enterprises reported at least one ICT security incident during 2025.

So most businesses with a site have nobody inside the company running it, while the other side of that equation is fully staffed. Updates, backups and security patches do not happen unless they are written into an agreement. Website maintenance covers what that includes and what it realistically costs; website security covers how sites are actually broken into.

How long, and how much?

A single campaign page runs about 1 to 2 weeks, a corporate site 2 to 6 weeks, an e-commerce store 4 to 8 weeks. What moves those ranges is not how hard the software is; it is when the content lands and how fast feedback comes back.

On price there is no single number, but the reason quotes for the same site can differ fivefold — and which costs sit outside the build price entirely — is explainable. What a website actually costs breaks it down line by line, and how to choose a digital agency covers how to compare proposals and which clauses are warning signs.

Frequently asked questions

What are the steps to build a website, in order?

Decide what job the site has to do; register the domain and hosting in the business's own name; prepare the content before the site exists; choose the platform; build the technical foundations during the build rather than after it; run a short pre-launch check; and write down who maintains the site once it is live. Platform choice comes fourth, not first, because the three decisions before it determine what the platform needs to be.

How many businesses actually have a website?

In Turkey, 56.7 percent of enterprises with 10 or more employees owned a website in 2026, according to TurkStat. The figure is 52.3 percent among those with 10 to 49 employees, 75.6 percent among those with 50 to 249 and 92.7 percent among those with 250 or more. The survey excludes micro-enterprises under 10 employees, so most businesses by count sit outside these rates.

Should content come before design?

Content first. Design is the work of arranging text and images that already exist; what gets arranged in place of missing content is a placeholder, and nobody can approve a site full of placeholders. Projects that plan to write the copy during the build slip for this reason: writing takes the client's own time, and that time does not appear on the agency's schedule.

Whose name should the domain and hosting be in?

The business's own. The domain registration, the hosting account and DNS control should sit in your accounts, with the agency added as an authorised user. Otherwise, moving to a different agency depends on the current one cooperating. This is a clause to settle before the contract is signed, not after.

How long does it take to build a website?

A single campaign page takes roughly 1 to 2 weeks, a corporate site 2 to 6 weeks and an e-commerce store 4 to 8 weeks. What sets the range is rarely the software; it is when the content is ready and how quickly feedback comes back. A client whose content is finished gets the same site in roughly half the time.

Is a social media account enough instead of a website?

For some businesses it can be. In TurkStat's 2026 data, 57.7 percent of enterprises used social media, slightly more than the 56.7 percent that owned a website. For a business whose sales run entirely through messaging, the site is less a sales channel than an address that proves the company is real. But a social account is rented ground: the rules, the reach and the risk of removal belong to the platform.

Who looks after the site after launch?

Answer this before the build starts. In Turkey, only 10.8 percent of enterprises with 10 to 49 employees employ an ICT specialist, so in most businesses there is nobody in-house to run the site. Updates, backups and security patches then have to be tied to a maintenance agreement, because otherwise they simply do not happen.

In short

Building a website is not a platform choice; it is seven decisions in order. The site's job, who owns the accounts and whether the content is ready all come before the platform. The technical foundations go in during the build, because retrofitting them is expensive. Launch is not the finish line — it is the day maintenance starts.

The TurkStat figures say two things at once: close to half of businesses still have no site, and plenty of those that do have nobody to run it. The second problem moves more quietly than the first.

At Caliency these seven steps run to a fixed price against a scope agreed in writing, and domain and hosting accounts are always opened in the client's own name. What each package includes is on the web development page. If you are not sure which step you are on, tell us where you are and we will work out the next one together.