Site architecture for a growing site, decided early

Aug 29
3 min read

Updated: 2 days ago

Introduction

A site launches with twelve pages arranged sensibly. Two years later it has ninety, added one at a time by whoever needed them, and nobody can explain why some services sit under a category and others sit at the top level.

Nothing was decided badly. Nothing was decided at all. Architecture is what a site ends up with when each page is placed individually, and the cost appears later as pages nobody can find, sections that compete with each other, and a menu that has to list everything because the structure explains nothing.

1. Site architecture for a growing site is about where the next page goes

Frame it as a rule rather than a diagram.

The useful output is not a chart of the current site but a decision about where a new service, a new location or a new article belongs when it arrives. If that question has an obvious answer, the architecture is working; if it produces a discussion every time, it is not.

2. Group by how customers think, not by how you are organised

The most common structural error.

Departments, internal terminology and historical divisions make sense to staff and mean nothing to visitors. Group pages by the problem somebody has or the outcome they want, because that is what they arrive knowing, and it survives internal reorganisation as well.

3. Keep the hierarchy shallow

Depth costs discovery.

Aim for anything important to be two clicks from the home page and no more than three. Deep structures bury pages from both visitors and crawlers, and they tend to grow deeper over time rather than shallower, so the starting point matters.

4. Make each level genuinely distinct

Overlapping categories create the confusion.

If a page could reasonably sit in two sections, the sections are not properly separated. That ambiguity produces duplicate pages, inconsistent placement and a menu where nobody can predict where anything lives, and it compounds with every addition.

5. Plan for the sections that will grow

Anticipate rather than react.

Services, locations and articles all expand. Deciding now how a section will behave at fifty pages rather than five prevents the restructure that becomes necessary at the worst possible moment, usually just after a busy period.

6. Use a central page for each major topic

The pattern that scales.

A main page covering a subject thoroughly, with supporting pages linked from it and back to it, concentrates authority and gives new content an obvious home. It also makes clear which page should rank for the broad term and which for the specific ones.

7. Let the address structure reflect the hierarchy

Consistency helps more than optimisation.

Paths that mirror the structure make the site easier to understand, easier to report on and easier to restructure later. This matters more for your own comprehension than for search, which is reason enough to be consistent about it.

8. Review what the menu says about priority

The menu is the architecture visitors experience.

If your most valuable service is buried while a rarely visited page occupies prime position, the structure is working against the business. Check this against actual revenue rather than against internal enthusiasm.

9. Restructure deliberately, not gradually

Half-completed reorganisations are the worst outcome.

If the structure genuinely needs changing, plan the redirects, update the internal links and do it in one piece. Sites carrying two competing structures because a reorganisation stalled are harder to work with than either structure alone would have been.

Write the rules down where whoever adds pages will see them. Most architectural decay is not disagreement but ignorance of the existing convention, and a short document naming where each type of page belongs prevents years of accumulated inconsistency at essentially no cost.

Conclusion

Treat architecture as a rule for placing the next page rather than as a diagram of the current site.

Group content by how customers think rather than by how the company is organised, keep important pages within two or three clicks of the home page, make categories genuinely distinct so nothing could sit in two of them, plan for the sections that will grow before they do, build a central page for each major topic with supporting pages linked around it, keep addresses consistent with the hierarchy, check the menu against what actually earns, restructure in one deliberate piece rather than gradually, and write the convention down for whoever adds pages next.