WEBSITE DEVELOPMENT

Websites built to be read.

A business website has a few plain jobs: load quickly, work for everyone, make sense to search engines and AI assistants, and get every enquiry to a person. We build sites that do those jobs.

What a business website actually needs

Most small business websites fail in ordinary ways. They take too long to load on a phone. They describe the business in a hero image with the words baked into the picture, so search engines see nothing. The contact form sends enquiries to an inbox nobody checks, or nowhere at all. None of this is visible from the office, which is why it goes on for years.

A website that earns its keep needs to:

  • say in plain words what you do, who you do it for and where
  • work properly on a phone, because that is where most people will first see it
  • load quickly on an ordinary mobile connection
  • work for people using a keyboard, a screen reader or a phone in bright sunlight
  • be readable by search engines and AI crawlers from its HTML, without running scripts
  • send every enquiry somewhere it will be answered, with a backup if that fails
  • belong to you, in accounts you control

Everything below is how we get each of those right.

How we build

We build in Next.js, a widely used framework for React. Pages are rendered on the server, so the words arrive in the HTML itself. That sounds technical, but it matters: many AI crawlers read the raw HTML and do not run JavaScript, so a site that only fills in its text once scripts run can look almost empty to them. Our free AI visibility check will show you whether that is happening to your current site.

If your team will want to edit pages every week, tell us at the start, because it changes how the site should be set up. A site that is edited twice a year needs something different from one that publishes every Monday.

We keep each site lean. Images are sized for the screen they appear on, fonts are served from your own domain, and we don't load scripts a page doesn't need. Most performance problems come from things added later, so we also show you what to watch for.

Performance

Google measures how real visitors experience a page through a set of signals called Core Web Vitals, covering how quickly the main content appears, how quickly the page responds to a tap, and whether things jump around while it loads. We test every page with Lighthouse on phone settings before launch and fix what it finds.

We won't promise you a score. Scores move with the test conditions, and a perfect number on a page nobody wants to read is worth nothing. What we promise is that we measure, fix what is slow, and show you the results.

Accessibility

Some of the people visiting your site are disabled. Many more are older, tired, on a cracked phone screen or reading in a glary carpark. We build to the WCAG 2.2 AA guidelines: text contrast that holds up, headings in a sensible order, every button reachable by keyboard, form fields with proper labels, and tap targets big enough for a thumb.

Automated tools catch some accessibility problems and miss others, so we test with a keyboard and a screen reader as well. It is also good for search, because the structure that helps a screen reader helps a search engine understand the page too.

Search and AI-search readiness

Being found starts with the basics, and the basics are where most sites fall down. Each page needs a clear title and description, one main topic, headings in order, and links to related pages. We set those up properly and submit a sitemap so search engines know what exists.

Then there is the newer layer: making sure AI assistants such as ChatGPT, Perplexity and Google's AI features can read and describe your business accurately.

  • Crawler access. Your robots.txt decides whether AI crawlers such as GPTBot, ClaudeBot and PerplexityBot may read the site. It is easy to block them by accident, through a firewall setting or a robots file copied from somewhere else. We set a policy you have actually chosen.
  • Structured data. Code that tells search engines in a fixed format who you are, what you offer and where you work. It must be as accurate as the visible page, because it is a public statement about your business too.
  • llms.txt. A short plain-text summary of the site for AI tools. It is a proposed convention, not a standard, and nobody can promise it gets read. It costs almost nothing to add, so we add it.

Nobody can honestly promise you a ranking or a mention in an AI answer. What we can do is make sure nothing technical is standing in the way. Our guide on getting mentioned in ChatGPT and Perplexity explains what you can measure, and our AI search visibility audit checks an existing site in depth.

Content

You know your business better than we ever will, so the substance has to come from you. What we bring is structure: one page per service, plain headings, answers to the questions customers actually ask, and words a person would say out loud. We can draft pages from a conversation with you, and you check every claim before it goes live.

That last step is not a formality. The Fair Trading Act 1986 prohibits misleading representations in trade, and a website is full of them if you are not careful. We won't publish invented testimonials, made-up statistics or a client logo without permission. If you can't back a claim up, it comes out.

Good service pages also answer the questions people ask before they get in touch: what it costs or what drives the cost, how long the work takes when you genuinely know, where you work, and what happens after they enquire. Those answers help a nervous buyer, and they are exactly what search engines and AI assistants look for when they describe a business.

Enquiries that actually arrive

A contact form is the most important thing on most business sites, and the easiest to get wrong without noticing.

We learned that the hard way on a site rebuild described in our case studies. The contact form passed every test and delivered nothing: the email provider reported success on failure and quietly rejected calls from cloud servers. We only found it by checking whether a real email arrived, not whether the request looked successful. We now test delivery, not status codes, and every form we build keeps a server-side record of each submission so an enquiry survives even if email fails.

From there, an enquiry can go straight into your CRM and start a follow-up sequence. That is the subject of our digital marketing automation page.

Hosting and ownership

Your domain is registered in your name. Hosting is in an account you own and pay for directly. Code ownership is agreed in writing before any build starts.

This is not theory. The same case study describes a business whose website was built on a no-code platform, broke, and could not be restored. We rebuilt it on Next.js, so the site no longer depends on the platform that failed.

How a website build runs

  1. Discovery & Audit. What the site is for: who visits, what they need to find, and what you want them to do next. We also list every page on your current site and what each one is worth keeping.
  2. Strategy & Roadmap. Structure: one page per service, plain navigation, and the questions each page must answer. This is agreed before anything is designed.
  3. Build & Integrate. Design and build together: your brand applied in the browser, on a phone first, so what you approve is what will ship. Your words go in edited for clarity, with every claim checked.
  4. Launch & Deploy. Testing for speed, accessibility and structured data, with every form tested by real delivery. At launch, every old address that still gets visits is redirected to its new page, so links from other sites and existing search rankings are not thrown away, and we set up Google Search Console so you can see how the site is found.
  5. Optimise & Scale. Once real traffic arrives, we check the redirects and the forms again.

What is included

Every website build includes:

  • page structure and the build itself, for phones first
  • performance and accessibility testing before launch
  • titles, descriptions, structured data, a sitemap, a robots policy and llms.txt
  • contact forms wired to where you want them, with a server-side backup, tested by real delivery
  • setup in accounts you own, and handover notes

These depend on what you need, and are added to the scope when you do:

  • logo and brand identity design
  • photography and video
  • ongoing SEO work after launch, such as regular content or link building
  • running paid advertising
  • email mailboxes for your domain
  • an online shop

When we are the wrong choice

You want to build and change pages yourself, every day. A hosted builder such as Squarespace or Wix will suit you better and usually costs less to run.

You mainly sell products online, at volume. Shopify and similar platforms are built for that. We can connect one to the rest of your systems rather than rebuild it in custom code.

You need a single holding page. You don't need us for that, and we would rather tell you than quote for it.

QUESTIONS

Frequently asked questions

Will my new website rank on Google?

Nobody can honestly promise a ranking. We make sure nothing technical is holding the site back: fast pages, clean structure, accurate titles and structured data, and a sitemap. What ranks after that depends on your content and your competition.

What does AI-search ready mean?

It means AI assistants such as ChatGPT and Perplexity can reach and read your site. The words are in the HTML rather than added by scripts, your robots.txt lets the crawlers you choose in, and structured data and llms.txt describe the business accurately.

Do we own the website?

The domain is registered in your name and hosting is in an account you pay for directly. Code ownership is agreed in writing before any build starts.

Can you rebuild a site that is stuck on a no-code platform?

Often, yes. We have rebuilt a business site in Next.js after its no-code deployment broke beyond repair. How much can be recovered depends on what content and source still exist, which we check first.

What does a website build include?

Everything needed to launch a fast, accessible, findable site with working enquiries. Depending on what you need, the scope can also cover logo and brand design, photography, ongoing SEO work after launch, paid advertising, email mailboxes and an online shop.

How do you stop website enquiries from getting lost?

Every form we build sends the enquiry where you want it and keeps a server-side record of each submission, so nothing disappears if email fails. Before launch we test that real messages arrive, not just that the form says thank you.

NEXT STEP

Talk it through before you commit to anything.

A scoping call is where we work out what the problem is and what, if anything, is worth building.