Ziya Teknik: from Wix to Astro, a service site that gets found

Context

Ziya Teknik is a workshop in Mersin that rebuilds lithium batteries and builds custom battery packs. I covered the ads and the Google Business Profile separately (Paid Ads); this page is about the site itself.

The old site was on Wix. It didn’t look bad, but it had two problems: all the services sat on one generic page, and we had no idea who was pressing which button. While putting budget and effort into ads and local search, we couldn’t see what the page the traffic landed on was actually doing.

What I did

1. Built from scratch with Astro

I rewrote the site from the ground up on Astro with Claude Code. The output is fully static: pages are generated as HTML at build time, and the only JavaScript sent to the browser is the menu, the cookie banner and a few small interactions. Even the FAQ accordion runs on plain HTML <details>.

For the design language, I went with “technical data sheet”: thin lines, monospace data labels, and orange on navy used only for emphasis. The battery pack drawing in the hero isn’t an image file; the cell grid, dimension lines and callout arrows are generated in code. A battery workshop’s site opens with a drawing of the workshop’s own work.

The old Wix addresses (/services-1, /hakkımızda) 301-redirect to the new pages. In a migration, the easiest thing to lose is the links that old addresses have built up.

2. Content: in the language of search

Not everyone looking for this workshop types the same words. The robot vacuum owner and the tradesman with a dead cordless drill are searching for different things. So each of the seven services has its own section with its own heading — along the lines of “Cordless Drill Battery Rebuild — Mersin”. Each section lists the common symptoms, the work done and the compatible brands.

I built the FAQ on the same logic. The questions aren’t “What does our service cover?” but the way people type into Google: device + symptom. Something like “My e-bike’s range has dropped a lot — does the battery need replacing?” 83 questions in total, split into eight groups by device. The answers make no price or fixed-turnaround promises; the site doesn’t make a promise the workshop can’t keep.

3. Technical SEO

• Local business schema: AutoRepair type with address, coordinates, opening hours and service area (Akdeniz, Yenişehir, Toroslar, Mezitli).
• Service catalog: OfferCatalog + Service on the services page.
• FAQ: FAQPage and BreadcrumbList schema.
• One canonical address: the www/apex split was closed off, and the sitemap is generated automatically.
• Security and cache headers: HSTS, nosniff, and a one-year cache on built assets.

4. Tracking

The site’s real job is to make the phone ring, so that was the first thing I measured. With Umami (cookieless), every click lands as a separate event: phone (from ten different places on the site), directions, map, Google review, Instagram, Facebook and IBAN copy. Phone events also record which section the tap came from, so you can see which button brings in work.

GA4 runs with Consent Mode v2. GA4 writes no cookies until the visitor gives consent in the cookie banner; Umami counts regardless of consent, since it uses no cookies. That way visitors who decline don’t drop out of the stats.

5. A QR channel for the shop

I also added a /qr page that moves walk-in customers into digital: scanning the sign on the counter opens payment details, social accounts and a Google review on one screen. I wrote it up separately on the QR channel page.

Result

The site went live in September 2026. Each service answers its own search, and every phone tap on the site is counted along with where it came from. Results on the ads and Google Business Profile side are in the other case.