Corporate Website

A corporate website is not a business card pasted onto a screen. Someone opens it from search, a referral, or a link the sales team sent. The first screen has to say what you do, who it is for, and what the next step is. Yuz Medya builds that page in Istanbul with design, software and content at the same table. The aim is a quote, an appointment or an enquiry that reaches the right person.

Recoloring a stock theme does not do this job. The menu, service pages, proof and the form have to recognize each other. After launch you should change copy, people and news from the panel. The site should not stay locked on the agency’s computer.

Who it is for

It fits companies that sell services, collect quotes, recruit dealers or candidates, or operate more than one location. A manufacturer, a consultancy, a school and a hotel do not share one template. One of them leads with product groups and documents. Another leads with the team, the method and a booking.

When the real job is a catalog and a cart, the path moves to an ecommerce website. When the editorial team already lives in WordPress, or the work needs a custom panel and API, the WordPress / PHP software brief opens beside this one. The corporate page set itself is the process described here.

What discovery has to settle

We start from the sentence of the business, not from a page inventory. We ask who decides, which objection sales hears every week, and what “done” means on the site. Without those answers the design can look finished while the visitor still does not know what to ask for.

• The offer in one sentence, and the work you knowingly decline
• A real hierarchy of services, sectors or locations
• Who receives the form, how fast, and which fields are required
• Which languages ship on day one
• What copy, logo, photography and reference permission you already have
• Who holds the domain, hosting and mailboxes

Information architecture and the first screen

The menu does not have to mirror the org chart. The path to the job a visitor came for stays short. A service page is not a copy of the about text; it states scope, process and the next step. References appear only with permission and with context. We do not add invented client counts.

The homepage does not shout everything at once. The top holds the offer, who it is for, and one primary button. Lower sections carry services, selected work, a proof block and a short contact band. A blog opens only if someone will actually write. An empty news category does not make the site richer.

Interface, mobile and the brand face

Layout starts at mobile width. The form, phone and address are reachable with a thumb. Type and space keep long service copy readable. Color comes from the identity you already have. If that identity is scattered or missing, corporate identity can share the same calendar. The site is not locked to a random palette.

Photography does not have to be a stock “team smiling in an office”. When a shoot is needed, photography is planned from the page layouts. Copy should sound like you. If content production is part of the job, voice is locked in discovery and the page launches with that text.

Laravel, Filament and a panel you run

The usual stack for these sites is Laravel, with Filament for the admin. Pages, services, references, people, articles and form entries live in the panel. An editor updates titles, summaries, images and SEO fields without writing HTML. Where roles differ, the person who drafts and the person who publishes can be separate.

Languages are built with the URL structure, not patched on later. Turkish sits on the root, English on its own path, with language tags from the start. Adding a language after launch means rebuilding menus and forms. Form notices go to email. If you already have a CRM, field mapping is a separate conversation. We do not pretend an integration exists when it does not.

Speed and lean markup

A pile of unused plugins and oversized images slows the first screen. Images are sized and key pages stay plain. Speed is on the pre-launch list. We do not recommend stacking the same third-party widget on every template.

Forms, privacy and access

Contact and quote forms do not ask for fields nobody will use. A privacy notice and consent sit next to the data you actually collect. The panel opens with a strong password and limited roles. Certificate, backups and the update routine are written into the launch note.

An SEO base, not a ranking promise

Title fields, descriptions, heading order, readable URLs, a sitemap and a Search Console connection are part of launch. That is a floor for visibility. Position depends on competition and on how long the content has been useful. We do not promise a first page. Deeper work sits in technical SEO and on-page and off-page SEO. If branches and map intent matter, local SEO can share the brief.

Clinics, practices and healthcare sites

A hospital group, clinic or practice does not fit inside a generic corporate template. Clinician profiles, a treatment hierarchy, appointments and privacy-aware contact need their own structure. Yuz Medya runs that work through Doktor Site Tasarım, the studio dedicated to healthcare websites. Services, references, careers and extra languages still follow the process on this page.

Launch, training and the first weeks

Drafts move with your approval. If copy arrives late, the calendar moves; we say that at the start. Launch checks the domain, redirects, the form and basic analytics events. Panel training happens once it is clear who will edit. Through the first month we stay for a broken form, a missing redirect and small copy fixes.

Duration follows page count, languages and integrations. A tight corporate site with copy ready is not the same job as ten services, two languages and a custom application flow. We write the range in discovery. We do not invent a three-day delivery line.

Project stages

A corporate site moves in six steps. The calendar depends on pages, languages and how fast copy is approved. If approval slips, launch slips. We write that down at the start.

• Discovery: the offer, the form owner, languages, the domain
• Map: menu, page types and one primary action
• Interface: mobile-first sample pages
• Build: Laravel, Filament, the form and languages
• Content: approved copy, images and redirects
• Launch: form test, training and the first month of fixes

Advantages

Design, the panel and measurement stay with one team. The page is not locked in an agency file. The person who enters content uses the Filament screen.

Common mistakes

The menu that copies the org chart and buries the service, the about text pasted on every page, and a form with ten fields are the three mistakes we see most. Adding English in the last week as a loose translation is the fourth. If the first screen does not say what to do next, the design is not finished.

What to send next

Send the current address, the languages you need and the enquiry you want from the site through the contact form. After discovery we lock the page map, the stack (Laravel and Filament) and the first delivery slice. If ads will run, landing pages belong on that map. We do not start a campaign on a button nobody can measure.