A product page has one job: get the right buyer to ask for a quote
An industrial product page works when a purchase engineer can decide from it alone that your product might fit, and then ask you for a price. It fails when it shows a photograph, a paragraph about quality and a link to a 12 MB catalogue, because the engineer has to call or download just to learn the basic numbers.
On many factory websites, the product page is the weakest page on the site, even when the home page looks smart. The reader of that page is not browsing. They have a requirement, often a drawing, and they are comparing three or four suppliers. Everything below is about letting them finish that comparison on your page. This piece sits in the website rebuilds hub, because the product page is where many rebuilds need the most work.
Use the name buyers type, then the name you use internally
The page heading should be the product name a buyer would search for, with the key qualifier: size range, material or type. Your internal code or brand name can follow it, but should not replace it.
Google's own SEO Starter Guide tells site owners to think about the words a user might search for, and notes that people who know a topic well use different words from those who do not. For engineered products that means covering both: the trade name a maintenance engineer uses and the standard description a buyer in a procurement office uses.
Say where the product is used before you describe it
The first paragraph should state the application: the industry, the medium or load, the working conditions. "For isolating water, oil and mild chemicals in process lines up to 150 °C" tells a buyer in one line whether to keep reading. Generic lines about precision and quality tell them nothing, because most competitors write the same thing.
Put the specifications in an HTML table, not only in a PDF or image
Specifications belong on the page as a real table with one row per parameter and units on every number. A table is readable on a phone, can be found by search, and can be copied into a buyer's comparison sheet. A specification printed inside a JPEG or buried on page 14 of a catalogue does none of that. The reasons are covered in more detail in why AI assistants struggle with a PDF catalogue.
Keep the PDF as a download. Just do not make it the only place the numbers live.
A worked example: the 50 mm ball valve page
Take a made-up but typical product, a 50 mm flanged ball valve. The before version on many sites looks like this: a photograph, the heading "Ball Valves", two sentences on "superior quality and durability", and a button labelled "Download Catalogue".
The after version starts with the heading "50 mm (2 inch) flanged ball valve, full bore, stainless steel", a one-line application statement, and then a table like this one. The values are illustrative.
| Parameter | Value |
|---|---|
| Size | 50 mm (2 inch), full bore |
| Pressure rating | Class 150 |
| End connection | Flanged, raised face |
| Body material | CF8M |
| Seat | Reinforced PTFE |
| Temperature range | minus 20 °C to 150 °C |
| Operation | Lever; gear or actuator on request |
| Design and test standards | The standard numbers you build and test to, written out |
| Other sizes | 15 mm to 200 mm (see sizes table) |
| Minimum order | 10 pieces per size |
| Typical lead time | 3 to 4 weeks from approved drawing |
Below the table come the sizes, the drawing, the certificates and the quote route. The same structure works for Fe 500D TMT bars, a cable, a casting or a pump: swap the parameters, keep the order.
Standards and approvals belong in text, with numbers
Write the standard number and the approval in words on the product page, not just as a row of logos in the footer. A buyer checking compliance wants to read "made and tested to [standard number]" next to the product it applies to. Certificate numbers, scope and validity belong on your certificates page, linked from here. The case for doing this in text is set out in why a logo strip of certificates is not enough.
Show sizes and variants in one table
When a product comes in many sizes, a second table with one row per size is clearer than a separate page per size. Columns typically cover size, dimensions, weight and any rating that changes with size. Give dimensions in millimetres, and add inches where your export or oil-and-gas buyers expect them.
Offer a drawing buyers can use
A general arrangement drawing with key dimensions, as a small image on the page plus a downloadable PDF or DWG, saves a round of emails. Without one, an engineer has to email you before checking that the part fits their layout. If you make to customer drawings, say so plainly and say which file formats you accept.
State the commercial facts that decide whether to enquire
Minimum order quantity, typical lead time, packing and dispatch point are the facts a buyer most often phones about. A range is fine: "MOQ 10 pieces per size; 3 to 4 weeks from drawing approval" is enough. Without these, a buyer with a small or urgent order may assume you are the wrong supplier and move on.
End with a quote route on the same page
Every product page should close with a short enquiry form or button that carries the product name into the enquiry, so the buyer does not retype it. Add a phone number and a WhatsApp link beside it for the buyer who prefers to talk. What that form should ask, and how to place it, is the subject of the quote form that gets industrial enquiries.
Markup helps, but only if it repeats what the page shows
Your developer can add Product structured data to each page. Google's product structured data documentation separates product snippets, for pages where people cannot buy directly, from merchant listings for pages with online purchase, so most industrial pages fall in the first group. Google's structured data policies also say the markup must be a true representation of the page and must not describe content readers cannot see. Write the page first, then mark it up.
A checklist to hand to your developer
- Heading uses the searched product name plus size, material or type.
- First paragraph states application and working conditions.
- Specifications in an HTML table with units on every value.
- Standards and approvals named in text, linked to the certificates page.
- Sizes and variants in one table.
- Drawing shown on the page and downloadable.
- MOQ, lead time and dispatch point stated.
- Quote form or button at the end, carrying the product name.
- PDF datasheet kept as a download, matching the page figures.
- Product markup that repeats only what the page shows.
For a fuller list of what buyers look for, see EbizIndia's breakdown of the parts of an industrial product page.
Questions founders ask
Should every size of a product have its own page?
Usually not. One page per product family with a sizes table works better for most manufacturers, because the application, material and standards are shared. Give a size its own page only when buyers search for it by name and its specifications differ enough to need their own explanation.
Is it safe to publish full specifications where competitors can see them?
The specifications buyers need to shortlist you are already in your catalogue, which competitors can get by asking. Publish what a buyer needs to decide whether to enquire. Keep process details, costings and customer drawings private.
Do I need to show prices on an industrial product page?
No. Most engineered products are priced per order, and buyers expect that. What they do want is the minimum order quantity, typical lead time and the information you need from them to quote, so they know an enquiry will get a useful reply.
Can I keep the specifications in a PDF and link to it?
Keep the PDF for buyers who want to save or forward it, but put the main specifications on the page as an HTML table as well. Text on the page is quicker to read on a phone, easier for search engines to index and simpler to keep in step with your catalogue.