Ferguson Media Group

What we do

Website Development

A website is a commercial instrument. It should be judged on whether it gets found, understood and acted on — not on whether it looks current.

Last reviewed

Website development at Ferguson Media Group means building sites around a commercial opportunity: the market, the audience, the questions people are asking and the business model that pays for it all. Structure and content are decided before visual design, and the finished site is fast, accessible, server-rendered and built to be understood by search engines and AI systems as well as by people.

What comes before design

Most website projects begin at the wrong end. A design is agreed, content is written to fill it, and the question of who is meant to arrive and what they are trying to do gets settled somewhere around launch.

The order that works is the reverse.

  • Market — what is traded here, by whom, and where does the money actually change hands?
  • Audience — who arrives, what do they already know, and what are they trying to decide?
  • Search demand — what are they typing and asking, and what does that reveal about intent?
  • User questions — what do they need answered before they will act?
  • Business model — what happens when the site works? An enquiry, a sale, a click, a subscription?
  • Information architecture — what the pages are, how they relate, and which ones do the work.

Design happens after that, and is considerably easier for it. A structure that reflects how people actually think about a subject mostly designs itself.

What gets built

The right build for a project is the simplest one that does the job and that you can still maintain in five years.

Static websites
Generated HTML, served directly. Fast, cheap to host, almost nothing to attack, and no dependency that stops working when it goes unmaintained.
WordPress
Where genuine editorial workflow is needed and a team will be publishing regularly, WordPress remains a reasonable choice — provided it is kept lean.
Content platforms
Structured publishing systems for sites where the content set is large, patterned and grows continually.
Lead-generation sites
Where an enquiry is the product, and the form, the validation and the delivery of that enquiry matter more than anything else on the page.
Affiliate sites
Research and comparison publishing with commercial links handled transparently.
Directories and databases
Structured records rendered as pages, where the data is the reason to visit.
Calculators and small applications
Focused tools that do one job well and can be linked to, cited and used on a phone.

The standards every build meets

These are not options on a specification. They are what makes the difference between a site that works and one that merely exists.

Speed
Minimal JavaScript, no framework where HTML and CSS will do, images sized properly, and layouts that do not shift while loading.
Discoverability
Clean URLs, correct heading structure, internal linking that reflects real relationships, structured data that describes what is actually on the page.
Structured information
Facts presented as facts — tables, lists, definitions — rather than buried in prose that has to be parsed to be used.
Usability
Navigation that survives a phone, tap targets that can be hit, forms that explain themselves and preserve what has been typed.
Accessibility
Semantic HTML, keyboard navigation, visible focus states, real labels, sufficient contrast, and respect for reduced-motion preferences.
Conversion
A clear next step on every page, specific to that page, without the aggressive funnel mechanics that make people leave.
Security
Validated and sanitised input, escaped output, sensible headers, a content security policy, and no credentials anywhere near the front end.
Scalability
A structure that still makes sense at ten times the page count, because the ones that work usually get there.

Built to be read by machines as well as people

A site built today has to be legible to search crawlers and to AI systems that read pages and summarise them. That does not mean writing for machines — it means removing the obstacles that stop a machine understanding writing intended for people.

In practice: semantic markup, content in the HTML rather than assembled by script, clear entity references instead of vague pronouns, sources named, dates visible, and information that stays consistent across the whole site. All of it helps a reader too, which is why it is worth doing rather than a trick. This is covered properly on the LLM and AI search optimisation page.

Common questions

What do you build sites with?

Whatever suits the project and can be maintained afterwards. Most sites are served as static HTML generated by a build step, with a small server-side layer where forms or data handling require one. WordPress is used where a team genuinely needs editorial workflow.

The consistent principle is to avoid dependencies that are difficult to keep working. A site with a large framework behind it needs continual maintenance simply to stay where it is.

Do you redesign existing websites?

Where there is a commercial reason to, yes — usually when a site is failing to be found, failing to convert, or built on something that has become a liability. A redesign undertaken because a site looks dated is rarely worth what it costs.

Is SEO included, or is it separate?

The structural part is not separable. URLs, headings, internal linking, page speed, structured data and information architecture are decided during the build, and retrofitting them later costs several times more than getting them right first. Ongoing content and search work is a separate matter — see SEO.