Every change is a negotiation because no one wrote down who decides.
Industrial website governance for estates that have outgrown informal arrangements: who owns which content, who approves what before it publishes, what a market team can change without asking, and how the whole estate stays consistent as people and priorities move on.
Governance answers a small set of recurring questions: who owns this content, who can change it, who has to approve it, and what happens when it is wrong. Estates without those answers do not become chaotic immediately; they degrade gradually as the people who held the conventions in their heads move on.
Approval workflows added to content with no clear owner produce queues rather than quality. The prior question is which function owns each type of content: product data with product management, technical specifications with engineering, claims and legal text with compliance, campaign material with marketing. Approval routes follow from ownership.
Applying the same approval path to a trade fair announcement and to a performance claim slows the first without improving the second. Governance that holds in practice distinguishes content by consequence, so low-risk material publishes freely and the material that carries technical, safety or legal weight gets a named reviewer.
Most groups cannot list their own web properties. A register of every domain and site, with its purpose, owner, platform, renewal date and status, is the foundational governance artefact. It is also what surfaces the properties still running that no one has looked at for years.
Guidelines that rely on people remembering them decay. Where a standard can be built into the platform, it should be: components that produce accessible and correct markup, required fields on product records, structured data generated rather than authored, and templates that make the compliant route the easy one.
An estate register, a content ownership model, proportionate approval routes, editorial standards implemented in the platform where possible, a role and permission structure, and a review cycle. See who signs off website content in industrial B2B.
Code Industrial is the industrial B2B practice of Code Barcelona, an agency building corporate websites and digital platforms since 2015. The same strategy, design and engineering team works on every industrial project, from the first scoping session through to life after launch.
What goes wrong depends on how the group is organised. Industrial website governance is designed around it.
What industrial groups ask when an estate has outgrown informal arrangements.
Who owns each type of content, who approves it before publication, what each role can change, which system is the source of record for product and document data, what properties exist across the group, and how all of that is reviewed. It is an operating model rather than a document, and the parts that can be built into the platform generally should be.
It should speed most of it up. The delay in ungoverned estates comes from uncertainty about who decides, so a routine page waits for an answer no one is clearly responsible for giving. Naming owners removes that. Approval is applied where consequence justifies it, and a trade fair announcement should not travel the same route as a performance claim.
Someone with the technical standing to verify them, usually in engineering or product management, and for regulated or safety-related statements a compliance or legal reviewer alongside. The essential thing is that the role is named rather than left to whoever is available, since an unnamed approver in practice means no approval. See technical and legal sign-off workflow.
Give them real autonomy within a defined boundary. Markets typically need to own campaigns, local cases, events and contact routing outright, while product data, brand components and legal content stay central. Autonomy defined this way is usually welcomed; what teams resist is a process where everything requires permission. See marketing team autonomy.
With the register, and it is a common starting point. Domain registrar records, DNS, hosting invoices, analytics properties and certificate inventories between them surface most of what exists. Each property then needs a purpose, an owner and a decision to keep, consolidate or retire, and the ones with no identifiable owner are usually the ones carrying most risk.
Enough that a new person can find who decides what without asking three colleagues, and no more. Long governance documents go unread. A short ownership and approval table, an estate register and a set of platform-enforced standards accomplish more than a comprehensive manual that no one opens after the week it was circulated.
Anything expressible as a rule: required fields on product and document records, components that produce accessible markup, generated structured data, read-only fields where another system owns the value, and workflow routing by content type. Standards that depend on recall degrade as people change; standards the system applies keep working.
Access rights every few months, the estate register at least annually, and technical or dated content on a cycle matched to how quickly it goes out of date. The governance model itself is worth revisiting yearly, since rules that no longer fit how the organisation works are the ones teams begin to route around.
Governance work usually sits alongside these.
An estate that has outgrown informal arrangements, or properties no one can account for. Tell us how your group is organised and we will tell you how we would approach the industrial website governance work.