Site architecture is the way a website’s pages are organised and connected: the hierarchy of sections, the URLs, the menus and the internal links that lead from the homepage to every other page. Good architecture lets visitors and search engines reach any important page quickly and see how pages relate to each other.
How site architecture works
Most sites are built as a hierarchy. The homepage sits at the top, main sections (services, products, locations, resources) sit below it, and individual pages sit below those. Navigation and links join each level, and URLs often mirror the structure, as in /services/boiler-repair/.
Search engines find pages mainly by following links. Pages reachable in a few clicks from the homepage tend to be crawled more often and treated as more important; pages buried deep, or reachable only through site search, may be crawled rarely. The number of clicks needed is the page’s click depth. A flat architecture, with most pages within three or four clicks of the homepage, is the usual aim, though not to the point of linking everything from the homepage.
Several elements work together: the main navigation, which signals the most important sections; breadcrumbs, which show where a page sits; category and hub pages, which group related content; contextual internal links in body copy; the URL structure; and the XML sitemap, which lists pages but cannot replace links.
Why it matters
Architecture shapes how authority flows. Links from the homepage and main menu carry weight, and the way you link onward from there decides which pages benefit. It also shapes what search engines think each section is about, and whether two pages end up competing for the same searches.
For visitors, a clear structure answers two questions: where am I, and where can I go next? A London restaurant group needs each venue easy to reach from the homepage. An online shop needs categories that match how people browse, not how stock is held in the warehouse. A service business covering several towns needs a location structure that does not create near-identical pages for every postcode.
Architecture is also the hardest thing to change after launch, because changing it usually means new URLs and redirects. Getting it right before a build or redesign costs far less than fixing it afterwards.
Common mistakes
- Orphan pages with no internal links pointing to them, often old landing pages or posts dropped from menus.
- Important pages buried five or more clicks deep, such as products reachable only through long paginated categories.
- Faceted filters on a shop generating thousands of crawlable URL combinations.
- Menus built around company structure or jargon rather than customer needs.
- Several pages covering the same topic in different sections, splitting relevance between them.
- Redesigns that change every URL without a redirect plan.
How to act on it
Crawl your site with a tool such as Screaming Frog or Sitebulb and look at click depth, orphan pages and how internal links are spread. Compare the pages that receive the most internal links with the pages that matter most to your business; they should largely be the same. Sketch the ideal structure as a tree, starting from your services or product categories and the way customers search, then map every existing URL to a place in it.
Fix what you can with links first: add contextual links to buried pages, link hubs to their children and back, and add breadcrumbs. Change URLs only when the benefit is clear, and always with redirects. Auditing and reshaping site structure, including planning it before a new build, is part of my technical SEO service.