Skip to main content
Vira Noafarin
Back to the Concept LabCorporate website

Industrial corporate site

A site that answers the industrial buyer’s real question: will this work for my application? The company introduction comes second.

This is a Noafarin concept and is not presented as completed client work.

Format
Original Noafarin concept
Business scenario
Industrial
Year
2026
Capabilities
Content strategy، Design، Development، Technical SEO
industrial-/-spec
INDUSTRIAL / SPEC

ENGINEERING CATALOG / REV.04

Process pump

AX-40
0250500750 mm
DRIVE / M1OUTLET / DN80ASSEMBLY VIEW · SCALE 1:8 · AX-40DWG-24-801

Interactive concept

Explore it like a technical buyer

Move between products, inspect specifications and prepare a demo quote request. The right information appears at the moment it is needed.

Industrial product explorerNOAFARIN / LAB
AX-40
TECHNICAL VIEW / NOT TO SCALE

AX-40

AX process pump

Designed for production lines where downtime is expensive. The page supports an engineering buyer with clear facts instead of promotional copy.

This is a usable concept prototype. Its data is illustrative and does not represent a real client or shipped product.

Walk the structure

This is the site’s full information architecture, down to the last level. Click into any section and keep going — the same route a real buyer takes to reach a technical specification.

www.example-industrial.ir/

Home

Home

A corporate site that answers the buyer’s question instead of introducing itself: will this product work for my job?

01

Challenge

Industrial sites are usually full of company history and slogans, and empty of what the buyer came for: specifications, dimensions, standards, and the conditions the part actually operates in.

The result is a sales team that spends its day sending PDF catalogues over messaging apps.

02

Discovery

Real search behaviour shows that buyers rarely begin with a brand name. They usually search for a specification such as a number, standard or size.

03

Strategy

The site is restructured around products and applications rather than the company’s org chart. Each product gets its own page with complete, searchable specifications.

Technical content is published as HTML instead of PDF, so that search engines can read it and phones can use it.

04

Approach

Technical data comes from a single source and is used on the page, in the comparison table, and in the structured data. Entered once, read in three places.

05

Design

Laying out technical tables in Persian is delicate work: the numbers and units are Latin while the text runs right-to-left. Without correct bidi isolation the tables fall apart.

Figures are set in tabular numerals so columns do not shift as values change.

06

Technology

The site is statically generated and served from the edge. For a visitor on a weak mobile connection, that is the difference between reading the page and closing it.

07

Launch

Migration keeps the old URLs and redirects them completely, so existing rankings are not thrown away.

08

Growth

After launch, product pages grow around the phrases people actually search for. Decisions come from evidence, not guesses.

09

Results

Proposed success measure

Because this is not a live client project, we do not invent results. On a real engagement, success measures are agreed before design and validated with live data after launch.

Have a project worth building properly?

Start a project