Service and area pages, not one thin homepage.
People search the job plus the place. We build local service sites as a set of pages with matching titles, and we treat Google Business Profile as a sibling, not a substitute for the website.
- 10
- Products built in-house
- 12
- Web projects in the portfolio
- 04
- Site languages: EN, TR, ES, DE
- UTC+3
- Overlaps US mornings and the full EU workday
A plumber, cleaner, or upholstery studio does not rank because the homepage says 'quality service in our city.' Search engines need a page whose subject is the service, and often a page whose subject is the service in a named area. MASAL Koltuk is the public example: fifteen days ago they had no website; today Google and AI put them first.
One job per URL
Sofa cleaning, mattress cleaning, and office cleaning are different queries. They can share a visual system. They should not share one paragraph on Home. Give each service a title, an H1, proof, price context if you publish it, and a form that names that job.
Area pages only exist when you actually serve that area. Copying the same text and swapping the town name is how you get ignored. Write what is true: travel, parking, typical buildings, response time.
Google Business Profile is not the website
The profile sends people who already trust the map pack. The website still has to answer the service query, show work, and take the request. Categories and photos on the profile should match the pages, not contradict them.
We do not sell 'we will get you into the map pack' as a product. We make the site a crawler can understand and a visitor can finish. Rankings on Maps depend on many signals we do not control.
What technical SEO means here
Titles, unique service copy, internal links between related jobs, canonicals, sitemap, and NAP consistency with the profile. Schema for LocalBusiness and the services you actually offer, without fake reviews or invented aggregate ratings.
A rebuild must redirect every service and area URL you already have. Local pages are often the only equity a small firm owns.
After the call comes in
If WhatsApp is how jobs are booked, the page should open a message that already contains the service and area. If the office needs a list of leads, that is a panel or a CRM handoff in scope.
Do not bolt a generic chatbot onto a one-page site and call it automation. The page set comes first.
Starting a local service site
List the jobs you sell, the areas you truly cover, the current domain, and whether price pages exist. Say if this is a first site or a replacement of a thin brochure.
We will tell you how large the page set should be. More towns is not automatically better. Honesty of coverage is.
Local Search & Lead Capture
Turn high-intent local searches into booked jobs
Dedicated page per service and area
Separate, non-duplicate pages for each core service and service corridor aligned with your Google Business Profile.
Instant mobile quote & call path
Sticky call/WhatsApp actions and 30-second estimate forms designed for customers searching on their phone.
CRM pipeline & review velocity
Every call and form submission lands in a simple dispatch board with automated follow-ups.
Scope
What is included
Custom Next.js frontend with mobile-first typography and fast page transitions
Role-based admin & CRM dashboard tailored to your catalog, inquiries, or bookings
Searchable HTML specification tables, media galleries, and structured intake forms
WhatsApp, Instagram, or AI assistant integration with human handoff summaries
Technical SEO & GEO package: reciprocal hreflang, canonicals, XML sitemap, and JSON-LD graph
Full source code ownership, staging reviews, and no third-party plugin lock-in
How a project runs
From first conversation to launch
Discovery
We document the business goal, audience, available material, and technical constraints.
Scope
Pages, features, priorities, responsibilities, and review criteria are written down.
Design
We establish the interface, component rules, and a CSS design system when the project needs one.
Development
We implement the approved interface and connect the required panels, CRM functions, or messaging tools.
Quality review
We review mobile behavior, performance, core accessibility requirements, and technical SEO.
Launch
The approved release goes live with the agreed support period and content handoff.
Technology used in this work
- HTML
- CSS
- JavaScript
- JSON-LD
- Local SEO
- OpenStreetMap
- Next.js
- React
- Tailwind CSS
Questions we are asked
How many area pages should we have?
As many as you serve and can write honestly. Ten copied towns is worse than three specific ones. We plan the set in the website scope, not as an afterthought.
Do you guarantee first place on Google Maps?
No. We build indexable service and area pages and keep names, address, and phone consistent. Map pack rank is not a deliverable anyone can honestly guarantee.
Can this include WhatsApp booking?
Yes. The form or button can pass the service name into WhatsApp. A full chatbot is a separate service when repeat questions justify it.
What is the MASAL example?
15 days ago they had no website. Today they sit first on Google and on AI. After launch, people called. The firm found new customers.
List the jobs and the areas you cover.
Current domain and whether prices are public. We will reply with a sensible page set, not a town-name generator.