Web design, redesigns and site migrations for UK businesses

What's included

• A page plan written for your business before any design happens. Qube needed a location hub, size and price guides and four use-case landing pages, while Leeds & Wakefield Skip Hire needed 39 local pages across the LS and WF postcode districts.
• A design system made for your site alone rather than a purchased theme configured to look slightly unlike everyone else running it. Aziz Consultancy's is a bespoke type and colour system with a fluid type scale, Brookstone's a hand-built CSS system with design tokens and self-hosted variable fonts.
• A front end written by hand, with accessibility work included rather than retrofitted (skip links, labelled sections and reduced-motion handling) plus responsive art direction serving AVIF and WebP with correctly sized fallbacks, so pages do not jump about as they load.
• Content migration from your existing site where there is one: Word4Word Translations had 37 articles and 7 pages pulled across verbatim by a migration pipeline rather than retyped by hand.
• A redirect map covering the addresses search engines already hold. Fleet Transport Consultants' 138 rebuilt pages kept their existing URLs, and Leeds & Wakefield Skip Hire's move off WordPress and WooCommerce shipped with 45 permanent redirects, one for every previously indexed WooCommerce address.
• Structured data written for what you actually are. ProfessionalService, Article, Breadcrumb and FAQ markup on Word4Word, one cross-referenced JSON-LD graph across every page on FTC, and markup on Qube that deliberately omits pricing, opening hours and ratings while the facility is still pre-launch, plus llms.txt and per-crawler rules where they earn their place.
• An enquiry pipeline hardened on the server side: honeypot filtering, validation with length caps, every field escaped, replies threaded back to the sender, and the mail credential held in managed secrets rather than a file sitting on the server. On Qube the registration is written before the emails are attempted, so a dead mail server costs a notification rather than a lead, and registering twice updates the existing contact instead of creating a duplicate.
• A way to change the site without calling us, where you need one. Word4Word got a word-processor-style editor that publishes instantly; Qube's page copy and unit details are served from the database, so they change without a redeploy.

How it runs

1. 1

   Scope and page plan

   We start with a call about what the site has to do, who is arriving, what you want them to do, and what happens to an enquiry once it lands. If there is an existing site we inventory it first: every page, every URL, everything worth keeping. You get a page-by-page scope and a fixed price before any work starts. If a rebuild is not the answer, we say so at that point rather than after you have paid for one.

2. 2

   Design

   Type, colour and spacing are settled first, then the templates carrying the most weight, usually the homepage, a service page, and whichever page the enquiry comes from. You review these as working pages in a browser on real devices, not as flat images, so what you sign off is what actually ships. Revisions happen here, while changing something still costs an afternoon rather than a rebuild.

3. 3

   Build and migration

   The remaining pages are built out, content is moved across from the old site, forms are wired to their server-side pipeline, and structured data goes in. On a replatform the redirect map is written and checked one address at a time against the URLs the old site already had indexed, so nothing that was previously findable lands on a 404.

4. 4

   Launch and afterwards

   We deploy, confirm the redirects resolve, check the forms deliver to a real inbox, and submit the sitemap. Then we show you the parts you control (the admin portal, the database-backed copy, whatever applies to your build) and leave you with them. Changes after launch are normal, and we stay on for them.

Where we've done this