Website design and build
Marketing sites built around what the business actually needs to say, with templates your team can extend without a developer for every change.
A good-looking site that search engines cannot read and assistants cannot quote is a brochure with a hosting bill. We build sites that load quickly, convert, and serve the same content to a person, to Googlebot and to GPTBot, because increasingly all three decide whether you get the enquiry.
Thanks — that’s with us.
A senior engineer reads every enquiry and will get back to you shortly.
Book a time that suits you, or send a message and get an answer sooner.
2020
Building since
1,000+
Clients served
UK
Registered company
4.6/5
Rated on Clutch
Quick answer
Three audiences, not one. A human has to understand the offer and act. A search engine has to crawl, render and index it. And now an AI assistant has to be able to fetch the page, read it without executing JavaScript, and quote it accurately. A site that satisfies the first and fails the other two loses enquiries it never knows about.
That third requirement has changed the technical defaults. Client-rendered single-page applications were an acceptable trade when Google's renderer was the only thing that mattered. AI crawlers generally do not run JavaScript, so a client-rendered site can be perfectly indexed and still serve ChatGPT an empty shell. Nothing warns you about this.
The other thing that has not changed is speed and clarity. Most conversion problems on sites we are shown are not design problems; they are a slow first load on a phone, a form asking for nine fields, and an offer that is never stated plainly above the fold.
We are a software company rather than a studio, which shapes what we are good at. If you need brand identity and campaign creative, an agency that specialises in that will serve you better. If you need a site that is fast, maintainable and findable, that is our ground.
What we build
Eight areas. Most projects are a rebuild, a migration or both.
Marketing sites built around what the business actually needs to say, with templates your team can extend without a developer for every change.
Core Web Vitals fixed at the cause: image and font delivery, script weight, layout shift. Measured in field data rather than in a lab score that flatters the result.
Content present in the HTML, so search and AI crawlers receive it without running JavaScript. This is now a visibility requirement rather than a preference.
URL mapping built from the real URL list and traffic data, redirects tested before launch and verified after. Where the largest avoidable losses happen.
WordPress, headless, or custom, chosen for who has to maintain it rather than for what is fashionable. A CMS nobody can use produces a site that never changes.
Shopify and custom stores built with catalogue structure, crawl behaviour and product data considered at build time rather than retrofitted by an SEO afterwards.
Keyboard navigation, contrast, labelling and structure. It is a legal consideration for many UK organisations and it overlaps almost entirely with being machine-readable.
Where the project is software with a front end rather than a website: portals, dashboards, booking systems and internal tools.
Why rebuilds disappoint
The most expensive website mistake in the UK is not an ugly site. It is a beautiful one launched over a migration nobody mapped properly.
About to rebuild? Talk to us before the URLs are decided
The largest avoidable losses happen at migration. Getting the mapping right before launch costs a conversation; fixing it afterwards costs months of traffic.
In practice
Six recurring briefs. These describe the work rather than named clients.
Built years ago by an agency that is gone, running on a version nobody will update, where every change is a quote. Rebuilt so the team can make routine changes themselves.
A site the business can actually change
New name, new domain, new structure. The design is the visible part and the redirect map is the part that decides whether the organic traffic survives the first month.
Equity carried across the rebrand
Sites that pass in a lab and fail in the field. The causes are usually oversized images, blocking scripts and late-loading elements shifting the layout under a thumb.
Field performance that matches the test
A modern framework site that Google indexes and AI crawlers receive almost empty. Fixed by server-rendering the content that matters rather than hoping for a second pass.
The same content for every reader
Usually not a design problem. A nine-field form, an offer stated below the fold, and a phone layout nobody tested on a phone. Cheap to fix and rarely diagnosed.
More of the same traffic converting
Location pages that are one template with the place name swapped, treated as duplicates. Rebuilt so each has a reason to exist, which is as much a content decision as a technical one.
Location pages that can rank
How we work
Migration planning starts at scoping, not the week before launch.
What the site has to do, who maintains it, and what currently works that must not be broken. Including which URLs carry traffic today.
Structure and templates first, decoration second. We design the pages that carry the traffic rather than only the home page.
Server-rendered, fast, accessible and editable, with the CMS chosen for whoever has to live with it after we leave.
Redirects mapped URL by URL, tested before launch, and verified afterwards against real crawler behaviour rather than assumed.
Clear scope · Regular demos · Full handover
Honest fit
We are engineers. That is a strength for some briefs and the wrong choice for others.
Sectors
Businesses where the website is a working part of the operation.
FAQ
What UK businesses ask before commissioning a build.
Still have a question?
Ask us directly — a senior engineer will get back to you.
Ask about your projectIt depends almost entirely on how much of it is bespoke and how much content work is involved. A marketing site on well-chosen templates is a different proposition from a portal with user accounts. We give a written range after scoping rather than a headline figure that we would have to revise.
It can, badly, and it is the most common expensive mistake we are called in to fix. The cause is nearly always a redirect map built by URL pattern, which covers the tidy majority and silently drops irregular URLs, often the valuable legacy ones. Done properly, with mapping from real traffic data and verification after launch, a rebuild should not cost you traffic.
It depends on who maintains it. WordPress is a reasonable default when a non-technical team needs to publish regularly. Custom makes sense when the site is really an application. We choose for whoever has to live with it, not for what we would enjoy building.
Because AI crawlers generally do not execute JavaScript. A client-rendered site can be perfectly indexed by Google and serve ChatGPT or Perplexity an almost empty page. Nothing reports this to you, so it goes unnoticed until someone asks why the assistants have never heard of the company.
No, and we would rather say so. We are a software company. We will work alongside your brand agency and apply existing guidelines carefully, but identity and campaign creative are not what we are good at.
That is a requirement we design for, not an afterthought. A site that needs a developer for routine changes stops being updated within a year, which is usually the real reason an old site looks neglected.
We can, and we are happy to deploy into infrastructure you already run. For UK clients we default to UK cloud regions. Either way you own the accounts rather than renting them through us.
A marketing site is usually several weeks; an application is longer. The honest constraint is normally content rather than development, because the pages that carry the traffic need decisions only your team can make.
It depends on the size of the site and the scope of the work, so we do not publish a fixed price: the honest range is wide. The first conversation and the audit are free, and the quote follows them, in pounds, once we both know what the work actually is.
SpiderHunts Technologies Ltd, registered at Companies House under number 16718403, with an office at 182-184 High Street N, Office 14607, London E6 2JA. You are invoiced in pounds. The engineering team works from Lahore, which we state openly rather than implying a room full of desks in London.
Start here
What it needs to do, who maintains it, and what is wrong with the current one. We will come back with an approach, the risks worth knowing about, and a realistic range in pounds. If a rebuild is not what you need, we will say so.
Thanks — that’s with us.
A senior engineer reads every enquiry and will get back to you shortly.
Book a time that suits you, or send a message and get an answer sooner.