Short answer
A company website should answer the questions of the customers, dealers, job candidates and investors who research you, without them having to call. That takes a page per service, references, a short quote form, KVKK notices, a fast mobile site, each language at its own address and tracking for enquiries.
The purchasing manager who took your business card at a trade fair looks at your site on their phone that evening in the hotel. If they can’t quickly find what you make, who you work with and how to get a quote, they move on to the next card. When people think about what a company website needs, the talk often drifts to colours, animations and the big image on the homepage. Yet the site’s real job is simpler: to answer the question on the mind of someone researching you, without them having to call you. In this article we cover who a company website serves, which pages and content it should have, multilingual setup, the choice of platform, measurement and the process. At the end there is a checklist you can use before you commission one.
The site’s job: who comes, and with what question
A company website doesn’t get just one kind of visitor. Writing down who comes and what they are looking for before design starts makes every later decision easier. At most companies, four groups stand out:
- Customers: “Can this company do my job, have they done something similar before, how do I get a quote?”
- Dealers or business partners: “What is the product range, where are the technical documents, who do I talk to in my region?”
- Job candidates: “What is it like to work here, are there open positions, where do I apply?”
- Investors or financial institutions: “How long has the company been around, who runs it, is the corporate information up to date?”
Each group’s question corresponds to a different page and a different path. The homepage’s job is to send each of them to the right place within a few clicks. If your company never deals with investors through the website, there is no need to make that section large; what matters is writing this list honestly for your own business.
Pages a company website should include
The list of pages varies by industry, but the skeleton is similar at most companies.
Service and product pages
Each main service or product group should have its own page. When five paragraphs sit side by side on a single “Our services” page, both readers and search engines struggle to tell what is what. A good service page explains who the service is for, which problem it solves, how it works and what is delivered in return. On the product side, technical specifications, dimensions, certificates and a downloadable catalogue or data sheet are the most used part of the page, especially for dealers and purchasing teams. If you sell to other businesses, our guide to B2B SEO explains how these pages get found in search.
References and case studies
A wall of logos is a start, but on its own it says little. Telling the story of a few projects is more convincing: what was the client’s situation, what was done, what was the result? If you can’t share the client’s name, describing it by industry and city also works. Not using made-up or inflated numbers here protects trust in the long run. Customer reviews on your Google Business Profile do the same job alongside your references; we explain how to grow them within the rules in how to get more Google reviews.
Process
“What is it like to work with you?” is the question people most want answered before they ask for a quote. Explaining on a short page which stages the work goes through, what is expected of the client and how delivery happens also speeds up the first meeting.
About us
The founding story, the team, the production facility or office, certificates and quality documents. Job candidates and investors look at this page most. Real photos always say more than stock images.
Contact and a short quote form
The contact page should state the address, a map, the phone number and the email address clearly. The quote form, on the other hand, should be short: name, company, contact details, the service or product of interest and a short note. Every extra field loses you some of the people filling it in. Getting the detail in the first meeting is better than keeping people waiting at the door with a long form.
KVKK notices
The privacy notice, the cookie policy and the explicit consent or information confirmations next to forms are a required part of a company website in Türkiye under KVKK (Türkiye’s Personal Data Protection Law, Law No. 6698). We suggest preparing the content of these texts with your legal adviser; the site’s job is to show them in the right place and to actually apply cookie preferences.
Speed and mobile
On most company websites the first visit comes from a phone: after looking at a business card at a trade fair, clicking a link in an email or following a search. A site that is hard to read on mobile, with buttons you can’t press with a finger, loses that visitor however good it looks on desktop. The accessibility standard WCAG 2.2 sets a floor here: its “Target Size (Minimum)” criterion asks for click and touch targets of at least 24 by 24 CSS pixels, or enough space between them. Speed is a design decision in the same way; large images, heavy fonts and scripts added later are the most common causes. We cover this in detail in why a fast site sells more.
You should be able to update the content yourself
Waiting for a developer to add a news item, an open position or a new product, or to change a phone number, is the most common reason a site goes stale over time. So content management should be planned from the start: which pages your team will edit, who will publish, how images will be uploaded. A good admin panel doesn’t let you change everything; it lets you easily change what needs changing without breaking the design.
Multilingual company websites
For exporters, the website is often the first point of contact for a buyer abroad. The purchasing manager you met at a trade fair looks at your site in their own language after the meeting. Three things are decisive here.
Real translation. Text produced by machine translation costs you trust, especially with technical terms and product names. Text should be translated, or at least reviewed, by a translator who knows the industry. Every language doesn’t have to have the same pages either; for some markets, different products, different certificates or different contacts can be put forward.
Each language at its own address. If the language is chosen only with a button that works in the browser, search engines often see only one language. Each language version should sit at its own address, for example in a folder such as /en/ or /de/, and the page should load in that language from the start. Google’s guidance on multilingual sites also recommends a separate URL for each language version instead of switching the language with cookies or browser settings. We cover the build decisions step by step in how to build a multilingual website.
Hreflang. Each page should point to its counterparts in the other languages with hreflang tags, so that the search engine shows the German version to someone searching in German. If you are moving an existing site to a multilingual structure, handle the address changes carefully; we explain this step by step in keeping SEO through a site rebuild.
WordPress or custom build
There is no single right answer to this question for everyone. Both routes have strengths and weaknesses; what matters is choosing knowing which one fits your needs.
WordPress and off-the-shelf platforms have a large ecosystem. There are ready-made plugins for many functions, the admin panel is familiar to a lot of people and you can get started quickly on a standard company website. The weak point is maintenance: the core, the theme and every plugin need regular security updates. As the number of plugins grows, so does the chance that one update breaks something else, and the site can become dependent on a plugin whose developer has stopped working on it. Ready-made themes look quick at first, but over time it becomes harder to go beyond the limits of the theme in the design.
A custom build, meaning the site is built from scratch around your business, gives flexibility and simplicity: there is only the code you need, the attack surface is small and speed is under control from the start. The weak point is that it needs more development at the outset, and the site needs a team that knows the code. That is why it matters that the source code is handed over to you and documented.
The cost logic should be read from the same angle. On an off-the-shelf platform the start may be lighter, but maintenance, updates and plugin licences add up over the years. With a custom build the start is heavier, but in the years that follow maintenance is usually more predictable. Make the comparison on the total burden over several years; the first invoice is only one part of that picture. For company websites we mostly build custom with Astro and Next.js; where an off-the-shelf platform makes more sense, we say so in the proposal, with our reasons. We explain how prices are put together in digital agency pricing.
Measurement: forms and quote requests
A company website’s success is measured by the enquiries it brings in, not by the number of visitors. These should be set up before launch: every submission of the quote form should be recorded as an event, with the page and source it came from visible. Clicks on phone and email links should be tracked separately. Catalogue downloads are also a good indicator of dealer interest. Without this measurement, you can only guess whether the new site works better than the old one.
What a website build timeline depends on
Giving an exact timeframe without knowing the scope wouldn’t be right. The main factors that set the timeline are these: the number of pages and templates, the number of languages, integrations such as an ERP, CRM or dealer system, custom functions and how quickly feedback is given.
In most projects, though, the longest task is preparing the content. While design and development move along on the planned schedule, text, product information, photos and translations can fall behind. Planning content at the start of the project, and writing down who will prepare which text and when, is the most effective way to protect the schedule. For companies that sell to other businesses, how to build a B2B content plan explains how to choose the topics and put them in order. You don’t have to write the text yourself; a content team can prepare it and put it to you for approval. But approval needs to come from the person who knows the company best.
Questions to ask the team that will build the site
A few questions we suggest asking a company before you commission a company website:
- In whose name will the domain, hosting and analytics accounts be opened?
- Will the source code and design files be handed over?
- From which panel, and by whom, will the content be updated?
- Who will handle maintenance and security updates after launch?
- Are multilingual setup and measurement included in the proposal?
Our web design and software service page explains how we handle each of these points. For a wider list of questions, see our article on how to choose a digital agency. If search will go to a separate team, the seven questions in how to choose an SEO agency will help too.
Company website checklist
- The visitor groups and each group’s question have been written down.
- Each main service or product group has its own page.
- References and at least a few case stories are ready.
- The process, about us and contact pages have been planned.
- The quote form is short; it contains only the fields that are needed.
- KVKK notices and cookie preferences are ready and working.
- The site is easy to read on mobile and opens quickly.
- Your team can update the content from the panel itself.
- Each language is set up at its own address, with real translation and hreflang.
- The choice of platform has been weighed together with the maintenance and update burden.
- Form submissions and phone and email clicks are being measured.
- The people responsible for preparing content, and the schedule, are clear.
Common questions
How many pages should a company website have?
There is no fixed number. Your main services or product groups, references, process, about us, contact and the legal texts form the skeleton. Decide the number of pages based on visitors’ questions; don’t add a section that will stay empty just for the sake of having it.
Is an English version enough for exporting?
In many markets English is a good start. But if there is a country where you make most of your sales, a version in that country’s language puts you closer to the buyer. Decide which languages you need by looking at your current and target markets.
Our old site is on WordPress; should we change platform for the new site?
If the current site works well, is kept up to date and meets your needs, there is no need to change. If it breaks often, the plugins have become dependent on each other or you are hitting limits in the design, a change can make sense. If you do change, make sure you plan redirects for the old addresses.
How does a website stay up to date after launch?
While your team updates the content from the panel, the technical side, meaning security updates, speed monitoring and error checks, runs on regular maintenance. If it is written down from the start who is responsible for each of these, the site won’t go stale over the years.
Before you talk to any company, fill in the checklist above with your own team. The items you can’t answer are the first questions to put to the companies you ask for a proposal; the ones you can answer let you compare proposals by the same measure. If you work with our web and software team, discovery starts from this list too.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 25 October 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.