Three searches, typed in one week by three different people. 2.5 sqmm 3 core armoured cable is 1554. ss 304 braided hose 1 inch od price. aluminium channel 25x25x3 weight per metre. Not one names a brand. Each is a specification with a search box wrapped around it.
SEO for manufacturers begins there. The manufacturing marketing hub argues why you should own this demand rather than rent it. This page is the mechanics, at the scale a real product range has.
Four shapes an industrial query takes
A part number. Somebody is holding a component or reading a drawing, and types the code off it. These convert better than anything else on your site. They are usually served by a distributor's listing, because you never gave the part its own URL.
A material grade. IS 2062 E250. SS 316L. EN8D. 6063 T6. The grade is the product, and buyers substitute between suppliers on grade alone.
A dimension, sometimes with a tolerance. 50 nb sch 40, 1/2 inch bsp male, bore 25 h7. Metric and imperial in one query, and a tolerance class that decides which of your lines can quote at all.
A standard designation. IS, ASTM, DIN, BS, ISO, and often a superseded IS number that a site engineer still writes from memory. If a product is made to ASTM A106 Gr B, that string belongs on the page in the forms people type: with the space, without it, and as a106 grade b.
Standards are worth their own pages
Most factories bury standard numbers in a table cell inside a PDF. A standard designation carries buying intent, because whoever typed it has been handed a specification and now has to find a supplier who makes to it.
So write to it directly. One page per standard your plant genuinely works to: what it governs, which of your families comply, which grades sit inside it, what test reports you can issue against it, and where it stops. Only a manufacturer can write this, which is what makes it defensible. Do not publish pages for standards you do not work to. Thin content and a credibility problem start at the same moment.
HSN codes, and who is typing them
An HSN code is searched by a buyer's accounts desk, a customs agent or an importer working out duty, not by the engineer who specified the part. Treat it as a supporting detail. Put the code on the product family page beside the technical table so it is findable and quotable, and never build a page whose only reason to exist is a code.
Where the page boundary sits
The hard question in a catalogue of several hundred items is not how to write a page. It is how many pages there should be.
One page per SKU gives you six hundred near-identical URLs differing by one number in a table. Google reads that as a doorway pattern and treats the lot as thin. One page for the whole range gives you nothing to rank. The workable line is a page per product family, with variants held in a proper HTML table on that page: size, grade, weight per metre, working pressure, whatever the trade compares.
Break a variant out into its own URL only when it earns one. It earns one when it has a part number people search, a distinct application, its own drawing, or a standard the rest of the family does not meet. A cable range, a hose range and an extrusion range each break at a different point, which is why this cannot be templated across a roster like Cabcon India, Steelflex and Shreyash Aluminium even though all three sell by size and grade.
Filters generate URLs faster than you can write pages
Faceted navigation is where industrial catalogues quietly destroy themselves. Four filters with eight values each, combinable and sortable, produce more URLs than your site has pages. Most return two products or none.
The controls are unglamorous and they work. Decide which facet combination deserves an indexable URL, usually family plus grade or family plus size, because those match real queries. Serve everything else behind parameters excluded from crawling. Canonical the sorted and paginated views back to the base one. Keep the XML sitemap to pages you would defend in a meeting.
Crawl budget matters here in a way it does not on a fifteen-page brochure site. If a crawler spends its allocation on ?sort=price&page=7, your new grade page waits weeks to be seen.
When your own PDF outranks your own page
This happens constantly. A spec sheet PDF ranks for the grade and the HTML page does not, so the buyer lands in a document with no navigation, no enquiry route and no other product in sight.
Do not delete the PDF. Buyers want it, and the website itself has to serve both. Fix the asymmetry: put the same numbers in HTML on the page, link the PDF from that page rather than a downloads dump, name the file so a human can read it, and set a title inside the document.
Schema for a product nobody buys online
Product markup expects a price and availability. An industrial part has neither, and inventing a price to satisfy a validator is a bad trade.
Use what is true. Product with sku, mpn, brand, material and additionalProperty entries carrying the technical values. Organization with the plant address. BreadcrumbList along the catalogue tree, which also helps a buyer who lands three levels deep and has to work out where he is.
The tree, and the links across it
A catalogue is a hierarchy, so link like one. Category down to family, family down to any variant that earned a page, everything back up. Then add the links a tree does not give you: application pages reaching sideways into every family used in that application, standard pages linking to compliant families, and a grade index a buyer can scan in one screen.
Application pages are the piece most manufacturers skip, and they catch the query with no product noun in it at all. Somebody hunting for the right cable for a solar earthing run does not know your family names yet.
What to fix, and in what order
Structure before content. Filters before pages. If the site is throwing out thousands of filter URLs, twenty new grade pages will not help, because they will not be crawled promptly. So: settle the URL rules, fix the page boundary, publish the technical tables in HTML, then build out standards and applications. Our search work on a catalogue starts with a crawl of what already exists, and the count is usually larger than the client expected. Where the platform cannot hold a catalogue tree at all, that is a build question first, which is why this often runs beside website development rather than after it.
Enquiry handling, once these pages start producing, is a separate discipline. It sits in B2B lead generation.
Digi Kydo, 17R Dover Terrace, Ballygunge, Kolkata, West Bengal 700029. Call +91 98305 45687 or write to [email protected].