Internal Linking Strategy
- Start every linking project with an audit: orphaned pages, under-linked pillar pages, and landing pages that link out too much
- Build links following the segment hierarchy: TOFU forward to MOFU, MOFU forward to BOFU, everything back to the pillar
- Anchor text varies by funnel stage, not by preference. Industry language at TOFU, product language at BOFU.
- Re-audit every time you add pages to a cluster. New content creates new linking opportunities and new orphan risk.
You have pages. They are indexed. The content follows segment intent at each funnel stage. But the pages are not yet a system. Without internal links built to a specific architecture, search engines see a collection of articles. With them, they see a topical cluster with clear authority signals and clear paths from awareness to conversion.
The strategic framing for internal linking covers why the architecture matters and how it connects to pipeline. This chapter covers how to build and maintain it. Open Screaming Frog, pull your crawl data, and follow along.
Link audit: where to start
Section titled “Link audit: where to start”Before you build anything, audit what exists. Every linking project starts with four questions, answered by crawl data.
Question one: which pages are orphaned? An orphaned page has zero or one internal links pointing to it. In Screaming Frog, run a full crawl, then filter the Internal Links report by “Unique Inlinks” with a maximum of 1. Every page that appears on this list is invisible to your link architecture. It might rank on its own merits (domain authority, backlinks), but it is not contributing to or benefiting from the cluster it belongs to.
Orphaned pages are the highest-priority fix. A page with zero internal links is a page your site doesn’t vouch for. Search engines notice.
Question two: is the pillar page the most-linked page in its cluster? The pillar page should receive more internal links than any other page in the segment cluster. It is the authority anchor. If a MOFU page or a BOFU page has more internal links than the pillar, the architecture is inverted, and search engines will treat the wrong page as the cluster’s center.
Pull internal link counts for every page in a cluster and rank them. If the pillar is not number one, you know where to add links first.
Question three: is the landing page linking out too much? Landing pages convert. Every outbound link on a landing page is a potential exit before the form fill. Count the outbound internal links on each segment landing page. If the number exceeds five or six, audit each one. Keep links to the pillar (for authority) and to one or two BOFU pages (for visitors who need more information before converting). Remove the rest.
I have seen landing pages with 15+ internal links in the body copy, each one an invitation to leave. The conversion rate on those pages was consistently 40-60% lower than on landing pages with tight link discipline.
Question four: what is the within-cluster link ratio? For any given page, count its internal links and categorize them: links to pages within the same segment cluster vs. links to pages in other clusters or to site-wide pages. If fewer than 80% of a page’s contextual body links point within its own cluster, the architecture is bleeding authority across segments.
This is the metric most teams never check. They link freely between clusters because the content feels related. It is related, but relatedness is not the organizing principle. Segments are. Cross-cluster links dilute the topical signal that makes clusters work.
Run these four checks before writing a single new link. The audit tells you exactly where the architecture is broken and what to fix first.
Building the segment link architecture
Section titled “Building the segment link architecture”With your audit results in hand, you build links in four passes. Each pass has a specific target and a specific constraint. Do them in order.
Pass one: pillar connections. Open every page in the cluster and confirm it contains at least one contextual link to the pillar page. “Contextual” means the link appears in body copy, not just in the sidebar or a related-posts widget. Search engines weight in-content links more heavily than navigational links. If a page has no body-copy link to the pillar, add one. The surrounding sentence should reference the pillar’s topic naturally. Do not force a link into a paragraph where it does not belong. If no paragraph fits, write a brief transitional sentence that does.
Then open the pillar page and confirm it links to every other page in the cluster. The pillar is the hub. It should be the single page from which a reader (or a crawler) can reach any page in the segment.
Pass two: funnel flow. TOFU pages link forward to MOFU pages. MOFU pages link forward to BOFU pages. BOFU pages link to the landing page. This mirrors the buyer’s direction of travel: awareness to consideration to decision. Your contextual links should follow the same direction.
For each TOFU page, add at least one link to a MOFU page in the same cluster. For each MOFU page, add at least one link to a BOFU page. For each BOFU page, add one link to the landing page. The text around each link should frame what the reader will find next, not just drop a hyperlink into a sentence.
Do not create backward links (BOFU to TOFU) in body copy. Readers who want to go backward can use the sidebar or the pillar page. Your contextual links move the reader forward.
Pass three: sibling links. Pages at the same funnel stage can link to each other when the content warrants it. Two MOFU pages about related problems should reference each other. Two TOFU pages covering different angles of the same industry should cross-link. These sibling links strengthen the layer and give crawlers more paths through the cluster.
The constraint: sibling links are supplemental, not primary. Every page’s primary links are (a) to the pillar and (b) forward in the funnel. Sibling links are a third priority. If a page already has four or five internal links, adding a sixth sibling link is not necessary.
Pass four: landing page cleanup. Revisit the landing page last. After the first three passes, the landing page should receive links from every BOFU page and from the pillar. Confirm those inbound links exist. Then audit the landing page’s outbound links. Remove any that are not strictly necessary for conversion context. The landing page’s link profile should be heavily asymmetric: many inbound, few outbound.
Anchor text rules
Section titled “Anchor text rules”The text inside your internal links carries signal. Search engines use anchor text to understand what the target page is about. Readers use it to decide whether to click. Both signals should match the funnel stage of the page you are linking to.
| Target Stage | Anchor Text Style | Example | Why |
|---|---|---|---|
| TOFU | Industry or topic language | ”procurement challenges in construction” | Reader is thinking about their industry, not your solution |
| MOFU | Problem or method language | ”evaluating vendor management workflows” | Reader is comparing approaches, not shopping |
| BOFU | Product or solution language | ”procurement software comparison for contractors” | Reader is ready to evaluate specific options |
| Pillar | Segment + methodology | ”the construction procurement playbook” | Signals the hub page’s breadth |
| Landing | Action-oriented | ”get started with procurement SEO” | Matches the conversion intent of the target |
Three guidelines keep anchor text honest and effective.
Vary your anchors. If every link to the pillar page uses the exact same anchor text, search engines may interpret that as manipulation. Use two or three variations that describe the pillar from different angles. “The procurement playbook,” “our procurement SEO methodology,” and “the full procurement cluster guide” all point to the same page but signal different facets of its content.
Do not over-optimize BOFU anchors. It is tempting to stuff exact-match keywords into links pointing to your conversion pages. Resist this. One exact-match anchor is fine. The rest should be natural descriptions of what the reader will find. If every BOFU link reads “best procurement software for construction companies,” the pattern is obvious to algorithms and annoying to readers.
Match the surrounding context. An anchor like “evaluating vendor management workflows” works if it sits in a paragraph about operational efficiency. It does not work if it appears in a paragraph about hiring challenges. The surrounding text and the anchor text should form a coherent reading experience. If you have to contort a paragraph to fit an anchor, the link does not belong there.
Cross-segment linking: when and how
Section titled “Cross-segment linking: when and how”The 80% within-cluster rule is the default. But there are legitimate reasons to link across segments, and doing it well requires a specific process.
Identifying valid bridge points. A cross-segment link is valid when a page in one cluster references a concept that is covered in more depth in another cluster, and the reader would genuinely benefit from that depth. The test: would a reader following this link find content that helps them, or would they land on a page written for a different role with different priorities?
A TOFU page in the SEO lead cluster that mentions forecasting can link to the CMO cluster’s MQL prediction model page, because an SEO lead curious about the business case will find useful context there. A BOFU page in the SEO lead cluster should not link to the CMO cluster, because an SEO lead ready to implement does not need to read about CFO conversations.
Use shared framework content as connectors. The frameworks section exists outside any segment cluster and serves all audiences. When you need to connect clusters, linking through a shared framework page is cleaner than linking directly between segments. A page in the SEO lead cluster and a page in the Growth cluster can both link to the same decision tree or template without creating cross-cluster dependency.
Audit cross-cluster links quarterly. As you add content, cross-cluster links accumulate. Some become stale (the target page changed scope), some become redundant (you built a better resource within the cluster), and some were mistakes from the start. Once per quarter, export your crawl data, filter for links that cross cluster boundaries, and review each one. Remove any that fail the “would the reader benefit?” test.
Maintaining links as content grows
Section titled “Maintaining links as content grows”A linking architecture is not a one-time build. Every new page you add to a cluster changes the link graph. New pages create new linking opportunities (pages that should link to them, pages they should link to) and new orphan risk (the new page itself starts with zero internal links unless you add them deliberately).
Build this into your content production checklist. Every time a new page goes live, three actions happen before you move on to the next piece.
Action one: add links from the new page. Before publishing, the new page should contain at least one link to the pillar, at least one link forward in the funnel, and optionally one sibling link. These are written during content production, not added afterward. If your writers are producing content without internal links, the content production workflow has a gap.
Action two: add links to the new page. Identify two to four existing pages in the cluster that should now link to the new page. Open those pages, find a natural location for the link, and add it. This step is the one most teams skip. They publish the new page, add links from it, and forget to update existing pages. The result: a page that links out but receives few links in return.
Action three: re-check the landing page. If the new page is BOFU, it should link to the landing page, and you should confirm the landing page’s outbound link count is still within bounds. If the new page is TOFU or MOFU, the landing page probably does not need to change. But check anyway, because the pillar page might need an update to reference the new addition.
These three actions add perhaps 15 minutes per new page. Without them, the linking architecture degrades with every piece of content you publish. After six months of publishing without maintenance, you will need a full re-audit, which takes days, not minutes.
[PLACEHOLDER: Insert specific client example showing the maintenance process in action. Before/after orphan counts, the time investment per page, and the cumulative impact on cluster authority over a quarter. Baba to provide from real engagement data.]
What links alone will not solve
Section titled “What links alone will not solve”A strong linking architecture is a multiplier. But multiplying zero still gives you zero. There are problems that no amount of internal linking will fix.
Content-intent mismatch. If a page targets a keyword but does not match the search intent behind it, internal links will push authority to a page that Google does not want to rank for that query. Fix the content first. Match the intent. Then link.
No search demand. Some segments are real business opportunities with no meaningful search volume. Internal linking cannot manufacture organic traffic for keywords nobody searches. In those cases, the content serves sales enablement or nurture sequences, and the linking architecture matters less.
Technical crawl problems. If pages are blocked by robots.txt, returning 404s, canonicalized to the wrong URL, or suffering from crawl budget issues, internal links will not reach their targets. Run a technical audit before investing time in link architecture. Fix the infrastructure first.
Missing external authority. If your domain has minimal backlinks and no topical authority in the segment, internal linking distributes authority you do not yet have. You need to build external authority in parallel: guest contributions, original research that earns citations, and the slow work of becoming a trusted source. Internal links distribute authority. Backlinks create it.
Linking is one piece of the system. It works when the other pieces are in place.
Get notified when new chapters publish
Summarize with AI