Case: Aleopt Plus (ChTPUP)
Aleopt: site and SEO — bulk materials, fertilizers, logistics in Babruysk
Replacing two “checkbox” WordPress sites with one intentional product: aleopt.by speaks in volume, delivery, and price — and captures local demand for aggregates, building materials, and fertilizers.
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 unified scope
Audit of two fragmented WordPress storefronts before the brand merge, redirect map to aleopt.by, agreed rubrics: aggregates, building materials, fertilizers, and services (logistics, heavy equipment).
SEO skeleton and semantics
Clusters for commercial intent: sand types, mixes, crushed stone fractions, fertilizers; title/description templates and schema for breadcrumbs and entities.
Card templates and order flow
Layouts for weight/packaging variants, pricing “with delivery in Babruysk”, “how to order” steps, lead forms and messengers — without mixing wholesale and retail in one funnel.
Next.js build
Catalog, category navigation, city/delivery direction selection, responsive UI, content from the approved Aleopt content structure.
Deep on-site SEO
Internal linking between related materials, duplicate URL cleanup, Organization and product microdata where appropriate, indexability and canonicals.
Local SERP and trust
NAP alignment (phone, warehouse address, hours), contact page and trust blocks; groundwork for maps visibility and reviews aligned with the new structure.
Launch and handover
aleopt.by go-live, redirects from legacy domains, baseline analytics and a post-release checklist for seasonal pricing and ongoing care.
Challenge
The old setup was generic WordPress: templated copy, weak ties to real assortment and how people search for sand, mixes, crushed stone, fertilizers, or tile. Two fragmented domains with overlapping offers and thin internal structure.
Approach
Single domain aleopt.by on Next.js: catalog branches for products and services with material types, fractions, and weight/volume on cards, plus delivery context for Babruysk and agreed locations. Technical SEO — clean URLs, metadata, internal links, JSON-LD, and fast pages.
Leads started within two weeks of launching the new structure. The site is now our main sales channel.
Implementation notes
How is the new site different from the old WordPress pages?
Each card targets a specific query: material type, fraction or packaging, price tied to delivery in Babruysk — not one paragraph “about everything”. Broader stack context is in the article on Next.js vs WordPress.
How did local visibility show up after the restructure?
When warehouse address, hours, and geography match what users see on the page, trust and the share of calls from maps and local modules grow. The “structure → leads” logic is closer to SEO architecture than one-off layout tricks.
What does ongoing support look like after launch?
Seasonal price and storefront updates, cluster monitoring, and targeted edits without breaking URLs — the frame stays stable. The search-care format is described under SEO support.
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.