Answers
Domain architecture

Should product sites
be separate domains?

Product sites should not be separate domains by default. A section of the corporate domain draws on history the domain already holds, sits inside one governance and patching framework, and links directly to the corporate evidence an industrial buyer checks. A separate domain is a deliberate exception with reasons behind it.

Those reasons do exist in industry: a brand acquired with its own installed base and distributor network, a line sold to a different audience through a different channel, a joint venture where ownership is shared, or a division being prepared for divestment. Each is a commercial argument rather than a search one.

In detail

What justifies a separate domain

The case for keeping it together

A product section on the corporate domain inherits the history that domain has accumulated, sits under one security and governance framework, and reports through one analytics property.

It also links the product detail to the corporate evidence an industrial buyer looks for: manufacturing capability, quality certifications, references and service coverage. Specifying engineers and procurement leads check the company as well as the product.

What a separate domain costs

A new domain begins without the history the corporate domain has built, so its visibility has to be established from the start. It also becomes a second property to patch, monitor, measure, govern and pay for.

Where marketing capacity is already stretched across a catalogue and several markets, splitting it across two estates is usually felt within the first year.

When a separate domain is warranted

An acquired brand that carries its own recognition, installed base and distributor network. A line sold to a different audience through a different channel, where the corporate positioning would be a poor fit. A joint venture or licensed brand where ownership is shared.

A division being prepared for divestment is another, since separating the estate later is more expensive than starting separately.

Brand identity is not the deciding factor

A product line can carry its own visual identity, tone and navigation inside a section of the corporate domain. Presentation and URL structure are independent decisions, and treating them as one is the most common reason a separate domain gets proposed.

Where the requirement is that the product looks distinct, that can be met without a second estate to maintain.

Describe the trade-off, not an outcome

The structural choice determines what the product content shares and what it has to establish for itself. It does not by itself determine how either will perform, which depends on the content, the terminology buyers use and the references pointing at it.

A separate domain with substantial content and an established distributor network can do well; a thin one usually will not, on any structure.

Record the decision, and plan the reversal

Whichever structure is chosen, write down the reason and revisit it when the commercial situation changes. Consolidating later is a full migration with individual URL mapping rather than a simplified version because the sites were related.

See product websites for how the content model is built either way.

Domain architecture questions

Should product sites be separate domains?

Not as a default. A section of the corporate domain draws on established domain history, sits within one governance and patching framework, and connects the product detail to the corporate evidence industrial buyers check. Separate domains suit specific commercial situations: an acquired brand with its own following, a different audience and channel, a joint venture, or a planned divestment.

Does a subdirectory limit the product's brand identity?

No. Visual identity, tone and navigation can be entirely distinct within a section of the corporate domain, since presentation and URL structure are separate decisions. Treating them as the same question is the most frequent reason a separate domain is proposed, and it usually adds an estate to maintain without addressing the underlying requirement.

What about a brand we acquired?

This is one of the clearer cases for keeping a separate domain, at least initially. An acquired industrial brand often carries its own installed base, distributor relationships, part-number history and inbound links, and folding it into the corporate domain too early discards that. Consolidation can follow once the commercial position is settled.

Can we consolidate separate domains later?

Yes, and it should be planned as a full migration: a complete URL inventory including documents and part numbers, one-to-one mapping to the closest equivalent, single-hop permanent redirects retained indefinitely, and monitored indexation afterwards. A prior relationship between the sites does not simplify any of that. See multi-brand consolidation for how the sequence is planned.

Does the accumulated authority transfer on consolidation?

A substantial part usually carries across where each old URL is mapped individually to its closest equivalent and the redirects stay in place indefinitely. Blanket rules to a category cost more of it. Some movement during the transition is normal while search engines reassess, and the external links pointing at the old domain continue to matter.

How many websites should we be running at all?

Fewer than most industrial groups have, in general, since each property carries patching, governance, measurement and content cost. See how many websites does an industrial company need for how that count is assessed against markets, brands and audiences rather than against the number of teams requesting one.

Domain architecture

Decide your product
site domain structure

Tell us about the product and the brand position and we will set out what fits.

contact us
Contact Form

Tell us
about your project

Tell us about your organization's context and the planned scope of the project.
Code Industrial, as the data controller, will process your data in order to respond to the query and/or request you submit through this contact form. Privacy Policy.
Our site uses cookies to collect information about your device and browsing activity. We use this data to improve the site, ensure security and deliver personalized content. You can manage your cookie preferences by clicking here.
Basic cookie information
This website uses cookies and/or similar technologies that store and retrieve information when you browse. In general, these technologies can serve very different purposes, such as, for example, recognizing you as a user, obtaining information about your browsing habits or personalizing the way in which the content is displayed. The specific uses we make of these technologies are described below. By default, all cookies are disabled, except for technical ones, which are necessary for the website to function. If you wish to obtain more information or exercise your data protection rights, you can consult our Cookie Policy".
Technical cookies needed Always active
Technical cookies are strictly necessary for our website to work and for you to navigate through it. These types of cookies are those that, for example, allow us to identify you, give you access to certain restricted parts of the page if necessary, or remember different options or services already selected by you, such as your privacy preferences. Therefore, they are activated by default, your authorization is not necessary.Through the configuration of your browser, you can block or alert the presence of this type of cookies, although such blocking will affect the proper functioning of the different functionalities of our website.
Analytics cookies
Analytics cookies are used to analyse website behaviour anonymously. They help us measure activity and improve the website.
Title
Popupcontent
Contact us
Code Industrial, as the data controller, will process your data in order to respond to the query and/or request you submit through this contact form. Privacy Policy.
Aceptar