# Manufacturer Website Architecture Website architecture is the internal link graph rather than the page inventory. It decides which capability pages accumulate authority, which are reachable in few clicks, and which exist without anything pointing at them. # Manufacturer Website Architecture
Website architecture is the internal link graph rather than the page inventory. It decides which capability pages accumulate authority, which are reachable in few clicks, and which exist without anything pointing at them.
Two different decisions get called architecture. Which pages exist and what they are called is one, covered at [URL structure](/technical/url-structure-manufacturing). **How those pages point at each other is the other, and it is what this page is about.** ## The link graph is the architecture A site's navigation is what a visitor sees. **An internal link graph is what a crawler and a ranking system actually traverse**, and the two diverge more on industrial sites than almost anywhere, because capability pages are usually reachable only through a menu. **A manufacturer website requires capability pages organized by process, material, and industry.** Those pages are where quote requests originate, and in most builds they are also the pages with the fewest inbound internal links. That produces a specific and common failure: a shop's most commercially important page sits four clicks from the homepage with two links pointing at it, both from navigation, while the blog index has forty. ## Where authority concentrates, and where it should **Authority concentration follows inbound internal links**, so a page linked from thirty others accumulates more than one linked from two. Navigation links count and body links count for more, because a link inside prose carries context a menu item does not. The practical consequence for a manufacturer is a reordering. **A hub page for a process should link down to every specification page under it and be linked back from each**, which concentrates authority at the hub and distributes it to the children rather than stranding both. **An orphan page is one nothing links to**, and on industrial sites they are usually the pages added last: a new capability, a new material, a new facility. They exist, they are in the sitemap, and nothing in the site points at them. ## Click depth is the other half **Click depth is the shortest path from the homepage to a page**, and it predicts both crawl frequency and how much internal authority arrives. Three clicks is a reasonable ceiling for anything commercially important. A capability page at depth five is a page the site is treating as marginal whether or not anyone intended that. The fix is rarely a navigation redesign. **Body links from high-authority pages shorten the effective path** without adding menu items, and a paragraph on a busy page linking to a specification page does more than a menu entry buried three levels down. ## What to link from where **Hub to child, child to hub, and sibling to sibling where the relationship is real.** A process page links to the materials it runs; a material page links back to the processes that use it. Those links are useful to a buyer and they are what makes the cluster legible as a set. **Do not manufacture relationships to satisfy a count.** A link that exists because a rule demanded three is a link a reader skips and a signal that means nothing, and the page it points at gains a reference nobody follows. Content-side structure sits at [capability page structure](/content/capability-page-structure), and the argument for treating industrial search as an architecture problem before a content one runs through [manufacturing SEO](/manufacturing-seo). The cluster is at [technical SEO for manufacturers](/technical). ## Common questions **How many internal links should a page have?** As many as the argument supports. A count is the wrong instrument, and pages padded to hit one are visible to a reader. **Does the navigation menu carry authority?** It carries some and it is diluted across every page it appears on. A body link from a relevant page is worth more. **How do I find orphan pages?** Compare the sitemap against the set of link targets in body content. Anything in the first and not the second is an orphan. **Should every capability page link to every other?** No. Link where the relationship is real, and a shop with forty capability pages fully cross-linked has 1,560 links that mean nothing individually. --- Source: https://manufacturingseo.ai/technical/manufacturing-website-architecture/ Last reviewed: 2026-08-13 Author: ManufacturingSEO.ai