MovingCompany + 59-area areaServed
MovingCompany + LocalBusiness schema; areaServed: 39 Istanbul districts + 20 cities, each with GeoCoordinates.
Moving & Logistics · Case Study
Şahtur Nakliye — Istanbul + 20-City Home Moving Logistics Portal
A local SEO portal for Şahtur Nakliye — an Istanbul-based moving company serving 20+ cities nationwide — wired with MovingCompany schema, a 24/7 lead-gen form, and a 100,000 TRY insured-transport trust signal.
Results
Measurable Outcomes
39 ilçe + 20 şehir / 39 districts + 20 cities
Service area
100.000 TL / 100,000 TRY
Insured transport coverage
17. kat / 17 floors
Hydraulic lift reach
7/24
Service hours
The Brief
What was the goal?
85% of local moving searches use patterns like "[district] home moving" + "[intercity] moving price". At the same time, B2C buyers need to see insurance + insured transport + reference trust signals within the first 30 seconds. A one-page site can't serve both needs.
The Approach
Which methodology pillars I applied
I applied the Entity pillar (MovingCompany + LocalBusiness schema with areaServed: 39 Istanbul districts + 20 cities), Technical pillar (mobile-first, one-tap WhatsApp/phone CTA, sticky bottom call bar), and AEO pillar (FAQ blocks for "how much is moving in Istanbul?", "what is insured transport?").
See the full process → 47-Point AI-Ready SEO Audit methodology.
Tech Stack
What it's built with
- Next.js 15
- TypeScript
- Tailwind CSS
- Schema.org MovingCompany/LocalBusiness
- Vercel
The Build
Key decisions and tradeoffs
Combined MovingCompany schema with LocalBusiness. The areaServed array lists 39 Istanbul districts + 20 cities like Ankara, Izmir, Bursa, Antalya — each with GeoCoordinates and postalCode. Cracking the top 3 of Google's Local Pack for "Istanbul home moving" is downstream of this structure.
Differentiating trust signals — 100,000 TRY insured transport + 17-floor hydraulic lift + 24/7 service — sit as a trust bar under the hero. B2C moving buyers won't fill the form without seeing those three signals; form submission went up 41%.
WhatsApp + phone CTA lives as a sticky bottom bar on every page. On mobile, "call now" wins 62%, WhatsApp 38% — the two channels don't cannibalize, they stack conversion.
Service pages (home moving, office, intercity, piano/antiques, storage) sit on separate routes; each carries Service schema + FAQ + matching trust signals. Long-tail queries like "Istanbul office moving" get their own landing — not stealing homepage traffic, capturing their own long-tail.
Steps Applied
Methodology in practice
Trust bar: insurance + lift + 24/7
3-column trust signal under hero: 100k TRY insurance, 17-floor hydraulic lift, 24/7 service — form submission +41%.
WhatsApp + phone sticky CTA
Mobile sticky bottom bar; call 62% / WhatsApp 38% split — channels stack conversion together.
Service-per-route + FAQ
Home / office / intercity / fragile / storage on separate routes — each with Service schema + FAQPage, long-tail targeted.
Honest Reflection
What I'd Do Differently
On v1 I shipped the 39-district areaServed array as a single homepage list block — no per-district routes. Result: we beat homepage competitors on long-tails like "Ümraniye home moving" but couldn't claim Local Pack presence per district because we weren't asserting separate district pages. On v2 I'd build a landing page per district — the city × district pattern that worked at Tabelatr is just as critical in moving. That's the piece I missed at launch.
Screenshots
Want this for your project?
Same 47-point methodology, $499 fixed price, 5-7 business days. Book the audit.