暫定日本語訳：Flat vs. Deep サイト Architecture: A Practical Decision Framework

暫定日本語案: TL;DR — A flat サイト keeps most ページ close to the homepage; a deep サイト 暫定日本語案: nests them through many category layers. Neither is automatically better — the 暫定日本語案: right amount of depth depends mostly on how clearly your categories divide up, 暫定日本語案: and secondarily on how big your サイト is. A small brochure サイト can usually stay 暫定日本語案: flat. A giant online store usually needs more layers. The practical goal is to 暫定日本語案: give important ページ short, clear, crawlable paths, and to test changes rather 暫定日本語案: than assume they’ll work; there is no universal three-click rule, and no change 暫定日本語案: guarantees クロール, ranking, or traffic gains. 暫定日本語案: Evidence for this claim Googlebot generally follows links between pages; important pages should be reachable through crawlable navigation rather than relying only on search boxes. Scope: Current Google ecommerce navigation guidance; no universal click-count threshold. Confidence: high · Verified: 2026-07-14 Google Search Central: Ecommerce navigation structure Evidence for this claim Google recommends linking important pages from relevant pages and using concise, descriptive anchor text. Scope: Current Google internal-link guidance. Confidence: high · Verified: 2026-07-14 Google Search Central: Link best practices

暫定日本語案: What “flat” and “deep” actually mean

暫定日本語案: Every サイト has some hierarchy — homepage at the top, then sections, then 暫定日本語案: individual ページ. The useful definition isn’t a fixed layer count, though — it’s 暫定日本語案: your サイト’s click-depth distribution (what share of ページ sit at depth 1, 2, 暫定日本語案: 3, 4+) and, more specifically, how many clicks your priority ページ need. 暫定日本語案: Flat describes a distribution where most ページ, especially priority ones, sit 暫定日本語案: one or two clicks from the homepage. Deep describes one where reaching typical 暫定日本語案: ページ means passing through several layers: homepage → category → subcategory → 暫定日本語案: sub-subcategory → ページ. The ページ-count and level bands later in this article are 暫定日本語案: labeled heuristics for calibrating that distribution — not the definition itself.

暫定日本語案: The neighboring articles in this cluster (サイト architecture and ウェブサイト structure) 暫定日本語案: already explain why a sensible pyramid beats both a pancake-flat サイト and a 暫定日本語案: needlessly deep one. This article is the practical follow-up: how do you decide, 暫定日本語案: for your actual サイト, how flat or deep it should be — and how do you check and fix 暫定日本語案: it?

暫定日本語案: The short answer

暫定日本語案: There’s no universal “correct” number of levels. It comes down to two questions:

1. 暫定日本語案: How many ページ do you have that need to be found on their own? A little 暫定日本語案: business サイト with 40 ページ can keep everything one or two clicks from the 暫定日本語案: homepage. A store with 20 000 商品 can’t — it needs categories and 暫定日本語案: subcategories, or the navigation becomes an unusable wall of リンク.
2. 暫定日本語案: How clearly do your categories divide up? If your sections are obvious and 暫定日本語案: don’t overlap (Shoes vs. Shirts), you can stay flatter. If they blur into each 暫定日本語案: other, you’ll usually need a little more structure to keep things organized.

暫定日本語案: The one rule worth remembering

暫定日本語案: Keep important ページ easy to reach through crawlable リンク. Google gives no 暫定日本語案: universal click-count threshold. Treat “three clicks” as a diagnostic heuristic, 暫定日本語案: not a 検索-engine requirement.

暫定日本語案: If a ページ you care about is buried five or six clicks down, you don’t have to rip 暫定日本語案: your whole サイト apart. Usually you just add a hub ページ (a category-style ページ) 暫定日本語案: that リンク straight to it from higher up — that alone can pull it from six clicks 暫定日本語案: to three.

暫定日本語案: Want the real decision framework — ページ-count thresholds, how to measure your 暫定日本語案: サイト’s depth, and how to fix it — switch to the Advanced tab, or jump to the 暫定日本語案: Decision Tree.

暫定日本語案: TL;DR — This is the “how do I decide and act” companion to the conceptual 暫定日本語案: pyramid-vs-flat coverage already in this cluster — I’m not re-arguing why a 暫定日本語案: pyramid beats both extremes. Depth should scale mostly with (a) how distinct the 暫定日本語案: natural categories, templates, and update patterns are, and secondarily with 暫定日本語案: (b) how many ページ need their own findable URL. Rough shape, as heuristics you 暫定日本語案: calibrate rather than fixed cutoffs: ~50-ページ brochure サイト → flat; a few 暫定日本語案: thousand ページ → shallow pyramid, 2–3 levels; 10 000+ SKUs → multi-level 暫定日本語案: hierarchy with hub ページ, or you get the mega-menu リンク-dump failure mode. 暫定日本語案: Google does not set a maximum number of clicks. Measure by クロール for a 暫定日本語案: segmented click-depth distribution (by template and priority, not a 暫定日本語案: sitewide average), then cautiously cross-reference GSC クロール Stats — 暫定日本語案: aggregate first-party データ, not per-URL proof — to find the depth cliff 暫定日本語案: where クロール drops off. Fix with hub ページ (the highest-ROI move), 暫定日本語案: related-コンテンツ modules, and breadcrumbs, testing each change against a 暫定日本語案: comparison segment with a monitoring window and a rollback trigger. URL-folder 暫定日本語案: depth ≠ click depth — リンク a buried ページ closer rather than rewriting its URL. 暫定日本語案: None of this guarantees クロール, インデックス登録, ranking, traffic, or AI-citation 暫定日本語案: gains. 暫定日本語案: Evidence for this claim Googlebot generally follows links between pages; important pages should be reachable through crawlable navigation rather than relying only on search boxes. Scope: Current Google ecommerce navigation guidance; no universal click-count threshold. Confidence: high · Verified: 2026-07-14 Google Search Central: Ecommerce navigation structure Evidence for this claim Google recommends linking important pages from relevant pages and using concise, descriptive anchor text. Scope: Current Google internal-link guidance. Confidence: high · Verified: 2026-07-14 Google Search Central: Link best practices

暫定日本語案: This isn’t the “why” article

暫定日本語案: Two other pieces in this cluster already own the conceptual case. サイト architecture 暫定日本語案: covers flat vs. deep hierarchies as one of the failure modes at the extremes, and 暫定日本語案: ウェブサイト structure makes the pyramid-beats-both-extremes argument with Mueller’s 暫定日本語案: quotes about context, クロール, and mega menus. I’m not going to re-derive any of 暫定日本語案: that here or re-run those quotes as the centerpiece. If you want the why, read 暫定日本語案: those first.

暫定日本語案: What neither covers — and what people planning a new サイト, replatforming, or 暫定日本語案: auditing an existing one actually need — is the operator’s manual: for my 暫定日本語案: specific サイト, how many levels should I have, how do I measure where I currently 暫定日本語案: sit, and how do I fix it when it’s wrong? That’s this article. The centerpiece is 暫定日本語案: the decision tree in the Decision Tree tab; everything below is the reasoning 暫定日本語案: and workflow behind it.

暫定日本語案: Depth is a function of category distinctness and size

暫定日本語案: There is no fixed right answer, and anyone who hands you one (I’ve seen “always 暫定日本語案: flat,” “always three clicks,” “never more than two subcategory levels”) is selling 暫定日本語案: a house style as a law. The honest framing is that hierarchy depth should scale 暫定日本語案: with two independent variables — lead with the first, since it’s the one SEO-only 暫定日本語案: advice usually skips:

1. 暫定日本語案: How distinct or overlapping the natural categories are, and what task the 暫定日本語案: user is on. Nielsen Norman Group’s research on 暫定日本語案: flat vs. deep ウェブサイト hierarchies 暫定日本語案: nails it: “Flat hierarchies tend to work well if you have distinct, 暫定日本語案: recognizable categories, because people don’t have to click through as many 暫定日本語案: levels,” and “Categories that are specific and do not overlap are the easiest 暫定日本語案: to understand.” Their bottom line matches the whole spirit of this framework: 暫定日本語案: “Like most design questions, there’s no single right answer, and going too far 暫定日本語案: to either extreme will backfire.” Also weigh which template a ページ uses, how 暫定日本語案: important it is to the business, and how often that section updates (Illyes’ 暫定日本語案: /news/ vs. /archives/ point below) — these matter as much as a raw ページ count.
2. 暫定日本語案: How many distinct items need their own findable ページ. Forty ページ and 暫定日本語案: 20 000 商品 are different problems, but ページ count on its own is a rough 暫定日本語案: signal, not the deciding factor — a small サイト with badly overlapping 暫定日本語案: categories can need more structure than a larger one with clean, distinct 暫定日本語案: sections.

暫定日本語案: Google’s own guidance points the same direction on the size axis. Gary Illyes has 暫定日本語案: said hierarchy should scale with the サイト — that for a large サイト it’s “likely 暫定日本語案: better to have a hierarchical structure” because it lets 検索 engines “treat 暫定日本語案: different sections differently, especially when it comes to クロール,” and that 暫定日本語案: if you “put everything in one directory, that’s hardly possible.” (Reported by 暫定日本語案: 検索エンジン Journal; 暫定日本語案: I’d treat the exact wording as trade-press transcription rather than a canonical 暫定日本語案: doc.) That’s the load-bearing point for the large-catalog end of the framework: 暫定日本語案: size forces hierarchy.

暫定日本語案: ページ-count rules of thumb

暫定日本語案: Nobody — not Google, not Bing — publishes a ページ-count-to-levels table, and no 暫定日本語案: dated study ties the ~50-ページ or 10 000+-ページ bands below to a specific サイト 暫定日本語案: population. Treat these as practitioner heuristics you calibrate to your own 暫定日本語案: サイト, not verified universal cutoffs — category distinctness, templates, and 暫定日本語案: update patterns (above) should move you off these bands in either direction:

• 暫定日本語案: Small / brochure sites (roughly under 50–100 ページ, few natural categories): 暫定日本語案: stay flat. Homepage → one level of section/category → ページ, with most コンテンツ 暫定日本語案: one or two clicks deep. Bing’s three-click figure is your outer bound, and you’ll 暫定日本語案: almost never hit it. NN/g’s “distinct categories work well flat” applies directly 暫定日本語案: here.
• 暫定日本語案: Mid-size コンテンツ sites (a few hundred to a few thousand ページ, several genuinely 暫定日本語案: distinct topic areas): a shallow pyramid — homepage → category → optional 暫定日本語案: subcategory → ページ, most コンテンツ within three clicks. This is the sweet spot the 暫定日本語案: cluster’s conceptual pieces describe, and it’s where this very サイト sits.
• 暫定日本語案: Large コマース catalogs, enterprise sites, publisher archives (10 000+ ページ 暫定日本語案: or SKUs): hierarchy stops being an aesthetic choice and becomes a necessity. 暫定日本語案: You need enough levels — top-level category → subcategory → (sometimes a 暫定日本語案: filtered/facet layer) → 商品 — that you’re not trying to expose the entire 暫定日本語案: catalog from one navigation surface. The classic failure here is over-flattening 暫定日本語案: a huge catalog into a mega menu that dumps hundreds of リンク one click from 暫定日本語案: the homepage; the mega-menu topic in the コマース cluster covers why that 暫定日本語案: strips the grouping signals 検索 engines rely on. The corrective isn’t “add 暫定日本語案: infinite depth” — it’s “add enough hierarchy to organize the catalog, then use 暫定日本語案: hub ページ to keep priority items reachable in three-to-four clicks anyway.”

暫定日本語案: You’ll see competitor guides assert crisp numbers here (“flat = 3 clicks or fewer,” 暫定日本語案: “keep subcategories to 2–3 levels,” “8 top-level categories × 4–8 subcategories”). 暫定日本語案: Those are useful as industry consensus — the SEO field’s de facto defaults — but 暫定日本語案: they’re not sourced to any 検索エンジン, so label them that way in your own head. 暫定日本語案: The uncontroversial, well-supported shape is simply: small catalog → flat, large 暫定日本語案: catalog → more hierarchy.

暫定日本語案: URL depth is not click depth (a reminder, not a re-derivation)

暫定日本語案: The url-structure and ウェブサイト-structure articles in this cluster already establish 暫定日本語案: the key fact: Google reads the リンク graph, not the slashes in your URLs. I’m 暫定日本語案: not re-arguing it. The reason it belongs here is purely operational, because it 暫定日本語案: changes how you fix a depth problem.

暫定日本語案: A URL like /category/subcategory/product/ looks three levels deep, but if a hub 暫定日本語案: ページ リンク to it directly, it’s one click from the homepage. Conversely, a ページ 暫定日本語案: with a short, tidy URL can be buried six clicks deep with no hub linking to it. So 暫定日本語案: two rules fall out for remediation:

• 暫定日本語案: Don’t “fix” click depth by rewriting URLs flatter. Stripping folders out of 暫定日本語案: the address while the リンク graph stays deep does nothing.
• 暫定日本語案: Do fix it by linking the ページ closer. Add or strengthen a hub リンク from a 暫定日本語案: shallower level. The URL can stay exactly as it is.

暫定日本語案: That distinction is what makes the worked example later (six clicks → three, 暫定日本語案: without renaming anything) possible.

暫定日本語案: Auditing your current depth, in order

暫定日本語案: You can’t decide where to go without knowing where you are. Three steps:

暫定日本語案: 1. Get the click-depth distribution from a クロール, segmented, not averaged. Run 暫定日本語案: Ahrefs サイト Audit (its Structure Explorer / depth 暫定日本語案: view) or Screaming Frog (the サイト 暫定日本語案: Structure tab and the クロール Depth column) and look at what percentage of your ページ 暫定日本語案: sit at depth 1, 2, 3, and 4+. Don’t stop at the sitewide number — break it out by 暫定日本語案: template, ページ purpose, business priority, and discovery source (internal リンク 暫定日本語案: vs. sitemap-only). See the クロール depth 暫定日本語案: article for the URL-level measurement mechanics. This is your ground-truth map of 暫定日本語案: how deep the サイト actually is in the リンク graph — not in the URLs. A healthy サイト 暫定日本語案: has its priority ページ, specifically, concentrated in the shallow buckets; a good 暫定日本語案: overall average can still hide a buried revenue template.

暫定日本語案: 2. Cross-reference with GSC クロール Stats — cautiously. The クロール tells you how 暫定日本語案: deep ページ are; Google’s 暫定日本語案: クロール Stats report 暫定日本語案: tells you what Google is actually choosing to クロール, and how often. It splits 暫定日本語案: requests into Discovery (URLs Google hadn’t crawled before) and Refresh 暫定日本語案: (recrawls of known ページ). Treat クロール Stats as aggregate, sitewide, first-party 暫定日本語案: データ — it isn’t a per-URL log, so it can’t by itself prove that any single ページ 暫定日本語案: or segment is suffering from depth specifically. The practical read — this is 暫定日本語案: practitioner interpretation, not a Google statement: if Discovery stays near zero 暫定日本語案: while you keep publishing, your internal linking isn’t surfacing new or deep ページ 暫定日本語案: to the クローラー; if Refresh drops sharply without ページ being removed, something 暫定日本語案: structural is suppressing recrawls. Almost no competitor guide connects the 暫定日本語案: クローラー’s depth データ to GSC’s クロール データ, and the join is where the insight lives — 暫定日本語案: but treat it as a hypothesis to test (compare a segment you changed against a 暫定日本語案: similar segment you didn’t), not a proof on its own.

暫定日本語案: 3. Find the depth cliff. Overlay the two: the depth level where クロール frequency 暫定日本語案: and coverage fall off a cliff is the practical, measured definition of “too deep” 暫定日本語案: for your サイト — far more useful than any generic number. You’re not guessing that 暫定日本語案: depth 5 is bad; you’re observing that on your サイト, クロール collapses past depth 暫定日本語案: 4 for a specific segment. (Note: you’ll find secondary コンテンツ claiming things like 暫定日本語案: “ページ get crawled 5–10× less at depth 5.” I couldn’t source that to any primary 暫定日本語案: Google material, so I won’t present it as a stat — measure your own cliff instead, 暫定日本語案: and hold it to a comparison group before you act on it.)

暫定日本語案: Fixing depth problems

暫定日本語案: In rough priority order:

• 暫定日本語案: Hub / category ページ — the single highest-ROI fix. Add or strengthen a 暫定日本語案: mid-level ページ that both humans and crawlers can use to reach buried コンテンツ in 暫定日本語案: fewer clicks. It shortens click depth without touching URLs. This is almost 暫定日本語案: always the first move.
• 暫定日本語案: Related-コンテンツ modules. End-of-article and sidebar リンク create additional 暫定日本語案: paths to deep ページ. They’re a weaker signal than body-コンテンツ リンク (Google 暫定日本語案: tries to identify a ページ’s primary コンテンツ area and weights contextual リンク 暫定日本語案: above navigational “module” リンク — I’d treat that as a well-attested read of 暫定日本語案: Mueller’s position rather than a verbatim quote), but at scale, more real paths to 暫定日本語案: deep ページ genuinely help.
• 暫定日本語案: Breadcrumbs. They reinforce hierarchy for users and 検索 engines, and the 暫定日本語案: machine-readable version is BreadcrumbList structured データ. Google’s own line: 暫定日本語案: “A breadcrumb trail on a ページ indicates the ページ’s position in the サイト 暫定日本語案: hierarchy, and it may help users understand and explore a サイト effectively.” 暫定日本語案: (See the breadcrumbs article in this cluster for the markup.)
• 暫定日本語案: Pagination — mind how it interacts with depth. The pagination article in this 暫定日本語案: cluster covers the mechanics; the depth-specific point is that a paginated 暫定日本語案: listing is itself a クロール path (ページ 1 → 2 → 3 …), so a 商品 or article that 暫定日本語案: only appears on ページ 4+ of a category listing inherits real extra click depth. 暫定日本語案: Don’t rely on deep pagination to carry your priority items — surface them via a 暫定日本語案: hub or related module instead, and keep the pagination self-canonicalizing so the 暫定日本語案: path stays open.

暫定日本語案: One nuance worth holding onto: depth is a risk factor, not an automatic penalty. 暫定日本語案: A technically deep ページ can still get crawled fine if it has strong external リンク 暫定日本語案: or lives in a frequently-updated, well-organized directory (Illyes’ /news/ example). 暫定日本語案: That’s exactly why the depth-cliff measurement beats assuming by depth number 暫定日本語案: alone.

暫定日本語案: None of these fixes can promise クロール, インデックス登録, rankings, traffic, or 暫定日本語案: AI-citation gains — depth is one input among many. Treat each change as 暫定日本語案: reversible and testable: pick a comparison segment you’re not changing, set a 暫定日本語案: monitoring window (a few クロール/recrawl cycles is usually enough to see a 暫定日本語案: directional shift in Discovery/Refresh or the depth distribution), and define a 暫定日本語案: rollback trigger up front — if a hub ページ adds clicks for some users without 暫定日本語案: shortening the クロール path you were targeting, unwind it rather than layering 暫定日本語案: more changes on top. See the Validation Tests tab for the fuller test/ 暫定日本語案: monitor/rollback table.

暫定日本語案: Worked example: six clicks to three

暫定日本語案: Take a 商品 buried like this: Home → top category → subcategory → 暫定日本語案: sub-subcategory → listing ページ 3 → 商品. That’s six clicks. It’s a genuinely 暫定日本語案: important 商品, but the クローラー has to traverse a deep listing to reach it, and 暫定日本語案: it’s getting recrawled rarely.

暫定日本語案: The fix isn’t a re-architecture and it isn’t a URL change. Add a hub / landing 暫定日本語案: ページ one level below the homepage — say a “Best Sellers” or seasonal collection 暫定日本語案: ページ — and リンク the 商品 directly from it: Home → collection hub → 商品. 暫定日本語案: Now it’s three clicks. The URL never changed (reinforcing that click depth, not URL 暫定日本語案: depth, was the problem), and you’ve added a shallow, high-value path that both users 暫定日本語案: and crawlers can follow. That single hub ページ can do the same job for a whole batch 暫定日本語案: of buried priority items at once.

暫定日本語案: When “get everything crawled” isn’t the goal

暫定日本語案: A closing reframe I keep coming back to in my 暫定日本語案: クロール-budget writing: more クロール doesn’t 暫定日本語案: mean better rankings. But a ページ that never gets crawled can’t rank at all — and the 暫定日本語案: ページ that go uncrawled tend to be exactly the newer, poorly-linked, deep ones this 暫定日本語案: framework is about. Most sites don’t need to obsess over クロール budget; Google’s own 暫定日本語案: guidance says the sites that do are roughly the 1M+ ページ sites changing weekly or 暫定日本語案: ~10K-ページ sites changing daily. For everyone else, depth is a findability and 暫定日本語案: signal-passing concern, not a クロール-budget emergency — but the fix (リンク priority 暫定日本語案: ページ shallower) is the same either way.

暫定日本語案: The neighboring topics — how internal リンク pass signals, how クロール depth affects 暫定日本語案: discovery, breadcrumbs, pagination, and the サイト-architecture models — all plug 暫定日本語案: into the decisions in the tree below.

暫定日本語案: AI summary

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

• 暫定日本語案: This is the “how do I decide” companion, not the “why a pyramid wins” article 暫定日本語案: — that’s already covered by the サイト-architecture and ウェブサイト-structure pieces in 暫定日本語案: this cluster.
• 暫定日本語案: Depth should scale mostly with category distinctness (templates, priority, 暫定日本語案: update patterns), and secondarily with ページ count. NN/g: distinct, 暫定日本語案: non-overlapping categories work well flat; there’s no single right answer. ページ 暫定日本語案: count alone is a rough signal, not the deciding factor.
• 暫定日本語案: ページ-count bands are practitioner heuristics, not verified cutoffs: ~50-ページ 暫定日本語案: brochure サイト → flat; a few thousand ページ → shallow pyramid (2–3 levels, within 暫定日本語案: 3 clicks as an operational target); 10 000+ SKUs → multi-level hierarchy, or you 暫定日本語案: get the mega-menu リンク-dump failure. Illyes: large sites are “likely 暫定日本語案: better” with hierarchical structure.
• 暫定日本語案: Only Bing states a number (important ページ within ~3 clicks, an operational 暫定日本語案: target, not a guarantee); Google deliberately states none — treat competitor 暫定日本語案: “3-click / 2-level” numbers as industry consensus, not official guidance.
• 暫定日本語案: URL-folder depth ≠ click depth. Google reads the リンク graph. Fix depth by 暫定日本語案: linking a ページ closer, not by rewriting its URL flatter. See the クロール depth 暫定日本語案: article for URL-level measurement mechanics.
• 暫定日本語案: Audit in order, segmented not averaged: (1) クロール for the click-depth 暫定日本語案: distribution by template/priority/discovery source (Ahrefs サイト Audit / 暫定日本語案: Screaming Frog); (2) cautiously cross-reference GSC クロール Stats (Discovery 暫定日本語案: vs. Refresh) — aggregate first-party データ, not per-URL proof — for what Google 暫定日本語案: actually crawls; (3) find the depth cliff where クロール drops, treated as a 暫定日本語案: hypothesis to test against a comparison segment, not a proof on its own.
• 暫定日本語案: Fix, in priority order: hub/category ページ (highest ROI), related-コンテンツ 暫定日本語案: modules, breadcrumbs (+ BreadcrumbList スキーマ), and mind how pagination adds 暫定日本語案: depth to items on ページ 4+. Treat every change as reversible: set a monitoring 暫定日本語案: window and a rollback trigger, and don’t promise クロール, インデックス登録, ranking, 暫定日本語案: traffic, or AI-citation gains.
• 暫定日本語案: Worked example: a 商品 at 6 clicks (Home → category → subcategory → 暫定日本語案: sub-subcategory → listing ページ 3 → 商品) pulled to 3 clicks via a new 暫定日本語案: collection hub — no URL change.
• 暫定日本語案: Depth is a risk factor, not an automatic penalty: a deep ページ with strong 暫定日本語案: リンク or in a fresh directory can クロール fine. Measure the cliff; don’t assume by 暫定日本語案: number.

暫定日本語案: How many hierarchy levels should your サイト have?

暫定日本語案: This is the centerpiece. Walk it top to bottom: it branches first on サイト size, 暫定日本語案: then on category distinctness, then on コンテンツ-update patterns, and lands on a 暫定日本語案: concrete recommendation with a target click depth and a first remediation move.

暫定日本語案: Whatever leaf you land on, the audit and remediation are the same: クロール for your 暫定日本語案: click-depth distribution, cross-reference GSC クロール Stats to find the depth cliff, 暫定日本語案: and shorten the path to buried priority ページ with a hub ページ first.

暫定日本語案: Official documentation

暫定日本語案: Primary-source guidance relevant to deciding, measuring, and fixing サイト depth.

暫定日本語案: Google

• 暫定日本語案: SEO リンク best practices (Make your リンク crawlable) — リンク must be <a href>, and “every ページ you care about should have a リンク from at least one other ページ” (the bar deep/orphan ページ fail).
• 暫定日本語案: Optimize your クロール budget — how wasted クロール on low-value URL patterns starves the rest of a large, deep サイト.
• 暫定日本語案: クロール Stats report (検索 Console Help) — the Discovery vs. Refresh breakdown that powers the depth-cliff diagnosis.
• 暫定日本語案: Breadcrumb (BreadcrumbList) structured データ — the remediation markup that signals a ページ’s position in the hierarchy.
• 暫定日本語案: Help Google understand your コマース サイト structure — hierarchical linking for large catalogs, and how Google infers importance from リンク.

暫定日本語案: Bing / Microsoft

• 暫定日本語案: Bing Webmaster Guidelines — the one place either engine states a hard number: keep important ページ within roughly three clicks of the homepage, with sitemap-first discovery.

暫定日本語案: Quotes from the source

暫定日本語案: On-the-record statements relevant to deciding depth (rather than re-litigating why 暫定日本語案: a pyramid wins — those quotes live in the サイト-architecture and ウェブサイト-structure 暫定日本語案: articles). Where the source ページ supports it, each リンク jumps to the passage.

暫定日本語案: Gary Illyes, Google — hierarchy scales with サイト size

• 暫定日本語案: “For a large サイト it’s likely better to have a hierarchical structure… that will allow you to do funky stuff on just one section, and will also allow 検索 engines to potentially treat different sections differently, especially when it comes to クロール.”
• 暫定日本語案: “Having a /news/ section for newsy コンテンツ and /archives/ for old コンテンツ would allow 検索 engines to クロール /news/ faster than the other directory.”
• 暫定日本語案: “If you put everything in one directory, that’s hardly possible.” 暫定日本語案: — Gary Illyes, Google, SEO Office Hours, reported by 検索エンジン Journal. 暫定日本語案: Relayed via trade-press transcription of an office-hours video, not a canonical doc ページ — confirm the exact wording against the original before treating it as final.

暫定日本語案: Google 検索 Console Help — the クロール Stats mechanism behind the “depth cliff”

• 暫定日本語案: Discovery: “The URL requested was never crawled by Google before.” / Refresh: “A recrawl of a known ページ.” 暫定日本語案: — クロール Stats report. 暫定日本語案: From a JavaScript-rendered help-center ページ; confirm the phrasing on the live ページ before treating it as final.

暫定日本語案: Google 検索 Central docs — breadcrumbs and hierarchy

• 暫定日本語案: “A breadcrumb trail on a ページ indicates the ページ’s position in the サイト hierarchy, and it may help users understand and explore a サイト effectively.” 暫定日本語案: — Breadcrumb (BreadcrumbList) structured データ. 暫定日本語案: The ページ uses JS-rendered tabs; confirm the deep-linked passage resolves on the live ページ.

暫定日本語案: Nielsen Norman Group — the UX-research counterweight (category distinctness)

• 暫定日本語案: “Flat hierarchies tend to work well if you have distinct, recognizable categories, because people don’t have to click through as many levels.”
• 暫定日本語案: “Categories that are specific and do not overlap are the easiest to understand.”
• 暫定日本語案: “Like most design questions, there’s no single right answer, and going too far to either extreme will backfire.” 暫定日本語案: — Kathryn Whitenton, Flat vs. Deep ウェブサイト Hierarchies, Nielsen Norman Group. 暫定日本語案: Not a 検索-engine source — cited as the strongest available UX research on tying depth to category distinctness and findability, which the SEO-only guidance tends to miss.

暫定日本語案: Depth decision & audit checklist

暫定日本語案: Work it top to bottom — decide the target first, then measure, then fix:

• 暫定日本語案: [ ] Sized the サイト. You know roughly how many ページ need their own findable 暫定日本語案: URL (the first branch of the decision tree).
• 暫定日本語案: [ ] Judged category distinctness. You know whether your natural categories are 暫定日本語案: distinct (can stay flatter) or overlapping (need hubs / cross-リンク).
• 暫定日本語案: [ ] Set a target. Priority ページ have an explicit click-depth target (~3 暫定日本語案: clicks for most sites; 3–4 for large catalogs).
• 暫定日本語案: [ ] Crawled for the click-depth distribution. You’ve run Ahrefs サイト Audit or 暫定日本語案: Screaming Frog and know what % of ページ sit at depth 1 / 2 / 3 / 4+.
• 暫定日本語案: [ ] Cross-referenced GSC クロール Stats. You’ve checked Discovery vs. Refresh and 暫定日本語案: response patterns for what Google is actually クロール.
• 暫定日本語案: [ ] Located the depth cliff. You’ve identified the depth level where クロール 暫定日本語案: frequency/coverage drops off — your measured “too deep,” not a generic number.
• 暫定日本語案: [ ] Priority ページ are shallow. No money ページ is buried 5–6 clicks deep with 暫定日本語案: no hub linking to it.
• 暫定日本語案: [ ] No mega-menu over-flattening. A large catalog isn’t dumped into one 暫定日本語案: navigation surface (grouping signals intact).
• 暫定日本語案: [ ] Hub ページ in place. Buried priority segments have a shallow hub/collection 暫定日本語案: ページ linking straight to them.
• 暫定日本語案: [ ] Breadcrumbs present with BreadcrumbList structured データ.
• 暫定日本語案: [ ] Pagination isn’t the only path to priority items that fall on ページ 4+ of a 暫定日本語案: listing.
• 暫定日本語案: [ ] You didn’t “fix” depth by rewriting URLs. Click depth was shortened by 暫定日本語案: linking closer, not by flattening the URL path.

暫定日本語案: The mental models

暫定日本語案: 1. Depth is a dial set by two inputs. 暫定日本語案: Turn it based on (a) how many findable ページ you have and (b) how distinct your 暫定日本語案: categories are. Small + distinct → flat. Huge + overlapping → hierarchy plus hubs. 暫定日本語案: Everything else is between.

暫定日本語案: 2. Only Bing gives you a number. 暫定日本語案: Bing’s ~3-click target is the one hard figure either engine states; Google 暫定日本語案: deliberately talks リンク-graph proximity, not level counts. Treat competitor “2–3 暫定日本語案: levels / 3 clicks” numbers as industry consensus, not law.

暫定日本語案: 3. Measure the cliff, don’t assume the number. 暫定日本語案: “Too deep” isn’t a universal constant. クロール for your depth distribution, overlay 暫定日本語案: GSC クロール Stats, and find the depth where クロール actually falls off. That’s your 暫定日本語案: サイト’s “too deep.”

暫定日本語案: 4. Fix with リンク, not URLs. 暫定日本語案: URL-folder depth ≠ click depth. To pull a ページ shallower, リンク it from a hub closer 暫定日本語案: to the homepage. Rewriting its URL flatter changes nothing.

暫定日本語案: 5. Hub ページ first. 暫定日本語案: Of every remediation, adding or strengthening a mid-level hub ページ is the highest 暫定日本語案: ROI — it can drop a batch of buried items from six clicks to three at once, with no 暫定日本語案: URL changes.

暫定日本語案: 6. Depth is a risk factor, not a penalty. 暫定日本語案: A deep ページ with strong external リンク or in a fresh, well-organized directory can 暫定日本語案: クロール fine. Depth raises risk; it doesn’t guarantee harm. The measurement, not the 暫定日本語案: number, tells you whether it’s actually a problem.

暫定日本語案: Worked example: pulling a 商品 from 6 clicks to 3

暫定日本語案: Before — 6 clicks deep

暫定日本語案: The 商品 is a priority item, but a クローラー has to traverse a deep, paginated 暫定日本語案: listing to reach it — so it’s recrawled rarely and inherits little internal 暫定日本語案: importance.

暫定日本語案: After — 3 clicks deep

暫定日本語案: What changed: one new hub ページ, linked from the homepage or main nav, that 暫定日本語案: リンク directly to the 商品 (and its peer priority items). The 商品’s URL 暫定日本語案: never changed — it can still be /footwear/running/trail/model-x/. That’s the 暫定日本語案: whole point of the URL-depth-vs-click-depth distinction: the fix is a shallow リンク 暫定日本語案: path, not a URL rewrite. One hub ページ can do this for an entire batch of buried 暫定日本語案: priority items simultaneously.

暫定日本語案: Reading a depth distribution

暫定日本語案: A クロール of a mid-size サイト might come back like this:

暫定日本語案: The number that matters isn’t “15% at depth 5+” in the abstract — it’s which 暫定日本語案: ページ are in that bucket. Cross-reference GSC クロール Stats: if those deep ページ show 暫定日本語案: little Refresh クロール and you care about them, that’s your worklist for hub ページ. 暫定日本語案: If they’re low-value tail コンテンツ クロール fine, leave them alone — depth is a risk 暫定日本語案: factor, not an automatic problem.

暫定日本語案: Forcing every ページ to depth one

暫定日本語案: A homepage or mega-menu that リンク to everything creates a low depth number but no 暫定日本語案: useful hierarchy. Keep the highest-value sections prominent, then use category and hub 暫定日本語案: ページ to provide clear paths through the rest of the inventory.

暫定日本語案: Adding categories that do not help anyone choose

暫定日本語案: Extra layers are not automatically organization. A subcategory with one child, vague 暫定日本語案: labels, or heavy overlap makes users guess and adds clicks without narrowing the task. 暫定日本語案: Merge weak layers or redesign the taxonomy around real distinctions.

暫定日本語案: Treating URL-folder depth as architecture depth

暫定日本語案: Moving /shop/shoes/trail/ to /trail/ does not make the ページ easier to discover if 暫定日本語案: the same リンク still lead to it. Measure リンク paths and change URLs only when there is 暫定日本語案: a separate information-architecture or migration reason.

暫定日本語案: Using the sitewide average as the decision

暫定日本語案: A pleasant average can hide a buried revenue template and a pile of shallow low-value 暫定日本語案: ページ. Segment depth by template, importance, indexability, and organic role before 暫定日本語案: deciding whether the architecture is too flat or too deep.

暫定日本語案: Removing hierarchy instead of strengthening hubs

暫定日本語案: When a deep section underperforms, deleting category levels can create a リンク dump. 暫定日本語案: First test whether better hub コンテンツ, contextual modules, pagination, and cross-リンク 暫定日本語案: can shorten important paths while preserving useful grouping.

暫定日本語案: The クロール looks flat but important ページ are still hard to find

暫定日本語案: Symptom: median depth is low, yet priority ページ remain buried. Likely cause: 暫定日本語案: navigation favors many low-value URLs or the average hides template differences. 暫定日本語案: Fix: join depth to a priority list, inspect shortest paths for those ページ, and 暫定日本語案: move リンク from generic sitewide clutter into relevant shallow hubs.

暫定日本語案: A new category layer caused クロール or traffic losses

暫定日本語案: Symptom: child ページ moved deeper and パフォーマンス fell after taxonomy expansion. 暫定日本語案: Likely cause: the new parent is itself hard to reach, リンク were removed, or old 暫定日本語案: URLs redirect through extra hops. Fix: compare before/after リンク paths, repair 暫定日本語案: navigation and redirects, and keep the layer only if it improves real grouping.

暫定日本語案: Flattening created an unusable navigation wall

暫定日本語案: Symptom: the menu contains hundreds of choices and engagement suffers. Likely 暫定日本語案: cause: depth reduction was implemented as sitewide リンク instead of better paths. 暫定日本語案: Fix: restore scannable categories, expose the most important destinations, and use 暫定日本語案: contextual リンク or related modules for the long tail.

暫定日本語案: The architecture is different for crawlers and users

暫定日本語案: Symptom: a rendered user can navigate to ページ a raw クローラー cannot discover. 暫定日本語案: Likely cause: client-only controls, hidden states, or リンク without usable href 暫定日本語案: values. Fix: use crawlable anchors for destinations and rerun the graph in the 暫定日本語案: rendering mode appropriate to the production implementation.

暫定日本語案: Prompt: evaluate a proposed hierarchy

Evaluate this proposed site hierarchy without applying a universal click-depth rule.
For each template and priority group, identify the shortest expected path from the
homepage, the parent that gives the path meaning, and any layer that has too few,
too many, or overlapping children. Flag mega-menu flattening, single-child categories,
and priority pages that are less prominent than comparable pages. Recommend changes
using only the supplied inventory and business priorities; do not invent categories.

Inventory:
[PASTE URL | TEMPLATE | PROPOSED PARENT | PRIORITY | PRIMARY USER TASK]

暫定日本語案: Prompt: interpret a クロール-depth distribution

Analyze this crawl export by template and business priority. Compare depth distribution,
orphan status, and shortest-path source. Find cases where the sitewide average hides a
buried important group or where many low-value links make the graph artificially flat.
Return evidence rows, likely architecture cause, and the smallest link or hub change to
test. Treat URL slashes as descriptive data, not click depth.

Crawl export:
[PASTE URL | TEMPLATE | DEPTH | SHORTEST-PATH SOURCE | INDEXABILITY | PRIORITY]

暫定日本語案: Validate an architecture-depth change

暫定日本語案: Test yourself: Flat vs. Deep Architecture

暫定日本語案: Five quick questions on deciding, measuring, and fixing サイト depth. Pick an answer 暫定日本語案: for each, then check.

暫定日本語案: Resources worth your time

暫定日本語案: My related writing

• 暫定日本語案: When Should You Worry About クロール Budget? — when depth actually starts to hurt クロール, and why most sites don’t need to obsess over it.
• 暫定日本語案: Internal リンク for SEO: An Actionable Guide — how hub ページ and internal リンク shape the リンク graph that is your architecture.
• 暫定日本語案: How to Structure Your ウェブサイト Architecture for SEO — the broader structure walkthrough this depth framework fits inside.

暫定日本語案: My speaking

• 暫定日本語案: How 検索 Works (SlideShare) — my walkthrough of クロール, rendering, インデックス登録, and ranking — the pipeline that click depth feeds into. (Standing disclaimer applies: this is my understanding of these systems, not an official spec.)

暫定日本語案: From around the industry

• 暫定日本語案: Flat vs. Deep ウェブサイト Hierarchies (Kathryn Whitenton, Nielsen Norman Group) — the rigorous UX-research take tying depth to category distinctness and findability.
• 暫定日本語案: Why Google Recommends Hierarchical サイト Structure For SEO (検索エンジン Journal) — Illyes on why large sites need hierarchy and how directory grouping helps クロール.
• 暫定日本語案: クロール Stats report (Google 検索 Console Help) — the Discovery vs. Refresh breakdown behind the depth-cliff diagnosis.
• 暫定日本語案: How To Audit クロール Depth & Improve クロール Efficiency (Sitebulb) — a hands-on クロール-depth audit walkthrough.
• 暫定日本語案: Structure Explorer (Ahrefs Academy) — using サイト Audit to see your click-depth distribution.
• 暫定日本語案: サイト Architecture & クロール Visualisations (Screaming Frog) — visualizing クロール depth and structure from a クロール.

変更履歴