Corporate websites

A design system built for your brand

If you already have a brand, that is where the design starts. A logo, a palette, brand guidelines, a licensed typeface: we work from what exists and extend it into everything a website needs that a brand book never covers, such as a real type scale, a spacing rhythm, a layout grid, a state for every interactive element and a dark scheme that matches the brand rather than fighting it. If there is no brand system yet, we design one from a blank page.

Either way the result is authored for you and committed as code: no theme, no page builder, no component kit carried over from the last project. That is why two sites we build do not look like each other.

The dark color scheme is designed alongside the light one rather than inverted at the end, so a visitor who keeps their phone in dark mode sees a considered page instead of a washed-out one.

Pages written for the search a buyer actually performs

One page per intent, in the words your market uses. Headings answer questions instead of decorating the layout, and the internal links make the hierarchy obvious to a reader and to a crawler. Thin pages do not rank and do not convert, so every page carries the substance its job demands and then stops.

A contact path that actually delivers

The form is plain HTML that posts to a serverless endpoint on the same domain. It is protected by a Cloudflare Turnstile challenge, a hidden honeypot field and a fill-time check, and it sends from a verified sending domain so the lead reaches an inbox rather than a spam folder.

A visitor whose submission is rejected sees an honest error and an email address, never a thank-you page for a message that was quietly dropped.

Every page in every language you sell in

Each language gets real routes and real copy, with the hreflang cluster, the self-referencing canonical and the right text direction handled per page. This site ships in eight languages as its own proof.

Imagery and typography resolved at build time

Photographs are resized, converted to a modern format and content-hashed during the build, then served from your own domain. Brand fonts are subset to the scripts your locales need and self-hosted, so there is no third-party font request and no layout shift while a face loads.

Hosting, deploys and a test suite that gates them

We host and run the finished site for a monthly fee: the edge platform, the certificates, the sending domain, the deploys and the watching. The site is standard code in a repository with automated checks and a one-command deploy, and the tests are not decoration: accessibility, locale parity, security headers, metadata hygiene and link integrity all run on every change, and a red run blocks the deploy.

An inventory before anything is designed

We list every URL the current site publishes, taken from its sitemap, its internal links, its server or CDN logs, and its Search Console history where you have it. Every URL then gets a decision: kept at the same address, moved, merged into a stronger page, rewritten, or deliberately retired.

The pages that already earn attention are protected first. If a thin, unloved page is quietly the reason half your enquiries arrive, that shows up in the inventory rather than after it has been deleted.

Content moved with its meaning intact

Copy, images, documents and downloads come across page by page. Where the volume justifies it we script the import, and then still read the result: an automated migration that mangles a table, loses a heading level or drops alternative text costs more to repair than it saved. Where the words still work we keep them, because a relaunch is not a licence to rewrite everything for its own sake.

The work is platform independent. Whether the current site runs on WordPress, a hosted site builder, a bespoke content system nobody maintains any more, or hand-written HTML from a decade ago, the content is treated as content and rebuilt into the new structure on its own terms.

A redirect map, written down and testable

Every address that changes gets a permanent redirect to its closest equivalent page. Never a blanket redirect to the home page, which search engines read as a soft deletion of everything you had. Merged pages point at the page that absorbed them, and a retired page points at the nearest parent that is genuinely useful to the person who followed the old link.

The map is a reviewable file in the repository, so you can read it before the switch instead of trusting that it exists. After cutover we request every old URL and confirm both its status code and its destination, and the redirects stay in place permanently rather than for a season.

What carries over, and what we drop on purpose

Carried over: the domain, the content that still works, imagery you own, your brand system, the address your form mail goes to, the analytics or advertising accounts you actually use, and every URL we can keep without bending the new structure around it.

Dropped on purpose: duplicate pages competing with each other for the same search, pages nobody has opened in a year, embeds and tracking scripts whose reports you no longer read, and plugins whose only job was patching the old platform. Every removal is a line on the inventory with a reason beside it, so nothing disappears by accident and you can veto any of it.

The cutover, and the weeks after it

The new site is live on a preview address long before the switch, so nothing is seen for the first time on launch day. At cutover we move the DNS, leave the old host reachable until the change has propagated everywhere, verify the redirect map, confirm form mail is arriving, submit the new sitemap, and ping the instant-indexing endpoints so engines re-crawl within days instead of whenever they next visit.

Then we watch. Search results move for a few weeks after any relaunch while engines re-crawl and re-evaluate the site: some queries settle higher, some dip before they recover. We track the fundamentals with you, meaning indexed pages, redirect health, Core Web Vitals and the queries that actually matter to the business, and we tell you what we see, including when the honest answer is that nothing needs doing.

What we will not do is promise a number. A careful migration protects what you have already earned and gives better content a fair chance to compete. Anyone who guarantees the outcome of a relaunch is guessing with your traffic.