Your website is a supplier-shortlisting tool

In manufacturing, a website is not a sales channel; it is a pre-qualification document. The buyer does not intend to spend time on the site — the intention is to reach a decision: can this company do the work, are the certificates in place, is the scale sufficient, who do I write to. The decision itself is taken on a call or in a meeting, but for that call to happen the site has to pass the filter.

This is why visitor count is the wrong measure for a factory website. The measure is this: how many steps and how many seconds does a qualified buyer need in order to find the technical information they came for?

The asymmetry matters here. A buyer in Germany, the Netherlands or the Gulf usually cannot visit the plant before the shortlist stage and cannot verify claims through a local network. The website therefore carries the whole burden of proof at the first stage. A capacity figure without a unit, a certificate shown as a logo without a number, or a product page that exists only in Turkish all read the same way: unverifiable.

We treat the reverse direction — how a global buyer searches for and evaluates a Turkish supplier — as a subject of its own on the export industry solutions page.

• Capacity is described, not stated. General phrasing replaces measurable facts such as annual output, number of lines, tolerance range, covered plant area and dispatch capacity.
• The certificate is a logo, not a record. An ISO or product certificate is placed as an image, while the certificate number, its scope, its validity date and the way to verify it are never written.
• The document archive is closed. Datasheets and technical drawings are either behind a login or not published at all.
• The language structure is half-built. The home page is in English while product pages stay in Turkish, and without hreflang the two versions are read as duplicates of each other.
• Contact runs through one channel. A procurement specialist cannot find the person who answers a technical question, and the generic form carries no response-time commitment.
• Mobile performance was never measured. Page weight has not been tested for a buyer opening the catalogue from a plant floor or while travelling.

These gaps share one property: none of them is a design problem. They are all information architecture and structured data problems.

Kocaeli, the province immediately east of Istanbul, holds one of the densest concentrations of manufacturing plants in Turkey. Along the Gebze, Dilovası, Körfez and Çayırova line it is common to find several producers in the same product group, inside the same zone, with overlapping capability. At that density the buyer decides on the only asymmetric information available: whose product data and technical documents were easier to reach.

The regional and local-search side of this is covered separately on corporate web design in Kocaeli, Turkey.

The table below shows what each role looks for and which page structure that requirement translates into. It is not a list of assumptions: these are the information items that recur in requests for quotation and in supplier evaluation forms, mapped onto pages.

We call the work of becoming the cited source inside answer engines AEO (Answer Engine Optimization), and the work of being citable inside generative engines GEO (Generative Engine Optimization). Both terms are defined separately in the digital visibility glossary.

In practice this means a product page has to meet three conditions: the answer to the question is written in the first sentence, the technical data exists as text rather than inside an image, and the page introduces itself to machines through structured data.

Services can also be taken individually; this table is a prioritisation proposal, not a bundle. Where the audit shows the existing site can be improved without a rewrite, we narrow Phase 1 accordingly. Deliverables and acceptance criteria per phase are written out in how we work.

If export is the main channel, the multilingual structure moves inside Phase 1; the detail of that decision sits on export industry solutions. Manufacturers who also run a dealer or distributor network should read dealer and branch network digital management alongside this page.

Capacity is made measurable by the same logic. A sentence such as “we produce in a modern facility” carries no information for a buyer; the number of lines, annual output volume, the material classes that can be processed, the tolerance range, the covered area and the dispatch capacity do. Those values are published as long as they are verifiable — a figure that cannot be verified is not put on the page.

A minimum example of how an individual product page introduces itself to a machine:

Which schema type does what, on which page, is set out in the Schema.org and JSON-LD guide.

The minimum fields of a document record:

• Identity: document name, revision number, publication and revision dates.
• Context: which product family and which individual products it belongs to, linked in both directions.
• Summary: a technical abstract that can be read on the page as text, without downloading the file.
• File: a PDF with a readable text layer; scanned image PDFs are blank pages as far as search is concerned.
• Permanence: the address does not change when the revision does, and the previous revision stays as an archive record.
• Access: general technical data is published openly; documents that contain commercial confidentiality are released through a request form. The decision is yours, and we put the consequences of both scenarios in writing.

One extra rule applies to CAD files: the file format, the unit system and the software version it was produced with are written into the record. An engineer will not download without seeing those three facts.

The difference between translation and rewriting is visible in manufacturing. An engineer who sees a mistranslated tolerance statement draws a conclusion about technical competence within seconds. Product and technical document copy is therefore handled as a rewrite by an editor who knows the field, not as a translation pass.

Target market selection, the language-versus-country decision and the detail of the hreflang setup are covered on export industry solutions.

Our own acceptance threshold sits below that value and is measured for every page we deliver. What the metrics mean is explained in the Core Web Vitals guide, and the correction method in the Core Web Vitals optimisation service. The measured values for this site are published on the proof page.

We also write down the limits of this framework: we do not give ranking guarantees, and we have no control over what an AI assistant outputs. What we measure in that channel is a sample of how often the brand is cited across a defined question set; it is recorded with a date stamp and shared in raw form in the report.

We hold our own site to the same standard: only measured values are published on the proof page, and any line that cannot be measured is deleted. The reasoning is set out on why Baki Bilisim.

For the digital requirements of other segments see the solutions directory; if you also manage a dealer or distributor network, continue with franchise and dealer networks.