Available for projects & agency overflow · Quick reply, from the person who does the work

A brochure website that makes first contact with a psychology centre easier

A psychology and counselling centre based in Turkey needed a Turkish-language website that presents each form of support clearly and makes getting in touch simple, especially from a phone.

Describe my issue Send a message

The context

The centre brings together a small multidisciplinary team: psychology, family counselling and dietetics. Each specialist runs their own consultations, and people looking for support mostly arrive through a local search, on a phone, with a specific question in mind: follow-up for a child, a relationship difficulty, nutritional guidance. Putting everything on a single generic page did not really answer any of those searches.

The sector adds its own requirements. Contacting a psychologist is not like ordering a product: the step is often a hesitant one, and first contact has to be simple, discreet and possible through whichever channel the person prefers. Even a name and a number left for a callback falls under KVKK, Turkey's personal data protection law, which requires clear information on how the data is used and how long it is kept.

The need

Expectations were clear: a site entirely in Turkish, a dedicated page for each service rather than a plain list, a presentation of the team that builds trust, several friction-free ways to get in touch, and content that could be found in local searches. The site had to stay fast on mobile, be hosted and maintained without the centre having to deal with it, and be able to evolve without depending on a third-party theme or plugin.

A bespoke PHP build was therefore chosen over a general-purpose CMS. The scope was known in advance and was not expected to change often; keeping the code to what the site actually needs reduces both the attack surface and the maintenance workload.

What I did

  1. One page per service

    Each service has its own page, with its own title and description, to answer a specific search rather than a generic query. An “About” page introduces the team and the centre's way of working.

  2. Several routes to first contact

    Appointment requests, a callback form and a WhatsApp button: visitors choose the channel that suits them. On mobile, a call bar stays fixed at the bottom of the screen so the centre is one tap away.

  3. A spam-protected callback form

    Callback requests go through a dedicated API endpoint that checks the submitted data and filters out automated submissions, so the team only receives genuine requests.

  4. A blog built for local search

    A section of articles covers the questions people ask before booking a consultation, with a local angle, so the site is found in searches from the area and not only on the centre's name.

  5. A KVKK information page

    A dedicated page explaining which data the forms collect, for what purpose, how long it is kept and how cookies are used.

  6. Performance, hosting and maintenance

    Versioned static assets, so browsers cache them without ever serving an outdated file after an update, and lightweight pages for mobile. I then look after hosting, on o2switch, and ongoing maintenance.

Services used on this project

Frequently asked questions

Why a bespoke site rather than a CMS?
The scope was stable and known in advance: service pages, a blog and a few forms. A targeted PHP build avoids carrying a theme and plugins the site would only have used a small part of, and cuts down the security updates to keep track of accordingly.
Why is the site only in Turkish?
The people who come to the centre are local and Turkish-speaking. A single, carefully written language serves that audience better than several approximate versions.
What does KVKK change for a site like this?
KVKK is Turkey's personal data protection law, often compared with the GDPR. As soon as a form collects a name or a phone number, the person must be told how that data is used and how long it is kept. In healthcare, where simply getting in touch is already sensitive, that transparency matters all the more.
How are callback requests protected against spam?
The form does not send an email directly: the request first goes through an API endpoint that checks it and filters out automated submissions before passing it on to the team.
Who looks after the site day to day?
I handle hosting and maintenance. The centre has no server to run and no technical updates to watch, and keeps a single point of contact for any question about its site.

Describe your need in one minute

A few targeted questions so I can reply with an estimate rather than another questionnaire.

similarite
difference (facultatif)
contexte
echeance (facultatif)
Please provide an email or a phone number so I can get back to you.

Please provide an email or a phone number so I can get back to you.