What a Manufacturing Website Needs
A manufacturing website is mostly read by engineers, buyers and distributors who are checking one thing: can this plant make my part, to my spec, in my volume? The site that answers that fastest, with real capabilities, real equipment and an easy way to send a drawing for a quote, wins the request. This guide covers the pages and details that do that work.
The rules and technical points here come from the FTC's guide Complying with the Made in USA Standard, the Made in USA Labeling Rule (16 CFR Part 323) in the official 2025 edition on govinfo, the OWASP File Upload Cheat Sheet, MDN's page on the accept attribute, Google's list of file types Google can index and the UK Government Digital Service post Why GOV.UK content should be published in HTML and not PDF. All were checked on November 15, 2026. The rest is our view from building websites for businesses. This is not legal advice.
The short answer
Give each process you run its own page, list the machines and the limits they work to, and say which industries you serve. Put a request for quote (RFQ) form on every capability page that accepts drawings safely. Publish product specs as normal web pages, with a PDF to download as an extra. Show certifications exactly as your certificate states them, and make origin claims such as "Made in USA" only when they meet the FTC standard. If you sell through distributors or reps, help visitors find the right one.
Capabilities and equipment pages
An engineer looking for a supplier usually starts with a process: CNC machining, sheet metal, injection molding, stamping, welding, finishing, assembly. In our view, one page per process works far better than a single "Capabilities" list, because each page can answer the questions that buyer has:
- What you do in that process, in the words buyers search with.
- Materials you regularly work with.
- Size and tolerance limits you can hold in normal production, stated honestly. A figure you can only reach on a good day loses trust when the first parts come back.
- Volumes: prototypes, short runs, production, or all three.
- Equipment: the machines that do the work, by type and size. An equipment list as text, not only as a photo, lets buyers check fit quickly.
- Secondary operations you do in-house or manage for the customer, so the buyer knows how much of the job you can own.
- Real photos of your floor and your parts, with the customer's permission where a part is theirs.
The same "one page per service" idea runs through our guide to turning a B2B website into a lead source, which also covers proof and follow-up.
Industries served
Buyers in medical, aerospace, automotive, food equipment or electronics want to see that you understand their world. Industry pages help, as long as each one says something specific: the kinds of parts you make for that sector, the requirements you work to, and how you handle documentation. A page that only swaps the industry name into the same paragraph does little for the buyer. If you name customers or show their parts, get their written permission first; many supply agreements limit what a supplier can say.
Certifications and claims
Quality certifications matter to buyers, and they check them. In our view, list each one exactly as it appears on your certificate: the standard and its version, the sites and scope it covers, the certification body and the expiry date. Link to a copy of the certificate if you are happy to share it, and take a certification off the site the day it lapses. Do not show a logo or a standard you do not hold, and do not imply that a certification covers a site or process outside its scope.
Origin claims are regulated in the US. The FTC's guide says that traditionally "the FTC has required that a product advertised as Made in USA be 'all or virtually all' made in the U.S." Under the Labeling Rule, 16 CFR 323.2, a product may be labeled Made in the United States only if "the final assembly or processing of the product occurs in the United States, all significant processing that goes into the product occurs in the United States, and all or virtually all ingredients or components of the product are made and sourced in the United States." The rule covers more than the words "made in": 323.1 lists claims that a product is "made," "manufactured," "built," "produced," "created," or "crafted" in the United States. The FTC adds that marketers "are now subject to civil penalties if they use an unqualified Made in USA label on a product that is not 'all or virtually all' made in the U.S., including in catalogs or online."
If your product does not meet that bar, a qualified claim may fit. The FTC describes it as one that "describes the extent, amount or type of a product's domestic content or processing", with examples such as "60% U.S. content" and "Made in USA of U.S. and imported parts". In our view, check every product page, spec sheet and banner for origin wording, not only the homepage.
The RFQ form and drawing uploads
The RFQ form is where a manufacturing site earns its keep. In our view it should ask for what you need to quote, and little more: contact details, company, the part or project, material, quantity (and annual volume if known), required date, and a place to attach drawings. A short note on what happens next, such as who will reply and roughly when, helps. Many buyers will not send a drawing to a stranger without an NDA, so say whether you sign one and how to request it.
Drawing uploads need care, because you are accepting files from strangers. The OWASP File Upload Cheat Sheet starts with "List allowed extensions", so accept only the formats you actually work with. It also says to "Validate the file type, don't trust the Content-Type header as it can be spoofed", "Set a file size limit" and "Store the files on a different server. If that's not possible, store them outside of the webroot". Its list also includes "Only allow authorized users to upload files", which a public RFQ form cannot fully meet; in our view that is a reason to keep uploaded drawings private, never link to them publicly, and have staff open them only after a malware scan. Setting the HTML accept attribute helps users pick the right file, but MDN notes that users can override the file chooser, so "you should make sure that expected requirement is validated server-side." Large CAD files often hit email and form limits, so decide where uploads go and test the biggest file a customer is likely to send. Our guide to file uploads in web apps covers storage and scanning in more depth, and form design covers labels and errors.
Product pages and spec sheets
If you make standard products as well as custom work, each product family deserves a page with its specs as real text and tables: dimensions, materials, ratings, options and part numbers. Google lists Adobe Portable Document Format (.pdf) among the file types it can index, so a PDF spec sheet is not invisible. But the UK Government Digital Service found that, compared with HTML, "information published in a PDF is harder to find, use and maintain", and that PDFs "do not change size to fit the browser", which matters to a buyer reading on a phone on the shop floor. In our view, put the specs in the page and offer the PDF as a download for people who need to file or print it. Keep one source for each spec so the page and the PDF never disagree.
A distributor or rep finder
Many manufacturers sell through distributors, dealers or sales reps. If you do, a buyer needs to know who to call in their region. In our view a simple list by region or a search by postcode is enough for most companies, as long as each entry shows the company name, what they carry, and a phone number and website. Say clearly whether visitors can also buy from you direct, and send RFQs from regions with a rep to the right person. Review the list when partners change; an out-of-date finder sends buyers to a company that no longer carries your line.
Design, templates and examples
A template can work for a small shop, but most manufacturers outgrow one once they need several capability pages, an RFQ form with secure uploads and product tables. In our view the things to check are speed on a phone, clear navigation by process and by industry, an RFQ button in the header, and room for your own photos instead of stock images of factories that are not yours. When you look at examples, note how quickly each site answers "can they make my part?" and "how do I get a quote?". If you want help, see our website development service.
A short checklist (our view)
- One page per process, with materials, limits, volumes and equipment as text.
- Industry pages that say something specific, with permission for any customer named.
- Certifications exactly as on the certificate, removed when they lapse.
- Origin claims checked against the FTC Made in USA standard on every page.
- An RFQ form on each capability page, with an NDA option and a note on what happens next.
- Uploads limited to your formats and size, checked on the server and stored outside the web root.
- Specs as HTML pages, with the PDF as a download.
- A distributor or rep finder that is kept current.
Related guides: B2B lead generation, consulting firm websites, trucking company websites and file uploads. See all our services.
Frequently asked questions
What pages should a manufacturing website have?
A page per process or capability with equipment and limits, industry pages, a quality and certifications page, product or spec pages if you make standard products, an about page with real photos, a distributor finder if you sell through partners, and an RFQ form that accepts drawings.
Can a manufacturer say "Made in USA" on its website?
Only if the product meets the FTC standard: final assembly or processing and all significant processing in the US, and all or virtually all components made and sourced in the US. Otherwise a qualified claim, such as "Made in USA of U.S. and imported parts", may fit.
Should spec sheets be PDFs or web pages?
Google can index PDFs, but the UK Government Digital Service found PDF information harder to find, use and maintain than HTML, and PDFs do not resize for phones. In our view, put specs on the page and offer the PDF as a download.
Is it safe to accept CAD files through a website form?
It can be, with the checks OWASP lists: allow only the extensions you need, validate the file type rather than trusting the Content-Type header, set a size limit, and store uploads on a different server or outside the web root.