Pick the sentence closest to yours: it shows which service to start with and what comes alongside. Each service’s specification is below — who it is for, what is delivered, how it proceeds.
SituationWebSEOGEOB2BAccessibilitySpeedMigration
start · alongside
SPECIFICATION FILE
Specifications for seven services.
01 / 07
Web Design + Development
From editorial art direction to a static, fast build: we do both the design and the code.
If this is you
“We need a new website.”
“Our site loads slowly.”
“We’re relaunching; we don’t want to lose our rankings.”
Delivered
Editorial design + type system
Multilingual architecture (TR · EN · DE)
Motion choreography — reduced-motion included
Accessibility: AA baseline
Performance: built to LCP < 0.8s
How it proceeds
Discovery + scope
Art direction
Build
Measure + handover
Timeline
A single-language site takes 3–5 weeks, a three-language corporate site 6–10.
What sets the price
We set the price by scope in a written quote; we do not publish a package list. Three variables carry the cost: how many templates, how many languages, how many third-party systems.
A search engine can only rank what it can read. We build pages that get crawled, indexed and read correctly.
If this is you
“We don’t show up on Google.”
“AI answers never mention us.”
“We export; buyers can’t find us in their own language.”
Delivered
Technical SEO audit and fix plan
Structured data: schema + entity
Content architecture and templates
Multilingual hreflang setup
Measurement: verifiable metrics only
How it proceeds
Audit
Architecture
Content system
Monitoring
When the effect shows
Technical fixes usually surface in crawl and index data within 2–6 weeks.
What sets the price
The audit and the build are separate items; we set the price by scope in a written quote. The variables that carry cost: site size, number of languages, and who implements the fixes.
AEO layer: question-answer structure and citable passages
llms.txt and AI crawler policy
Agent visibility: first-party crawler logging
How it proceeds
Visibility audit
Entity architecture
Citable structure
Agent measurement
What sets the price
The audit and the build are separate items; we set the price by scope in a written quote. The variables that carry cost: site size, number of languages, and the current state of your entity architecture.
A buying committee first gets to know a manufacturer or exporter through its website. We build products, certificates and the route to a quote in the target market’s language, and we measure them.
If this is you
“We export; buyers can’t find us in their own language.”
Delivered
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
How it proceeds
Product and document inventory
Product architecture
Built in the target market’s language
Quote flow and measurement
What sets the price
We set the price in 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.
We fix keyboard, contrast and screen-reader issues directly in the code. We audit the site criterion by criterion against WCAG 2.2 and document the result; if Turkey’s Presidential Circular or the European Accessibility Act applies to you, we also provide proof of compliance.
If this is you
“Accessibility rules apply to us.”
Delivered
WCAG 2.2 AA audit: by template and critical flow
Ministry checklist (level A): question by question
Keyboard, screen reader and contrast testing — by hand
Fixes at the source or a prioritized fix list
Accessibility statement and regression checks
How it proceeds
Inventory and scope
Automated and manual testing
Fix at the source
Re-test and statement
SPECSPC-05SERVICE@type ServiceTIMELINEin writing, by scopeUPDATED2026-11-16SHEET05 / 07
We first measure why the site is slow, then fix the cause at the source. We start from real-user data, trace the root cause and hand over speed with a budget for the three Core Web Vitals: LCP, INP and CLS.
If this is you
“Our site loads slowly.”
Delivered
Core Web Vitals audit: LCP, INP, CLS — field and lab
Root-cause report from a browser trace
Image, font and JavaScript weight fixes
Performance budget and pre-release measurement
Optimise or rebuild: a decision with reasons
How it proceeds
Field data first
Root-cause trace
Fix at the source
Budget and guard
SPECSPC-06SERVICE@type ServiceTIMELINEin writing, by scopeUPDATED2026-11-16SHEET06 / 07
When we redesign a site, we connect every address Google knows to the right place on the new site. We take an inventory of the old addresses, build a chain-free 301 map, test every redirect on launch day and monitor for 90 days after the move.
If this is you
“We’re relaunching; we don’t want to lose our rankings.”
Delivered
Old address inventory: Search Console, sitemap, crawl
301/410 redirect map — no chains
Line-by-line verification on launch day
Domain, HTTPS and www migrations
90-day post-migration monitoring report
How it proceeds
Address inventory
Redirect map
Launch-day verification
90-day monitoring
SPECSPC-07SERVICE@type ServiceTIMELINEin writing, by scopeUPDATED2026-11-16SHEET07 / 07
We do not report an improvement as “done” unless we can measure it.
Not an extra, the baseline
Accessibility — WCAG 2.2 AA
Performance budget
Multilingual architecture
FREQUENTLY ASKED QUESTIONS
@type FAQPageQuestion × 8
S. 01 / 08
Should I buy web design and SEO together?
Buying them together is not cheaper, but it is less work: a design decision sets the performance budget, a template decision sets schema coverage. When different people do them, the decisions get reversed later. They can still be bought as separate items.
S. 02 / 08
How much does a custom website cost in Turkey?
We do not publish a package list; we set the price by scope in a written quote. Three variables carry the cost: number of pages and templates, number of languages, and third-party integrations. We scope it in one call and send the written quote the same week.
S. 03 / 08
How long does it take to build a website?
A single-language site takes 3–5 weeks, a three-language corporate site 6–10. The process has four steps: discovery and scope, art direction, build, measurement and handover. We do not start production without your approval.
S. 04 / 08
Where are you based, and do you work with clients outside Turkey?
The studio is based in Istanbul, and we work fully remotely with clients across Turkey and Europe, in Turkish, English and German. We meet on site when it matters, but proximity is not a requirement.
S. 05 / 08
Why static sites instead of WordPress?
A static build is the most direct way to hold the performance budget (LCP < 0.8s, CLS 0): no plugins running on a server, no version upgrades, no attack surface. If a project genuinely needs WordPress, we say so in the first call.
S. 06 / 08
Can I buy the services separately?
Yes. Web design and development, SEO consulting and GEO consulting are separate items and can be bought on their own. When you buy them together, we make each decision once and measure it across all three layers.
S. 07 / 08
Will you work alongside our existing team?
Yes. If you have a content, marketing or engineering team, we build on top of their work; the handover includes a layer of rules (design tokens, schema at template level, pre-release audit steps) so the decisions survive after you take over.
S. 08 / 08
Who owns the site after handover?
We transfer all code and content sources to you; you are not tied to a locked panel or a subscription. The handover package includes repository access, setup notes and the measurement tools.