Service
Web development
Websites for businesses that need to be found and called, and multilingual platforms for manufacturers selling in more than one country.
Most business websites fail at one of two points. Either nobody finds them, because the pages were written in the language of the trade rather than the language of the problem, or people find them and leave, because the thing they came to do — call, ask, check whether you cover their town — is three taps away on a phone.
The work starts from what the visitor is actually trying to do when they arrive. For an emergency service that is a phone number within reach at every scroll position. For a manufacturer it is the right market, in the right language, on a domain the local partner can stand behind. Those are different sites, and building both the same way is how you end up with neither.
What this covers
- Business and service websites, written around how the problem is searched for rather than what the industry calls it
- Multilingual platforms across several domains, with reciprocal hreflang that actually pairs the language versions
- Landing pages and campaign sites where a single action has to work
- Technical search work: structured data, sitemaps, canonical URLs, and a machine-readable site description
- Responsive layouts built for the phone first, because that is where the traffic is
- Contact forms, privacy policies and designed 404 pages — the parts that get skipped
How it goes
The problem, not the specification
The first conversation is about what is going wrong now: who you need to reach, what they type into a search box, and what has to happen once they land. Scope, timing and cost come out of that, not before it.
Structure before design
Which pages exist, what each one is for, and which search each one answers. A site with one page per service ranks for one service each. A site with everything on the home page ranks for nothing.
Build
Static pages wherever the content allows it — no CMS to keep patched, no database to keep online, nothing between a visitor and the page. Where an editor is genuinely needed, it gets built for the person who will use it.
After launch
Hosting is usually cheap or free because of how the site is built. Several of the sites listed below have been maintained over years rather than handed over and forgotten.
Where this has been done
Real projects, with links where a public link exists.
Plumber.hr
Nine service pages, each written for the way that service is searched for, plus a tenth that made the site memorable.
NoDig — European Website Network
Seven domains, eight languages, each domain a closed hreflang cluster — the part most multilingual builds get wrong.
Odštopavanje Osijek — Hidros
An emergency service where the whole design question was how few taps it takes to place the call.
Questions about web work
How much does a website cost?
It depends on how many pages have to earn their own search, and whether anything has to be editable afterwards. A single-service local site and a seven-domain multilingual network are not the same job. You get a figure after the first conversation, once the scope is real — never before, because a number given before the problem is understood is a guess dressed as a quote.
Do you build on WordPress?
Usually not. Most business sites do not change often enough to justify a CMS, and a CMS is a login, a database, a plugin folder and a patching schedule that somebody has to own. Static pages remove all of that and cost almost nothing to host. Where content genuinely changes weekly, an editor gets built for it.
Will the site be found on Google?
The technical half is included as standard: structured data, sitemap, canonical URLs, reciprocal hreflang, fast static pages and a sensible page structure. The other half is time and links, and neither can be bought honestly. A new site does not rank in its first month no matter who builds it.
Can you build a site in several languages?
Yes, and it is a large part of the work. NoDig runs across seven domains and eight languages. The part that decides whether it works is not translation but structure: each domain a closed hreflang cluster, every language version declaring the others reciprocally.
Can you take over a website somebody else built?
Yes. Modernizing, fixing and extending existing work is a large part of what comes in. What is worth keeping and what is worth replacing is the first thing to establish, and I will tell you plainly when rebuilding is cheaper than repairing.
Have a site that needs to be found?
Send a description of the problem rather than a specification. What is going wrong, what you have now, and what should happen instead.
Start a conversation