The team that builds it is accountable for its visibility.
We combine corporate web, mobile and brand identity delivery with SEO, AEO, GEO and Core Web Vitals engineering under a single contract — and we publish our own measured scores, with measurement dates.
Baki Bilisim is a corporate digital agency in Turkey, based in Kocaeli, working with manufacturing plants, retail chains, dealer and franchise networks, export industry and holding groups.
- Lighthouse Performance (mobile) 100/100
- Largest Contentful Paint (LCP) 1.5s
- Cumulative Layout Shift (CLS) 0.00
- Total JavaScript shipped by this page 4.0KB gzip
What gets lost when your digital work is split between two agencies?
What gets lost is the engineering side of visibility. A marketing agency produces content and campaigns; a software agency writes code. Structured data, an LCP commitment, hreflang setup, AI crawler policy and WCAG accessibility appear in neither contract, so they fall into the gap between the two teams and stay unowned.
The table below names no competitor. It compares the two common operating models in the market as categories. In your current setup, how many of these rows have an owner?
| Responsibility | Marketing agency | Software agency | Baki Bilisim |
|---|---|---|---|
| Who writes the Schema.org structured data? | Partly, usually through a plugin | Out of scope | Responsibility written into the contract |
| Who commits to an LCP target? | Out of scope | Partly, without a numeric target | Responsibility written into the contract |
| Who sets up hreflang in a multilingual site? | Partly | Partly | Responsibility written into the contract |
| Who decides the AI crawler policy? | Out of scope | Out of scope | Responsibility written into the contract |
| Who keeps mobile app and website content in sync? | Out of scope | Partly, content ownership undefined | Responsibility written into the contract |
| Who produces dealer and branch location pages? | Partly, template duplication | Partly, template without content | Responsibility written into the contract |
| Whose job is WCAG 2.1 AA accessibility? | Out of scope | Partly, no acceptance criterion | Responsibility written into the contract |
You know SEO. Who manages AEO, GEO and Core Web Vitals?
AEO covers being cited in answer boxes and AI assistants. GEO covers being recognised and quoted correctly by generative engines. Core Web Vitals covers the measured user experience of the page itself. None of the three is a sub-heading of SEO, and in most corporate organisations none of them has a named owner.
AEO — Answer Engine Optimization
AEO is the work of making a page directly quotable inside search engine answer boxes and AI assistants. SEO targets ranking; AEO targets being the source of the answer.
What this means for your site: if the answer to a buyer's question is given on the results page or inside an assistant, ranking first does not by itself bring a visitor. The source being quoted has to be you.
GEO — Generative Engine Optimization
GEO is the visibility work that makes generative engines such as ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews recognise your company correctly and cite it as a source.
What this means for your site: a procurement specialist looking for a supplier can now have the shortlist drafted by an assistant. Whether you appear on that list depends less on backlink counts than on machine readability and entity clarity.
Core Web Vitals
Core Web Vitals are the three measurable user experience metrics published by Google: loading speed (LCP), responsiveness to interaction (INP) and visual stability (CLS).
What this means for your site: a product catalogue that will not open on a weak mobile network inside a plant is not a technical detail. It is a supplier evaluation you lost without hearing about it.
Structured data (Schema.org)
Structured data is the JSON-LD code that tells search and AI engines, in machine-readable form, what your company, your services and your content actually are.
What this means for your site: if address, telephone, service and question-and-answer data are not marked up, an engine reads your page but does not learn your company. Rich results and correct citation both start here.
2.5 s
The LCP threshold Google classifies as "good". A page above this threshold keeps the user waiting more than 2.5 seconds for the largest piece of content to appear.
Source: Google web.dev — Core Web Vitals · Accessed: 29 July 2026 · web.dev/articles/vitals
| Metric | "Good" threshold | What it measures |
|---|---|---|
| LCP | ≤ 2.5 s | Time until the largest content element becomes visible |
| INP | ≤ 200 ms | Response time to a user interaction |
| CLS | ≤ 0.1 | How much the page shifts unexpectedly while loading |
The thresholds in this table come from Google's public documentation. We publish no number on this site without a source and an access date, and we use no percentage that promises a conversion rate or a revenue increase.
Our own site, measured
We have no published corporate case studies yet. Instead of references we publish measurements: this site's own scores, each with the tool and the date it was measured. You can repeat every one of them in your own browser. Rows we cannot measure are deleted, never marked as pending.
- Lighthouse Performance (mobile) 100/100
- Lighthouse Accessibility (mobile) 100/100
- Lighthouse Best Practices (mobile) 100/100
- Lighthouse SEO (mobile) 100/100
- Largest Contentful Paint (LCP) 1.5s
- Cumulative Layout Shift (CLS) 0.00
- Total page weight (first load, compressed) 94.8KB
- Third-party requests on first load 0
In July 2026 the homepage weight of 5 Turkish digital agencies was measured in the 180–530 KB range. This page: 94.8 KB. The comparison names no company and reports only measured values. This row is part of what it measures, so consecutive rounds land a few dozen bytes apart; we publish the higher reading.
Every row states its measurement environment and date. Scores are re-measured at each release and this page is updated. Lab measurement and real user data (CrUX) can differ, so we label the two separately.
See every measurement, the method and the measurement history
Eleven disciplines under one contract
Eleven services in three groups: build (website, mobile app, brand identity, e-commerce), visibility (SEO, AEO, GEO, Core Web Vitals) and scale (structured data, dealer network management, transformation consulting). They can be commissioned together under one contract or separately. With no handover point between them, accountability stays in one place.
GROUP 01
Build
Website, mobile app, brand identity and e-commerce — the four construction disciplines the visibility layer is built on.
- Corporate Website Information architecture, design system and codebase, delivered against written performance, accessibility and schema acceptance criteria.
- Mobile App Development iOS and Android applications for dealer ordering, field and service teams, production tracking and internal communication.
- Brand Identity An identity is not a PDF but a working system: colour, type and spacing decisions ship as a CSS token file the developers actually use.
- E-commerce B2B dealer portals, customer-specific pricing and account flows, ERP integration, product data quality and Product schema.
GROUP 02
Visibility
SEO, AEO, GEO and Core Web Vitals — the engineering of being findable in search engines, answer engines and generative engines.
- SEO Technical foundation, information architecture, content clusters and international SEO. We do not promise rankings; we write the measurement rhythm up front.
- AEO — Answer Engine Optimization Question-and-answer architecture, extractable passage structure and FAQPage or HowTo schema, so the answer is sourced from you.
- GEO — Generative Engine Optimization AI crawler access policy, llms.txt, entity modelling and periodic sampling of how often the brand is cited.
- Core Web Vitals and Performance Root-cause analysis for LCP, INP and CLS, a defined performance budget and regression protection; lab and field data reported separately.
GROUP 03
Scale
Structured data, dealer and branch network management, transformation consulting — the work that keeps a multi-location structure in one system.
-
Structured Data (Schema.org)
Entity map,
@idarchitecture and the JSON-LD graph, with validation and protection against regressions caused by content edits. - Dealer and Branch Network Management Location page architecture that holds central brand control and local visibility together, multiple LocalBusiness schema and NAP consistency.
- Digital Transformation Consulting Digital asset inventory, maturity assessment, a twelve-month roadmap and a written division of labour between the in-house team and the agency.
See the scope matrix for all eleven services and how they combine
Which companies do we work with?
We work with manufacturers, retail chains, dealer and franchise networks, exporters and holding groups. What they share is a multi-location or multilingual structure, documentation-heavy content, and a corporate buyer who uses the website as a shortlisting tool. Each segment's digital problem is different, so the service mix differs too.
- Manufacturing and Factories Procurement and engineering buyers use the site to shortlist suppliers; if capacity, certificates and technical documents cannot be found, the company is filtered out.
- Retail Chains When store data lives separately in the site, the app and the business profile, the address and opening hours end up wrong in three places at once.
- Franchise and Dealer Networks If each franchisee builds its own page the brand fragments; if head office collapses everything into one page, local search visibility is lost.
- Export Industry A multilingual site launched without hreflang returns the wrong language version in the target country's search results.
- Corporate Holdings Subsidiary domains, sites and accounts sit with different teams, and nobody has sight of the full digital asset inventory.
Review the recommended service combination for each of the five segments
No phase begins until the previous one has passed its measurement criterion.
A six-phase working model
Six phases: analysis, strategy, content planning, production, optimisation and reporting. Each phase has a written deliverable, a numeric acceptance criterion and a named owner on both sides. The next phase does not begin until the criterion is met, which removes the end-of-project argument about who committed to what.
-
Analysis
We inventory the existing digital assets: domains, sites, applications, accounts and data flows. The sector and competitor scan is done with measurements rather than assertions; every finding is recorded with the page address and the measurement date.
-
Strategy
Audience, decision-maker profile and business goal are translated into measurable statements. Instead of "more traffic", we write down which query set, which page type and which measurement tool will be used to track it. Scope, priority and explicit out-of-scope items go into the same document.
-
Content Planning
We build a question inventory from search data, the questions the sales team hears most often and support records. Each page gets one primary question, an answer-first opening paragraph and an internal link map. Technical terms are defined where they first appear.
-
Production
The design system is written as a token file, pages are built in semantic HTML, and the JSON-LD graph and the multilingual structure are constructed at the same time. The visibility layer is part of production, not a plugin added afterwards.
-
Optimisation
After launch, lab and field data are tracked separately. Core Web Vitals regressions, index coverage errors, broken schema and broken internal links are scanned on a regular cycle, and every fix is recorded with a before-and-after measurement.
-
Reporting
The monthly report states which metric was measured, with which tool and on which date. Interpretation and measurement are kept in separate sections, and the last item in every report is the priority list for the following month.
Read the full deliverable and acceptance criteria list for all six phases
Are we the right partner?
We are the right partner for corporate-scale work: multi-location or multilingual structures, a measurable goal and a horizon of at least three months. We are the wrong partner for one-off small jobs, logo-only or poster-only requests and low-budget personal projects; those we redirect, free of charge, to smaller studios.
We are the right partner
- Corporate-scale companies with an identified decision maker and an allocated budget
- Multi-location structures: plants, branches, dealer or franchise networks
- Multilingual sites, or sites written for export markets
- Projects with a measurable goal — not "more traffic", but visibility in a named query set
- Content built around technical documentation, product catalogues or structured product data
- A working horizon of at least three months and a regular measurement rhythm
We are not the right partner
- One-off, single-page jobs
- Requests limited to a logo, a poster or social media artwork
- Low-budget personal projects and hobby ventures
- Expectations of a ranking guarantee or a "first page by a given date" commitment
- Engagements where measurement and reporting are to be left out of scope
- Procurement processes decided on price alone
We work at corporate scale and on a project basis; we do not sell monthly retainer packages. We state our starting budget threshold in the first minutes of the discovery call, before a proposal is written, so neither side loses time. For the requests in the right-hand column we make a referral, and we charge nothing for it.
The six questions we are asked most before a project starts
What exactly does Baki Bilisim do?
Baki Bilisim is a corporate digital agency based in Kocaeli, Turkey. We deliver corporate websites, mobile applications and brand identity systems, and we run SEO, AEO, GEO, Core Web Vitals and structured data engineering for the same client under the same contract. We work mainly with manufacturers, retail chains, dealer and franchise networks, exporters and holding groups. All eleven services can be commissioned together or separately.
Why should build and visibility sit with one agency?
Because the work that sits between them has no owner. Schema.org structured data, an LCP target, hreflang setup, AI crawler policy and WCAG 2.1 AA accessibility are written into neither the classic marketing contract nor the classic software contract. A single contract removes the handover point, and with it the answer that arrives after launch: that was not in our scope.
What size of company do you work with?
We work with corporate-scale organisations that have a multi-location or multilingual structure, an identified decision maker and an allocated budget. One-off small jobs, logo-only or poster-only requests and low-budget personal projects fall outside our scope; we redirect those to smaller studios free of charge. We state our starting budget threshold during the discovery call, before any proposal is prepared.
Do you have published case studies?
Not yet, and we do not present something we do not have as if we had it. Instead of references we publish measurements: this site's Lighthouse scores, Core Web Vitals values, page weight and structured data validity, each shown with the measurement tool and the measurement date. You can repeat the same measurements in your own browser.
How do AEO and GEO differ from SEO?
SEO targets ranking. AEO (Answer Engine Optimization) targets being the source of the answer: question-and-answer architecture, extractable passages, FAQPage and HowTo schema. GEO (Generative Engine Optimization) targets being recognised and cited correctly by generative engines such as ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews, through entity clarity, crawler access policy and signals such as llms.txt. The three do not replace each other.
Do you work with clients outside Turkey?
Yes. We are based in İzmit, Kocaeli and work remotely with head offices and buyers outside Turkey; the English side of this site exists for that reason. Delivery, documentation and reporting are produced in Turkish and English. On-site workshops are practical in the Kocaeli and İstanbul region; elsewhere we work by video call. Commercial terms, currency and invoicing are agreed in writing before the project starts.
See the measured state of your digital assets within five working days.
The audit is free and creates no obligation to work with us. The report itemises AEO answerability, AI crawler access, Core Web Vitals, structured data validity and WCAG 2.1 AA gaps.
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.
Baki Bilişim · Karabaş Mah. Salim Dervişoğlu Cad., Ncity AVM, Kat 2 (Bowlingo katı), İzmit / Kocaeli, Türkiye · +90 507 817 27 17 · bilgi@bakibilisim.com