Skip to content
Strynal, Digital Agency

AI Visibility 5 min read

URL Structure and Site Hierarchy for SEO

How to design URLs and site architecture so search engines crawl efficiently, understand your content model, and surface the right pages for every query.

By Strynal Team

Crawlers don’t experience a site the way a user does. They follow links, track depth, and build a map from the signals you give them. The URL you assign a page and its position in the site tree are two of those signals. Design them poorly and you dilute crawl budget on pages that don’t matter, bury the pages that do, and make the site harder for engines to understand.

What search engines infer from a URL

A URL is a machine-readable sentence. Crawlers parse the path segments before they even read the page, using them to guess topic, format, and whether the content fits the site’s declared scope.

A few practical implications:

  • Include the primary keyword. /services/seo-audit beats /services/page-23. The keyword in the path is a weak but real signal, and it appears as a bolded match in SERPs when the query term hits it.
  • Keep paths short. Three to four segments is the practical ceiling for most pages. Each additional segment dilutes the path-level signal and pushes the page further from the root.
  • Use hyphens, not underscores. Crawlers treat hyphens as word separators. Underscores can fuse tokens and obscure the intended terms.
  • Lowercase only. Mixed-case paths create duplicate-content risk when servers treat /Blog/Post-Title and /blog/post-title as the same URL but HTTP responses differ on casing.

Consistency matters more than perfection. A coherent pattern applied across thousands of pages is more valuable than an optimal pattern applied to a handful and abandoned elsewhere.

Site hierarchy: the map engines follow

URL paths reflect hierarchy, but hierarchy is an architectural choice that predates any individual URL. Get it right at the design stage and the URL problem largely solves itself.

A well-structured site has:

  1. A root domain covering the site’s primary purpose.
  2. A shallow set of top-level directories for the main content categories (/blog, /services, /work, /about).
  3. Most commercial content at or close to the second level, so crawlers reach it quickly from the root.

The deeper a page sits from the root, the less crawl equity it receives by default. A product page at /shop/category/subcategory/product-name has four levels to traverse before a crawler reaches it, against one for /shop/product-name. You can compensate with internal linking, but structure is cheaper than patching bad structure.

Hierarchy is a promise to the crawler: this is how importance distributes across the site. Every unnecessary level of depth signals that the content at that level matters a bit less.

For content clusters, the hierarchy should mirror topical relationships. If /blog/technical-seo-checklist is your cornerstone, all supporting posts should link back to it and ideally live in the same directory. The structure Google’s documentation and years of practitioner work both point toward is the same: a clear parent, clear children, and clean links between them.

Crawl budget and how structure spends it

Crawl budget is the number of pages a crawler will fetch from your site in a given period. Large sites run into this limit regularly. Smaller sites often don’t hit it, but the concept still matters: budget wasted on low-value pages is budget not spent on pages that need to be found and ranked.

Common budget drains:

  • Faceted navigation. Filter combinations on e-commerce sites generate thousands of URL variants. A product grid filtered by colour, size, and brand simultaneously creates a combinatorial explosion. Block these in robots.txt or use canonical tags to collapse duplicates.
  • Session IDs and tracking parameters. If URLs change by session or UTM combination without canonical tags, the crawler sees thousands of pages that are really one. Every version consumes budget.
  • Orphaned pages. Pages with no inbound internal links are hard for crawlers to find. Run a crawl and eliminate or link up anything sitting alone.
  • Soft 404 pages. Pages that return HTTP 200 but show “no results” consume crawl budget and signal low quality. Return proper 404 or 410 status codes, or redirect to a page with real content.

The full checklist of technical issues worth auditing before any other SEO work is in the technical SEO checklist.

Naming conventions that help on-page signals too

URL path choices intersect with on-page optimisation. The slug you pick feeds into the page title pattern, breadcrumb labels, and the og:url tag. When all four say the same thing, the signal is coherent. When the URL says /services/page-7 and the title says “Enterprise SEO Consulting,” you’ve created ambiguity that on-page content alone cannot fully resolve.

This is one reason it pays to think about URL conventions when you’re still deciding what pages exist, not after the site is live. Changing a URL after indexing requires a redirect, and while a permanent redirect passes link equity, it adds a step in the chain and a record in your redirect table you’ll maintain indefinitely.

Slug formatting also affects how content clusters hold together. A post at /blog/seo-for-saas clearly belongs to the blog; a post at /articles/2024/march/q1-update-post-4 is ambiguous about topic and permanence. Clear, keyword-accurate slugs make the cluster structure legible to both crawlers and readers.

For a complete treatment of the on-page variables that complement URL structure, the on-page SEO guide covers title tags, heading structure, and internal linking.

How Strynal approaches URL structure and site hierarchy

URL structure is a decision made early and lived with for years. We treat it as part of the information architecture conversation, before a page is built, not after migration becomes unavoidable.

On new projects, we map the directory structure against the content strategy: which pages are commercial, which are editorial, how the cluster hierarchy should distribute equity. From there we write a URL convention document covering slug formatting, parameter handling, and the rules for new content types. Everyone adding pages later works from the same pattern.

On existing sites, we audit the current structure for depth problems, duplicate paths, and crawl-budget drains, then propose a migration plan that preserves earned equity while reducing structural debt.

Both tracks feed into the broader work of making a site readable to engines and AI systems alike. Clean URL structure is foundational to that. It’s where our AI visibility practice starts: structure, markup, and content working together so the right pages get found, understood, and cited. A coherent site hierarchy is the base everything else builds on.