The organic-growth process behind Cydro Engineering’s website
A six-year platform relationship with Cydro Engineering, a Sri Lankan construction and engineering firm — rebuilt onto modern Next.js in 2026, and now the live, currently-running example of the process behind the Landing Pages & Organic Growth service: intent-mapped pages, a clean technical foundation, and continuous keyword/backlink monitoring.
Freelance Full-Stack Engineer & Organic Growth Consultant — platform build plus ongoing SEO engagement
Platform: 2020–present, rebuilt 2026 · Organic-growth engagement: a few months in, ongoing
Cydro Engineering offers construction, architectural, structural, and quantity-surveying services across Sri Lanka. The site started in 2020 as a Create React App build on Prismic CMS and was rebuilt in 2026 on Next.js 14 — same long-term client, modernized platform. Separately, and more recently, an organic-growth engagement began: turning that rebuilt site into an actual lead-generation channel rather than a static brochure.
The challengeA construction company's website traditionally exists to look credible, not to generate leads. Making it do the latter requires more than a redesign — it requires the right pages for how people actually search (by service, and by city — Colombo, Kandy, Kurunegala are different searches with different intent), a technical foundation that doesn't fight the CMS or the framework, and a way to know what's actually working versus what to change next, in a market where buyers search in English, Sinhala, and Tamil.
Approach
Rebuilt the technical foundation first: Next.js 14 with server-rendered metadata, a generated sitemap with intent-weighted priorities, and structured SEO tooling — the baseline everything else compounds on, done once rather than fought against on every subsequent change.
Mapped real search intent to dedicated pages instead of one generic "Services" page — separate landing pages per service category and per target city, matching how a construction buyer actually searches rather than how the company internally organizes its offerings.
Localized for the real market: trilingual English/Sinhala/Tamil content and routing, not an English-only site with a translate widget bolted on.
Instrumented before optimizing: Google Search Console and Ubersuggest were connected as the first step of the growth engagement, not an afterthought — so every subsequent change is measured against real query and ranking data, not guessed at.
Run the engagement as a continuous backlog, not a one-time push: Ubersuggest's tracked opportunity queue — quick-wins, competitor gaps, technical SEO issues — becomes the actual monthly work plan. That backlog, not a delivered audit PDF, is what an organic-growth retainer is actually for.
What shipped
Seven intent-driven landing pages live and indexed — by service and by city — weighted appropriately in the sitemap rather than competing with each other for the same generic keywords.
A full technical SEO baseline: structured metadata, sitemap and robots configuration, and a CMS-driven content model that content updates don’t require a redeploy for.
Trilingual routing and content (English/Sinhala/Tamil) matching how Sri Lankan buyers actually search.
A live monitoring stack — Search Console for real query/page/country performance, Ubersuggest for keyword tracking, backlink monitoring, and competitor-gap analysis — reviewed and worked through as part of the ongoing engagement, not a one-time report.
Scale of ownership
6 yrs
Platform relationshipNext.js 14
Rebuilt onto7
Intent-driven landing pages3
Languages supportedOngoing
Organic-growth engagementA redesign alone doesn't produce organic growth — visibility compounds from a system: intent-mapped pages, a clean technical foundation, and continuous measurement against real search data. That's why the growth phase of this engagement started with instrumentation before a single ranking-focused change was made, and why the actual monthly work is a prioritized backlog rather than a one-time audit. The numbers here are still early — expected, a few months into a channel built to compound over years, not weeks — and that's exactly the shape of engagement this service is built around: showing up every month, working the backlog, and measuring what's real.
Have a codebase or product with similar problems?
Tell me what you're working on and where you're stuck. I'll determine whether I can help.
Discuss a Project