Does the hash URL really transmit PageRank without being indexed?

What are hash URLs and how do they actually work?

Hash fragments (the #section after the URL) have historically been used to navigate to specific sections of a page without reloading the document. When you click on an internal link like https://example.com/page#chapter-2, the browser scrolls to the corresponding HTML element.

For crawlers, the hash fragment poses a technical ambiguity. According to HTTP standards, the fragment is never sent to the server—it remains client-side. Search engines have therefore long ignored everything that follows the #.

Why does Google claim it can index these URLs then?

Google has developed the ability to interpret certain hash fragments in specific contexts, particularly for JavaScript applications that use hash routing (old SPAs before the advent of the History API). In these cases, the displayed content truly depends on the fragment.

But Mueller makes it clear: this remains rare. Most sites use hashes for simple navigation anchors, not to load distinct content. Googlebot will not systematically create separate index entries for each hashed variation of the same URL.

What does this mean for the transmission of PageRank?

The essential point of this statement concerns the flow of popularity. If an external site points to https://example.com/guide#step-3, Google passes this weight to https://example.com/guide—the canonical version without hash.

This mechanism protects your internal link structure. You can multiply deep anchor links without artificially fragmenting your juice among multiple URL versions. Crawl budget and PageRank remain consolidated on the main page.

• Hash fragments are generally not indexed as distinct pages
• Links to hash URLs do transmit their weight to the non-hash version if it exists
• JavaScript hash routing is the exception where Google may attempt to index
• Your internal linking with anchors does not dilute your popularity
• External backlinks pointing to specific sections benefit the entire page

Is this statement consistent with real-world observations?

Yes, overall. It is indeed observed that hash URLs rarely appear in SERPs, even on high crawl budget sites. The exceptions mainly involve old Angular or Backbone applications that use hash routing, and even then—often poorly indexed.

What’s interesting is the explicit confirmation regarding the transmission of PageRank. Some SEOs still believed that a link to an anchor diluted the juice. This statement clears that up: the weight does indeed flow back to the canonical page.

What nuances should be considered based on the technical context?

Beware of the specific case of modern SPAs with hash routing. If your application loads distinct content based on the fragment, Google may try to index it—but success is not guaranteed. [To be verified]: Mueller does not specify whether PageRank transmission works differently when the hash is used as a router.

Another gray area: massive external links to specific anchors. If 50 backlinks point to #section-x, does Google consider that section X deserves a contextual boost in the overall page? Nothing in this statement confirms that. The transmission appears uniform, without semantic weighting.

In which cases might this rule not apply?

If you are using hashes to track content variations client-side (A/B tests, personalization), Google will see only one version. The crawler does not replay complex JavaScript interactions that modify the DOM based on the fragment.

Hash fragments used for modals or overlays also pose problems. If #popup-contact triggers a modal window without changing the main content, Google will index the base page—not the modal. The link will transmit its weight, but the user intent (accessing the form) will not be preserved in the index.

What should you do with your internal anchors?

Continue using navigation anchors (#) to enhance user experience—table of contents, links to return to the top of the page, navigation between sections. You do not lose any internal link juice, so this practice remains fully valid for UX and SEO.

However, if you want Google to index specific sections as distinct entry points, create separate pages or use the structure /page/section-name. Hash fragments are not a reliable indexing lever.

How to handle external backlinks pointing to anchors?

If you notice natural backlinks to specific sections of your long content, rejoice: the weight flows back to the main page. There’s no need to redirect these URLs or disavow them.

However, keep an eye on search intentions. If an external link points to #pricing and this section contains substantial content, consider making it a dedicated page /pricing. You will better capture transactional queries and provide a better UX for visitors from that link.

What mistakes to avoid with hash URLs?

Never build a site architecture based on hash routing if you are launching a new project. Modern frameworks (Next.js, Nuxt, SvelteKit) use the History API and server-side rendering—much more SEO-friendly.

Also, avoid canonicalizing to a hash URL. If you have /page and /page#section, the canonical tag should point only to /page. Google will consolidate anyway, but it’s best to clarify your intention.

• Use anchors (#) freely for internal navigation without fearing PageRank dilution
• Create separate pages if you want to index sections as SEO entry points
• Migrate old hash-based SPAs to modern routing (History API + SSR)
• Monitor external backlinks to your anchors to identify opportunities for dedicated pages
• Never canonicalize to a URL containing a hash fragment
• Check in Search Console that Google is not massively indexing your hashed variants