B2B Websites.
PROCESS
-
Product and document inventory
Catalogue, technical data sheets, certificates and pricing policy: which becomes a page, which stays a downloadable document and which is shared only on request.
-
Product architecture
Product family, variant and application area are built as three separate axes; a buyer reaches what they need by a short route, a machine reaches every product at a single address.
-
Built in the target market’s language
Each language lives at its own address and is written for its own search demand; the hreflang cluster, the language switcher and the schema translation are part of the architecture from day one.
-
Quote flow and measurement
The quote form is the first screen of the sale: short, with few required fields and errors that are stated plainly. Page speed, layout shift and accessibility are measured and reported with the handover.
WHAT’S INCLUDED
- Product and certificate pages: a catalogue in HTML that machines can read too
- Multilingual architecture: an address, hreflang and a switcher per target market
- Quote (RFQ) form: short, accessible, straight to email
- Structured data: organisation, product family and FAQ
- Measurement: field speed, layout shift and AI crawler access
MEASURED DIAGRAMS
Languages and addresses — export sites
Largest Contentful Paint — three live projects
SCOPE
Manufacturer websites
A manufacturer’s website is not a shop window but the first document of a supplier evaluation. The buying committee looks for concrete information, not aesthetics: production capacity, product family, technical specification, certification and delivery terms. That is why product information is not buried in a PDF but built as pages — so that the buyer, a search engine and an answer engine can all read it. The engineering side of the catalogue starts with the static site or CMS question.
Exporter websites: in the target market’s language
The language of an export site is not a translation but a market decision. The German page is written with the words a buyer in Germany searches for and in the register they expect; translating sentences keeps the meaning but loses the query. Language-specific keyword research, German text expansion and hreflang errors are the measured parts of this work; this site itself runs in three languages, its German in the formal Sie.
Technical product pages and catalogues
A technical product page answers three readers at once: the engineer reads the specification table, the buyer the delivery terms, the machine the structured data. The table is a real HTML table, units are written in the text and images load with their size reserved — the page does not shift while it opens. The rules of the image layer are measured in the image size reservation and AVIF and WebP guides.
Quote (RFQ) forms
In B2B a sale starts with a request for quotation, not a basket. The form stays short: product, approximate quantity, target market and contact are enough; the details come in the first reply. Error messages sit next to the field and are announced to screen readers too, and no touch target is smaller than 44 pixels. The form error messages guide explains why.
TEXTILES: TWO LIVE CASES
Fersan Tekstil: seven languages, one architecture
Fersan’s site stands on a single architecture in seven languages and explains the path from sample to shipment with interactive calculators. The measurement date, the method and what seven languages make harder are written on the case page: the Fersan Tekstil case study.
Karcem: colour accuracy and a certificate layer
Karcem’s multilingual knitted-fabric site builds colour accuracy as a system; laboratory verification and certificates sit in a separate evidence layer. The measurement strip and the architecture are in the Karcem case study.
LOCATION: ISTANBUL
Istanbul, TR — remote by default; on site when it matters.
FREQUENTLY ASKED QUESTIONS
-
How much does a B2B website cost?
The price is set by a written quote based on scope. Three variables carry the cost: the number and structure of products, the number of languages and the system the quote flow connects to. At the same product count, a two-language catalogue and a seven-language catalogue are two different jobs.
-
How many languages does an export website need?
As many as the markets you sell to or plan to. Each language is its own publishing job: translation, that market’s search demand and an update rhythm. A common start is English plus the language of the largest market; because the architecture is multilingual from day one, later languages join the same skeleton.
-
Should a product catalogue be a PDF or a web page?
Both, but the page comes first. The PDF stays as a downloadable document; the product information lives on an HTML page so that search engines, answer engines and screen readers can read it. A table inside a PDF is searchable but appears as a document cut off from its context; a table on the page sits at the product’s own address, together with its schema.
-
Should a B2B website show prices?
That is a sales decision, not a technical one. For products with a list price, the price can sit on the page and in the structured data; for products sold by quotation, the page shows the route to a quote instead. In both cases no invented price goes into the schema.
-
Can my existing site become multilingual without a rebuild?
Often, yes — but the architecture is audited first: an address per language, the hreflang cluster and whether the templates are language-independent. When a second language is added to a template built for one, the cost piles up in fixes, not in translation.
-
How do SEO and GEO work on a B2B website?
In the same layer. Once product and certificate pages are built in real HTML with structured data, a search engine can rank them and an answer engine can cite them. The details of both services are on the SEO consulting and GEO consulting pages.
-
Which fields belong in a quote (RFQ) form?
Few and meaningful ones: product or product family, approximate quantity, target market and contact. Every extra required field makes the form longer; the details are asked in the first reply. Error messages are written next to the field and in a way that screen readers announce.
-
How should certificates be shown on the site?
As evidence, not as badges: with the document’s name, the issuing body and the validity date. A wall of logos does not create trust; verifiable information does. In the Karcem case study, certificates sit in a separate evidence layer.