WebsiteClient case study

Rebuilt a clinic site around local search so patients book without phoning

Project: Pearl Dental ClinicVisit the live site (drmitali.com) ↗
Pearl Dental Clinic · live
Pearl Dental Clinic — Live Production Screenshot
30%upfront — less than almost any agency
Demostrigger the remaining payments — working milestones, not dates
100%refund if milestone one doesn't earn your trust. No questions.
What changed

Before, and after

Before

Patients phoning to ask basics

  • The site did not say what a treatment involved, so the question arrived by phone instead.
  • Booking meant calling during opening hours, and an unanswered call is a patient who rings the next clinic.
  • It was competing in one of Bengaluru's densest dental markets without the pages a local search would match.
  • Reception time went on questions a page could have answered.
After

Treatment pages that answer first

  • A page per treatment — implants, braces, root canal — that answers before the call.
  • Direct booking, so an enquiry does not depend on someone being free to pick up.
  • Built around local search rather than as a brochure.
  • Honestly: the ranking this was meant to win is still held back by client-side rendering. See the difficulty below — we would scope it server-rendered today.
01 / The situation

What they were up against

An implants, braces and root-canal clinic competing in one of Bengaluru's densest dental markets, with a website that wasn't bringing patients through the door. The practice trades as Pearl Dental Clinic and its site sits on the founding dentist's own domain, drmitali.com.

02 / What we built

What we shipped

A rebuild around local search — clear treatment pages, direct booking, and a structure Google can actually read.

03 / The hard part

What went wrong, and what we did

The site renders its content on the client, which search engines handle unevenly. It works for patients but it holds back the ranking this rebuild was meant to win, and moving it to server-rendered pages is the honest next step — we would scope that differently today.

The full account

What was asked for, and what was done

Asked for

The brief in their words.

  • A site that brought patients in rather than just existing.
  • Fewer phone calls asking what a treatment involves and what it costs.
Delivered

What actually shipped.

  • A page per treatment — implants, braces, root canal — each answering the question a patient would otherwise ring to ask.
  • Direct appointment booking, so an enquiry does not depend on someone being free to pick up.
  • A structure built for local search rather than as a brochure.
  • A 96/100 performance rating and first load under 800ms, which matters on a phone in a waiting room.
We suggested

Not in the brief. Proposed by us.

  • A section for international patients, which was not in the brief and is where the higher-value enquiries come from.
  • Moving the site to server-rendered pages. We have not done it yet and it is the honest next step — see the difficulty above.
Built to grow

Pointed at customers and revenue.

  • Treatment pages answer before the call, so reception time goes to patients who are already in.
  • Booking runs outside opening hours, and an unanswered call is a patient who rings the next clinic.
  • Local search is where a dental enquiry starts, and the site is now shaped for it.

Get your number in 2 minutes.

Instant estimate range. Exact quote after one 20-minute call. Held build slot. Money-back milestone one.

Book a call