Actualiza Tec
A two-language WordPress and Elementor build for a tech services company, with the enquiry path designed into the pages instead of bolted on at the end.
The brief
Two audiences, two languages, one company — and a site that had to feel native in both rather than like a machine translation with a flag in the corner. Every page needed a genuine counterpart, correctly linked so search engines understood the pair.
Underneath that, the commercial job: visitors researching a technical service compare three or four suppliers. The site had to answer their questions in order and make contacting the company the easiest thing on the page.
The problem
Two languages
Language switching that keeps you on the page you were reading, hreflang done properly, and menus, forms and legal pages translated — not just the marketing copy.
Trust before contact
Technical buyers do not fill in a form because a button is orange. They need the service explained, the scope bounded and the company made credible first.
Findability
Two language trees double the ways structure can go wrong: duplicate titles, orphaned pages, sitemaps that disagree with each other. It had to be right at the root.
How I built it
01 · Set the system before the pages
Global colours, global type, container presets and a spacing scale taken straight from the Figma file — so every page after the first one inherited the design rather than re-implementing it.
02 · Build to the design, ask before improvising
Every section checked against the file at desktop, tablet and phone. Where the design didn't specify a breakpoint I proposed one and got it signed off instead of guessing quietly.
03 · Build the enquiry path, not just a contact page
A relevant next step at the end of each service section, forms short enough to actually finish, and GA4 events on each one so the client can see which page is doing the work.
04 · Hand it over properly
Named containers, a short recorded walkthrough of the sections they'd actually edit, and two weeks of cover afterwards for anything that came up.
Two language trees, one design system, and an enquiry path built into the pages — the same Figma to Elementor build process applies whether a site serves one language or two. The extra work is structural, not cosmetic.