Can brand and product sites share one IA?

You can share a design system; trees usually diverge—brand sites lean capability and trust; product sites lean features, pricing, docs. One forced nav loses both audiences.

Should the newsroom stay in primary nav?

If news is not a primary conversion or compliance disclosure need, park it in the footer or under About. Spend primary nav on services, cases, and contact.

How fast can IA freeze in a redesign?

With preparation, one or two workshops plus a week of async revision often freezes v1; changing the tree after visuals is the expensive path.

Experience Design

Navigation is not menu aesthetics—it is the sales pipeline projected onto URLs

KSX Studio · 可上线Updated 2026-07-2110 min read

Shanghai B2B brand sites often grow into equity-site templates—group intro, newsroom, contact—with a hero reel, fifteen top-level items, and cases buried in layer-six PDFs. Buyers and partners do not navigate org charts; they scan risk (can you do this), fit (anyone like us), and path (who do we talk to). Information architecture for Shanghai B2B brand sites is the discipline of wiring service bounds, proof, team credibility, and inquiry into a crawlable, tellable, convertible tree with minimal depth. At KSX Studio we pressure menus in discovery workshops before visuals; validate three-click rules in design wireframes; ship stable URLs and CN/EN routing in build; then audit IA honesty with search queries and form sources after launch. Below: audience matrix, tree principles, page types, bilingual forks, local trust signals, and redesign migration—so you do not reskin a broken tree.

Audience matrix: procurement, business owners, technical evaluators, talent, press

List 3–5 visitor types and success tasks: procurement wants contract and capability bounds; business owners want industry cases and timelines; technical evaluators want stack and collaboration mode; talent wants project realism; press wants a clear positioning line. Mark one primary success URL per type. If newsroom and IR dominate the top nav while services and cases sit in the footer, IA serves internal politics, not pipeline. In Shanghai, referral traffic is high—they arrive half-trusted; IA should deliver proof fast, not another origin myth.

Tree depth and labels: seven or fewer, verb-aware, no internal jargon

Primary nav candidates: Home, Capabilities/Services, Work/Cases, Method or Insights, About, Contact—merge Method into About or Insights when needed. Labels in visitor language: “Web & product,” “Growth & SEO,” “AI in production” beat internal codenames. Avoid “Solutions” with twenty empty industry shells. Reach body copy in two clicks max; use in-page TOC for a third level instead of mega-menus. Homepage card entry labels must synonym-match the nav so you do not ship two IAs. Test labels with two people outside the company—if they hesitate, the word is internal. Prefer concrete capability names over poetic brand pillars that only the founder understands. When stakeholders demand every department in the nav, push overflow into the footer or a single Company group rather than flattening politics into eight equal tabs. Print the nav on one slide for executive sign-off so later design critiques cannot quietly reintroduce a twelfth item.

Core page types: services, cases, insights, about, contact—clear jobs

Service pages: bounds, process (discover→design→build→launch), deliverables, fit/non-fit, links to cases and inquiry. Case pages: evidence—not stand-ins for the whole SEO homepage. Insights: method and long-tail intent, linking back to services. About: team provenance (honest internet-company backgrounds when true), Shanghai location, ways of working—no fake awards pile. Contact: form + reachable email + response expectation; maps help local visits, secondary for remote buyers. Brand story can live under About; do not steal hero budget from services and cases. Write a one-sentence job for every template type and paste it into the design file cover; drift happens when case pages start selling every service. Keep legal and privacy linked but visually secondary so compliance does not look like a product. If thought leadership is a real pipeline channel, give Insights a top-level slot; if it is rare, nest it rather than promising a magazine you will not staff. Contact pages should state response time expectations in plain language next to the form.

Topic clusters: service hub → sub-service → case → insight

One hub URL per billable capability; split children only when difference is real (Web vs SEO yes; twelve empty industry pages no). Hang cases and insights on their hubs; hubs list flagship proof. Search and humans then see how you make money. Manufacturing digital, real-estate platforms, gaming, and Web3 proof should be labeled by industry—not explode the nav. Skip programmatic city/industry pages without unique substance—thin pages tax the whole domain. Cluster maps belong in the SEO brief and the sitemap generator as the same list. When a case spans two services, pick a primary hub for IA and mention the secondary in body links rather than duplicating the case under two equal parents. Prune hubs that have no case and no insight after two quarters; empty hubs train users that navigation lies. Resist homepage modules that invent a fourth taxonomy orthogonal to the nav.

CN/EN and multi-market: when to fork nav vs content only

When Chinese root serves Shanghai and domestic buyers, nav can stress local delivery, ICP-aware realities, and local cases; English for international founders can stress collaboration hours, remote process, and globally readable capability names. Keep structures isomorphic for hreflang; if a capability sells only in China, hide it in EN rather than empty-translate. Machine-translated menus are not bilingual IA. Lock URL strategy (Chinese root + `/en`) on the IA map early so engineering does not rewire routes late. Decide x-default and whether English is a full peer or a thinner subset before design freezes wireframes. Translators need the IA map with notes on intentional omissions, not a spreadsheet of every Chinese string. If sales in English only sell two services, the English nav should show two services—honesty beats symmetrical emptiness. Route locale switchers to the equivalent node when it exists, else to the locale home with a notice, never to a 404.

Local trust and conversion paths: where Shanghai signals sit

“Shanghai” as trust and local SEO signal belongs in About, Contact, and situational service copy—not crammed into every H1. Visit expectations, time zones, invoicing/contract norms can live under Contact/ways of working. Primary path: any service or case → contact/scoping; secondary: insight → service → contact. Persistent header CTA is fine if it does not fight the nav for meaning. Thank-you pages should route to related cases or calendar—not a dead end. Put office reality such as district, hybrid, or by appointment where visitors plan meetings, not in every hero. Local SEO phrases should appear in titles and body where true, without turning the whole brand into a city directory. Measure whether contact submits from service pages beat the homepage; if yes, IA and CTAs on services deserve more design time than another homepage animation. Keep WeChat QR as secondary for bilingual buyers who still need email trails.

Redesign migration: 301s and content inventory from old tree to new

Inventory URLs first: anything with traffic, backlinks, or indexation must map—no “all-new paths” cleaver. When merging thin pages, pick one authority and 301 the rest. When labels change but jobs stay, keep slugs when possible. PDF cases should become HTML case pages before SEO claims. Launch list: redirect table, nav click tests, locale switch targets, legal footer pages, 404 with search and contact. We put IA acceptance next to visual QA at Launch. Export Search Console top pages before freeze and require a redirect row for each; missing rows become the post-launch fire drill. Preserve high-equity case slugs even if the visual template changes completely. Communicate URL changes to sales so old proposal links get updated in decks. Validate that 301 chains stop at one hop and land on 200 HTML, not on soft 404 templates that look fine to humans and empty to crawlers.

Workshop outputs and how KSX co-defines IA

A useful IA workshop ships: audience matrix, final primary nav, page-type job table, cluster map, CN/EN fork notes, primary conversion path, open questions—then wireframes and design systems. Engineering receives a URL-bearing tree, not a “feels right” menu screenshot. If you are mid-redesign, send current menu, top 20 Search Console queries, and sales’ win paths to hi@keshangxian.com (Shanghai); we prune from tasks, not cosmetics. Schedule a ninety-minute IA workshop with sales, marketing, and eng in the same room—async decks alone rarely kill pet menu items. Exit criteria include a signed nav, URL list, and conversion path diagram attached to the project brief. If scope later adds a product login, park it as a utility link rather than rewriting the brand tree mid-sprint. KSX can facilitate the workshop and hand engineers a machine-readable tree for Next route groups.

Checklist

13–5 visitor types have written primary tasks and success URLs
2Primary nav ≤7 items; service/case body within two clicks
3Each primary service has a hub with cases/insights attached—no empty industry shells
4CN/EN structure and URL strategy decided so hreflang can ship
5Redesign has old-URL map/301 table and launch nav acceptance

Key takeaways

B2B brand-site IA is the sales pipeline as URLs—not the corporate org chart on the web.
Service hubs + case proof + insight method form crawlable clusters; thin industry pages and mega-menus hurt SEO and buyer patience together.
Workshop the tree and conversion paths before visuals and build; redesigns need 301 inventories or you reskin into de-indexation.

FAQ

Can brand and product sites share one IA?: You can share a design system; trees usually diverge—brand sites lean capability and trust; product sites lean features, pricing, docs. One forced nav loses both audiences.
Should the newsroom stay in primary nav?: If news is not a primary conversion or compliance disclosure need, park it in the footer or under About. Spend primary nav on services, cases, and contact.
How fast can IA freeze in a redesign?: With preparation, one or two workshops plus a week of async revision often freezes v1; changing the tree after visuals is the expensive path.