暫定日本語訳：コマース サイト Architecture

暫定日本語案: TL;DR — コマース サイト architecture is how your store’s ページ — categories, 暫定日本語案: subcategories, and 商品 — are organized and linked together. The goal is a 暫定日本語案: shape like a pyramid: your homepage at the top, broad categories under it, then 暫定日本語案: narrower subcategories, then 商品. The point is that a shopper and Google 暫定日本語案: can get from your homepage to any 商品 in just a few clicks by following 暫定日本語案: リンク. The single most useful thing to know: Google figures out which ページ 暫定日本語案: matter by looking at how you リンク between them, not by reading your URLs.

暫定日本語案: What “サイト architecture” actually means

暫定日本語案: When people say site architecture (or site structure, or information 暫定日本語案: architecture), they mean two related things:

1. 暫定日本語案: The hierarchy — how your ページ nest. A store usually goes homepage → 暫定日本語案: category (e.g. “Shoes”) → subcategory (“Running Shoes”) → 商品 (“Brand X 暫定日本語案: Trail Runner”).
2. 暫定日本語案: The リンク — which ページ リンク to which. Your navigation menu, your category 暫定日本語案: ページ, your breadcrumbs, your “related 商品” — all of those are リンク that 暫定日本語案: tie the hierarchy together.

暫定日本語案: Good architecture means a shopper can find what they want fast, and a 検索 暫定日本語案: engine can クロール from your homepage to every 商品 without getting lost or stuck.

暫定日本語案: The pyramid shape

暫定日本語案: Picture a pyramid:

• 暫定日本語案: Top: your homepage.
• 暫定日本語案: Next: a handful of broad categories (linked from your main menu).
• 暫定日本語案: Below that: subcategories.
• 暫定日本語案: Bottom: individual 商品 ページ.

暫定日本語案: This shape works because it tells Google how your ページ relate. “Running Shoes” is 暫定日本語案: clearly part of “Shoes.” “Brand X Trail Runner” is clearly a Running Shoe. Those 暫定日本語案: relationships help Google understand your store.

暫定日本語案: A lot of guides tell you to make everything “flat” — every 商品 reachable in 暫定日本語案: the fewest possible clicks. That sounds good, but it’s a myth that flatter is 暫定日本語案: always better. Google’s own John Mueller said outright that a “super flat 暫定日本語案: structure” is not better than a “reasonable pyramid structure.” If 暫定日本語案: everything is one click from the homepage, you’ve told Google that every ページ is 暫定日本語案: equally important — which isn’t true, and isn’t helpful.

暫定日本語案: The flip side is also a trap: don’t bury 商品 so deep that it takes ten clicks 暫定日本語案: to reach them. The sweet spot is a pyramid that’s shallow enough that important 暫定日本語案: 商品 are only a few clicks from the homepage.

暫定日本語案: リンク are what matter (not your URLs)

暫定日本語案: This surprises people. Your URL can read /shoes/running/brand-x-trail-runner or 暫定日本語案: just /products/brand-x-trail-runner — and Google mostly doesn’t care which. 暫定日本語案: What Google looks at is your リンク. As their コマース documentation puts it, 暫定日本語案: Google “doesn’t look at the structure of URLs to work out the structure of a 暫定日本語案: サイト. Instead, it analyzes the linkages between ページ.”

暫定日本語案: So if you want a 商品 to do well, the best thing you can do is リンク to it 暫定日本語案: more — from your homepage, from category ページ, from blog posts. The more (good) 暫定日本語案: リンク a ページ has pointing at it, the more important Google assumes it is.

暫定日本語案: The four things to get right

1. 暫定日本語案: Use real リンク. Your menu and navigation need to be actual 暫定日本語案: <a href="..."> リンク. If your menu only works through JavaScript clicks with 暫定日本語案: no real リンク underneath, Google may not be able to follow it.
2. 暫定日本語案: Use breadcrumbs. “Home > Shoes > Running Shoes > Brand X” at the top of a 暫定日本語案: 商品 ページ helps shoppers and gives Google a clear hierarchy signal — and it 暫定日本語案: can show up in your Google listing.
3. 暫定日本語案: Control your filters. Those “filter by color / size / price” controls on 暫定日本語案: category ページ can create thousands of junk URLs. Left unmanaged, they waste 暫定日本語案: the time Google spends クロール you. (This has its own deep dive — see 暫定日本語案: faceted navigation.)
4. 暫定日本語案: Make your mobile サイト match. Google crawls the mobile version of your 暫定日本語案: サイト. If your mobile menu hides categories or strips out コンテンツ, that’s the 暫定日本語案: version Google sees.

暫定日本語案: The thing most people get wrong

暫定日本語案: Don’t restructure your URLs just for SEO. Changing 暫定日本語案: /shoes/running/brand-x to /products/brand-x won’t lift your rankings — URL 暫定日本語案: structure barely matters as a ranking factor. But the change itself breaks リンク 暫定日本語案: and creates redirects that can hurt you temporarily. Pick a sensible URL format 暫定日本語案: early and leave it alone.

暫定日本語案: Want the deep version — flat vs. pyramid with the actual Mueller quotes, the 暫定日本語案: duplicate-コンテンツ trap with multi-category 商品, mega-menu リンク equity, and 暫定日本語案: the faceted-navigation クロール-budget fix? Switch to the Advanced tab.

暫定日本語案: TL;DR — Google reads your リンク graph, not your URL paths, to infer 暫定日本語案: hierarchy and relative importance — “Google generally doesn’t look at the 暫定日本語案: structure of URLs… it analyzes the linkages between ページ.” So a reasonable 暫定日本語案: pyramid (homepage → category → subcategory → 商品) with strong internal 暫定日本語案: linking beats both a flat structure (Mueller: a super-flat structure is not 暫定日本語案: better than a reasonable pyramid) and a too-deep one (you don’t want to “click 暫定日本語案: through a million times”). URL structure is barely a ranking factor; URL 暫定日本語案: stability is the real risk. The commerce-specific failure points are 暫定日本語案: multi-category 商品 (canonical them), mega menus (リンク-equity dilution + 暫定日本語案: crawlability), faceted navigation (クロール-budget killer — robots.txt > canonical), 暫定日本語案: and mobile-first nav (your mobile nav is your SEO nav).

暫定日本語案: Architecture serves two masters

暫定日本語案: コマース サイト architecture is the hierarchical organization of a store’s ページ — 暫定日本語案: categories, subcategories, 商品, and supporting コンテンツ — plus the navigation, 暫定日本語案: internal リンク, and URL patterns that connect them. It has to satisfy two 暫定日本語案: audiences at once: shoppers who want 商品 in as few clicks as possible, and 暫定日本語案: 検索 engines that need to discover every ページ, understand how ページ relate, and 暫定日本語案: assign relative importance.

暫定日本語案: The whole topic comes down to one principle that most architecture guides bury or 暫定日本語案: miss: Google reads リンク, not URLs.

暫定日本語案: Google reads リンク, not URLs

暫定日本語案: This is the load-bearing fact. From Google’s コマース documentation:

暫定日本語案: “Google generally doesn’t look at the structure of URLs to work out the 暫定日本語案: structure of a サイト. Instead, it analyzes the linkages between ページ to gain 暫定日本語案: insights about the relative importance of different ページ on a サイト.”

暫定日本語案: And the mechanism for “relative importance”:

暫定日本語案: “the more リンク a ページ has to it within a サイト, the higher the relative 暫定日本語案: importance of the ページ to other ページ.”

暫定日本語案: So your internal リンク graph does the heavy lifting. Whether the URL reads 暫定日本語案: /shoes/running/brand-x or /products/brand-x is secondary. The 商品 that’s 暫定日本語案: linked from your homepage, your top category, and three blog posts will get more 暫定日本語案: クロール attention and more PageRank than a 商品 two clicks deep with nothing 暫定日本語案: pointing at it — even though the second one has the “shallower” URL.

暫定日本語案: The practical chain Google recommends:

暫定日本語案: “add リンク from menus to category ページ, from category ページ to sub-category 暫定日本語案: ページ, and finally from sub-category ページ to all 商品 ページ.”

暫定日本語案: And the warning for large catalogs:

暫定日本語案: “If category ページ don’t include direct リンク to all 商品 in a category, 暫定日本語案: Googlebot might not find all of your 商品 by クロール alone.”

暫定日本語案: When direct linking to every 商品 isn’t feasible at scale, fall back to XML 暫定日本語案: sitemaps and (for 商品) a Merchant Center feed as secondary discovery paths — 暫定日本語案: but those are a backstop, not a substitute for a crawlable リンク graph.

暫定日本語案: Flat vs. pyramid — the myth, busted

暫定日本語案: Nearly every competitor guide repeats some version of “flat is better” or “keep 暫定日本語案: everything within three clicks.” That advice is half-right and badly framed. The 暫定日本語案: nuance comes straight from John Mueller (Google, Feb 2, 2021 office-hours):

暫定日本語案: “On the other hand, kind of more the top down approach or pyramid structure 暫定日本語案: helps us a lot more to understand the context of individual ページ within the 暫定日本語案: サイト.”

暫定日本語案: “So in particular, if we know this category is associated with these other 暫定日本語案: subcategories then that’s a clear connection that we have between those parts.”

暫定日本語案: “So from my point of view, I think for a lot of sites it makes sense to have 暫定日本語案: more of a pyramid structure.”

暫定日本語案: And the line that kills the myth outright:

暫定日本語案: “But it’s not the case that a super flat structure is going to be better than a 暫定日本語案: kind of reasonable pyramid structure.”

暫定日本語案: Why a totally flat structure hurts: if every ページ is one or two リンク from the 暫定日本語案: homepage, you’ve flattened the importance signal too. You’re effectively telling 暫定日本語案: Google “everything here is equally important,” which strips away the context it 暫定日本語案: uses to understand which categories own which subcategories own which 商品.

暫定日本語案: But don’t overcorrect into a deep tree, because Mueller capped that too:

暫定日本語案: “But at the same time you don’t want it to be such that it’s like you have to 暫定日本語案: click through a million times to actually get to the actual コンテンツ.”

暫定日本語案: So neither extreme wins. The target is a pyramid that’s shallow enough: broad 暫定日本語案: categories at the top, narrowing to 商品, with click depth kept low for 暫定日本語案: anything that matters. As a practical rule of thumb, aim for most 商品 within 暫定日本語案: ~3–4 clicks of the homepage on a large store, 2–3 on a small one — but treat that 暫定日本語案: as a guideline, not a Google directive (see the click-depth note below).

暫定日本語案: The “3-click rule” is consensus, not a Google rule

暫定日本語案: You’ll see “every ページ must be within 3 clicks of the homepage” everywhere. It’s 暫定日本語案: useful as a heuristic, but Google has not stated a specific click number. The real 暫定日本語案: risk on a large catalog isn’t exceeding a click count — it’s orphaning ページ 暫定日本語案: (nothing リンク to them) or burying them so deep that crawlers rarely reach them. A 暫定日本語案: long-tail 商品 four or five clicks deep can rank fine if it sits in a logical 暫定日本語案: hierarchy and appears in your sitemap. Click depth is a crawlability and 暫定日本語案: PageRank-flow concern, not a direct ranking factor.

暫定日本語案: This is also why internal linking beats URL depth. A 商品 five clicks deep 暫定日本語案: in the hierarchy but linked directly from the homepage gets more クロール attention 暫定日本語案: than a 商品 two clicks deep with no inbound internal リンク. If you’ve got an 暫定日本語案: important 商品 sitting deep in the tree, the fix isn’t to re-architect the whole 暫定日本語案: URL scheme — it’s to リンク to it from higher-authority ページ.

暫定日本語案: URL structure: stability matters, depth doesn’t

暫定日本語案: Google’s URL guidance for コマース is mostly about hygiene, not hierarchy:

暫定日本語案: “use long-term, persistent URLs. Avoid internally linking to temporary 暫定日本語案: parameters, such as session-IDs, tracking codes, user-relative values 暫定日本語案: (location=nearby, time=last-week), and the current time.”

暫定日本語案: “Minimize the number of alternative URLs that return the same コンテンツ to avoid 暫定日本語案: Google making more requests to your サイト than needed.”

暫定日本語案: “Use ?key=value URL parameters rather than ?value, where possible. URL 暫定日本語案: parameters allow Google 検索 to understand your サイト’s structure and クロール and 暫定日本語案: index more efficiently.”

暫定日本語案: Notice what’s not there: any mandate about nesting depth. Google’s URL docs do 暫定日本語案: not say /category/subcategory/product is better or worse than /product/slug. 暫定日本語案: Depth is a サイト-structure decision, not a URL prescription.

暫定日本語案: Mueller has rated URL structure low (roughly 1 out of 7) as a direct ranking 暫定日本語案: factor, and said making URLs artificially flat provides no SEO benefit. The 暫定日本語案: takeaway for コマース: URL structure is barely a ranking factor, but URL 暫定日本語案: stability is a real risk factor. Restructuring /category/subcategory/product 暫定日本語案: into /product later causes redirect chains and temporary ranking disruption even 暫定日本語案: if the end state is neutral. Pick a consistent, descriptive format early 暫定日本語案: (/product/black-t-shirt beats /product/3243) and don’t churn it.

暫定日本語案: Multi-category 商品 and the duplicate-コンテンツ trap

暫定日本語案: The one place URL structure does bite you is 商品 that live in multiple 暫定日本語案: categories. If your URL encodes the category path, the same 商品 can be reached 暫定日本語案: at /shoes/running/brand-x and /sale/brand-x and /brand-x-page — three 暫定日本語案: URLs, one 商品, duplicate コンテンツ. Two fixes:

• 暫定日本語案: Flat 商品 URLs (/products/brand-x) — one canonical URL regardless of 暫定日本語案: which category path the shopper took to get there. This is the Ahrefs コマース 暫定日本語案: guide’s recommended default, precisely to sidestep this problem.
• 暫定日本語案: Category-nested URLs with a canonical — pick one primary category, build the 暫定日本語案: 商品 URL under it, and canonicalize 暫定日本語案: every other path to that primary.

暫定日本語案: Either way, you resolve the ambiguity with a single canonical. Then you restore the 暫定日本語案: hierarchy signal — which the flat URL throws away — with breadcrumb スキーマ 暫定日本語案: (below).

暫定日本語案: Internal linking is the actual mechanism

暫定日本語案: PageRank and クロール attention flow through <a href> リンク, so your internal 暫定日本語案: linking strategy is your architecture in practice. A few patterns that matter:

• 暫定日本語案: リンク best-sellers and priority 商品 from the homepage and high-authority 暫定日本語案: ページ. Google explicitly notes you can signal importance by linking popular 暫定日本語案: 商品 from the homepage, blog posts, or newsletters.
• 暫定日本語案: Category ページ are リンク-equity distributors. They take authority from the 暫定日本語案: homepage/nav and pass it down to 商品. A category ページ that doesn’t リンク to 暫定日本語案: all its 商品 leaves some undiscoverable by クロール alone.
• 暫定日本語案: Editorial → 商品 リンク. Blog コンテンツ that リンク to relevant 商品 both 暫定日本語案: passes equity and creates topical context.
• 暫定日本語案: Related 商品 / “customers also bought” add cross-リンク across the tree so 暫定日本語案: crawlers (and shoppers) don’t hit dead ends.
• 暫定日本語案: Breadcrumbs are internal リンク too, not just UX.

暫定日本語案: I’ve made the internal-リンク case for years. As I wrote in 暫定日本語案: The Most Important Thing SEOs Overlook: Internal Links: 暫定日本語案: “By adding internal リンク, you are directing the flow of your ウェブサイト authority to 暫定日本語案: the best コンテンツ, which in turn signals to 検索 engines which ページ you consider 暫定日本語案: the most important.” And the part teams forget: “you may be frequently producing 暫定日本語案: new pieces of コンテンツ in which you add internal リンク, but are you remembering to 暫定日本語案: go back to your older pieces” — on a store, that means linking new arrivals from 暫定日本語案: existing category and editorial ページ, not just publishing them and walking away. 暫定日本語案: The reason this is worth the effort: “リンク on your サイト are a lot easier to get 暫定日本語案: than リンク from other sites, and they can be just as effective.”

暫定日本語案: For the full treatment, see internal リンク.

暫定日本語案: Breadcrumbs: hierarchy signal + internal リンク + rich result

暫定日本語案: Breadcrumbs earn their keep three ways: they’re internal リンク, they give Google an 暫定日本語案: explicit hierarchy signal, and they can render as a breadcrumb trail in the SERP. 暫定日本語案: From Google’s structured-データ docs:

暫定日本語案: “A breadcrumb trail on a ページ indicates the ページ’s position in the サイト 暫定日本語案: hierarchy.”

暫定日本語案: Crucially, breadcrumbs let you communicate hierarchy even when your URLs are 暫定日本語案: flat. A 商品 at /products/black-t-shirt can still carry 暫定日本語案: Home > Clothing > T-Shirts > Black T-Shirt via BreadcrumbList markup. And 暫定日本語案: Google’s recommendation is to model the user path, not the URL:

暫定日本語案: “We recommend providing breadcrumbs that represent a typical user path to a 暫定日本語案: ページ, instead of mirroring the URL structure.”

暫定日本語案: For 商品 that belong in multiple categories, you can supply multiple 暫定日本語案: BreadcrumbList markups for the different navigation paths. A BreadcrumbList 暫定日本語案: needs at least two ListItem entries (each with position, name, and item) to 暫定日本語案: be eligible for the rich result; the final crumb’s item is optional. (For what 暫定日本語案: it’s worth, Mueller has said breadcrumb placement on the ページ doesn’t matter for 暫定日本語案: SEO — so optimize it for users.)

暫定日本語案: Navigation menus and mega menus

暫定日本語案: Two separate issues live here: crawlability and リンク-equity dilution.

暫定日本語案: Crawlability. Google can only follow リンク that are real anchors:

暫定日本語案: “Google can only クロール your リンク if it’s an <a> HTML element with an href 暫定日本語案: attribute.”

暫定日本語案: JavaScript is fine as long as the rendered DOM contains real anchors — “リンク 暫定日本語案: are also crawlable when you use JavaScript to insert them into a ページ dynamically 暫定日本語案: as long as it uses the HTML markup shown above.” What breaks is onclick-only 暫定日本語案: handlers, routerLink-style attributes, or javascript: hrefs:

暫定日本語案: “Google can’t reliably extract URLs from <a> elements that don’t have an 暫定日本語案: href attribute or other tags that perform as リンク because of script events.”

暫定日本語案: So a JavaScript mega menu can be crawlable — the myth that “JS menus can’t be 暫定日本語案: crawled” is false — but only if it renders proper <a href> リンク.

暫定日本語案: リンク-equity dilution. Every リンク in your global nav siphons a slice of the 暫定日本語案: homepage’s authority. A 200-リンク mega menu spreads that authority thinly across 200 暫定日本語案: destinations. Mueller has also flagged that very large, frequently-changing mega 暫定日本語案: menus can be hard for Google to interpret. The pragmatic move: keep the global 暫定日本語案: nav to top-level categories (a manageable count, not the whole taxonomy), and let 暫定日本語案: category ページ handle the deeper subcategory and 商品 navigation. That’s the 暫定日本語案: pyramid expressing itself in the nav.

暫定日本語案: Faceted navigation: the クロール-budget killer

暫定日本語案: This is the single biggest クロール-budget leak on most コマース sites. Filters 暫定日本語案: (price, color, size, sort order) each generate crawlable URLs, and the 暫定日本語案: combinations explode — a modest catalog can hide millions of filtered URLs.

暫定日本語案: Google’s hierarchy of fixes, in their stated order of effectiveness:

暫定日本語案: “Use robots.txt to disallow クロール of faceted navigation URLs”

暫定日本語案: That’s the preferred method. The soft signals — notably rel=canonical — are 暫定日本語案: acknowledged but “generally less effective in the long term than the previously 暫定日本語案: mentioned methods.” (This is the reverse of what a lot of guides recommend, which 暫定日本語案: lead with canonical.) Other levers:

• 暫定日本語案: URL fragments (#) for filter state passively avoid クロール, since “Google 暫定日本語案: 検索 generally doesn’t support URL fragments in クロール and インデックス登録.”
• 暫定日本語案: Return 404 for empty combinations: “If there are no green fish in the サイト’s 暫定日本語案: inventory, users as well as crawlers should receive a ‘not found’ error.”

暫定日本語案: The strategy decision comes before the technical one: identify which filter 暫定日本語案: combinations have genuine 検索 demand (and deserve to be indexable landing ページ) 暫定日本語案: versus pure-UX filters (which should be blocked or built so they never mint a URL). 暫定日本語案: This topic has its own deep dive — see faceted navigation 暫定日本語案: — and it ties directly to クロール budget.

暫定日本語案: Mobile-first: your mobile nav is your SEO nav

暫定日本語案: Google indexes the mobile version of your サイト:

暫定日本語案: “Google uses the mobile version of a サイト’s コンテンツ, crawled with the smartphone 暫定日本語案: agent, for インデックス登録 and ranking.”

暫定日本語案: That has structural consequences. コンテンツ parity is required —

暫定日本語案: “Make sure that your mobile サイト contains the same コンテンツ as your desktop 暫定日本語案: サイト.” — and so is structured-データ parity — “Make sure that your mobile and 暫定日本語案: desktop sites have the same structured データ.” And critically:

暫定日本語案: “Google won’t load コンテンツ that requires user interactions (for example, 暫定日本語案: swiping, clicking, or typing) to load.”

暫定日本語案: So if your mobile nav hides categories behind a hamburger that only renders リンク 暫定日本語案: on tap (via JS click events rather than real <a href> リンク in the DOM), those 暫定日本語案: category and 商品 リンク may receive no クロール signal through navigation. Whatever 暫定日本語案: hierarchy you built on desktop has to survive on mobile, as real anchors, with the 暫定日本語案: same コンテンツ and スキーマ.

暫定日本語案: Sitelinks: influenced, not controlled

暫定日本語案: Those clusters of リンク that sometimes appear under your homepage result are 暫定日本語案: sitelinks, and good architecture makes them more likely — but you can’t pick 暫定日本語案: them. Google: “Our systems analyze the リンク structure of your サイト to find 暫定日本語案: shortcuts.” And: “If the structure of your サイト doesn’t allow our algorithms to 暫定日本語案: find good sitelinks… we won’t show them.” You influence quality through a logical 暫定日本語案: structure, descriptive ページ titles and headings, and concise, relevant anchor text; 暫定日本語案: you can’t specify which ページ appear. If a bad one shows up, the lever is to 暫定日本語案: noindex or remove that ページ.

暫定日本語案: Where this fits

暫定日本語案: This is one piece of the サイト-structure cluster 暫定日本語案: under コマース SEO. It connects directly to 暫定日本語案: faceted navigation (the クロール 暫定日本語案: side), category ページ SEO and 暫定日本語案: 商品 ページ SEO (the ページ 暫定日本語案: types), and internal リンク (the mechanism). For how 暫定日本語案: crawlers traverse all this, see クロール.

暫定日本語案: AI summary

暫定日本語案: A condensed take on the Advanced version:

• 暫定日本語案: Google reads リンク, not URLs. “Google generally doesn’t look at the 暫定日本語案: structure of URLs… it analyzes the linkages between ページ.” Your internal リンク 暫定日本語案: graph determines hierarchy and relative importance — “the more リンク a ページ has 暫定日本語案: to it within a サイト, the higher the relative importance.”
• 暫定日本語案: Pyramid beats flat — and beats too-deep. Mueller: a “super flat structure” 暫定日本語案: is not better than a “reasonable pyramid”; but don’t make users “click 暫定日本語案: through a million times.” Aim for a shallow pyramid.
• 暫定日本語案: The “3-click rule” is industry consensus, not a Google rule. The real risk is 暫定日本語案: orphaning ページ, not exceeding a click count. A deep-but-linked 商品 beats a 暫定日本語案: shallow-but-orphaned one.
• 暫定日本語案: URL structure is barely a ranking factor; URL stability is the risk. Pick a 暫定日本語案: consistent, descriptive format early; don’t restructure (it breaks リンク/causes 暫定日本語案: redirect chains).
• 暫定日本語案: Multi-category 商品 create duplicate URLs — fix with a single canonical 暫定日本語案: (flat 商品 URL or a primary category), then restore hierarchy with 暫定日本語案: BreadcrumbList スキーマ (model the user path, not the URL).
• 暫定日本語案: Mega menus: crawlable only if they render real <a href> リンク; huge menus 暫定日本語案: dilute リンク equity — keep global nav to top-level categories.
• 暫定日本語案: Faceted navigation is the top クロール-budget leak. Google prefers 暫定日本語案: robots.txt disallow; rel=canonical is “less effective in the long term.” 暫定日本語案: 404 empty filter combinations.
• 暫定日本語案: Mobile-first: Google indexes the mobile version. Your mobile nav must use 暫定日本語案: real anchors with the same コンテンツ and structured データ — “Google won’t load 暫定日本語案: コンテンツ that requires user interactions… to load.”
• 暫定日本語案: Sitelinks are influenced by structure, titles, and anchor text — not directly 暫定日本語案: controlled.

暫定日本語案: Official documentation

暫定日本語案: Primary-source documentation, mostly Google’s コマース specialty docs.

暫定日本語案: Google — コマース structure & URLs

• 暫定日本語案: Help Google understand your コマース サイト structure — the menu → category → subcategory → 商品 linking pattern, and “Google analyzes the linkages between ページ.”
• 暫定日本語案: Designing a URL structure for コマース sites — persistent URLs, ?key=value parameters, minimizing alternative URLs.
• 暫定日本語案: コマース SEO overview — the specialty-docs hub.
• 暫定日本語案: Pagination and incremental ページ loading — why traditional pagination is more crawlable than “load more” / infinite scroll.

暫定日本語案: Google — リンク, breadcrumbs, sitelinks

• 暫定日本語案: SEO リンク best practices (crawlable リンク) — the <a href> requirement and what breaks crawlability.
• 暫定日本語案: Breadcrumb (BreadcrumbList) structured データ — markup spec; “represent a typical user path… instead of mirroring the URL structure.”
• 暫定日本語案: Learn about sitelinks — how Google generates them from リンク structure; what you can and can’t control.

暫定日本語案: Google — クロール, facets, mobile, international

• 暫定日本語案: Managing クロール of faceted navigation URLs — robots.txt as the preferred fix; 404 empty combinations.
• 暫定日本語案: Optimize your クロール budget — capacity + demand; eliminating duplicates.
• 暫定日本語案: Mobile-first インデックス登録 best practices — コンテンツ/structured-データ parity; interaction-loaded コンテンツ.
• 暫定日本語案: Managing multi-regional and multilingual sites — the ccTLD / subdomain / subdirectory tradeoffs; don’t use IP detection.

暫定日本語案: Bing / Microsoft

• 暫定日本語案: Keeping コンテンツ discoverable with sitemaps in AI-powered 検索 (Canel & Madhavan, Jul 2025) — sitemap scale limits and the lastmod freshness signal for large catalogs.

暫定日本語案: Quotes from the source

暫定日本語案: On-the-record statements from Google and Bing. Each リンク deep-リンク to the quoted 暫定日本語案: passage where the source allows it.

暫定日本語案: Google — how Google reads structure

• 暫定日本語案: “Google generally doesn’t look at the structure of URLs to work out the structure of a サイト. Instead, it analyzes the linkages between ページ to gain insights about the relative importance of different ページ on a サイト.” 暫定日本語案: Jump to quote
• 暫定日本語案: “the more リンク a ページ has to it within a サイト, the higher the relative importance of the ページ to other ページ.” 暫定日本語案: Jump to quote
• 暫定日本語案: “add リンク from menus to category ページ, from category ページ to sub-category ページ, and finally from sub-category ページ to all 商品 ページ.” 暫定日本語案: Jump to quote
• 暫定日本語案: “If category ページ don’t include direct リンク to all 商品 in a category, Googlebot might not find all of your 商品 by クロール alone.” 暫定日本語案: Jump to quote

暫定日本語案: Google — URLs, リンク, breadcrumbs

• 暫定日本語案: “use long-term, persistent URLs. Avoid internally linking to temporary parameters, such as session-IDs, tracking codes, user-relative values (location=nearby, time=last-week), and the current time.” 暫定日本語案: Jump to quote
• 暫定日本語案: “Minimize the number of alternative URLs that return the same コンテンツ to avoid Google making more requests to your サイト than needed.” 暫定日本語案: Jump to quote
• 暫定日本語案: “Google can only クロール your リンク if it’s an <a> HTML element with an href attribute.” 暫定日本語案: Jump to quote
• 暫定日本語案: “We recommend providing breadcrumbs that represent a typical user path to a ページ, instead of mirroring the URL structure.” 暫定日本語案: Jump to quote

暫定日本語案: Google — facets, sitelinks, mobile

• 暫定日本語案: “Use robots.txt to disallow クロール of faceted navigation URLs.” 暫定日本語案: Jump to quote
• 暫定日本語案: “Our systems analyze the リンク structure of your サイト to find shortcuts.” 暫定日本語案: Jump to quote
• 暫定日本語案: “Google uses the mobile version of a サイト’s コンテンツ, crawled with the smartphone agent, for インデックス登録 and ranking.” 暫定日本語案: Jump to quote

暫定日本語案: John Mueller, Google (office-hours, Feb 2, 2021 — via 検索エンジン Journal’s verbatim reproduction)

• 暫定日本語案: “So from my point of view, I think for a lot of sites it makes sense to have more of a pyramid structure.”
• 暫定日本語案: “But it’s not the case that a super flat structure is going to be better than a kind of reasonable pyramid structure.”
• 暫定日本語案: “But at the same time you don’t want it to be such that it’s like you have to click through a million times to actually get to the actual コンテンツ.” 暫定日本語案: Read the coverage

暫定日本語案: Architecture audit checklist

暫定日本語案: A pass to confirm both shoppers and crawlers can navigate your store:

• 暫定日本語案: [ ] Your store follows a pyramid: homepage → top-level categories → 暫定日本語案: subcategories → 商品 (not totally flat, not buried deep).
• 暫定日本語案: [ ] Important 商品 are within a few clicks of the homepage and linked 暫定日本語案: from high-authority ページ (homepage, top categories, editorial).
• 暫定日本語案: [ ] No orphan 商品 — every 商品 is linked from at least its category ページ.
• 暫定日本語案: [ ] Category ページ リンク to all their 商品 (or you have sitemaps/feeds as a 暫定日本語案: backstop for very large catalogs).
• 暫定日本語案: [ ] Navigation and menu リンク are real <a href> anchors in the rendered DOM — 暫定日本語案: not onclick-only / javascript: / routerLink handlers.
• 暫定日本語案: [ ] Global nav is trimmed to top-level categories; deeper navigation lives on 暫定日本語案: category ページ (mega menu isn’t dumping the whole taxonomy into every ページ).
• 暫定日本語案: [ ] Breadcrumbs are present, use BreadcrumbList スキーマ, and model the user 暫定日本語案: path (not the raw URL).
• 暫定日本語案: [ ] Multi-category 商品 resolve to a single canonical URL.
• 暫定日本語案: [ ] URL format is consistent, descriptive (/product/black-t-shirt, not 暫定日本語案: /product/3243), and stable — no recent or planned restructures purely 暫定日本語案: for SEO.
• 暫定日本語案: [ ] Faceted navigation is controlled: robots.txt disallow on filter URLs (not 暫定日本語案: relying on canonical alone); empty filter combinations return 404.
• 暫定日本語案: [ ] Mobile nav exposes the same categories/商品 as desktop, as real 暫定日本語案: anchors, with the same コンテンツ and structured データ.
• 暫定日本語案: [ ] XML sitemap lists canonical, indexable URLs with accurate lastmod, submitted 暫定日本語案: in Google 検索 Console and Bing Webmaster Tools.

暫定日本語案: The mental models

暫定日本語案: 1. リンク are the structure; URLs are just labels. 暫定日本語案: Google infers hierarchy and importance from your リンク graph, not your URL 暫定日本語案: paths. Before you touch a URL scheme, ask what リンク to the ページ and what it 暫定日本語案: リンク out to. That’s what moves the needle.

暫定日本語案: 2. The pyramid, between two failure modes. 暫定日本語案: Too flat = no importance signal, Google can’t tell what owns what. Too deep = 暫定日本語案: ページ starve for クロール attention and PageRank. Aim for a shallow pyramid: 暫定日本語案: homepage → categories → subcategories → 商品, with important ページ kept close 暫定日本語案: to the top via internal リンク.

暫定日本語案: 3. Depth is about discoverability, not a magic number. 暫定日本語案: The “3-click rule” is a heuristic. The actual risk is orphaning, not exceeding a 暫定日本語案: click count. A deep-but-linked ページ beats a shallow-but-orphaned one.

暫定日本語案: 4. URL decision rule: stable beats clever. 暫定日本語案: Pick a consistent, descriptive, persistent format once. Don’t restructure for SEO 暫定日本語案: — the change costs you (broken リンク, redirect chains) more than the new structure 暫定日本語案: gains you (≈nothing, as a ranking factor).

暫定日本語案: 5. The four commerce-specific leaks to plug.

• 暫定日本語案: Multi-category products → one canonical + BreadcrumbList スキーマ.
• 暫定日本語案: Mega menus → real anchors, trimmed to top-level categories.
• 暫定日本語案: Faceted navigation → robots.txt disallow (preferred over canonical); 404 empties.
• 暫定日本語案: Mobile nav → it IS your SEO nav; parity in リンク, コンテンツ, and スキーマ.

暫定日本語案: コマース architecture — cheat sheet

暫定日本語案: Flat vs. pyramid (what each does)

暫定日本語案: Click depth guidelines (rules of thumb, not Google rules)

暫定日本語案: Depth is a crawlability + PageRank-flow concern, not a direct ranking factor. 暫定日本語案: An orphaned shallow ページ loses to a linked deep ページ.

暫定日本語案: URL structure fast facts

• 暫定日本語案: Google reads リンク, not URL paths, to infer hierarchy.
• 暫定日本語案: URL structure ≈ 1/7 as a ranking factor (Mueller) — stability is the real risk.
• 暫定日本語案: Descriptive > numeric: /product/black-t-shirt beats /product/3243.
• 暫定日本語案: Persistent URLs; avoid session IDs / tracking params in internal リンク.
• 暫定日本語案: ?key=value parameters over bare ?value.
• 暫定日本語案: Multi-category 商品 → one canonical + hierarchy via BreadcrumbList スキーマ.

暫定日本語案: Navigation & リンク

• 暫定日本語案: Crawlable = real <a href>. JS menus OK if they render anchors. onclick-only / javascript: = not crawlable.
• 暫定日本語案: Trim global nav to top-level categories; push deeper nav onto category ページ.
• 暫定日本語案: Breadcrumbs: BreadcrumbList スキーマ, model the user path, multiple trails allowed for multi-category 商品.

暫定日本語案: Faceted navigation (クロール-budget order of preference)

1. 暫定日本語案: robots.txt disallow filter URLs — Google’s preferred fix.
2. 暫定日本語案: URL fragments (#) for filter state — passively un-crawled.
3. 暫定日本語案: rel=canonical — “less effective in the long term.”
4. 暫定日本語案: 404 empty filter combinations.

暫定日本語案: Mobile-first

• 暫定日本語案: Google indexes the mobile version → mobile nav = SEO nav.
• 暫定日本語案: Same コンテンツ + same structured データ as desktop. Interaction-loaded コンテンツ may not be seen.

暫定日本語案: Sitelinks — influenced (structure, titles, anchor text), not controlled. Bad one? noindex/remove the ページ.

暫定日本語案: Where should a new コマース ページ live?

暫定日本語案: Architecture mistakes to avoid

暫定日本語案: Making every 商品 one click from the homepage

暫定日本語案: Why it fails: a super-flat graph removes meaningful priority and overwhelms the 暫定日本語案: navigation. Do instead: use a reasonable pyramid and reserve prominent リンク for 暫定日本語案: categories and 商品 that matter most.

暫定日本語案: Treating URL folders as the hierarchy

暫定日本語案: Why it fails: Google derives structure from リンク, not directory depth. Do instead: 暫定日本語案: build crawlable parent-child リンク, breadcrumbs, and category paths; keep URLs stable and 暫定日本語案: readable without relying on them to communicate importance.

暫定日本語案: Exposing every facet as a crawlable リンク

暫定日本語案: Why it fails: combinations multiply into a large duplicate URL space. Do instead: 暫定日本語案: decide which filtered demand deserves a curated landing ページ and constrain the rest.

暫定日本語案: Designing desktop and mobile navigation separately

暫定日本語案: Why it fails: important リンク hidden from the mobile version may be missing from the 暫定日本語案: version Google primarily evaluates. Do instead: preserve essential hierarchy and 暫定日本語案: ordinary anchor リンク across responsive states.

暫定日本語案: Tools for auditing コマース architecture

• 暫定日本語案: Use the Internal リンク Cluster Visualizer with a supplied 暫定日本語案: リンク graph to find orphans, weakly connected sections, and ページ receiving little 暫定日本語案: internal importance.
• 暫定日本語案: Use the リンク Analyzer on representative category and 商品 暫定日本語案: HTML to verify crawlable anchors, breadcrumbs, and destination URLs.
• 暫定日本語案: Use the Faceted Navigation Auditor to classify 暫定日本語案: parameter patterns before promoting or blocking filtered ページ.
• 暫定日本語案: Use Scout サイト Audit Free for a bounded クロール that can expose 暫定日本語案: broken routes and ページ the intended pyramid does not reach.

暫定日本語案: Standing architecture metrics

暫定日本語案: Crawlable click depth by template

暫定日本語案: Metric: distribution of shortest internal-リンク depth for categories, subcategories, 暫定日本語案: and 商品. What it tells you: whether important inventory is buried or disconnected. 暫定日本語案: How to pull it: a repeatable クローラー export, segmented by template. Benchmark / 暫定日本語案: realistic range: establish a baseline by template and investigate material regressions; 暫定日本語案: there is no universal three-click ranking rule. Cadence: monthly and after navigation 暫定日本語案: or taxonomy releases.

暫定日本語案: Orphan and weakly linked ページ count

暫定日本語案: Metric: indexable sitemap URLs with no crawlable inlinks, plus priority ページ with very 暫定日本語案: few inlinks. What it tells you: where the declared catalog and actual リンク graph 暫定日本語案: disagree. How to pull it: reconcile sitemap URLs with a クロール and analytics or GSC 暫定日本語案: landing ページ. Benchmark / realistic range: true indexable orphans should be zero; 暫定日本語案: minimum inlink needs depend on the store hierarchy. Cadence: monthly.

暫定日本語案: Organic landing-ページ coverage

暫定日本語案: Metric: share of intended category and 商品 templates receiving organic impressions. 暫定日本語案: What it tells you: whether architecture makes the important catalog discoverable and 暫定日本語案: eligible to surface. How to pull it: 検索 Console ページ exports joined to the canonical 暫定日本語案: URL inventory. Benchmark / realistic range: compare by template and inventory state, 暫定日本語案: using the store’s own trend rather than an invented industry target. Cadence: monthly 暫定日本語案: with quarterly taxonomy review.

暫定日本語案: Resources worth your time

暫定日本語案: My related writing

• 暫定日本語案: The Most Important Thing SEOs Overlook: Internal リンク (検索エンジン Land) — why internal リンク direct authority to your best ページ, and the part teams forget (going back to リンク old コンテンツ).
• 暫定日本語案: The Beginner’s Guide to Technical SEO — where サイト structure sits in the bigger technical picture.

暫定日本語案: On this サイト

• 暫定日本語案: コマース SEO — the pillar hub.
• 暫定日本語案: Faceted navigation — the クロール-budget deep dive.
• 暫定日本語案: Category ページ SEO and 商品 ページ SEO — the two ページ types this architecture connects.
• 暫定日本語案: Internal リンク — the mechanism that makes architecture work.
• 暫定日本語案: クロール and クロール budget — how bots traverse your structure.

暫定日本語案: From others

• 暫定日本語案: コマース SEO: A Beginner’s Guide (Chris Haines, Ahrefs) — covers hierarchy, URL structure, and the flat-商品-URL recommendation for multi-category 商品.
• 暫定日本語案: 11 Ways to Improve コマース Category ページ for SEO (Sam Underwood, Ahrefs) — operational detail on pyramid structure, breadcrumbs, and category URL patterns.
• 暫定日本語案: How to Structure Your ウェブサイト Architecture for SEO (Ahrefs) — the general (non-コマース-specific) structure guide.
• 暫定日本語案: John Mueller Recommends Pyramid サイト Structure (Roger Montti, 検索エンジン Journal) — the verbatim source of the pyramid quotes.

暫定日本語案: From around the industry

• 暫定日本語案: Google Recommends Pyramid Navigation Structure (Barry Schwartz, 検索エンジン Roundtable) — Schwartz’s coverage of the same Mueller office-hours session; useful secondary confirmation of the pyramid recommendation.
• 暫定日本語案: Google: URL Structure Not So Important For SEO (検索エンジン Roundtable) — Mueller rates URL structure ~1/7 as a direct ranking factor; argues stability matters more than depth.
• 暫定日本語案: コマース SEO Guide (Jenn Mathews, 検索エンジン Land) — broad practitioner guide covering サイト structure, クロール budget, and category architecture.
• 暫定日本語案: Importance of リンク Architecture (Google 検索 Central Blog, 2008) — the foundational Google post explaining how internal リンク structure distributes PageRank through a サイト.
• 暫定日本語案: Managing クロール of Faceted Navigation URLs (Google) — official primary source for the robots.txt-first approach to faceted nav; the article’s quotes リンク here.
• 暫定日本語案: Bing Webmaster Guidelines (Microsoft Bing) — Bing’s counterpart to Google’s クロール/インデックス登録 guidance; covers リンク reachability requirements and sitemap submission.

暫定日本語案: Test yourself: コマース サイト Architecture

暫定日本語案: Five quick questions on コマース hierarchy and internal リンク. Pick an answer for each, 暫定日本語案: then check your work.

変更履歴