Site structure that still works at a thousand pages

13 August 2026 · Structure

Nearly every structure works at forty pages. The interesting question is what happens at four hundred, when the menu can no longer list everything and whoever invented the categories has moved on.

The menu is not the structure

A navigation menu is a shortcut to the handful of places most people want. The structure is the full set of paths by which any page can be reached, and most of it lives in index pages, listings and links inside body copy. Sites fail at scale because they try to express the whole structure in the menu, which either becomes an unusable multi-level tree or quietly stops covering most of the site.

Sections earn their existence

A section is worth creating when three things are true: enough pages belong in it that a reader benefits from the grouping, the grouping matches a distinction readers already make, and the section index has something to say beyond a list of links. Sections created because a category field required a value produce archives with two entries and no purpose.

The reverse failure is a flat pile: two hundred articles in one undifferentiated stream, where the only way to find anything is chronology or a search box. Chronology is fine for recent things and useless for reference material.

Index pages carry the weight

A good index page is a page, not a directory listing. It states what the section covers, orders its entries by something meaningful, and says a line about each so that choosing between two similar titles is possible. It is also the natural landing point for broad queries, which a bare list of links never satisfies.

Depth, and the number that matters

Count clicks from the homepage to your least reachable page. If the answer is more than four for anything you care about, the structure is doing badly regardless of how tidy the diagram looks. Depth accumulates in paginated archives: page fourteen of a listing is fourteen steps from anywhere, and the pages only reachable from it inherit that distance.

Addresses are part of the structure

Paths that describe the hierarchy, in lowercase, with hyphens between words and no parameters, remain readable in a link, in a log file and in a results listing. They also make the structure legible to you when you later have to audit it. Avoid encoding volatile facts in a path: dates, years and campaign names become wrong, and changing them means either a stale address or another redirect to maintain.

Test the structure by asking questions of it

Write down eight questions a reader might arrive with. Then, starting from the homepage, try to reach the answer to each without using the search box. The failures are your structural work list, and they are usually specific: one missing index, one section that should be two, one article that nothing links to.

Permalink: /notes/site-structure-that-holds-up/