Manufacturing website redesign
When should a manufacturer redesign its website?
A manufacturer should redesign when the site's structure no longer matches what the shop sells, not when the site looks dated. Appearance costs nothing measurable. A page structure built around a capability set the shop has outgrown costs it the enquiries it now wants, every week, invisibly.
Redesign, rebuild, or leave it alone
Three different jobs get called a redesign, and picking the wrong one is how budget goes to the part that was already working.
| Response | Correct when | Wrong when |
|---|---|---|
| Leave the structure, fix the content | Pages rank and the structure matches what you sell; the capability detail is thin | The site has no pages for half of what you now do |
| Redesign the surface | Structure is sound, the visual language is dated, and conversion is the gap | Traffic is arriving at pages that describe work you no longer want |
| Rebuild the structure | The page set reflects a capability set you have outgrown | The current site earns well and only looks old |
What a redesign puts at risk
A manufacturing site that has been live for a decade has usually accumulated the only links the domain has ever earned, often on pages nobody internally thinks about: a technical article, a materials chart, a page for a process that a supplier once linked to.
Those pages are the first casualties of a rebuild, because they do not appear in any stakeholder's list of important pages. Dropping them converts a redesign into a ranking loss that takes a year to recover, and the loss shows up two months after launch when the cause is no longer obvious.
The second casualty is gated assets. Spec sheets and CAD files behind a form frequently move without their access rules, and either become public or stop resolving. Both are discovered by customers rather than by the team.
What breaks in a manufacturing website redesign
The failures below are specific to industrial sites and are rarely on a general agency's checklist.
| What breaks | Prevention |
|---|---|
| Old URLs dropped with their links | A full URL inventory mapped one to one before build, redirects tested pre-launch |
| Gated files lose their access rules | Assets migrated with their gating, and each one checked after cutover |
| Capability detail cut for visual cleanliness | Tolerance and material tables treated as required content, not optional detail |
| Part number URLs change shape | Catalog URL pattern preserved, or mapped item by item where it cannot be |
| The RFQ form is simplified into a contact form | Field set agreed with the quoting team before design, not after |
| Tracking rewritten, history lost | Event names carried across so before and after remain comparable |
How rankings survive a rebuild
Preserving rankings is mostly clerical work done early rather than clever work done late. Every existing URL is inventoried from analytics, the crawl and the server logs together, because each source misses something the others catch.
Every URL then gets a destination, including the ones being retired, and the redirects are tested against the live map before launch rather than spot-checked after. Where a page is being merged, the merge target has to actually contain the content that earned the link, or the redirect is a soft 404 with extra steps.
What a redesign will not fix
If the site gets no traffic, a redesign does not create any. If enquiries arrive but are unqualified, the intake is the problem and it can be fixed on the existing site in a fraction of the time.
A rebuild is the right answer when the structure is wrong. It is an expensive answer to a content problem and an even more expensive answer to a form problem.
What to read before deciding
What drives the cost of a manufacturing website redesign
Redesign cost is driven by what has to be carried across from the old site, which is usually larger than anyone expects until the URL inventory is done.
| Driver | Costs less when | Costs more when |
|---|---|---|
| Number of existing URLs | A small site with a handful of pages | A decade of accumulated pages, many still earning links |
| Gated asset library | No gated files | Hundreds of spec sheets and CAD files with access rules to preserve |
| Catalog URL structure | No catalog, or a pattern that can be preserved | Part number URLs that have to be mapped item by item |
| Content reuse | Existing capability content is accurate and current | Everything has to be re-established with the floor before it moves |
| Platform change | Staying on the same platform | Replatforming, with data export, transformation and reconciliation |
| Parallel running | A clean cutover | Sections launched in phases, with two systems live at once |
Frequently asked questions
Our website is ten years old. Do we redesign or rebuild?
Redesign if the structure still matches what you sell and only the surface is dated. Rebuild if the page set reflects a capability set you have outgrown, because a visual refresh in that case preserves the exact thing costing you the enquiries you want.
Will a redesign hurt our rankings?
It can, and the usual cause is dropped URLs rather than design changes. A full URL inventory mapped one to one before build, with redirects tested pre-launch, is what prevents it. The pages carrying your earned links are usually old and unglamorous.
How long does a redesign take compared with a new site?
Often longer. A new site has no migration surface. A redesign adds URL inventory, redirect mapping, asset migration and reconciliation, and those run alongside the build rather than instead of part of it.
Can we redesign in phases?
Yes, and it is often sensible for large catalogs. Phasing means two systems live at once, so it costs more in coordination and needs a clear rule about which system owns which URL during the overlap.
Request a quote
Placeholder: scope and next-step copy. Section 8.1 puts RFQ submission at tier 1.