Corporate websites built to measurable acceptance criteria
Corporate website development is not a visual preference; it is the sum of information architecture, performance, accessibility and machine-readability decisions. For manufacturers and multi-location companies we deliver the site against thresholds written into the contract: mobile Lighthouse Performance of at least 95, LCP under 1.8 seconds, WCAG 2.1 AA conformance and zero schema validation errors. The source code and the copyright are yours.
In a corporate web project, who owns which piece of work?
Three items are routinely left unowned in a corporate web project: structured data, the performance threshold and multilingual matching. Marketing takes the content, the software team takes the code, and the technical visibility layer between them enters neither contract. We put all three into the same contract and hand them over with measurements.
| Responsibility | Marketing agency | Software agency | Baki Bilisim |
|---|---|---|---|
| Who commits to the new site's LCP threshold in writing? | Out of scope | Partly | In scope |
| Who writes the Schema.org graph for each page type? | Partly | Out of scope | In scope |
| Who builds and verifies hreflang matching in a multilingual structure? | Out of scope | Partly | In scope |
in scope · partly, as additional scope · out of scope. Why this split is a contractual question rather than a positioning claim is set out under delivery and visibility held by the same team.
Why does a procurement team use your website as a shortlisting tool?
A corporate buyer looks at your website before drawing up a supplier shortlist. If capacity, product families, certificates, technical documents and contact routes are not findable within the first few minutes, the company drops off the list. The site here is not a brochure but a pre-qualification file, and a file that will not open is never assessed.
This filtering turns into concrete loss at three points. The first is not being found: if the product family lives inside a single PDF catalogue rather than as browsable categories, neither the search engine nor the buyer can reach it. The second is not being verifiable: if capacity, facility and certificate information is not present on the page in a machine-readable form, the company stays incomplete in the entity records that search and AI systems build. The third is not being reachable: if the person, unit or regional manager a procurement specialist is looking for sits behind one generic form, no contact is made.
In an industrial context there is a fourth. Evaluation frequently happens on a factory floor or during a site visit over a weak mobile connection, not at an office desk. Performance is therefore not an aesthetic detail on a corporate site; it is a condition of access.
2.5 s
The threshold Google defines as «good» for Largest Contentful Paint (LCP) — the time it takes for the largest content element on the page to become visible.
Source: Google web.dev — Core Web Vitals · Accessed: 2026-07-29 · open source (opens in a new tab) ↗
The threshold we apply on corporate website projects sits below that public limit: in lab measurement, LCP is accepted under 1.8 seconds. The reasoning and the measurement method are set out in our guide to LCP, INP and CLS thresholds and the lab versus field gap.
What exactly is delivered in a corporate website project?
Nine items: an information architecture map, a design system with its token file, a static or headless codebase, the multilingual structure with hreflang mapping, the structured data graph, a performance report, an accessibility report, content management training and the source code transfer. The format and delivery moment of each item is written into the contract.
| # | Deliverable | Format | When |
|---|---|---|---|
| 01 | Information architecture map and redirect plan | URL tree, page type mapping and 301 table | At discovery sign-off |
| 02 | Design system and token file | tokens.css + component catalogue + state definitions |
At design approval |
| 03 | Static or headless codebase | Version-tagged Git repository + staging environment | At end of development |
| 04 | Multilingual structure and hreflang mapping | Language-to-path map + reciprocal hreflang matrix | At end of development |
| 05 | Structured data graph | JSON-LD per page type + validation output | At pre-launch acceptance |
| 06 | Performance report | Mobile Lighthouse + lab and field comparison, dated | At pre-launch acceptance |
| 07 | Accessibility report | WCAG 2.1 AA item by item; automated scan + keyboard pass | At pre-launch acceptance |
| 08 | Content management training | Live session + recording + written handbook | In launch week |
| 09 | Source code and copyright transfer | Repository access, licence list and handover letter | At launch, with final payment |
What falls outside scope is written down too: copywriting and photography are separate items, hosting and domains stay in your name, and third-party software licences are purchased by the client. The scope matrix for all eleven services shows in one table which work belongs in which contract.
Which six phases does a corporate website go through?
Six phases: discovery and inventory, information architecture, design system, development, measurement and acceptance, handover and maintenance. Each phase has its own deliverable, measurement criterion and accountable party, and no phase begins before the previous one is accepted. If a criterion is missed, the correction is ours and is not billed as an extra item.
-
Discovery and inventory
Existing domains, pages, content, measurement setup and search visibility are inventoried. The buying scenario of the target audience, the decision-maker roles and the digital maturity of competitors are defined. This phase produces data, not decisions.
-
Information architecture
The URL tree, page types, navigation, language structure and search intent mapping are established. Every address indexed on the current site is given a counterpart in the new structure or a 301 redirect, so traffic and link value carry across.
-
Design system
Colour, typography, spacing and component decisions are written straight into a token file. Hover, focus, error and empty states, the dark theme and behaviour between 360 and 1440 pixels are defined. The design is handed over as a system that turns into code, not as a screenshot.
-
Development
Semantic HTML, the performance budget, the structured data graph, hreflang mapping, forms with their consent flow and the content management layer are built. Budget and validation checks run before every merge, so regressions are caught before they reach production.
-
Measurement and acceptance
Mobile Lighthouse, a lab versus field data comparison, schema validation, an automated accessibility scan with a manual keyboard pass and a site-wide crawl report are executed. Results are recorded with the measurement date; launch is not accepted until the criteria are met.
-
Handover and maintenance
Source code and copyright are transferred, content management training is delivered, and regression protection with a measurement rhythm is put in place. On day 30 after launch the acceptance criteria are measured again and reported. Your in-house team can take maintenance over; no dependency is engineered.
These six phases are the web-project adaptation of the working model we use across every service. For the general definition of the phases, the reporting rhythm and the division of work, see the full definition of the six-phase working model.
Which acceptance criteria is a corporate website delivered against?
Against eight criteria: mobile Lighthouse Performance of at least 95, LCP under 1.8 seconds, CLS under 0.05, INP under 200 milliseconds, WCAG 2.1 AA conformance, zero structured data validation errors, a unique title and description on every address, and reciprocal hreflang. The measurement tool and date are written in the report.
| Criterion | Threshold | Measurement tool |
|---|---|---|
| Lighthouse Performance (mobile) | ≥ 95 | Lighthouse, mobile emulation |
| Largest Contentful Paint (LCP) | < 1.8 s | Lighthouse lab measurement |
| Cumulative Layout Shift (CLS) | < 0.05 | Lighthouse + field data |
| Interaction to Next Paint (INP) | < 200 ms | Field data + interaction testing |
| Accessibility | WCAG 2.1 AA | Automated scan + manual keyboard and screen reader pass |
| Structured data | 0 errors | Schema.org validator + rich results test |
| Title and description | Unique on every address | Site-wide crawl report |
| Multilingual matching (hreflang) | Reciprocal, x-default included | Site-wide crawl report |
4.5:1
The minimum contrast ratio WCAG 2.1 AA requires for normal-size text. During acceptance testing, every text and background pair in the design system is verified individually against this threshold.
Source: W3C — WCAG 2.1, Success Criterion 1.4.3 · Accessed: 2026-07-29 · open source (opens in a new tab) ↗
WordPress, or a static or headless structure?
The decision is made on who updates the content and how often, not on technology preference. The four criteria below settle the project-specific answer in a single meeting.
| Decision criterion | WordPress makes sense | Static or headless makes sense |
|---|---|---|
| Update frequency and number of editors | Many users enter content daily | Content changes rarely, or a single publishing team manages it |
| Performance budget | Plugin count can be limited and the theme is custom-built | Thresholds go into the contract; a static build fixes the budget upfront |
| Security and maintenance load | An in-house owner handles updates on a regular schedule | Attack surface and maintenance load are to be kept to a minimum |
| Integration needs | The ready-made plugin ecosystem is the deciding factor | ERP, PIM or product data is read through an interface |
Whichever option is chosen, the acceptance criteria do not change: thresholds are tied to the outcome, not to the platform. If WordPress is selected, plugin and theme decisions are bound in writing to the performance budget.
LCP, INP and CLS thresholds and how they are measured definitions of static site and headless CMS
In which industries is a corporate website structured differently?
The structure changes across five segments: manufacturing, retail chains, franchise networks, export industry and holdings. The difference is architectural rather than visual — product family depth, number of locations, language structure and subsidiary hierarchy directly determine the URL tree and the structured data graph.
- 01 Manufacturing and factories Product families, capacity and technical document access sit at the centre of the information architecture, so a procurement specialist or engineer finds what they need in a few steps.
- 02 Retail chains City, district and store levels are each built to be indexable and distinct, and store data is fed from a single source into the site, the app and the business profiles.
- 03 Franchise networks Central brand control and local visibility run in the same template without colliding; the permission and approval model is built as part of the site rather than bolted on later.
- 04 Export industry The multilingual structure, hreflang mapping and market-specific content differences are built in the first release; a language layer added afterwards creates redirect debt.
- 05 Corporate holdings The hierarchy between subsidiary sites and the parent brand is defined in navigation and in the entity graph, so each company keeps its own identity while staying attached to the group structure.
The eight questions corporate buyers ask most often
The eight subjects corporate buyers raise most often are: timeline, platform choice, ownership of source code and design, migration of existing content, which sections a corporate site needs, adding a multilingual structure later, maintenance after launch, and how contracts and invoicing work for clients outside Turkey.
How long does a corporate website take to launch?
A typical corporate website goes live within 8 to 14 weeks. Three variables set the duration: content readiness, the speed of the approval cycle and the scope of the multilingual structure.
If the content is ready the timeline approaches the lower bound; a product catalogue, a technical document library or a dealer location structure pushes it towards the upper bound. A dated plan is issued as part of the discovery output.
Should I choose WordPress or a static site?
The decision follows update frequency and in-house capability rather than technology preference. If many users update content daily, WordPress offers a familiar management layer.
If content changes rarely, or if performance thresholds will be written into the contract, a static or headless structure fixes the budget from the outset and lowers the maintenance load. Where WordPress is chosen, plugin count and theme decisions are tied in writing to the performance budget. The decision criteria are itemised in the comparison table above.
Who owns the source code and the design?
The source code, the design files and the content are yours. Repository access is transferred at the end of the project and a licence and handover letter is signed; no locked panel and no hosting arrangement that depends on us remains.
The licences of the open source components and typefaces used are listed individually in the handover file.
Will my existing content be migrated?
Yes. Existing addresses and content are inventoried during discovery; every indexed address is given either a counterpart in the new structure or a 301 redirect.
Content that has lost its value is not carried across as it stands: it is merged or rewritten. The redirect map is part of the information architecture deliverable and is verified line by line on launch day.
What sections does a corporate website need?
In the order a corporate buyer asks: what you produce (the product or service family), at what scale (capacity, facilities, documents and certificates), for whom (industries and applications), how you work (process), proof (documents, measurements, technical data) and contact.
Manufacturers additionally need technical document access, a multilingual catalogue and a location structure. The sections that change by industry are defined separately on the solution pages for the five segments.
Can a multilingual structure be added later?
It can, but it costs more than building it from the start. The language structure affects the URL tree, hreflang mapping, the structured data graph and navigation; added later, part of the existing addresses change and redirect debt accumulates.
If a second language is on your 12-month horizon we build the skeleton in the first release and add the content afterwards. The definition of hreflang and the reciprocity rule is in the glossary.
How does maintenance work after launch?
Maintenance runs under three headings: security and dependency updates, content and structure changes, and the measurement rhythm. On day 30 after launch the acceptance criteria are measured again and a dated report is shared.
Monthly measurement and a quarterly structural review are recommended thereafter. A maintenance agreement is not mandatory; because the source code is yours, your in-house team can take it over.
Do you work with clients outside Turkey?
Yes. Delivery is remote and the working languages are Turkish and English. Further languages are handled with translation supplied or approved by you, while the technical structure — hreflang, the structured data graph, the URL tree — is built by us.
Contract language, currency, invoicing and jurisdiction are agreed before the project starts and stated in the proposal rather than assumed here. Our registered address is in İzmit, Kocaeli, Türkiye; the contact routes are listed on the contact and project brief page.
See the measured state of your website within five working days.
The audit is free and creates no obligation to work with us. The report itemises findings on AEO answerability, AI crawler access, lab-measured Core Web Vitals, structured data validity and accessibility (automated scan). The report does not make the rebuild decision; it gives you a basis grounded in measurement for discussing that decision.
We work with corporate-scale, multi-location or multilingual organisations. One-off small jobs fall outside our scope; in that case we point you to smaller studios.