Marketing
Internal Linking for SaaS: Beyond 'Related Posts'
Internal linking SaaS teams actually need (not the 'related posts' widget)
The best internal linking strategy for a SaaS site is a hub-and-spoke cluster where every spoke article links up to its pillar, sideways to 2-4 sibling articles, and down to the product or feature page that sells the topic. Not a "related posts" sidebar. Not a footer link dump. A deliberate graph that tells Google which page is the canonical answer for a topic, and tells the reader where to convert.
Most SaaS blogs do not do this. According to Common Ground's audit data, around 82% of internal linking opportunities are missed across the sites they review. That number tracks with what we see in Gravidy audits. The blog has 80 posts, the product has 12 feature pages, and the only thing connecting them is a navbar.
This guide is the model we use when we rebuild internal linking for a SaaS client. It assumes you already have content. It assumes you want rankings and conversions, not one or the other.
Why 'related posts' widgets quietly hurt you
Most CMS-generated "related posts" modules pick siblings by tag overlap or recency. That is not a topical relationship. It is a string match.
Three problems compound:
The same 5-10 high-authority posts get linked from everywhere, while your conversion-relevant pages stay orphaned.
Anchor text is the post title, every time. You teach Google nothing about why the link exists.
The widget sits below the fold. Google still crawls it, but contextually it is weaker than an in-body link, and users almost never click it.
If you turn the widget off tomorrow, your rankings will not move. That alone tells you it is doing nothing for you.
The pattern that works: pillar, cluster, product page
The architecture has three layers. We covered the foundation in topic cluster architecture for SaaS, so here we focus on the linking rules inside it.
Pillar page. One per major topic. Long, definitional, links down to every spoke in the cluster.
Spoke articles. Specific, intent-matched. Each spoke must link: - Up to its pillar with descriptive anchor text (not "click here", not the post title verbatim) - Sideways to 2-4 siblings in the same cluster - Down to the relevant product or feature page, in-body, near the section where the reader's intent peaks - Out to one or two adjacent clusters when topics genuinely overlap
Product or feature page. Receives the conversion-intent traffic. Should also link back up to the pillar so the loop closes. Most SaaS teams forget this last step, which is why their feature pages never accumulate topical authority.
The product-page integration is the part competitor guides skim over. Backlinko, Ahrefs and Semrush write about cluster topology in the abstract. They rarely show how to wire /blog/reduce-churn-with-onboarding-emails to /features/lifecycle-emails without it reading like an ad.
The trick: link from the section that names the problem, not the section that names the solution. If you link from the solution paragraph, the reader has already taken the value and bounces. If you link from the problem paragraph, the reader is still confused, and the product page is the answer.
How many internal links per page is right?
There is no hard cap. Google removed the explicit "100 links per page" guideline years ago, and as LinkStorm notes, Google's current Search Essentials guide replaced it with a reminder to keep links crawlable rather than a number.
That said, you still need a working heuristic. Straight North's review of practitioner guidance lands on 2-4 internal links per 500 words of body content. We use a similar floor on Gravidy projects, with three rules layered on top:
Every internal link must answer a question the reader is about to ask in the next paragraph. If it does not, cut it.
Never link to the same destination twice in one article. Google ignores the second one and the reader feels cluttered.
The first link to your highest-converting page should appear above the fold of the article body, not in the conclusion.
A 1,500-word spoke article ends up with 6-12 internal links by this method. Roughly half point sideways to siblings, a third point up or down the cluster, and one or two go out to adjacent clusters or the homepage.
If your post has more than 15 internal links, you are not linking, you are name-dropping. Cut the weakest half.
Anchor text rules that actually move rankings
Anchor text is the cheapest ranking signal you have direct control over, and most SaaS teams waste it.
The default failure modes:
Linking with the post title every time (low specificity, bad for both reader and Google)
Generic anchors ("learn more", "this guide", "read here")
Exact-match keyword stuffing on every internal link to the same target (looks manipulative when scaled)
Anchors that do not match what the destination page is actually about
Use this hierarchy instead. Vary across the four types so no single page accumulates only one anchor pattern:
Descriptive phrase anchors. "How we structure SaaS topic clusters" pointing at a cluster pillar. Best default.
Branded anchors. "Gravidy's audit checklist" when linking to your own asset.
Partial-match anchors. "internal linking strategy" inside a sentence, not as the full anchor scope.
Long-tail question anchors. "what counts as duplicate content" pointing at a post that answers exactly that.
Avoid exact-match anchors that read like ad copy. "Best SEO agency for SaaS" linked 40 times across your blog is a flag, not a signal.
What we find in real SaaS internal-link audits
Three patterns show up in nearly every SaaS audit we run, regardless of stack or vertical.
Orphan product pages. The pricing page gets links from the navbar and nothing else. Feature pages get one link from the homepage and zero from the blog. The blog meanwhile has hundreds of internal links flowing between articles. Google ranks what your site links to, and your site is loudly telling Google that your blog is more important than your product.
Top-heavy clusters. Pillar pages link down to spokes. Spokes do not link back up. Result: pillar authority leaks out and never recovers, and the pillar slides on rankings month over month.
The same five "winner" articles getting all the love. Whichever five posts ranked first become the only ones linked, which compounds their authority while every other post starves. PageRank is a flow, not a balance sheet, and lopsided distribution kills your long-tail coverage. We covered this dynamic in why 70% of B2B blog content never ranks.
The fix for all three is mechanical, not creative. Pull a crawl, export the inlinks-per-URL table, sort ascending, and you will see the orphans on page one of the report. From there it is a half-day of editorial work to add 5-15 contextual links per orphan from existing posts.
Putting it into a workflow your team can actually run
The reason internal linking decays is that nobody owns it after the launch sprint. Build the workflow into content production, not into a quarterly audit:
When publishing a new post, update at least three older posts to link to it with varied anchors
When updating an old post, check it links to the most recent two posts in its cluster
When launching a new product feature, audit the top-10 ranking posts in the relevant cluster and add a contextual link to the feature page from the problem paragraph
When sunsetting a post, redirect it and rewrite the inlinks rather than letting them 404
This works because every editorial action triggers an internal-linking obligation. It does not require a separate "internal linking sprint" that gets deprioritized in week two. The same logic that makes content production sustainable, covered in content is king, but context rules, applies here.
Frequently Asked Questions
How many internal links per page should a SaaS blog post have?
Aim for 2-4 internal links per 500 words of body copy, which works out to 6-12 links for a typical 1,500-word post. There is no hard upper limit from Google, but past about 15 links per page the marginal value drops and reader experience degrades.
What is the best anchor text for internal links?
Use descriptive phrase anchors that summarise what the destination covers, not the destination's title and not generic phrases like "learn more". Vary anchor types (descriptive, partial-match, branded, question) across links to the same page so no single pattern dominates.
What is the best internal linking strategy for SaaS?
Build hub-and-spoke clusters where every spoke article links up to its pillar, sideways to 2-4 siblings, and down to a product or feature page through the problem paragraph rather than the solution paragraph. Pair this with a workflow that updates internal links every time a post is published, refreshed or sunset.
Do 'related posts' widgets help SEO?
Marginally. They generate crawlable links but the anchor text is always the post title, the placement is below the fold, and the related-post selection is rarely topical. In-body contextual links built into your pillar-and-spoke architecture do far more for rankings.
How often should you audit internal links?
Run a full inlinks-per-URL audit once a quarter, and a focused orphan-page check whenever you publish or sunset more than ten posts. Day-to-day maintenance happens inside the editorial workflow, not in a standalone audit.
Stop linking by accident
Most SaaS sites we audit have between 30 and 60 orphan or near-orphan pages, and at least one product page that the blog links to fewer than three times. If you want to know which of those are silently capping your rankings, book a free SEO audit call. Thirty minutes, specific findings on your real URLs, no slide decks.
