The problem
The PWA handles bookings and staff operations, but the client needed a separate public website for services, reviews, identity and indexable content.
Case study
The H501 marketing website connected to the booking PWA.
The public H501 website is the marketing layer for the same H501 client: public content, services, work gallery, reviews, structured business data and direct CTAs into the PWA at h501.app.
Project facts
EcosystemH501 Barber
IndustryBarber brand
ProductMarketing website
StackNext.js 16, Vercel
StatusOnline
Related services
Live links
The solution
A dedicated Next.js 16 website was created with technical SEO structure, public pages, HairSalon/LocalBusiness structured data and booking flows linked back to the existing H501 PWA.
Features
- Next.js 16 App Router with static rendering
- Marketing homepage for H501 Barber Urbe
- Services, work gallery, reviews, about and contact pages
- Metadata, canonical, Open Graph, Twitter card, robots and sitemap
- HairSalon and LocalBusiness JSON-LD
- Privacy, cookie policy and terms
- Booking CTAs connected to h501.app
- Security headers and CSP configured
Technical stack
Verifiable evidence
- The project README documents the Next.js 16 marketing website for H501 Barber Urbe.
- The project responds publicly at home.h501.app.
- The live website includes canonical, robots, sitemap and HairSalon/LocalBusiness JSON-LD.
- Booking buttons point to the H501 PWA at h501.app.
Need a serious SEO website next to a PWA?
We separate what sells and ranks from what runs operations, without breaking the existing flow.