In repair work customers do not search for a brand, they search for their problem: “fridge not cooling”, “boiler error F28”, “washing machine repair in Yahşihan”. The site we built for Çalışkan Beyaz Eşya is split along exactly that language. It has 55 error-code pages branching by brand under six appliance categories, 12 brand service pages and a separate service-area page for each of nine districts including the centre; each of its 109 pages maps to a real search. The site is published statically, so pages open instantly — for someone searching from a phone while the appliance is broken, that is the metric that matters most. The red trade identity is built around one-tap calling and WhatsApp on every screen, plus an open service-pricing page.
Çalışkan Beyaz Eşya — Local Search Site
A 109-page local search site for an appliance and boiler repair service in Kırıkkale, built around error-code and district pages.
Visit site ↗
For Çalışkan Beyaz Eşya, an appliance and boiler repair service in Kırıkkale, a 109-page local search site built around error-code and district pages.
Problem
In repair work customers do not search for a brand, they search for their problem: “fridge not cooling”, “boiler error F28”, “washing machine repair in Yahşihan”. A single-page brochure site answers none of these — visitors never find it, and when they do, the fault they came for is not there. And the person running these searches already has a broken appliance: they decide within minutes, almost always from a phone.
Solution
- A 109-page structure built in the language of the search — each page answers exactly one real need
- 55 error-code pages branching by brand under six appliance categories — the user types the code on their display and lands straight on the answer
- Separate service-area pages for nine districts: centre, Yahşihan, Bahşılı, Keskin, Delice, Karakeçili, Sulakyurt, Çelebi and Balışeyh
- Twelve brand service pages plus appliance-level pages (fridge, washing machine, dishwasher, boiler, air conditioning, oven, dryer)
- A conversion-focused red trade identity: one-tap call and WhatsApp on every screen, and an open service-pricing page
- Static publishing — no server-side computation, pages open instantly; for a user waiting with a broken appliance that is the metric that matters most
Technology
Technical service is one of the most local-search-driven trades there is: the customer searches while the fault is happening and dials the first number that earns their trust. A one-page brochure will not do; the work needs a structure split along the language of search, with dedicated pages per fault and per district. The model we built for Çalışkan Beyaz Eşya is our reference for local appliance, boiler and air-conditioning services.
FAQ
Why so many pages? +
Each page answers a different search. “Boiler service”, “Vaillant F28 error” and “appliance repair in Keskin” are not the same query; trying to serve them all from one page means appearing in none of them.
What are the error-code pages for? +
When someone sees a code on their appliance display, the first thing they do is search it. That search sits closest to actually calling a technician. A page that explains the code and says what to do genuinely helps the visitor and puts the company in front of them at precisely that moment.
Could you build this for another city or trade? +
Yes. The model scales across cities and service breakdowns; the district, brand and fault tree is re-derived from the realities of the business. What matters is not the page count but that every page maps to a real search and a real answer.