Landing pages for one offer
A landing page has one job: turn a visitor from an ad, a post or a QR code into a request. We build it as one fast page with one form, no menu that leads people away, and a thank-you state you can count in GA4 or in cookie-free statistics. The form posts to a webhook, so the lead reaches your CRM or a Telegram chat within seconds instead of waiting in a mailbox. A lesson from msdf.dk: nearly every request came through one dedicated quote page, not through the forms on thousands of product pages, so that is where the effort goes.
Company websites with more than a brochure
A company site of five to thirty pages: services, cases, team, jobs, legal pages and a contact path that works on a phone. We fix the structure before the design, with one page per service you actually sell, so Google never sees ten pages that say the same thing. Privacy, cookie and terms pages exist in every language the site has. Analytics tags load only after consent, while server logs and form protection keep working regardless. lynbro.dk runs exactly like this: legal pages, careers, a price calculator and a blog in Danish, English and Ukrainian.
Multilingual sites
Danish, English and Ukrainian, or any other set, each on its own URL with hreflang, the translated text present in the HTML from the build, and dates, prices and numbers written the local way. Made for Danish firms with foreign customers and for Ukrainian-speaking businesses in Denmark.
Learn more →Redesign of an existing site
A redesign starts by measuring what the old site does: Lighthouse score, page weight, Core Web Vitals, which pages bring visitors and which URLs must keep their address. For Oksana Kolesnyk Beauty Studio (oksana.dk), a WordPress site with a slider and an online booking plugin, the homepage went from a Lighthouse score of 34 to 68 and from 3.9 to 2.0 MB. Layout shift fell from 0.57 and 0.90 to zero, and a server page cache cut time to first byte from 1.0 to 0.15 seconds. Changed URLs get 301 redirects, so rankings follow the content.
Webshops
Online stores, checkout and payments have their own page under e-commerce: /en/services/ecommerce/. On a company website we add the smaller pieces, such as a price calculator, a paid booking or a Stripe payment link, without turning the site into a shop.
Learn more →WordPress and CMS
WordPress when your team wants to edit pages themselves: a block theme, a short plugin list, and our own plugins from plugins.lynbro.dk where the usual ones are heavy or send visitor data elsewhere. Upgrades of large plugins are tried on a staging copy before they touch the live site.
Learn more →Next.js and headless
Headless makes sense when the same content appears in several places or the site has outgrown a theme. We choose between a static build, a React app on an API and Next.js by how often your content changes, who edits it and how many pages there are.
Learn more →SEO built into the build
We do not sell SEO as a monthly retainer; we build sites that search engines can read from the first day. That means text in the HTML rather than injected by scripts, hreflang between language versions, one canonical address per page, a sitemap that lists every language, JSON-LD for the organisation, breadcrumbs and FAQs, and an llms.txt for AI assistants. On lynbro.dk the Danish URLs once showed English text to crawlers, because translation ran in the browser; a prerender step in the build corrected every page in one pass. On msdf.dk a missing sitemap index was traced to an nginx rule.