Inside Kumari Sarsafai Sewa: Building a Sanitation Service Website That Was Designed to Rank, Not Just Look Good

Sanskar Shrestha

Author

6 min read
Inside Kumari Sarsafai Sewa: Building a Sanitation Service Website That Was Designed to Rank, Not Just Look Good — Development | SudamHub Blog

When Kumari Sarsafai Sewa approached SudamHub to build their website, the brief wasn't about animations or a clever layout. It was about something far more practical: when someone in Kathmandu's overflowing septic tank searches for help at 11 p.m., can they find this business before they find a competitor?

That single question shaped almost every decision we made on this project — from how the admin panel was structured, to what counted as "content," to which parts of the site got built first.

Sanitation and cleaning services are an unusual category to build for. Nobody browses a septic tank company's website for inspiration. People land on it because something has gone wrong and they need it fixed, or because they're planning ahead and comparing who covers their area. That means the website has exactly one job: show up in the search, and answer the visitor's question in the first ten seconds. Everything else is secondary.


The Brief: A Business Built on Trust and Local Visibility

Kumari Sarsafai Sewa offers both cleaning and waste/sanitation services — septic tank cleaning, soak pit maintenance, and general sanitation work — based out of Nayabasti, Boudha, in Kathmandu. Their actual service radius stretches well beyond the valley: Kathmandu, Lalitpur, and Bhaktapur as the core market, with coverage extending out to Dhading, Trishuli, Kavre, and Sindhupalchowk.

That geography mattered more than it might for a typical business site. A generic "we serve Nepal" website would rank for nothing. A site that clearly, structurally signals which neighborhoods and districts it actually serves has a real shot at showing up when someone nearby searches for help. So from day one, SEO wasn't a phase we'd get to later — it was the priority the entire build was organized around.


Why We Didn't Start With Design

Most website projects start with how it should look. This one started with how it should be found.

Before a single hero section was styled, we mapped out the actual search intent: what does someone type when their tank is overflowing versus when they're planning routine maintenance versus when they're comparing sanitation companies in Boudha? Those are three different visitors with three different levels of urgency, and the site needed to serve all three without making any of them dig for what they came for.

That decision meant treating the blog and service pages as first-class, structured content from the start — not an afterthought bolted onto a template. It also meant getting the technical foundations right before anything else: canonical URLs, structured schema markup, an actual sitemap and robots.txt, none of which existed on the business's previous basic setup. Before this project, the site had nothing beyond a title tag and a meta description — no canonical tags, no schema, no sitemap. Search engines had almost nothing to work with.


Built on Laravel and Filament — With an Admin Panel the Client Can Actually Use

We built the site on Laravel with a Filament admin panel, which is our standard stack for client sites that need to be genuinely self-manageable after handover — not sites where every content change requires calling the developer back.

The panel covers four core areas: Hero Slides, Services, Blog, and Legal Pages, each with its own dashboard widgets — stats overviews, charts, and tables — so the client can see engagement and content activity at a glance without digging through raw data.

A few decisions here were deliberately specific to how this business actually operates, not generic CMS defaults:

  • Footer settings are a singleton, not a list. There's only ever one footer configuration, so instead of forcing the client to manage a "table" of one row, we built it as a dedicated settings page tied to a single record.

  • Social links use a fixed platform dropdown (Facebook, Instagram, YouTube, TikTok, X, LinkedIn) paired with a URL field, stored as JSON — enough structure to keep icons and ordering consistent, without limiting how many platforms the client can add.

  • Locations, emails, and phone numbers are each stored as JSON arrays, because a sanitation business fielding calls across multiple districts genuinely needs more than one contact point listed, and the admin panel needed to make adding another one as easy as clicking "add," not editing a template file.

  • Operating hours are a single shared range, not per-day scheduling — because that's how the business actually operates, and adding per-day complexity would have made the admin panel harder to use for no real benefit.

The hero section on the homepage mixes static and dynamic content on purpose: the two call-to-action buttons stay fixed, since those drive the exact conversion paths the business wants every visitor to see, while everything else in the slider — images, headlines, copy — is fully editable from the Hero Slides resource.


Making SEO Structural, Not Cosmetic

The single biggest technical shift on this project was moving SEO out of "add some keywords to the page" territory and into the site's actual architecture.

We built out a hybrid local SEO strategy: Kathmandu as the primary target market, with Boudha and Nayabasti — the business's actual home turf — layered in as secondary, service-area-specific targeting. That distinction matters because it lets the site rank for broad searches across the valley while still winning the tightly local searches where the business has a genuine home-field advantage.

Rather than write a separate SEO audit document and hand it over as a report, we implemented every fix directly in the Blade templates as we found it — canonical tags, schema markup, proper meta structures, sitemap and robots.txt generation. For a project where the client's priority was visibility, not documentation, shipping the fix was more useful than writing about the fix.

The business's Google Business Profile existed before we started but wasn't optimized — a common gap we see with service businesses that got a listing set up early on and never revisited it once the actual website caught up.


What This Project Reinforced

Not every website needs a signature animation or an experimental layout. Some websites need to be fast, structurally sound, easy for a non-technical team to update, and built around exactly how people search when they need this specific kind of help right now.

Kumari Sarsafai Sewa's website isn't trying to impress anyone with its design. It's trying to be the result someone finds in Boudha, in Kathmandu, in Kavre, at the moment they actually need it — and to let the business update its own services, hours, and contact points without ever needing to open a code editor.

That's the kind of project we enjoy building, because success isn't subjective. It's measurable: does the phone ring more, and did it show up in the search that mattered.

Have a service business that needs a website built around how customers actually find you? Get in touch — sudamhub.com/contact — for a free consultation.

Tags

#Kumari Sarsafai Sewa website #Laravel Filament project Nepal #septic tank service website #sanitation website Kathmandu #SEO web development Nepal #Filament admin panel Nepal #SudamHub case study #waste management website Nepal #custom CMS Laravel Nepal #local SEO Kathmandu website
SUDAMHUB
Let's Connect

Have a project
in mind?

We are always excited to collaborate on innovative projects. Let's create something amazing together!