ProjectsWork with meWritingAboutSay hi →
ON THIS PAGE01/07
  1. 01The problem
  2. 02Constraints
  3. 03What I shipped
  4. 04The hard parts
  5. 05Result
  6. 06What I'd do differently
  7. 07Takeaway
ON THIS PAGE01/07
  1. 01The problem
  2. 02Constraints
  3. 03What I shipped
  4. 04The hard parts
  5. 05Result
  6. 06What I'd do differently
  7. 07Takeaway
All writing
Conversion Landing Page — one clean page fixed visibility, trust, and bookings in a week
Case study

Conversion Landing Page — one clean page fixed visibility, trust, and bookings in a week

A local shop had zero online presence — searching for them returned nothing. One clean, fast page fixed all three problems in a week.

eBy eloi·November 10, 2025·4 min read
SHARE
Client
Private — local business
Role
Design · Build · SEO
Year
2025
Stack
Astro · Tailwind · Cloudflare · GA4

The problem

A local shop with a good real-world reputation had zero online presence. Searching for them by name returned nothing. Searching for their category in their neighborhood, competitors filled the first page.

Three failures compounding:

  • Not findable. No Google Business Profile, no site indexed, no local citations.
  • Not trustable. Anyone who did find them landed on nothing. No hours, no services, no pricing, no way to see if they were legit.
  • Not bookable. Even if a customer was ready, no way to book online. Everything went through walk-ins or phone.

They didn't need a full marketing site. They needed one clean, fast page that fixed all three — findability, trust, bookings — for a fixed one-week timeline and a landing-page budget.

Constraints

  • One week end-to-end. Design, copy, build, launch, handover.
  • Landing-page price point. Fixed at the Landing Page package. No scope creep.
  • Mobile-first, always. Most local searches happen on phones — desktop was a nice-to-have.
  • One-tap booking. Not a form to fill in. Not “call to book.” One tap → a live booking calendar.
  • They own it after handover. Domain, DNS, hosting all in their name. No “we host it and it breaks the day you stop paying us.”

What I shipped

  • Mobile-first page built to convert, not decorate. Hero → value props → services → pricing → photos → book. Every section earns its scroll.
  • Clear services, transparent pricing, one-tap booking. No “call for a quote.” Every service is listed with a real price, and every service has a “Book →” button that opens a calendar in one tap.
  • Real photography woven into the layout. Existing photos re-cropped, color-corrected, and placed intentionally — not the generic “hero + stock photo grid.”
  • On-page SEO + structured data + GA4. Schema.org LocalBusiness markup, opening hours, service catalog, pricing. Sitemap, robots.txt, meta tags done properly. GA4 wired in with event tracking on booking clicks.
  • Domain, DNS, and hosting handed over ready. Domain registered in their name, DNS on Cloudflare, hosting on Cloudflare Pages. Full admin credentials on delivery.

The hard parts

One week isn't much for a page that converts. The temptation is to build the page fast and worry about conversion later. Instead I built the page in two days and spent the remaining three refining copy and the booking flow. A page that ranks but doesn't convert is a slower failure than a page that doesn't rank.

Local SEO on a fresh domain. A brand-new domain doesn't rank overnight. I did what I could pre-launch: LocalBusiness schema (with hours, address, phone, service catalog), Google Business Profile setup + verification, submission to local directories (Google, Apple Maps, Waze, local aggregators), and page copy written for the actual queries their customers use (colloquial local terms, not industry-standard jargon).

Choosing Astro. For a static landing page with SEO priority, Astro ships less JS than Next.js and gets top Lighthouse scores by default. Tailwind for styling, Cloudflare Pages for hosting (free, fast global CDN, no cold starts). Right stack for the page's actual needs — React would've been overkill.

Result

Ranks locally · measurable bookings. Within a month, they were showing up on the first page of local searches for their category. Bookings coming through the one-tap calendar are trackable (GA4 event), so they know exactly what the site is producing.

The client operates it themselves. Pages, prices, photos, and Cloudflare DNS all in their control. No ongoing dev dependency.

What I'd do differently

Should've set up uptime monitoring on day one. The site is on Cloudflare Pages (which basically never goes down), but the client's Google Business Profile has been paused twice for verification issues that a simple monitor would've caught faster. Adding it retroactively, but should've been part of launch.

Takeaway

Landing pages are underestimated. A well-built single page can outperform a 20-page marketing site for local businesses whose actual traffic pattern is “someone Googles them, checks legitimacy, books.” Everything past “one page” is scope for scope's sake if the business goal is bookings — not brand storytelling.

NEWER POST

Wednesday — a Python voice assistant with a cold personality

Case study
KEEP READING

You might also like

  • Case studyAug 5, 2026

    Portfolio + Quotation Site — a decade-old modular design firm goes online

    A Philippine modular design + construction firm needed a proper web presence — portfolio-forward, quotation-ready, and a dealer login for their agent network.

  • Case studyJul 20, 2026

    Client Portal — one branded hub for an agency drowning in tabs

    Leads in one tool, chats in another, campaigns somewhere else. The agency needed a single branded place that answered "what's actually happening this week?" So I built it.

designed, built & shipped
by one person.
Site
ProjectsWritingWork with meProcessAbout
Where
Philippines
Working worldwide
GMT+8 · async-friendly
Talk
eloi · made with care · © 2026
Privacy·Terms·Sub-processors
Available for new projects