Site architecture and internal linking for SaaS marketing sites

Run a crawl of your site and export internal link counts per URL. On most B2B software sites, the top ten by inbound internal links are the homepage, the blog index, the pricing page, and seven navigation items. The pages that produce pipeline are somewhere below 200 with four links each.

That distribution is not an accident. It is what happens when the only internal links on a site come from global navigation and a “related posts” widget.

What internal links are doing

Two things, and they are different.

They distribute authority. A page with links from thirty relevant internal pages is being told, structurally, that it matters. This is the part people mean when they talk about internal linking for SEO.

They also define what a page is about, through anchor text and the context around the link. Twenty articles about keyword research linking to your keyword tool page with descriptive anchors is a strong topical signal, distinct from the authority effect.

Most sites do neither deliberately.

The shape that works

The structure that has worked consistently on SaaS marketing sites is three tiers with explicit routing between them.

At the top, your commercial pages: category page, product pages, use-case pages, vertical pages, comparison and alternative pages, pricing. These are the destinations. They should receive links, not send many.

In the middle, topic hubs. Substantial pages covering a theme comprehensively, linking down to supporting content and across to the commercial pages the theme relates to. Three to six of these for a typical company, not thirty.

At the bottom, supporting content. Individual articles, each linking up to its hub, across to one or two siblings, and into the specific commercial page it exists to support.

The routing rule we apply: every supporting article must contain at least one contextual link to a commercial page with descriptive anchor text, and that link should appear in the body rather than in a call-out box at the end. Links inside prose carry more weight and get clicked more.

URL structure, and the parts that are expensive to change

Some decisions here are cheap to revisit and some will cost you a migration.

Flat versus nested is mostly cosmetic. /blog/post-name/ versus /blog/category/post-name/ makes little difference to rankings and a large difference to how painful it is when a post changes category. We default to flat for blog content and nested for product and service pages where the hierarchy is stable.

Trailing slashes matter only in that you must pick one and enforce it with a redirect. Serving both is a duplicate content problem that is trivially avoidable and appears on maybe a third of sites we audit.

Dates in URLs are a mistake for evergreen B2B content. They advertise age and they make refreshes look dishonest or require a redirect.

Subdomain versus subdirectory for docs, blog, and help centre is the expensive one. Subdirectories consolidate authority onto one domain and are generally the better choice, and moving an established docs subdomain into a subdirectory is a serious project with real risk. If you are early enough to choose, choose subdirectories. If you already have subdomains and things are otherwise working, I would not do this migration purely for SEO.

Language and region paths need deciding before you have any international content, because retrofitting hreflang onto a site that grew organically is genuinely miserable.

Navigation, and the trade-off nobody talks about

Every link in your global navigation appears on every page, which distributes authority widely and thinly. Adding twelve items to a mega menu does dilute what each one receives.

But navigation exists for humans, and a menu optimised for link equity distribution at the expense of usability is a bad trade. Conversion rate beats crawl efficiency every time.

The reasonable compromise is to keep the global navigation clean and human, and to build the depth through contextual links in content and through hub pages that are themselves linked from the navigation. A “Solutions” nav item pointing to a solutions hub, which links to twenty vertical pages, works better than twenty items in a dropdown.

Orphans and near-orphans

An orphan page has no internal links pointing at it. On a SaaS site these are usually landing pages built for a campaign, old product pages from a repositioning, and programmatic sets that were shipped with only a sitemap entry.

Near-orphans are more common and harder to spot: pages with one or two links, both from a paginated archive on page seven. Functionally similar.

Both are found by comparing your sitemap against your crawl. Every page in the sitemap with fewer than three internal links either needs links or should not be in the sitemap. That reconciliation is a twenty-minute job and it consistently surfaces things nobody knew were live.

Pagination and archives

Blog archives, category listings, and tag pages generate a lot of low-value URLs and absorb crawl attention. Tag pages in particular are usually a net negative on B2B sites — they duplicate category pages, rank for nothing, and exist because the CMS created them by default.

Our default is: category pages indexable if they have unique introductory content and more than about eight posts, paginated pages indexable but with self-referential canonicals, tag pages noindexed unless someone can articulate what they are for.

Measuring whether any of this worked

Before and after a restructuring, track three things: internal links received by each priority commercial page, crawl frequency of those pages from server logs, and their impressions in Search Console.

Crawl frequency usually moves first, within two to three weeks. Impressions follow over six to twelve. If crawl frequency does not move at all, the links you added are not being followed, which usually means they are rendered client-side or buried in a component that loads on interaction.