Case: SP Valery Markevich (Delt)
Delt: site and SEO — demolition, waste haul, and aggregates in Homiel region
WordPress mixed demolition, hauling, and bulk sales into one blur; delt.by is a separate product story by scenario and city, with marketing and SEO aligned to real queries.
Project stack
- Next.jsv14.1
Framework
- Reactv18
Framework
- TypeScriptv5
Developer tooling
- Tailwind CSSv3.4
Developer tooling
- Node.jsv22
Runtime
- Hoster.by
Infrastructure
Production hosting
Key milestones
Dates and wording are generalized to illustrate the process; the actual schedule and artifacts were recorded in the project working docs.
Kickoff and scope alignment
Legacy WordPress audit: where services and product lines blurred; separate flows for “demolition/haul” vs “aggregates”, city list for the first wave of landings.
IA and SEO draft
URL tree for local and service-led queries; meta drafts without duplicated intent across branches.
Next.js build
Service and bulk catalog, geo navigation, lead forms, fast pages for mobile traffic.
Deep SEO pass
Commercial phrase clustering, H1–H2 and body copy tuned to intent, catalog and local block interlinking.
Iterations and tech
Feedback-driven tweaks, microdata checks, stable rendering in search snippets.
Launch
delt.by go-live, handover playbooks for price updates and geo expansion without changing the URL frame.
Challenge
The old site collapsed different lines: demolition, waste removal, and crushed stone reads as one vague service. Neither search nor people got a clear answer by city or intent.
Approach
New delt.by: split service and bulk branches, geo navigation, distinct request flows. A short brand domain scales better than keyword domains locked to a single query.
The site reflects the full cycle — demolition, hauling, and supplies — so clients pick a scenario and submit a lead.
Implementation notes
Why not keep everything on one long page?
Different jobs need different proof and forms: hauling vs crushed-stone supply differ in timing, equipment, and logistics. Mixing on one screen raised bounces and diluted search relevance — see structure and conversion.
How did geography enter the UI, not just the footer?
Users pick city or direction context before pricing and CTAs — less “we don’t care where you call from”. A similar milestone pattern lives on the Bureau page.
Does a new service or town always mean a new site?
No: the URL and navigation frame was built to extend with new pages and links, not a full rebuild. Technical routing patterns are in the solution library.
Want a similar systematic outcome?
Name, phone, and site in the brief form. The reply covers structure, phases, and a budget range; market specifics follow on the call.