Client

Atlas Components

Industry

Manufacturing

Engagement

Discovery, UX, web development, SEO, performance

Duration

3 months

Illustrative case study. Atlas Components is not a real client. This describes the kind of engagement Apply Studio is built to deliver, using an invented company name. No client names, metrics or results are claimed anywhere on this page.

A components manufacturer selling through distributors and directly to engineering teams. The website was a company brochure: an organisational chart rendered as navigation, with divisions, subsidiaries and a news feed, and product information buried in downloadable PDFs.

The people it needed to reach were engineers and procurement specialists searching for a component specification, not for a company.

The challenge

The site described the company accurately and was almost useless to its audience. The structural problem was that navigation mirrored internal organisation rather than the questions buyers arrive with.

  • Product data existed only inside PDF datasheets, invisible to search and unusable on mobile.
  • Navigation was organised by business division, which is meaningless to someone searching for a specification.
  • The site had been built with a page builder, so every page was a unique arrangement and nothing was consistent.
  • The marketing team could publish news but could not add a product without a developer.

Objectives

  • Restructure around product categories and applications rather than internal divisions.
  • Bring specifications out of PDFs into structured, indexable content.
  • Give the marketing team a content model they can maintain without development support.
  • Establish technical SEO foundations and a strong performance baseline.
  • Meet the accessibility requirements increasingly present in procurement processes.
01

Strategy

Keyword and intent research was run against the way engineers actually search: by specification, by application, and by the problem being solved – not by product family name or brand. The resulting information architecture is organised on those three axes, with the corporate structure content reduced to the small section it deserves.

A content audit found a substantial body of genuinely useful technical material trapped in PDFs. Converting that to structured web content, with the PDF retained as a download, was the largest single opportunity identified.

02

Content model and design

Products were modelled as structured records with typed specification fields, application tags, related products and downloadable documents – not as free-text pages. That makes specification tables consistent, comparison possible, and structured data accurate, because the markup is generated from the same fields the page displays.

The design system is deliberately plain and information-dense. For this audience, a specification table that is easy to scan on a phone is worth considerably more than a photographic hero. Type, spacing and table design took most of the design effort.

03

Build

The site was built as a custom theme over a structured content model, with a component library the editorial team assembles pages from – rather than a page builder that allows every page to become unique.

Technical SEO was part of the build rather than a later pass: one canonical form per URL, generated sitemap, structured data emitted from the product fields, a deliberate internal linking model from applications to products to related content, and breadcrumbs throughout.

The performance budget was agreed before design sign-off. The pages carry no web fonts, use vector graphics for diagrams, and serve product photography in modern formats at correct responsive sizes.

04

What changed

Specifications became findable. Content that had existed for years inside PDF files became indexable pages that answer the query someone actually typed.

Operationally, the change that mattered most to the client was smaller and less visible: the marketing team can now add a product, and it appears correctly in navigation, in search, in the sitemap and in structured data without anyone writing code.

Diagrams are schematic illustrations drawn for this page, not screenshots of delivered software.

What the engagement delivered

Capability changes, not performance claims. This is an illustrative case study and carries no client metrics.

Search-intent architecture

Navigation organised by specification, application and problem rather than by business division.

Specifications as content

Technical data modelled as structured fields, indexable and readable on mobile, with PDFs retained as downloads.

Editorial independence

New products published by the marketing team, appearing correctly in navigation, sitemap and structured data.

Accessibility as a procurement asset

Built to WCAG 2.2 AA criteria, which the sales team can answer for during tender processes.

Technology

Platform

  • CMS with structured content models
  • Custom theme
  • Component-based editing

Frontend

  • Semantic HTML
  • System font stack
  • Responsive specification tables

Search

  • Generated sitemap
  • Product structured data
  • Internal linking model

Performance

  • Agreed performance budget
  • Modern image formats
  • No render-blocking fonts

Recognise this problem?

Most of the engagements we take on start with someone describing a version of one of these. Tell us yours.

Message us on Telegram (opens in a new tab)