Imogen Labs
Start a project

Websites & content systems

A site that says what you sell.

A good site explains the offer, shows the work and gives the next person a useful step. We build sites that read well for people, search engines and AI assistants, and content systems your business can run itself.

Start a project

Problems we solve

Our homepage tries to say everything

We put the answer first and move the deep explanations onto their own pages. A visitor should understand the offer before they meet the detail.

Our site looks fine, but search and AI cannot read it

Every page carries real text, its own title and description, structured metadata and a place in the sitemap. Checks reject missing titles, thin pages and unlinked routes.

We cannot publish without a developer

We build a content system with a visual editor that works from a phone. Authors write and publish, and the site reads the published posts. Technical fields stay out of the way.

Our documentation is always out of date

Where the product owns the facts, the site reads them. Command references and guides come from the product itself, so a change in the product reaches the documentation.

Our pages are heavy and slow

We size images, set explicit dimensions and decide loading priorities. In one company-site pass, image weight fell from 8.7 MB to 1.6 MB.

Our shop works, but customers do not trust it

We build a storefront around your existing checkout, with product detail, reviews and evidence such as lab reports. The front end never touches card details.

What we build

Marketing sites

A clear offer, honest proof and one next step, with a page for each product or service.

Product documentation

Guides and references fed from the product, with search, stable links and text equivalents for diagrams.

Content systems

A publishing tool your team can use without a developer, connected to a fast site.

Storefronts

A new front end for the commerce system you already run, with a safe handoff to checkout.

Forms that reach the back office

A quote or enquiry form that creates a structured record, not an inbox full of half-answers.

Search and sharing basics

Page-specific previews, structured metadata, sitemaps and real error pages.

Who it’s for

Software companies

A website that explains a complicated product before the visitor gives up.

Local and regional service businesses

A site that works on a phone at a jobsite and sends dispatch the details it needs.

Specialist retailers

A trustworthy shop front on the checkout and payment setup already in place.

Teams with fast-changing products

Documentation that follows the product instead of trailing it.

How we work

  1. Understand

    We start with the buyer’s problem and the decision they need to make, then work out what the page has to say.

  2. Design

    We write the pages, plan the routes and design the content system around who will publish and how.

  3. Build

    We build each route with real text, its own metadata and checks on content, navigation and indexing. Nothing is built until its ticket is ready, and releases are recorded automatically.

  4. Run

    We check the whole journey after launch, from first visit to the form or checkout, and keep claims true as the product changes.

Proof

Questions

How long does a website take?

It depends on the number of pages and whether you need a content system or a storefront. We usually launch a clear core first, then add to it.

Can you work with our existing shop or back office?

Yes. We have built around established checkouts and invoicing systems rather than replacing them. The existing system stays the source of truth.

Who owns the site and the content?

You do, outright. Whatever you pay us to build is yours, with full rights: the site, the complete source code and the content, in a system you control.

What happens after launch?

We can stay on to maintain the site, check it and keep the content system running, or hand it over with what your team needs.

Have a similar problem?

Let’s build
what comes next.

Start a project