Site architecture covers the hierarchy of pages, the URL structure, the navigation and the internal links between pages. A clear architecture lets visitors find what they need, lets crawlers reach every important page in a few clicks, and signals which pages matter most by how often and how prominently they are linked. For SaaS companies, it also means deciding how the marketing site, blog, docs and app fit together.
What good structure looks like
The aim is that both a new visitor and a crawler can understand the site from its navigation alone.
- A shallow hierarchy where important pages are reachable within a few clicks of the homepage
- Logical groupings (product, solutions, integrations, resources, docs) that match how buyers think
- Hub pages that link to every page in their group, and pages that link back up and sideways
- Readable, stable URLs that reflect the hierarchy without being overly deep
- Breadcrumbs on deep sections
Subdomains versus subfolders
SaaS sites often split content across subdomains: blog.example.com, docs.example.com, app.example.com. Google has said it can handle either setup and does not treat subdomains as a ranking problem by default. In practice, subfolders keep content on one host, which is simpler for internal linking, one robots.txt and one Search Console property, and many SEOs prefer them for content meant to rank. Subdomains are reasonable when a separate platform or team genuinely requires it.
Whichever you pick, link heavily between the properties. A blog that links to the product, and docs that link to relevant feature pages, keep the whole site connected.
Architecture for programmatic pages
Programmatic sets, such as integrations, templates, use cases or comparisons, need their own hubs. Without them, hundreds of pages hang off the sitemap with no internal links. A hub per set, category pages where the set is large, and cross-links between related pages (for example, integrations in the same category) give each page a path and context.
example.com/
product/ (features hub)
integrations/ (hub, linked from main nav)
crm/ (category page)
salesforce/
hubspot/
compare/ (comparison hub)
blog/
docs/ (or docs.example.com, cross-linked)Planning changes
Restructuring changes URLs, so it needs a redirect map, updated internal links and sitemaps, and monitoring afterward. Plan the target structure from keyword and buyer research first, then map existing pages into it.
Example
Solutions pages nobody could reach
A fictional customer success platform, Retainly, built twenty industry solution pages, linked only from a dropdown that rendered on hover with JavaScript. Most visitors and crawlers never found them.
Adding a Solutions hub in the main navigation with plain links to each industry, and linking each solution page from relevant blog posts and case studies, gives every page several crawlable paths.
Common mistakes
Mirroring the org chart
Structure by how buyers look for things, not by which team owns which pages.
Changing URLs for cosmetic reasons
Every URL change costs redirects and a period of recrawling. Only restructure when the benefit is clear.
Questions
There is no official limit. As a rule of thumb, important pages should be a few clicks away, and anything buried deep tends to be crawled less and linked less.
Either can work. Subfolders are simpler to manage for SEO; subdomains are fine if the docs platform requires it, as long as you cross-link and set up each property properly.
