What Is Link Juice in SEO: How PageRank Flows Between Pages

Link juice is shorthand for the idea that a hyperlink can pass some link-based authority from one page to another. The term is not an official Google metric. It grew out of explanations of PageRank, which modeled links between documents as weighted votes rather than treating every page as equally important.

The model is useful because it highlights direction. An external site can link to a resource on your domain. That resource can link internally to a related guide. The related guide can link to a product, service, or other primary page when that connection is useful to the reader. Each link creates a relationship that search systems can crawl and interpret.

What the model does not give you is a precise transfer amount. Modern ranking systems use many signals, and Google does not publish a live PageRank score for each page or a formula that lets publishers calculate how much value a specific link contributes. Third-party page-authority metrics are estimates created for analysis, not the underlying Google score.

For site owners, the practical components are easier to observe: the linking page, the destination page, the anchor text, whether the link is crawlable, whether the destination resolves cleanly, how the pages relate topically, and whether users can reach the destination through a sensible path. Those components are more actionable than arguing over an invisible quantity.

Supporting pages matter because they can explain narrower questions and then point readers to the primary page that owns the broader task. The primary page can also point back to supporting detail when a reader needs it. That creates a useful network without requiring every page to link to every other page.

A page enters the internal link graph through the links that point to it. Some of those links may come from other websites, while others come from navigation, breadcrumbs, contextual body copy, related-resource modules, or other pages on the same domain.

Together, those connections help crawlers discover the page and help search systems understand how it relates to the rest of the site.

The PageRank analogy suggests that a linking page does not duplicate an unlimited pool of authority every time it adds another link. That is a useful reason to avoid indiscriminate linking, but it should not be converted into a hard rule about a fixed number of links. Add a link when it gives the reader a sensible next step or clarifies a relationship between pages.

Depth also matters operationally because deeply buried pages can be harder for users and crawlers to reach. The goal is not to force every priority page into the main navigation. It is to create short, logical paths from relevant hubs and supporting pages.

A specialist glossary entry, for example, may sit several clicks from the homepage and still be well connected if its topic hub and related guides point to it clearly.

Topical relationship is another important constraint. A contextual link from a closely related guide can communicate a more useful relationship than a generic sitewide link. That does not mean the contextual link carries a publicly known multiplier; it means the surrounding content makes the reason for the link easier to interpret.

Think of authority flow as one layer of information architecture. The same link should ideally help a user navigate, help crawlers discover a destination, and express a genuine relationship between pages. If it only exists to push an abstract score, the architecture is likely serving the model instead of the site.

The PIPE Audit in the source can be kept as a site-review heuristic rather than treated as a Google-defined framework. Its value is that it forces a team to look for structural situations where link relationships stop being useful.

The first area is pagination. On archives with page 2 and page 3, review whether important resources become difficult to reach as they move deeper into the sequence. Pagination is not automatically an authority leak; the issue is whether useful pages depend on weak or obscure paths for discovery.

The second area is orphaning. A page with no internal links pointing to it is disconnected from the site's navigational context even if it is known through a sitemap or an external link. For a page that still serves a real purpose, add relevant internal references from pages that naturally lead to it.

If the page no longer has a distinct purpose, consolidation or retirement may be more appropriate than manufacturing links.

The third area is hub selection. A hub should help readers understand a topic and choose the right supporting resource. If a thin archive or outdated post has become the de facto center of a topic simply because many templates link to it, decide whether a more useful page should own that role.

The fourth area is external linking. Do not label every external reference as bleed. Review whether each link supports a claim, gives the reader a useful source, or serves another legitimate purpose. Remove links that are broken, irrelevant, manipulative, or obsolete, but keep citations that make the page more useful and verifiable.

The audit is complete when each important page has a clear purpose, viable inbound paths, working destinations, and a defined relationship to the primary page and supporting pages around it.

The River Model in the source is most useful as a way to visualize page roles. It is not a claim that Google literally routes authority through named channels. Use it to make page relationships explicit before adding links.

1. Headwaters: externally referenced resources. These are pages that attract links or citations from outside the site. Their editorial job is to remain useful enough to deserve those references. Their architectural job is to connect readers to relevant next steps, which may include a hub or a more specific page.

2. Tributaries: supporting pages. These answer narrower questions, examples, definitions, or use cases. They should link to the primary page when that helps a reader understand the broader topic, and the primary page should link back when the supporting detail is useful but too specific for the main explanation.

3. Main channel: topic hubs or primary guides. A hub should help readers orient themselves, understand the main concept, and choose the appropriate supporting path. It does not need to absorb every keyword or repeat every answer from the supporting pages.

4. Delta: decision or commercial pages. These pages serve evaluation or action intent. Educational pages may point to them when the reader is ready for that next step, but the link should fit the content naturally rather than turning every informational page into a sales funnel.

A well-designed model therefore has bidirectional usefulness. Supporting pages can strengthen context around a primary page, while primary pages can help users reach deeper explanations. Commercial pages can receive relevant referrals without becoming the mandatory endpoint for unrelated content. The model is successful when the paths make sense to a reader even if ranking systems are ignored.

Internal linking becomes useful when the destination is clear, the relationship is relevant, and the link appears where a reader would reasonably want more detail or a next step. The mechanics are simple, but the editorial judgment matters.

Use descriptive anchor text. The words in a link should tell the reader what they will find. Generic labels can be appropriate in interface elements, but contextual prose usually benefits from specific language.

Avoid stuffing the same exact phrase into every link to a page; natural variation can describe the destination accurately without creating repetitive copy.

Prefer direct destinations. If an internal link points to a URL that redirects, update the link when practical so users and crawlers reach the current destination directly. Redirects are useful for migrations and retired URLs, but they should not become the default structure of the internal graph.

Resolve competing page roles. When several pages answer the same core question, decide whether they truly serve distinct intents. If not, consolidation may create a clearer experience than building more links between overlapping pages. Internal linking works best after page ownership is clear.

Link from maintained resources when the relationship is real. Updating an established guide is a good moment to review whether it should point to newer supporting content or a more current primary page. The purpose is to keep the information network accurate, not to manufacture freshness or promise a ranking change.

Avoid arbitrary link quotas. Long guides may need many internal references; concise glossary entries may need few. Count links when auditing patterns, but decide link-by-link based on usefulness, redundancy, and destination quality.

These practices make internal linking a maintainable editorial system. They also make it easier to diagnose problems because each link has an understandable reason to exist.

Link attributes are often discussed as if they were valves that let a site hoard or redirect link juice. That is not a reliable way to use them. Modern Google documentation treats nofollow and related attributes as signals about the nature of a link, not as a PageRank-sculpting system that publishers can use to preserve a fixed pool for other destinations.

Use nofollow when it accurately communicates the relationship intended by the link and use the sponsored or user-generated attributes where their documented purposes apply. For ordinary editorial citations, a followed link can be appropriate when you are comfortable referencing the destination.

The choice should come from the relationship and policy context, not from fear that every followed external link weakens the page.

External references can improve a guide's usefulness by letting readers verify a source, inspect documentation, or understand background material. Removing relevant citations solely to retain theoretical authority can make the page less trustworthy and less useful.

Internal nofollow sculpting is likewise a poor default. If a page should not be indexed, use the appropriate indexing controls. If a link has no value to users, remove or redesign it rather than relying on nofollow to reshape authority.

If a utility page must remain accessible, its presence does not require pretending it participates in a precise authority budget.

Canonicalization is a separate issue. Canonical hints help search systems understand preferred versions among duplicate or near-duplicate pages. They should be consistent with internal links, redirects, sitemaps, and the actual content relationship. Canonicals are not a substitute for deciding whether duplicated URLs need to exist.

The operational rule is straightforward: make link attributes truthful, keep external references useful, keep internal destinations intentional, and do not use nofollow as a substitute for sound architecture.

Authority Gravity is another source concept that works best as a planning metaphor. It does not describe a documented Google force. The useful question is whether an important page receives enough relevant, understandable internal references to be a clear part of the site's information architecture.

Start by defining the page's role. A commercial page should help a reader evaluate or take an action. A glossary page should define a concept. A guide should teach a process. When the roles are clear, the supporting links become easier to choose because each page has a distinct job.

Next, identify pages that naturally lead to the priority destination. A guide about a problem may link to the service or product page that addresses it when that is a useful next step. A glossary page may instead link to a deeper guide first. Do not force every topically adjacent page to point directly at the commercial destination.

Then examine outbound paths from the priority page. Links that help a user compare, verify, understand requirements, or find supporting detail may be appropriate. The goal is not to make the page a dead end in order to retain authority. It is to keep the page focused on its decision task while providing necessary context.

Supporting pages can strengthen clarity by answering questions that would otherwise overload the primary page. Link them where the detail is useful, and link back to the primary page when a reader needs the broader context. This produces a network with clear ownership rather than a one-way funnel.

Finally, maintain the map as the site changes. New articles, products, services, and guides can create better paths or make old links obsolete. Review the graph when content roles change, not because an arbitrary cadence is assumed to be a ranking factor.

Because link juice is not a public metric, measurement should focus on observable inputs and outcomes. Start with the internal graph: which priority pages gained relevant links, which broken or redirected destinations were corrected, which orphans were connected, and which overlapping pages were consolidated.

Then separate technical confirmation from performance evaluation. Technical confirmation asks whether the changed links are present in crawlable HTML, whether their destinations return the intended response, and whether important pages remain indexable.

Performance evaluation asks whether impressions, clicks, query coverage, and rankings change after search systems recrawl and reevaluate the pages.

Use a before-and-after record for the specific pages you changed. Note the internal sources that were added or removed, the destination, the reason for the change, and any concurrent content edits. This matters because internal links are rarely the only thing changing on a live site, and attribution becomes weak when several variables move together.

Crawl data can also show whether discovery paths improved, but increased crawl activity should not be treated as proof of higher authority. It is an observation about crawler behavior. Likewise, a ranking improvement after an internal-link change is evidence worth recording, not proof that a precise amount of PageRank moved along one link.

For supporting-page systems, evaluate whether the architecture is becoming clearer. Can users move from the primary page to deeper explanations without dead ends? Do supporting pages link back to the main concept when appropriate?

Are duplicate pages declining because ownership is clearer? Those questions are often more actionable than trying to infer an invisible authority score.

A good measurement process therefore combines graph quality, crawlability, indexation, search performance, and reader navigation. The output is a stronger site structure and a record of what happened after specific changes, without turning correlation into a guaranteed causal claim.