Linardics Kft.

The site's base language is Hungarian, but the market is Austria and Germany. The routing table could not simply be "translated": one table has to feed the navigation, the mega menu, the language switcher, the hreflang and the sitemap, across all three languages. How to handle slugs per language was a separate question inside that — with a Hungarian base language it is not the same job as on an English-first site.

Based on: if the switcher and the hreflang build URLs from separate logic, any drift between them throws no error — it just leads to a 404, and you only find out when someone clicks.

Three languages with per-language routes, hreflang and a sitemap generated at build time. The Organization / WebSite / LocalBusiness JSON-LD sits statically in the document head rather than being injected client-side.

Based on: in an SPA the client-side meta layer is not necessarily seen by the first, non-rendering crawl — a static head always is.

Eighteen machines grouped by technology, each card carrying a photo, the manufacturer and the single figure the decision needs — power, tonnage, or the fact that it is a combi machine. The filter shows counts, so one glance tells you whether there is any tube bending capacity at all.

Based on: the old site had the same content as a sixteen-row accordion of names — no photo, no data, no filtering.

The client interviews surfaced a sharp split. Large buyers send procurement emails so every supplier quotes on the same basis — a form will never catch them. Smaller, one-off customers do fill in forms, but rarely with everything needed to price the job. Every one of those leads means a call and a conversation — a lot of man-hours before anyone even knows whether it is worth it.

Based on: this is why the form states a net HUF 50,000 minimum before you start and asks for project data up front — it is not screening the customer, it is protecting the manufacturer's time.

Step one asks only for contact details, step two for project data, step three for the drawing upload. Put on one screen, the sheer number of fields needed for qualification would scare off even the people who would otherwise complete it.

Based on: with a long single-page B2B form, completion is decided on the first screen.

Content and user management for machines, articles, categories and images, in all three languages, and — worth the most of all — a built-in guide for new staff. One of the original complaints was that publishing new content was hard; you cannot fix that with a nicer editor field, only by having the system teach the person using it.

Based on: over a site's lifetime people write into it far more often than anyone plans for.

What greets an editor after login is not a set of charts but a "What do you need to do now?" list: a red bar for a draft waiting to be published, amber for a missing English or German translation and for a missing cover image, grey for an empty category. The button beside each row does not open the section, it jumps to the specific field and highlights it in red. With nothing outstanding you get a green "All good!" and, below it, suggestions that are not urgent — that an article has not been touched in six months, for instance.

Based on: an editor does not want to know how much content is in the system, they want to know what is missing from it. The counts are still there, they are just not the headline.

Under almost every field sits a line saying where the value shows up: "This is what appears in the listing on the public machinery page", "4:3 or wider recommended, min. 1200 px". At the top of the machine list one sentence settles the rule that matters most: only machines marked "Published" appear on the public page. Even the figure shown on the card — 5 kW, combi — is not free text buried in a description but a field of its own: "Highlighted value, shown as a red badge on the card".

Based on: a new editor is not afraid of failing to fill a field in, they are afraid of breaking something on the public site. If the interface says what a field does, the question never gets asked.

The audit log records every administrative action — logins, creation, deletion, reordering, password changes — and for edits it shows, field by field, what the value was before and what it is now. The log is deliberately not deletable. Alongside it come a few built-in constraints: some admin accounts are "protected" and cannot be deleted, with at least one always required to stay active; and the knowledge base allows exactly one featured article — mark another and the system unmarks the old one, but it will let you neither unmark nor delete the last one.

Based on: these cases come up once a year, and when they do they cannot be resolved without a developer. Writing them down as rules is cheaper than recovering from one of them once.

The technical data is already in the system, so advertising used equipment does not mean entering new content: the same data gets a second, sales-side view. A salesperson sends a link rather than copying a specification into an email.

Based on: the same data serving two business processes — so the second page is not new content, it is a new view.

Turnaround would have been too long, and we could not find an agency we fully trusted — in the shadow of AI-generated text, the word "translation" is no longer a guarantee on its own. Instead we worked with AI translation models, and then the client's own salespeople working in each language corrected the mistakes. We exported the translatable content into separate, readable files so they would not have to edit in a developer format.

Based on: technical accuracy does not come from the translator, it comes from the person who sells the product in that language. We shaped the process around that.

The machine specifications came across from the old site, and the previous URLs 301 to their new equivalents. Over ten years a site like this accumulates links and rankings — throwing that away is a loss you get nothing for.

Based on: the domain's ten-year history was one of the project's most valuable assets, not its baggage.

Material guides and technology comparisons — "powder coating vs. wet paint", steel grades — which is exactly what a buyer types into a search box before deciding.

Based on: service pages catch the search for a named technology; the knowledge base catches the search for a problem.

A Vite build with code splitting along React / React Router / GSAP, a preloaded hero image, and only the font weights the site uses. The home page went from 7.8 MB to 3.0, and the LCP from 7.6 seconds to 1.8.

Based on: the hero image is the LCP — every other optimisation only pays off after that one.

The company won EU funding, and displaying that carries precise rules — size, placement, wording. We did not leave it to the client: the Széchenyi block and the page behind it were built to the requirements.

Based on: whoever builds the site has to know the obligations the client does not know to ask about.